SAP HANA permits OLTP and OLAP workloads on the same platform by storing data in

highspeed memory, organising it in columns and partitioning and distributing it

among multiple servers.

IBPF = Simple finance + BPC Embedded + Pre delivered content

2 types of info Object: Key figure and characteristics

Real Time infocubes: they contain planning dat and are write optimized

Standard Infocubes : they contain actual data and are read optimized

Composite Provider: these do not contain data, used to union/ join Infoprovider
and/or HANA views

DSO: they contain more detail data in general.It uses the OVERWRITE FUNCTION BASED
ON KEY FIELDS LIKE DOC NUMBER. Hence we used multiple info objects as key
fields.Also data is not totaled at node level.

Aggregation Level : becomes the info provider for planning enabled query which can
be used for Bex reportThey represent a drill down level ina query,AL represents a
selection of characteristics and key figure for underlying info provider and
determines the granularity of the planning.

BW QUERY TO BE INPUT READY:

1. REAL TIME INFO CUBE: REAL TIME OPTION IS CHECKED IN INFOCUBE
2. When creating queries for planning, you need to include every infoobject in the
aggregation level.Any characteristics not included in rows and columns must be
included in the filter and restricted to single values
3. To Include ALL THE MASTER DATA, GO TO EXTENDED TAB AND CHOOSE MASTER DATA.
4. In the key figure, go to planning : input ready (relevant for locking)
5. In query property : Start query in input mode.

Composite provider should always be used even if only 1 real time info cube is
needed because it provides flexibility for modelling changes.

1. Real time info cube, DSO

2. create a composite provider in HANA studio
2. Agg.level in BW
3. Bex Query

Model is created based on Composite provider

COMMENTS DSOs; 1. create a DSO

2. Data Type: characteristics lenght - 250, lowercase letters, no master data, no
text
2. Charateris tics as key figure turned ON
2. SET IT TO DIRECT INPUT
3. TURN ON PLANNING IN SETTTING

LOCAL PROVIDER: It can be used without any corresponding BW Infoobject and used for
ad hoc reporting and planning.
IT DOESNT APPEAR AT BACK END.IT CREATES ENTRIES IN HANA DATABASE.ONCE U CREATE IT ,

IT CREATES AN AGG LEVEL Automatically AT BACK END BEGINNING WITH @3B

LOCAL DIMENSION CAN BE CREATED WHEN CREATUNG LOCAL PROVIDERS VIA FILE UPLOAD.

A GLOBAL DIMENSION CAN BE USED AS REF OBJECT TO CREATE A LOCAL DIMENISON WHEN:
1. IT SHALL NOT BE AUTHORIZATION RELEVANT
2. IT SHALL HAVE MASTER DATA
3. IT IS EXPOSED AS AN INFO PROVIDER IN BW
4. REF BW WORKSPACE NEED TO ALLOW CREATION OF MASTER DATA

Filters Can Be Maintained from either RSPLAN OR IN BW QUERY.

Planning functions:
1. Pre defined functions
2. FOX formulas
3. ABAP

How to Debug FOX Formulas in BW-IP PAK

1. set a break point in ABAP. SE80 navigate to the class CL_RSPLFR_CONTROLLER, and
search for the method EXECUTE_SERVICE.We set a break-point in the first line of the
coding.
3. execute the planning function in trace mode as this always forces an execution
ion ABAP. We choose this (more direct) option.
4. Start the Fox DebuggeR We stop at the break-point before the execution of the
actual planning function and see the ABAP debugger. We change to the tab Script
and load the script RSPLFC_DEBUGGING_SCRIPT_FOX. After that we start the script.
5. In order to start the debugging press Start Debugging. If you want you can set
a break-point before starting the debugging.
6. Debug the Function Logic : You can now use several features in the debugger. You
can set break-points, move forward by a single step, or jump to the next break-
point.

Data Audit:

1. In RSA1 edit the infocube in change mode, under setting tick the Auditable
option
2. An extra BW "Audit Function" will be created with 4 characteristics:
a. Audit stamp
b. USer
c. Audit mode
d. Source of data.

Price Planning should be done in DSO of Direct update because key figures in real
Time Info providers sum up on node levels.Using DSO its possible to use a key
figure with the setting " No Aggregation"

Disaggregation (also known as top down allocation)

Type of Disaggregation
1. No Disaggregation
2. Disaggregation Value entered
3. Disaggregation diff to value entered : If it is equal distribution : Incremental
amount and then divided by the number of nodes
If it is analog distribution (Self
Referenace ) : Based on ratio of prior product value * incremental
Analog distribution (with ref to
following structure element) : the diff between old and new is dissagg according to
the sum of all products for the ref element "Sales quantity"

Type of distribution:
1. Equal distribution
2. Analog distribution (Self reference )
3. Analog distribution (with ref to following structure element)

Disaggregation behaviuor depends on key figure aggregation type.

For Key figures with Agg "SUM" actually a disaggreation is executed according to
the selected type of distribution
For Key figures with Agg "No Aggregation" no diaggregation takes place but the node
value is copied to leaves

ABAP is not recommended in PAK because it is not HANA embedded and runs slower in
HANA.FOX is faster than ABAP since at run time FOX is converted into HANA calc
scheme and for the same reason SQL Script is faster than FOX.

cHARATERISTICS RELATIONSHIP: They provide for permissible combinations of

characteristics value.
They check for cells in an inout ready for invalid characterisitcs combinations are
not ready for input.
Characteristics relationships affect all aggregation levels of the provider and all
associated Multi provider.

4 types of characteristics relationships:

1. Attributtes
2. Hierarachies
3. DSO
4. Exit class

The diff between characteristics and navigational is that navigation attributes are
only designed for selecting and as information but cannot be used for planning.

Charateristics relationship can be used for both selecting and planning.

Data Slices are a concept for protecting data in a real time infoprovider or DSO be
changed for a certain time or over written with current data.