Working With Series 338928866.doc Effective Mm/dd/yy Page 1 of 25 Rev 1
Working With Series 338928866.doc Effective Mm/dd/yy Page 1 of 25 Rev 1
Working With Series 338928866.doc Effective Mm/dd/yy Page 1 of 25 Rev 1
Overview
Page 1 of 25
338928866.doc
Rev 1
Distribution
Oracle Demantra Fundamentals
Job Title*
Ownership
The Job Title [list@YourCompany.com?Subject=338928866.doc] is responsible for ensuring that
this document is necessary and that it reflects actual practice.
Page 2 of 25
338928866.doc
Rev 1
Schedule:
Timing
60 minutes
60 minutes
120 minutes
Topic
Lecture
Practice
Total
Page 3 of 25
338928866.doc
Rev 1
Objectives
Objectives
Page 4 of 25
338928866.doc
Rev 1
Agenda
Agenda
Page 5 of 25
338928866.doc
Rev 1
Understanding Series
Understanding Series
A series is a set of data that can be displayed in a worksheet table or graph, at any aggregation
level. For example, sales data and the forecast are both series. A series is usually a timedependent set of data, although there are a few special cases where this is not the case. Series can
be editable, read-only, or conditionally editable.
Although most series are time-dependent, Demantra also supports other types of special-purpose
series:
A matrix series is used for data that varies by item and location, but does not vary by
time. For example, a Ship From address may vary by item and/or location but does not
vary by time.
A level series is associated with a specific level. Each data point in the series
corresponds to a given member of that level.
Instructor Note
Copyright Oracle, 2007. All rights reserved.
Page 6 of 25
338928866.doc
Rev 1
In the Collaborator Workbench, show examples of imported, calculated and userinputted series:
Page 7 of 25
338928866.doc
Rev 1
Series Types
Understanding Series
Series data is most commonly numeric, but it can also be a string or date.
Page 8 of 25
338928866.doc
Rev 1
Server Expressions
Server Expressions
A server expression is a SQL expression that aggregates lowest-level data to any worksheet level.
A very common server expression has the following form:
sum (table_name.update_column_name)
Here table_name.update_column_name is the table and column that stores data for this series.
If you view a combination at the lowest level, this expression reads the series value for one row
in the given table. On the other hand, if you view a combination at a higher level, this expression
sums the series values associated with all the rows that correspond to the child members.
When creating server expressions, you are free to use any aggregating SQL expression. For
example:
sum
avg
Copyright Oracle, 2007. All rights reserved.
Page 9 of 25
338928866.doc
Rev 1
min
max
For a complete list of available server expressions, see Consultant Help > Reference Guide >
Server Expression Functions and Operators.
Page 10 of 25
338928866.doc
Rev 1
Client Expressions
Client Expressions
A series can also have a client expression, which calculates data in a different way. In contrast to
server expressions, a client expression always refers to data at the same level. You use client
expressions to calculate numbers that cannot be calculated by aggregation from lowest-level
data.
Page 11 of 25
338928866.doc
Rev 1
Client expression: how to calculate data for the series based on other series, if needed.
Page 12 of 25
338928866.doc
Rev 1
Instructor Notes
Refer to Guided Demo Using the Series Editor [LAB402EY]
Page 13 of 25
338928866.doc
Rev 1
Aggregating Data
Aggregating Data
Demantra only stores data at the lowest possible aggregation level:
In the above example, a partial product hierarchy is shown with the Category, Segment, Brand,
and Item levels. Data is only stored at the Item level.
When you edit aggregated data, Demantra must disaggregate that data in order to store the
changes. For example, if you edit inventory levels for the aggregated Brand category, Demantra
disaggregates these changes to the individual child brands before saving the changes to the
database. Demantra uses a user-defined proportional calculation series to determine how these
values are disaggregated.
Copyright Oracle, 2007. All rights reserved.
Page 14 of 25
338928866.doc
Rev 1
Similarly, Demantra automatically aggregates data to the level in which it is required. For
example, if a worksheet displays data for a product family, Demantra aggregates data for all
products within that family.
Instructor Notes
Implementers should choose their time buckets with care. When choosing your time
buckets, the granularity of your data largely depends on your industry and the quality of
data. The more granular the data you store, the more technical overhead associated
with sorting this information.
Page 15 of 25
338928866.doc
Rev 1
Page 16 of 25
338928866.doc
Rev 1
Page 17 of 25
338928866.doc
Rev 1
Disaggregating Data
Disaggregating Data
Demantra disaggregates data in one of two ways:
Proportional series: split the data, dividing it like a pie. For example: sales figures,
budgets, units sold. Most series are proportional.
Non-proportional series: dont split the data. All members of the lower level inherit the
same value. For example: item price, dates, and inventory threshold.
To ensure that the disaggregation is done in a sensible manner, Demantra looks at the values in a
proportional calculation series and uses those to determine proportions. Each proportional series
can be configured separately to use whatever reference series makes sense. In most cases, use
either the history or the forecast.
Instructor Note
Refer to Guided Demo Choosing a Proportional Calculation Series [LAB402DY]
Copyright Oracle, 2007. All rights reserved.
Page 18 of 25
338928866.doc
Rev 1
Page 19 of 25
338928866.doc
Rev 1
Page 20 of 25
338928866.doc
Rev 1
Page 21 of 25
338928866.doc
Rev 1
If the proportional calculation series has null values for some records, those records
receive zero from the split.
If the proportional calculation series has null values for all relevant records, Demantra
instead uses the stored proportions for the combinations.
Page 22 of 25
338928866.doc
Rev 1
Summary
Summary
Page 23 of 25
338928866.doc
Rev 1
Page 24 of 25
338928866.doc
Rev 1
Page 25 of 25
338928866.doc
Rev 1