Script Logic examples

Are any script logic examples available anywhere which I can refer to? (like Fox Formula examples in BPS).
Is there any book that I can refer to?
Please let me know.
Thanks.

The central notes for each of the BPCNW Support Pack releases contain helpful information on a variety of topics, as well as information on specific script logic functionality. Please review notes: 1306898, 1349538, 1349538, and 1366582.
http://help.sap.com/saphelp_bpc70sp02/helpdata/en/a1/532226947C49A5B2E2BD32450CB2D1/frameset.htm
Business Planning and Consolidations (BPC) Tips -3 u2013 Sheldon Edelstein
/people/sheldon.edelstein/blog/2008/04/21/business-planning-and-consolidations-bpc-tips-3
/people/sheldon.edelstein/blog
/people/sheldon.edelstein/blog/2008/04/23/business-planning-and-consolidations-bpc-tips-4
SAP Library BPC Administration Guide
https://websmp108.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000085368&_SCENARIO=01100035870000000112&_OBJECT=011000358700001123512008E
****How to Use BPC Scripting Logic
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ffae4b-99d5-2a10-4e9f-96149969aabb?quicklink=index&overridelayout=true
SAP BUSINESS PLANNING AND CONSOLIDATION SCRIPT LOGIC, PART 2
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a066c75e-3077-2b10-c6a6-b8af14b91775
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a066c75e-3077-2b10-c6a6-b8af14b91775?quicklink=index&overridelayout=true
SAP BUSINESS PLANNING AND CONSOLIDATION SCRIPT LOGIC, PART 3
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50c75047-3077-2b10-61b2-9a1b9373b0ee
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50c75047-3077-2b10-61b2-9a1b9373b0ee?quicklink=index&overridelayout=true
HOW TO... PASS DYNAMIC PARAMETERS TO SCRIPT LOGIC
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d01ce779-f1b2-2b10-07ba-da3734013245
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d01ce779-f1b2-2b10-07ba-da3734013245?quicklink=index&overridelayout=true
You can go to and check under "article library"
http://www.sdn.sap.com/irj/scn/advancedsearch?query=bpc+nw

Similar Messages

Script logic: differences between MS and NW?

Hi to all,
at last SAP Tech Ed I've bought a book on SAP BPC 7, Netweaver version...I did it because I'm already working with the MS version, but I hoped to get a better vision on BPC over NW, and to understand some critical subjects.
One question that I've been wondering is this one: I've found that some script logic examples that I've been able to reuse even in the MS version of BPC, while other won't. For example, I've found the *RUN_ALLOCATION (which I couldn't find in the logic assistent helper installed), and used it happily , and at the same time, I've found the *RUN_PROGRAM, which I don't really get any help from the web. I've found some posts in the NW version, not in the MS.
So: is there any kind of document about the differences between scripting logic for MS and NW?
Thank you
Daniele

Between 7.0 M and 7.0 NW we have a document with differences.
But after that new SP or release was bringing new functionalities into NW.
So it is depending what versions you will compare.
Any way you will find key words into NW which are not into M version and oposite.
So my suggestion will be to check the help documentation for version of NW used and to use the key words existing into that version.
Principle of script logic is the same.
Regards
Sorin Radulescu

Need Example for AVG() function in script logics...

Hi Everyone,
I need to calculate average for all the account members ...
so if anybody worked with this AVG() in Script logics please share with me...................

What do you mean by calculate average? Average for the period or for some other parent or..? Where do you want to store this average? How do you want to use this average???

Script Logic: Using a property in MDX *REC statement (BPC NW)

Hi,
Is it possible to use a Property in an MDX statement without using *LOOKUP() function? I have script successfully working but it takes 15 minutes to execute and would like to speed it up.
I understand that [DIMENSION].[MEMBER].Property is not valid syntax, and do not believe NW has any other functions to resolve the issue, except *LOOKUP which takes a long time.
Specific Example is below:
I have a piece of script that successfully splits JV Expense by customers. A Profit Share planning driver determines the percentage that each customer is entitled to. Typically this will be 100%, but could be 50% between two customers.
The PROFIT SHARE planning drivers records, and PARTNER_INCOME transactional records are below:
ACCOUNT
ENTITY
PARTNER
SIGNED DATA
PROFIT_SHARE
UK_001
PARTNER_A
0.5
PROFIT_SHARE
UK_001
PARTNER_B
0.5
PROFIT_SHARE
UK_002_PLANNING_DRIVERS
PARTNER_B
1.00
PARTNER_INCOME
UK_001
NO_PARTNER
$5,000
PARTNER_INCOME
UK_002
NO_PARTNER
$5,000
UK_001 has two partners that are each entitled to 50% of the $5,000 NET PROFIT.
For UK_002, one one single Partner is entitled to 100% of the $5,000 NET PROFIT.
Using script logic, you can scope the Profit Share account (PROFIT_SHARE) - , and use a *REC statement to multiply this by the driver. It would look like:
*XDIM_MEMBERSET ACCOUNT = PROFIT_SHARE
*WHEN ACCOUNT
IS *
*REC (EXPRESSION = %VALUE% * ([ACCOUNT].[PROFIT_SHARE],[PARTNER].[NO_PARTNER]), ACCOUNT = PARTNER_PROFIT_SHARE)
*ENDWHEN
This wouldn't be a problem if the Planning Driver is always stored on the same Entity that the Income is stored on, but for UK_002, the planning driver is stored on another Entity - which is stored in a the PLAN_DRIVER_REF property of the entity. It should use UK_002_PLAN_DRIVERS
ID (Entity)
PLAN_DRIVER_REF
UK_001
UK_002
UK_002_PLAN_DRIVERS
UK_002_PLANNING_DRIVERS
In this scenario, we need to switch out the Entity used in the MDX, however I do not believe you can use a property in MDX - can anyone confirm?
I have currently implemented the *LOOKUP functionality to loop through, changing each *LOOKUP partner for each loop.
Lookup:
*LOOKUP PLANNING_JV_US
*FOR %LOOP_ASLS% = %ASL_LOOKUP_LOOP_VARIABLE%
*DIM LOOK_%LOOP_PARTNERS%:ACCOUNT = "PROFIT_SHARE"
*DIM LOOK_%LOOP_PARTNERS%:PARTNER= %LOOP_PARTNERS%
*NEXT
*DIM ENTITY = ENTITY.PLAN_DRIVER_REF                   //   Use PLAN_DRIVER_REF Property of Entity
*ENDLOOKUP
Scope and *REC:
*XDIM_MEMBERSET ACCOUNT = PROFIT_SHARE
*WHEN ACCOUNT
IS *
*FOR %LOOP_PARTNERS% = %PARTNER_LOOKUP_LOOP_VARIABLE%      // 1000 Partners
*REC(EXPRESSION = %VALUE% * LOOKUP(LOOK_%LOOP_PARTNERS%), PARTNER= %LOOP_PARTNERS%, ACCOUNT = TCOJVSHAR_CALC, AUDIT_ID = PP_EXPENSE_BY_PARTNER)
*NEXT
*ENDWHEN
The problem with the above, is that because the Lookup is being generated for every single Partner, there are significant numbers of loops.
Does anyone know of another way this can be implemented in Script Logic? Otherwise we'll need to explore BAdI route.
Thanks,
Nick

Hi Nick,
Use property in LOOKUP - will dramatically speed up the calculation without FOR/NEXT.
Vadim

Use of LEFT in Script Logic

I am having one doubt reagrding usage of excel function like LEFT, MID, RIGHT in script logic of SELECT Statement.
Let me know with example if its possible.
I tried the below statement:
*SELECT(%EQACC%,"ID","ACCOUNT","LEFT(ID,6)='BE9001' AND CALC='N' AND ID<>'BE9001010'")
But it throw the error as "invalid select statement"
Anurodh

Anurodh,
what you are trying to do is not supported. As a workaround you can try to create a new property in the dimension (for example IDSHORT), putting in this filed just the first 6 characters of the ID and you can filter on it like in the following example:
*SELECT(%EQACC%,"ID","P_ACCT","IDSHORT='CE0004' AND CALC='N'")
Regards,
Simmaco

Greater Than Function in Script Logic File

BPC Experts,
I've got a pretty simple script logic file to calculate salary amounts, overtime, etc. The purpose of this logic is for forecasting. I have two referenced dimensions, TIME and SCENARIO, where TIME.MONTHNUM is equal to its relative month number (eg: Jan monthnum = 1), and SCENARIO.CURRMONTH is equal to the relative amount of actual months data, (eg Jan currmonth = 0, Feb = 1) because if you are completing a February forecast, you have one month of actual.
The ACTUAL scenario is never touched, but after a month closes, we copy the ACTUAL data to, for example, FEB_FCST. So, after January closes, its actuals are copied to the FEB_FCST scenario so we can complete an actual/forecast (one month actual, 11 months forecast).
Currently, the default logic skips anything in the ACTUAL scenario, by stating "*WHEN SCENARIO, *IS <> "ACTUAL" yada yada yada.
However, when the default logic runs on the forecast scenarios, it takes the same inputs from the months that are copied over from the ACTUAL scenario and adds to the original amount, essentially doubling the value--ultimately causing an incorrect actuals number in the forecast scenario.
My script right now looks like this:
*XDIM_MEMBERSET DATASRC=INPUT
*XDIM_MEMBERSET PRODUCT=NO_PRODUCT
*XDIM_MEMBERSET SHIFT=NO_SHIFTS
*XDIM_MEMBERSET MEASURES=PERIODIC
*WHEN SCENARIO
*IS <> "ACTUAL"
     *WHEN TIME.MONTHNUM
     *IS > SCENARIO.CURRENTMNTH
          *WHEN ACCOUNT
          *IS "SALARIED_MANPOWER"
               *REC(EXPRESSION=((([ACCOUNT].[SALARIED_AVG_WAGE] * (1 + [ACCOUNT].[SALARY_TIMEAHALF]))* [ACCOUNT].[SALARIED_MANPOWER])),ACCOUNT="01100")
          *ENDWHEN
*ENDWHEN
*ENDWHEN
*COMMIT
When it hits line 9 (*IS > SCENARIO.CURRENTMNTH) during validation, it errors. How can I use a "greater than" function to dictate whether or not a given scenario should run default logic on a specific month?
If not, is there a different/better way to do it?
Thank you!
ABF

Hi Alex
Take this sample logic, check the properties in your Time dimension to trouble shoot your issue.
*SELECT(%CAT_VAR%, "ID", CATEGORY, ID= PLAN_APRIL)
*XDIM_MEMBERSET CATEGORY = ACTUAL, PLAN, %CAT_VAR%
*SELECT(%CATMTH%, "STARTMTH", CATEGORY, ID= %CAT_VAR%)
*SELECT(%ACT_PERIOD%, "ID", TIME, MONTHNUM < %CATMTH% AND LEVEL = MONTH AND YEAR = 2010)
*SELECT(%PLAN_PERIOD%, "ID", TIME, MONTHNUM >= %CATMTH% AND LEVEL = MONTH AND YEAR = 2010)
*XDIM_MEMBERSET TIME= %ACT_PERIOD%
*XDIM_MEMBERSET CATEGORY=ACTUAL
*WHEN CATEGORY
*IS ACTUAL
*REC(EXPRESSION=%VALUE%, CATEGORY = %CAT_VAR%)
*ENDWHEN
*XDIM_MEMBERSET TIME= %PLAN_PERIOD%
*XDIM_MEMBERSET CATEGORY=PLAN
*WHEN CATEGORY
*IS PLAN
*REC(EXPRESSION=%VALUE%, CATEGORY = %CAT_VAR%)
*ENDWHEN
Thanks

SQL functions in Script Logic

I want to build a script logic but the dimensions that I am testing do not have the fields I want in the format I want. In my case I would like to test the "Start" property in the Employee dimension. The property represents the employee start date but is a var char in the format dd.mm.yyyy rather thna a date field. I want to test whether it is five years prior to the date being processed.
My time dimension has a year property and a monthnum property. Each of these are varchar. I can write SQL that would convert these to a date and compare them with the start property on the employee dimension.
Can I do iinsert SQL functions in the When statement. An example would be
*When convert(datetime, substring(employee.start,4,2) + '/' + substring(employee.start,1,2) + '/' + substring(employee.start,7,4))
Can I use SQL functions in the Is statement? An example would be
*Is <DateAdd(YY,-5 , convert(datetime, Time.Monthnum + '/01/'' + time.year)
Finally when I use such techniques and look at the log by using "show log" in the logic debugger I see no reference to the SQL I used. It is as if the generated SQL has not made use of my functions. Instead all I seee are the extract statements from the three fact tables. Is this normal? Is there a way to see what SQL is really being generated and run?
At the moment it seems my only option is to make changes, try running it and hope I get an output. If no records are written I can't be sure whether it is because embedding SQL function is not supported or because I have made some other error.

No, the "BPC SQL" script logic doesn't allow for this extensive use of real SQL within the scripting syntax. As a concept, it's best to think of "BPC SQL" script logic as, "this unique BPC logic syntax will generate real SQL code when it's executed."
There's very little real SQL that you can use within the syntax itself, and definitely not within the WHEN or IF statements. Nothing like cast, convert, substring, etc. (Except you CAN use these, a little bit, in a *SELECT statement. But I don't see how that will solve your current problem.)
Plus, when you consider how the logic engine processes a set of data, it's helpful to think of it in terms of selects & reading through a recordset. So in that regard, a SQL background can be helpful, in understanding the concepts. (Sort of helpful, except when it confuses you, or frustrates you since you don't have all the power you want.)
Anyway, to solve your problem, you might be able to restate the problem, and then use something like this code, which is valid syntax:
*WHEN TIME.TIMEID
*IS >= VERSION.FirstPlanMonthTimeID
In this case, FirstPlanMonthTimeID is set up in the version dimension as, for example, 20090400 (representing 2009.APR). This timeID is set by BPC automatically when processing the time dimension, and I need to ensure that my Version property value is set to match it.
A key point is that in BPC fact tables, the time dimension is stored as TIMEID (not ID, unlike all the other dimensions), and can be used for comparative evaluation in script logic WHEN/IF. The comparison property needs to be stored as an 8-digit integer value. If your time dimension has days in it (along with months), check the TIMEID after processing, and you should see the pattern for assigning values to TIMEID for days and months, etc.
Normally, TIMEID is assigned pretty sensible and stable values. If it doesn't meet your logic requirements, you can create another property (be careful of USERTIMEID, since that has a specific purpose in the system which I've never fully understood) and assign that whatever (integer) values make sense.

*Prior statement in script logic

Hi,
I'm getting started with script logic and I'm trying to create a record that will be the result of the current amount in a specific account minus the amount for the same account in the previous period.
I was thinking to use a "prior" statement, but not really sure how to do that. Do somebody could write me an example that would sbustract my current amount minus the amount from the previous period where the account is the same in a sql logic?
Thanks
Martin

Hi,
This should do the trick.
*INCLUDE SYSTEM_CONSTANTS.LGL
*XDIM_MEMBERSET TIMEDIM=PRIOR,%TIME_SET%
*XDIM_Member DataSrc=INput
*WHEN *
*IS *
*REC(EXPRESSION=GET(DATASRC="INPUTSAP",TIME=PRIOR)-GET(DATASRC="INPUTSAP"),NOADD,DATASRC="Movement")
*ENDWHEN
*commit
Cheers,
AvdB
Edited by: Gert Andries van den Berg on Aug 12, 2009 9:14 AM

Rounding up in script logic

Dear all,
I am using BPC 7.0 MS
I tried to perform rounding up in script logic using Round and a negative number, but it didn't work.
Any other suggestions?
Cheers,
Lip Chean

So in this case you might need to use division instead of multiplication, for example:
(int(28/100)+1)*100
In my previous example I was assuming that you might need to get rid of two decimals and round to the full currncy unit.
cheers,
Madis
Edited by: Madis Udam on Mar 17, 2010 9:30 PM
Edited by: Madis Udam on Mar 17, 2010 9:31 PM

Handling Ranges in Script Logic

Hi Experts
Is it possible to put logic to check a range of values in Script Logic.
For example, if I need to check if the value in Quantity Account is between 200 and 800, then only some Quantity Discount is calculated against this.
What command should one use for this
Any input would be very helpful.
Regards
Krishnendu

Hi Krishnendu,
I believe that you can use MDX or a BADI to do this. Using MDX, for example, the following should write 100 to the QUANT_DISC account in the event that QUANTITY is greater than 200 and less than 800:
[ACCOUNT].[QUANT_DISC] = IFF(([ACCOUNT].[QUANTITY]) > 200,IIF(([ACCOUNT].[QUANTITY])<800,100,0),0)
This is just example MDX code - you'll have to adapt and test yourself. I suggest using the script logic tester to speed the process. Performance may be less than ideal, and you can certainly implement this in a BADI in that event.
It would be nice if it were possible to do this using WHEN/IS statements in script logic, but at present conditional logic based on measure values is not supported in that context.
Ethan

Help in script logic

Hi Experts,
We are using SAP BPC 7.5 NW Version SP08. We are using a script logic that calculates the opening value of inventory(ASSTCAINVAMO) for each month except the 1st month of financial year for which the value is entered from an input schedule. The opening value of inventory of each subsequent months are calculated when the parameters for production(e.g. OSDA) are entered from a separate input schedule. The following script logic is written for the calculation:
*FOR %TIM_MEM%=%TIME_SET%
*XDIM_MEMBERSET TIME =%TIM_MEM%
*WHEN P_ACCT2
*IS "OSDA",
REC(EXPRESSION=[P_ACCT2].[ASSTCAINVAMO]+[P_ACCT2].[RDPA][P_ACCT2].[EFFA][P_ACCT2].[OSDA]-[P_ACCT2].[CONVAMUR][P_ACCT2].[RDPU][P_ACCT2].[EFFU][P_ACCT2].[OSDU]-([P_ACCT2].[SALQAMBC]+[P_ACCT2].[SALQAMM]),P_ACCT2="ASSTCAINVAMO",TIME=TIME.NEXT)
*ENDWHEN
*COMMIT
*NEXT
The loop works fine, but it seems the list of time values are not coming in proper sequence. For example, the loop is running for 2011.NOV before it iterates for 2011.OCT. So when it iterates for 2011.NOV, it is not getting the opening value for the month and consequently 2011.DEC's opening value is calculated assuming 2011.NOV's opening value to be 0. In the input schedule the months are in proper sequence.
Is there any way out so that the months come in proper sequence in the logic as well?
Thanks in advance for any help.

We had similar issue . we changed TIME members from Monthnames to numbers . i.e changed 2011.JAN to 2011.01 . Then you get correct result as you are expecting . Issue when using month names in combination of TMVL is that , instead of getting 2011. MAY for TMVL(1,2011.APR) , it gets 2011.FEB . TMVL function some how takes alphabetical order instead of taking month order . Not sure if this behavior is with service pack . But never saw any thread reporting this issue .
Anyways ,you can wait for other responses as i am too curious to know if any one faced this issue and how did they resolve.

Calculations in Script Logic

Dear Experts,
I am trying to do some calculations using script logic.
Foe example: In account dimension I have three members A, B & C.
Now i want to do A = B multiply C using script logic.
I will insert data for B and C. The B, C should get multiply and insert in to A.

hello experts,
i am newbie to bpc & scriptlogic, i am, me too, trying to do some calculations using scriptlogic.
i've created a dimension S_GOSTERGE with members SATISTUTARI, SAT_Fiyat, SAT_Miktar
i want to calculate SATISTUTARI = SAT_Miktar * SAT_Fiyat
so i've writed the script below.
*XDIM_MEMBERSET S_GOSTERGE = SATISTUTARI
*XDIM_MEMBERSET S_GOSTERGE = SAT_Fiyat
*XDIM_MEMBERSET S_GOSTERGE = SAT_Miktar
*WHEN S_GOSTERGE
*IS SAT_Miktar
*REC(FACTOR = GET(S_GOSTERGE ="SAT_Fiyat") , S_GOSTERGE = SATISTUTARI)
*ENDWHEN
*COMMIT
when i click ''validate'' i get the error message : cannot find dimension ""SAT_FIYAT")"
please, can you help me to solve this?
thanks in advance.

Next, Prior Time in Script Logic

Hi there,
I have a problem about script logic. I have 2 monthly rate types. One of them is end-of-period rate(EPR) and other is average rate(AR). i want calculate average rate(AR) summing two consecutive end-of-period rate, dividing 2. But i donu2019t know how can i get previous end-of-period rate. I used prior and next(-1) but it does not work. Can you explain it how can i do this?
Example;
--Jan-Feb---Mar
EPR -2-3----4
AR----22,5--3,5
*WHEN KUR_ACCOUNT
*IS EPR
*WHEN TIME.MONTHNUM
*IS 1
*REC(KUR_ACCOUNT=AR)
*ELSE
*REC(EXPRESSION=(%VALUE% + GET(TIME=NEXT(-1)) / 2, KUR_ACCOUNT=AR)
*ENDWHEN
*ENDWHEN
*COMMIT
Thanks in advance.

What version and support package of BPC do you work on? In BPC 7.5 a new time offset is possible with the keyword TMVL.
Thanks and best regards,
[Jeffrey Holdeman|http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman]
SAP Labs, LLC
BusinessObjects Division
Americas Applications Regional Implementation Group (RIG)

Display entire log in script logic?

When users run a script logic, eg to push data from one model to another, they get errors like:
Invalid Members [ACCOUNT_DTL]=61500270
Invalid Members [ACCOUNT_DTL]=51301500
However these errors are at the very end of the log and the user cannot see them, because they exceed the maximum log length to be displayed in data manager package status.
The script logic executes successfully and does not throw an error, but records do not post. It causes large errors because they're unaware of the issue as no error is thrown and the log does not display all lines.
I have to go into UJFS, download the zip file with their full log in it and send the errors to them.
Is there a setting either:
1. Flag the log as 'error' and do not allow it to post?
2. Display the entire log in the data manager package "View Status" - all lines? Or at least all errors?
Thx, Aaron

Vadim,
We have a logic that pushes from model1 to model 2.
Due to supporting some existing/legacy code, logic is as follows:
*RENAME_DIM ACCOUNT_C=ACCOUNT_DTL
ACCOUNT_C is in Model1. ACCOUNT_DTL is in Model2.
Value for some GL account "32100000" for example has been created in account_c but not in account_dtl, so when the logic creates *REC's it fails.
If no solution is available on the error log I will probably create BPC master data package to update both account_c and account_dtl at once from BI. Will be the only way to keep them in synch.
Thanks for checking, Aaron

Use of prompted hierarchy's base members in Script Logic

Hello all,
I have a data manager package which prompts the user for a dimension called P_BUDGET_MODEL. The prompt is SELECT hence the user selects a hierarchy node on this dimension.
In the relevant Script Logic I have a variable %P_BUDGET_MODEL_SET%, which is automatically created by the system. I would like to run the logic for the basemembers of the hierarchy node.
Please note - the basemembers are not direct children of the selected hierarchy node (i.e. the selected node is the "grandparent" of the basemembers).
I tried the following simple logic command:
*XDIM_MEMBERSET P_BUDGET_MODEL = BAS(%P_BUDGET_MODEL_SET%)
It yielded a message that "Member BAS() does not exist".
I have also noticed the following thread:
[BPC 7.5 NW - HIER NODE in PROMPT using Formule in Package ?;
If I understood properly it is not relevant to my case because the hierarchy is more that 2 levels deep.
Any ideas?
TIA
Avihay

Hi,
As it seems after further investigation the problem is that I use "_" in the dimension names and variable names. This creates a problem to BPC in some cases.
For example here there is no problem:
*SELECT(%MODEL%,ID,P_BUDGET_MODEL,ID="%P_BUDGET_MODEL_SET%")
Here there is a problem hence the use of [ ]
*XDIM_MEMBERSET P_MONTH = BAS([%P_VERSION_SET%.YEAR].TOTAL)
Here there is not "_" so the code is fine:
*XDIM_MEMBERSET P_BUDGET_MODEL = BAS(%MODEL%)
Strange yet seems that this was the problem...
Avihay

Script Logic examples

Similar Messages

Maybe you are looking for