sap bpc script logic

5/21/2018 SAP BPC Script Logic

1/8

SAP BPC Version 10 Script Logic

BACKGROUND:

1. Once the initial versions of dataset are chosen/prepared, there comesthe need of script logic in BPC, which are required to help in the copy

process, to apply various seasonality, to reflect external conditions to

the plan data, to calculate various rebates, discounts & offers etc,Anything that your company participates in a normal business process

can be integrated into the plan data, automatically using script logics.Script logics can also be used for on-the-fly-calculation (real-time)

nature and also for obvious/automatic data transformations such ascurrency transformation, consolidation etc at a chosen/scheduled time.

2. Script Logics can be used for PLANNING; as well as forCONSOLIDATION activities.

3. Script Logics, for most of the Consolidation activities are providedthrough available SAP Standard scripts

4. Technically; Script Logic is always created against a model, for amodel. Example model: HR, Overheads, Exchange Rates, Project

systems.5. Functional planning is done at each model, before they are merged

into management model, where financial statements are formed, such

as P/L Statement, Balance Sheet or a Cash flow statement.6. And Custom built Script logics are used for COMPLEX transformation

during functional planning, during management model integration, for

consolidation, during transfer between the models.7. Standard (SAP Delivered) script logics can also be used/edited before

they are used for balancing the Cash flow statement or working out

the Consolidation steps (Currency Translation, Intercompanyelimination etc)

TECHNICAL :

1. Administration tab in BPC > Rules > Logic Scripts > SelectModel >New/Edit/Delete/Copy > Editor screen >Add code

2.DEFAULT.LGF is the standard (SAP Delivered) script logic, which isexecuted anyway during any planning process. In order to achieve

efficiency & easy maintenance; it is probably a good idea toinclude/embed all other script logics into this DEFAULT script logic

using INCLUDE command.3. During a SAVE process, data is first committed to the SELECTED model

and the DEFULT logic is run on the model data.


2/8

4. DEFAULT LOGIC can also be invoked from a DATA MANAGER, duringexecution of a planning process.

5. Beauty is with the standard logic, SYSTEM_CONSTANTS.LGF which isused to default the actual Dimension names in the BPC system.Every time, dimension name changes, the constants in the file have to

change, manually.

STRUCTURE OF SCRIPT LOGIC:

1.Scoping (Restrict the dataset; using which the calculation will beperformed)

2.Body part / coding (Perform Calculation, Transformation,Aggregation etc )

3.Commit (Save the calculated result to the database)TYPES OF SYNTAX IN SCRIPT LOGIC:

1. SQL based syntax (Choose this option for better performance)2. MDX based syntax (Choose this option for specific record level

calculations)

ADVANTAGES:

Helps in model level calculation, not at a member level of the

dimensions. It has multiple uses, it can be done using many differentways and it can be executed from many different places and also it has

many different options, as far as syntax selection goes. Name of thegame is therefore; flexibility.

DISADVANTAGES:

Cant handle very complex calculation processing or bigger datavolume. That is when the ABAP-BADI option comes into picture. ABAP-

BADI codes can be executed from the script logics. Script Logics canbe executed/run using Data Manager. ABAP-BADIs can also be

executed directly from the DATA MANAGER.

TESTING / DEBUGGING:

1. Can be done using transaction UJKT. Script Logic code can be directlyinputted into the screen, data set can be selected, and Test isexecuted.

2. The analysis will show various things such as: data selection,performance, error analysis etc


3/8

PERFORMANCE CONSIDERATION:

1. Use *COMMIT statement as few times as possible (if possible once, atthe most) in a script logic.

2. Access the complexity of the requirement and choose whether a scriptlogic or ABAP-BADI is a better option.

3. Using MDX should be avoided as much as possible; due to lowerperformance reasons.

4. Use memory carefully to load only the data records, which are requiredin the script logic for calculation.

5. Make sure less numbers of nested statements, loops are used withinthe script.

6. Script logic should be used only for real-time calculations only. Allother calculations for the existing data, actual data, market data; etc

are completed before they are used in the planning process or in the

script logic.

Two types of Syntax options in SAP BPC Script Logic. They are:

1. SQL based syntax (Choose this option for better performance)2. MDX based syntax (Choose this option for specific record level

calculations)

SQL based syntax Simplification:

1.*ADD / *ENDADD =Value of set of members (accounts) areadded and included in another account.

2. *INCLUDE = Multiple Script Logic files with different purposecan be added into a single fine using this command. During LGXgeneration, all codes are combined into one big piece of code,during runtime.

3. *REC = This statement generates a record / modifies a

record; to be posted in the database. Even if it is for the samedestination cell, a source record can generate as many

destination cell records. Multiple REC statements possiblebetween *END/*ENDWHEN statement

4. *XDIM_MEMBERSET = It restricts the data, filters the

source dataset to the required dataset for specific calculation,

intended in the script logic. For each restriction using adimension, there can be a separate XDIM statement. Generally it

is followed by the Dimension name & Member value/value set.


4/8

5. *XDIM_ADDMEMEBERSET = This statement is used to add

more member values to the scope of member value alreadydefined with the XDIM statement for conditional calculations.

6. *XDIM_FILTER =Filters the members of the scope of that

dimension. It does not filter the scope of data, rather filters fromavailable scope.

7. XDIM_MAXMEMBERS =Specifies the maximum number ofmembers that should be included in one query, per dimensionthe syntax is associated with.

8. XDIM_PACKAGEBY = This syntax is used for parallelprocessing. However configuration needs to be done in SPROneed to be done before using this.

9. *SELECT / *ENDSELECT =Like any other SQL statement,this syntax helps to retrieve a list of values from the master data

table (Dimension) and store them in a defined variable. Can bewritten in any part of the logic and the resultant value can be

used in any part of the logic as well. Generally better to write inthe beginning of the logic structure.

10. *WHEN / *ENDWHEN = *WHEN/*ENDWHEN can be used

with property values of the dimension; to further createconditions for data

processing/transformation/modification/manipulation, for theREC statement. Ex: *WHEN ACCOUNT *IS XY00001234. Same

as SELECT/ENDSELECT statement, but this it used whendifferent transformation is needed for different type of field

values in a record. Hence multiple *WHEN/*ENDWHEN

statements possible within a script logic. It works as a loopstatement.

11. *DESTINATION_APP =Use to make the datasets of one

model available for other. It transfers the data from one model

to another. Between Dimension Category values. It is acts likea MOVE-CORRESPONDING statement in traditional ABAP.

12. *LOOKUP / *ENDLOOKUP = Similar to*DESTINATION_APP but this does not transfer the data

between the model, rather looks up for the required calculation.It is acts like a READ statement in traditional ABAP. Example:


5/8

While doing currency translation of a value, it will be required to

look into the EXCHANGERATES model.

13. *TMVL =This is used to retrieve a time value after takinginto consideration an offset value from a given time period.

Similar concept existed in traditional ABAP. Example traditionalABAP statement X = Y+0(4). If value of Y = 27.08.2013 or

20130827. X will return a value = 2013. This can be usedwith WHEN, FOR, REC statements. Can be used with variables.Multiple offset values with TMVL statements can be used withXDIM statements.

14. *COMMIT = Saves/stores the calculated values in thedatabase. In case of two dependent calculations, resulting valueof the first calculation must be saved into the database with a

*COMMIT statement, before its value is used in anothercalculation formula within the script logic.

15. *ADD_DIM =While copying data between two models, ifsource model does not contain all the dimensions as the

destination model, missing dimensions in the source model canbe created/added using this syntax before data copy. Possible to

use this for multiple dimensions in one statement.

16. *RENAME_DIM = While copying data between two models,if dimension names between the models do not match; then

mismatching dimension names can be renamed to be the samebefore copy process. Possible to use this for multiple dimensions

in one statement.

17. *SKIP_DIM =While copying data between two models, if

destination model does not contain all the dimensions as thesource model, some of the destination models can be skippedfrom copying process using this syntax. Possible to use this formultiple dimensions in one statement.

18. *SELECTCASE / *ENDSELETC = This is select statementwith a CASE together to encourage conditions within. Works asIF, ELSEIF & ENDIF statement in traditional ABAP.

19. *START_BADI / *ENDBADI =

20. *RUN_ALLOCATION =


6/8

21. *BEGIN / *END =These syntaxes are used with Boolean

Expressions (YES / NO). Similar concept, as may have seen inBW-BEX formulas. The individual conditions will be enclosed in

parenthesis. If the condition is true, return value will be 1, else0.

22. *IIF = These syntaxes work, just as IF, ELSEIF, ENDIF

statements in traditional ABAP. If the condition satisfies, then itdirects the record to undergo a calculation.

23. *DIMNAME_DIM =

24. *DIMNAME_SET =

25. *SUB/*ENDSUB =

26. *FOR / *NEXT =This syntax is used with a variable, whichreturns/contains multiple values. This syntax then helps to

process individual variable values, once by one. It works likeFOR EACH statement in FOX formula.

27. *GET =Retrieves the value from the memory

28. *FUNCTION / *ENDFUNCTION =

29. *WHEN _REF_DATA = It sets the focus to either master

data or transactional data. When is set to master data, it loopsthrough all the master data values of the dimension. And when

set to transactional data, it loops through all transactional data,which uses the dimension/values in its scope. Without an explicit

definition, transactional data mode is selected by default.

Notes:

* at the beginning of a statement, means it is an executablestatement.

There is no FULL STOP needed in any of the above statements.

DimensionName.Property = ACCOUNT.RATETYPE. In this exampleAccount is the Master data and Rate type is the attribute. IfProperty is not defined or missing, then the Primary Key is assumed,

which in this case would be Account ID OR GL Account. Constant values of Numeric form, should not be included in double

quotes. Constant value with String form, should be included in double quotes.


7/8

While a comma between the member values reads/recordsindividual member values; a single member value after the = sign;summarizes all children values of the members to one parent record.

Bas () syntax with a member value is used to read all children valuesof a member defined. Generally used to copy values between time

periods at a summary level, without defining every single member. A BAS () syntax can not be combined with another member value in a

single statement. [# ] syntax with a member value is used as the target destination; to

hold value after calculation in the memory, before saving it into thedatabase with a *COMMIT statement.

Statement *REC(FACTOR=4, CATEGORY=FRCST) is usedto multiplythe value of the record by 4 and to the result under the categoryFRCST.

Statement *REC(EXPRESSION=%VALUE% + 750) is used to add theoriginal value of the record, which is represented by a variable with750.

Variables are represented with notation %VARIABLE% (percentagesign before and after).

MDX based syntax Simplification

More detail or granular level calculation possible with MDX basedsyntaxes in script logic

It is possible to focus on a specific record by indicating a dimensionvalue.

Generally the syntax contains two parts: Dimension itself andDimension value with a decimal point in between to tie them up

Both Dimension & Dimension value are bracketed as below for theMDX syntax to work

Most of the syntaxes written above with SQL approach, can be writtenwith MDX approach as well

MDX syntax is straight forward, but may incur a performance penalty. The SQL syntax involves the creation of two records: one with the

value originally held by A and one with the value originally held by B.

The two new records , assigned to account C by the REC statements,

then aggregate up to the correct value. MDX: [#C] = [A] + [B] The calculated member is prefixed with a # SQL: *WHEN ACCOUNT *IS A *REC(ACCOUNT= C ) *IS B *REC(ACCOUNT= C ) *ENDWHEN


8/8

Revaluation example with MDX: [ACC].[#KEYFIGURE] =[ACC].[KEYFIGURE] * 1.10

Addition example with MDX : ADD%ACCT%=[ACCOUNT1],[ACCOUNT2], [ACCOUNT3], [ACCOUNT4]

SAMPLE SYSTEM VARIABLES

USER% - Returns current planning & consolidation User %APPSET% - Returns current planning & consolidation AppSet %APPLICATION% - Returns current planning & consolidation

Application %YEAR% - Returns current planning & consolidation Current Calendar

Year

sap bpc script logic

Documents