6.1 Discussing Data Modelling Flashcards

1
Q

What are the 2 styles of models

A

Planning model

Analytics model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Planning model dimensions, preconfig and offered

A
  • Preconfigured with Time and version dimensions

- offer multi currency on model and dim level

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Planning model write back capaiblities

A
  • users w/ planning privileges can create own version of model
  • users can write data to the model
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Analytics model (3) differences from planning model

A
  • does not support categories
  • doesn’t require time dim
  • read only
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

SAC Datasources for stories (3)

A

Datasets
Planning models
Analytics models

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Datasets can be live under these two conditions

A
  • only for HANA

- only used for Smart Predict, not for stories

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the 2 viewing options for a data model

A
  • structured view

- data foundation view

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What does a structure view show you?

A
  • star schema

- dimension box (version, date shows hierarchy)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How do you add a new dimension or existing dimension to your model

A
  • toolbar

- schema view

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What does the data foundation view show you

A
  • fact table that has transactions

- in planning can switch between different public versions of the data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Main difference between old model and new model

A

Old: only 1 measure column in transaction, so relied on accounts to describe values (rev, cost, admin)
New: allows multiple data columns. Not all modelling features supported yet in the new model.
Classic account models can be converted to new model.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Benefits of the new model - describe the flexible model structure benefit

A

Flexible model structure - both accounts and measures are available as structures, so data can be displayed more precise. EG:

  • aggregate over a measure instead of account
  • explicit data types - measures can be integers or decimals
  • disaggregation of data for measures - with integers, distribute entire value but avoid decimals
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Benefits of the new model - describe the optional account dimension

A

When using measures, you can add accounts to a generic dimension instead of an account dimension

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Benefits of the new model - describe improved calculations

A
  • calculated measures in models that can be used across stories, apps, etc.
  • calcs on numeric dim properties: flip signs on account values based on dim properties (eg, show expenses as positive)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Benefits of the new model - describe enhanced currency features

A
  • add multiple base currency measures and add currency conversion on top of them
  • plan based on any base or conversion measure, and see results across dependent currencies immediate.
  • apply currency conversion while copying data from a base measure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Benefits of the new model - describe data integration

A
  • the way a measure is set up is very similar to in HANA/BW/etc, so you don’t have to apply as many transformations from the source
17
Q

Benefits of the new model - describe clearer terminology in charts and tables

A

because non-fin data is removed from members of the account dim (aka no longer see them in the measures), charts will be easier for non-fin people to use

18
Q

Limitations of the new model - account/measure based formulas and calcs

A
  • link formula between models not supported. use LINK function instead
  • time dependent formulas (YoY) can’t be used with measures
  • can’t do cross model copying between classic and new model. instead use LINK function
19
Q

Limitations of the new model - stories and apps

A
  • no blending when there’s an account dim
  • no table threshold when there’s an account dim
  • no geo maps
  • can’t copy/paste data between currency measures
  • measures only sorted via Edit Member Order
  • Stores created on old account are not migrated, must be adjusted
20
Q

Limitations of the new model - import of data

A
  • dim members must exist first in the modeler before you import fact data, or import data to a global dimension
  • any models created from cvs/excel file or data source are still created as classic account models
21
Q

Limitations of the new model - integration with Microsoft office

A
  • default currency for currency variables must be set
  • if you migrate a classic model used in workbook to new model, you need to re-insert the model with existing workbook created with SAC add-in for MS
  • cannot use new model with AFO edition for SAC
22
Q

Old model - how measures work (2)

A
  • values stored in 1 measures

- and use account structure to add calcs, units, aggregations

23
Q

New model - how measures work (2)

A
  • measures are single entities

- you can configure multiple measure with aggregation and units (instead of just 1)

24
Q

SAC dimension types (public vs private)

A
  • private (model specific, copied with model if it is coped/deleted)
  • public (shared by several models)
25
Q

5 SAC dimension types (6)

A
  • account
  • organization
  • generic
  • date
  • timestamp
  • version
26
Q

Describe the account dimension type (3)

A
  • called measures in live data models
  • mandatory in classic, optional in new model
  • system generated hierarchy
27
Q

describe organization dimension type (4)

A
  • org structure (CC, PC, BU)
  • properties: currency and person responsible are system generated. others can be added
  • hierarchies can be added
  • optional
28
Q

describe generic dimension type

A
  • generate, free format dim
  • properties: as needed
  • hierarchies can be added
29
Q

describe date dimension type

A
  • built in dim, defined start and end dates of models timeline
  • defines granularity of time
  • 1+ in a model
  • hierarchy is system generated, can be changed to fiscal time
30
Q

describe timestamp dimension type

A
  • similar to date dim, includes hours, milliseconds, etc

- no hierarchy

31
Q

describe version dimension type

A
  • built in dim
  • defined data version in stories (actual, budget, planning, forecast, rolling forecast
  • no hierarchy
32
Q

what are the account dim properties (6)

A
  • account type (can sign flip)
  • rate type (currency conversion)
  • units and currencies
  • formula (Calcs logic)
  • hierarchy (if exist)
  • aggregation info (avg, last, first, rank, etc)
33
Q

what is a dimension formula

A
  • used to create new measures based on existing measures.

- similar to measure calculations in a story, but created ina model

34
Q

how are hierarchies created?

A
  • using a property of a dimension
  • standard feature
  • stores the parent ID
  • account dim has ONLY 1 HIERARCHY
35
Q

What are the two types of hierarchies

A
  • level based (country, state, city)

- parent-child

36
Q

how to maintain parent-child hierarchies?

A
  • manually in SAC
  • import from files
  • import from SAP systems
  • Note - in planning models, make sure you can’t book data to the parent node
37
Q

Limitations of hierarchies

A
  • in planning models, make sure you can’t book data to the parent node
  • a dim can only use 1 type of hierarchy (but can have multiple of that type)
  • date dim has predefined hierarchy is predefined and based on granularity, cant change it other than that.
  • version dim, no hierarchy
38
Q

3 options for Wrangling data

A
  • transformations (remember from datasets)
  • custom expression editor (for more robust needs)
  • combining data sources