Script Logic - YTD Salary

//Calculate YTD Salaries & Wages
*CALC_EACH_PERIOD
*LAST_MEMBER TIME=%PREFIX%.NOV
*WHEN ACCT_HCM.ID
    *IS "SALARYYTD","TOTALSW"
    *WHEN TIME.PERIOD
        *IS "JAN"
            *REC(EXPRESSION=0.001,ACCT_HCM="SALARYYTD")
            *REC(ACCT_HCM="SALARYYTD",TIME=NEXT)
        *ELSE
            *REC(ACCT_HCM="SALARYYTD",TIME=NEXT)
    *ENDWHEN
*ENDWHEN
*COMMIT
2005.jan - monthlyrate -$7500
2005.jan totalsw=7500
First time when I run the logic , it calculates the salaryytd correctly as 7500 for 2005.DEC.But when I run the logic again I get incorrect value 15000(DEC = prev dec value + new value) for DEC period . I am expecting to see the same 7500 for dec.Only for DEC month i have this issue.
How to fix this? I donu2019t see anything wrong in my script. Pls help.
Thanks.

Logic works fine for Jan to Nov. only for DEC month i have this issue.
Not able to figure out how its calulating the DEC value

Similar Messages

Calc Previous YTD periods in SQL script logic

Hi, experts!
I need help in writing SQL script logic. I want to calculate such logic
(Account = Acc3, TIME = 2009.FEB ) = (Account = Acc1, SUM(TIME = (2009.JAN; 2009.FEB))) - (Account = Acc2, SUM(TIME = (2009.JAN)))
(Account = Acc3, TIME = 2009.MAR ) = (Account = Acc1, SUM(TIME = (2009.JAN; 2009.FEB; 2009.MAR))) - (Account = Acc2, SUM(TIME = (2009.JAN; 2009.FEB)))
..... and so on
Thanks all for help.

Hi Petar,
Thanks for your advice.
Legalapp in my Apshell do not have any account transformation rules. But looking at the account transformation table, I can see it requires dimension type datasrc and subtable for datasource and flow fields. But currently my application is similar to the Finance application from Apshell and do not have these dimension types.
Still I created a rule in account transformation table by having these fields blank and the validation was successful. Then I used SPRUNCALCACCOUNT in default.LGL file to trigger this rule but I don't see this working.
Can you help me on below questions:
1. Is it necessary to have datasrc and subtable dimensions to create account transformation rule?
2. Will SPRUNCALCACCOUNT write the values to WB table or should I use COMMIT or any other command along with his to have the values written?
3. Is there any way/place where I can get the examples of Account Transformation rules ?
Thanks
Sharath

Variable in script logic

Follow is the script code from previous post
*XDIM_MEMBERSET ACCOUNT = ACC1
*FOR %My_Var% = %ENTITY_DIM%
*WHEN ENTITY
*IS *
*REC(EXPRESSION = (GET (ENTITY = %My_Var%.PROP1)), ENTITY = %My_Var%)
*ENDWHEN
*NEXT
I understand that both %My_Var% and %ENTITY_DIM% are variables, my question is how %My_Var% and %ENTITY_DIM% get the value during the process of the code, do we neeed to define the variable some where else before we use them? I remeber in FOX, we need to define the variable before we can use it.
also is there a difference if I use $My_Var$ to replace %My_Var%?

nilanjan,
Thanks for the explanation,I have another question regarding to the variables.
I need to get the YTD salary. in BPS the pseudocode code is as following:
data YTD_salary type amount
loop at each_month,
   YTD-Salary = YTD-Salary + current_month.
   if the YTD-Salary > FICA CAP.
   exit.
Endloop
How can we archive the same in BPC script logic with a variable to capture the YTD-Salary and pass it to next month?

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

Custom Measure in Script logic

Hi,
We have a custom measure created which is more or less the same as the YTD, but it starts not at the beginning of the year, but instead it starts at a given month.
The measure creation was ok and we can use it perfectly well in reports and input shedules and the cumulation of data is ok.
However, if we want to use this measure in a script logic it does not work.
- Validating the script in the admin console goes fine
- Executing the script gives the error:
- Root element is missing
- validating in UJKT gives the erro:
- UJK_VALIDATION_EXCEPTION:Invalid Measures value: "T_232"
The script we try to use is below. If we change the LTD (our custom measure) by YTD it works perfectly fine:
*XDIM_MEMBERSET BUILDSTATE=NABS
*XDIM_MEMBERSET BUSAREA=V1
*XDIM_MEMBERSET CATEGORY=FCSTCUR
*XDIM_MEMBERSET DATASRC=INPUT
*XDIM_MEMBERSET ENTITY=201
*XDIM_MEMBERSET MARKSEGM=NAMS
*XDIM_MEMBERSET ORIGIN=OBOOK
*XDIM_MEMBERSET PRODUCT=ELEVATORS
*XDIM_MEMBERSET PROFCENT=201251
*XDIM_MEMBERSET RPTCURRENCY=LC
*XDIM_MEMBERSET SALESORG=SO_201
*XDIM_MEMBERSET TECHPLATF=NATP
*XDIM_MEMBERSET TIME=2010.OCT
*XDIM_MEMBERSET TYPE=T_PLAN0
*XDIM_MEMBERSET NEBACCOUNT =BAS(T_232)
*XDIM_MEMBERSET MEASURES=PERIODIC
[NEBACCOUNT].[#A232]=([MEASURES].[LTD],[NEBACCOUNT].[T_232])
*COMMIT
Thanks for any input on this. We want to avoid going via a BADI!
Kind regards,
Christophe Posson

Hi Christophe,
I'm in a similar position to you and wish to avoid use of a BAdI if we can - despite the MDX parser engine being pretty pathetic at handling YTD or custom measures.
Did you get a resolution to this? If so, could you please share it with everyone?
As much information as possible would be apprecaited. Our next move is to contact SAP for confirmation that there is no possibility of using custom measures in Script Logic.
Many thanks,
Nick

MEASURES in script logic

Hi All!
How can I use YTD measures in script logic? My aplication is PERIODIC ( YTDInput set to No) and I need in my script logic to use YTD values for some calculation. I tried following syntax
*REC(EXPRESSION=([C_ACCT].[PLM],[MEASURES].[YTD]))
but after validation error appears
http://screencast.com/t/q2gChPrqbVXy.
Please help, how to use measures dim in script logic??
Regards,
Justyna

Full script not it is working fine after change *XDIM_MEMBERSET MEASURES=YTD to *XDIM_MEMBERSET MEASURES=PERIODIC
*XDIM_MEMBERSET C_ACCT = VALCON_EN020
*XDIM_MEMBERSET MEASURES=PERIODIC
*WHEN_REF_DATA = MASTER_DATA
*WHEN C_ACCT
*IS VALCON_EN020
*REC(EXPRESSION=([C_ACCT].[PLM],[MEASURES].[YTD]))
*ENDWHEN
*COMMIT

Cumulative value calculation in script logic

Hi,
Assuming i have the following values:
Acc1, time1 = 2
Acc1, time2 = 10
Acc1, time3 = 20
Acc1, time4 = 30
What script logic can i write such that the end results are:
Acc2, time1 = 2
Acc2, time2 = 12
Acc2, time3 = 22
Acc2, time4 = 32
time1 could start from any month of the year, and the next month is always one month after the current month (i.e. if time1 = june, then time2 = july).
Basically the above calculation involves some sort of cumulative effect. I would like to have this cumulative amounts stored in the database, hence i don't want to rely on measures="ytd" in the report.
Cheers

Hi Raja,
You can get the daywise cumulative value for the user selected date range by creating a formula on the KF & turning on the 'Cumulated' checkbox in the 'Calculations' tab.
--Priya

Use of MEASURES dimension in a RUNALLOCATION in a script logic

Hi everybody,
We are trying to use MEASURES dimension inside a RUNALLOCATION in a script logic, because we need to work with the information at a YTD element
Example:
It works:
*XDIM_MEMBERSET C_CATEGORY=%C_CATEGORY_SET%
*XDIM_MEMBERSET TIEMPO=%TIEMPO_SET%
*XDIM_MEMBERSET PRODUCT=BAS(TOT_PRODUCT)
*XDIM_MEMBERSET MARKET=BAS(TOT_MARKET)
*RUNALLOCATION
          *FACTOR=USING
          *DIM ACCOUNT     WHAT=Cost;          WHERE=Import;           USING=Units;
//        *DIM MEASURES    WHAT=PERIODIC;      WHERE=PERIODIC;         USING=YTD;
          *DIM CLIENT      WHAT=CLIENTE_NA;    WHERE=>>>;              USING=BAS(TOT_CLIENT);
*ENDALLOCATION
*COMMIT
It doesn't work:
*XDIM_MEMBERSET C_CATEGORY=%C_CATEGORY_SET%
*XDIM_MEMBERSET TIEMPO=%TIEMPO_SET%
*XDIM_MEMBERSET PRODUCT=BAS(TOT_PRODUCT)
*XDIM_MEMBERSET MARKET=BAS(TOT_MARKET)
*RUNALLOCATION
          *FACTOR=USING
          *DIM ACCOUNT     WHAT=Cost;          WHERE=Import;           USING=Units;
          *DIM MEASURES    WHAT=PERIODIC;      WHERE=PERIODIC;         USING=YTD;
          *DIM CLIENT      WHAT=CLIENTE_NA;    WHERE=>>>;              USING=BAS(TOT_CLIENT);
*ENDALLOCATION
*COMMIT
How can we do it? Is possible to use Measures dimension?
Any idea out there?
Kind regards
Albert Mas

Hi Albert,
I believe you are correct that using MEASURES in this way is not possible. Depending on whether you have data in future periods, you may just be able to use the time dimension instead of the measures dimension:
*DIM TIME WHAT=2010.AUG; WHERE=2010.AUG; USING=2010.TOTAL;
You could also manually maintain a property and select on the property to do the same thing, which would allow you to exclude future periods.
Another option might be to make your Units account a balance sheet account, which should make it always behave as a YTD value, or create a second UNITS_YTD account as a balance sheet account and populate it with the Units YTD value using script logic before running the allocation, then use the UNITS_YTD account as your allocation driver.
Ethan

How to calc accumulate rate in a script logic?

Hi experts,
We are trying to generate a monthly accumulate rate in a script logic. We have a Unit rate in 12 months and we want UnitAccum rate (like YTD) in the same 12 months
Finally, we need to use this new rate in a multiplication.
How can we do it with a script logic? Any idea out there?
Kind regards
Albert Mas

Hi Ethan,
You are understanding ok
We are working on SAP BPC NW version 7.0, SP05, and at the moment, it's impossible to update to SP08.
We have done all the following tests, trying to find some solution, under these conditions (we knew that some tests weren't going to work well, but anyway, we had to try them):
- always for only one product (*XDIM_MEMBERSET PRODUCT=Product1)
- UNITS and UNITACCUM are ACCOUNT base members
- UCostVtaAcumDimFor is an ACCOUNT Formula Base Member ([ACCOUNT].[UNITS],[MEASURES].[FYTD])
- FYTD is a Measures base member for Fiscal Year To Date (we use it because we want to see as Year to Date (YTD) as Fiscal Year To Date (first month of the year is September and the last one is August) (it works well)) (We have also tested on YTD instead of FYTD, with the same results)
(1)
*XDIM_MEMBERSET TIEMPO=2010.FEB
[ACCOUNT].[#UNITACCUM] = ([ACCOUNT].[UNITS],[MEASURES].[FYTD])
*COMMIT
Result: MEASURES not specified. Failed
(2)
*XDIM_MEMBERSET TIEMPO=2010.FEB
*WHEN ACCOUNT
*IS UNITS
*REC(EXPRESSION=([ACCOUNT].[UNITS],[MEASURES].[FYTD]), ACCOUNT=UNITACCUM)
*ENDWHEN
*COMMIT
Result: MEASURES not specified. Failed
(3)
*XDIM_MEMBERSET TIEMPO=2010.FEB
*WHEN ACCOUNT
*IS UNITS
*REC(ACCOUNT=UNITACCUM,MEASURES=FYTD,FACTOR=1)
*ENDWHEN
*COMMIT
Result: Unknown Dimension Name in Keyword "MEASURES". Failed
(4)
*XDIM_MEMBERSET TIEMPO=2010.FEB
*WHEN ACCOUNT
*IS UNITS
*REC(ACCOUNT=UNITACCUM,TIEMPO=TIEMPO.NEXTMONTH,FACTOR=1)
*ENDWHEN
*COMMIT
Result: it takes too much time (more than five minutes) without ending the process --> We stop this test
(for 2010.FEB, TIEMPO.NEXTMONTH=2010.MAR)
(5)
*XDIM_MEMBERSET TIEMPO=2010.FEB
*WHEN ACCOUNT
*IS UNITS
*REC(ACCOUNT=UNITACCUM,TIEMPO=TIEMPO.PREVMONTH,FACTOR=1)
*ENDWHEN
*COMMIT
Result: it takes too much time (more than ten minutes) without ending the process --> We stop this test
(for 2010.FEB, TIEMPO.PREVMONTH=2010.JAN)
(6)
*XDIM_MEMBERSET TIEMPO=2010.FEB
*WHEN ACCOUNT
*IS UNITS
*REC(ACCOUNT=UNITACCUM,FACTOR=1)
*ENDWHEN
*COMMIT
Result: Cancelled
(7)
*XDIM_MEMBERSET TIEMPO=2010.FEB
[ACCOUNT].[#UNITACCUM] = [ACCOUNT].[UCostVtaAcumDimFor]
*COMMIT
(UCostVtaAcumDimFor is a Formula Base Member ([ACCOUNT].[UNITS],[MEASURES].[FYTD]))
Result: Cancelled
Some more ideas?
Thanks in advance,
Albert Mas

How can i write this syntax in script logic....

hi all
i need to write below syntax in bpc script logic..
If Headcount = 0, then Salary = 0 Else:
If Month <> March and Month <> September:
Salary = Salaryprevious month1 + [(Headcountcurrent month - Headcountprevious month1) * (Band Rate + Band Salary Factor)]
If Month = March:
Salary = [Salaryprevious month1 + [(Headcountcurrent month - Headcountprevious month1) * (Band Rate + Band Salary Factor)] ] * (100% + Band Annual Increase + Band Annual Increase Factor)
in the above code headcount,salary,bandrate etc all got ids.
thanks guys

Hi,
In your query, when you say that headcount = 0, do you mean the signed data? In this case, it will difficult to do. When you have a signed data as 0 in SQL, once you optimize the application or compress it, that particular record will go and your logic will not work.
If I look at your logic,
If Headcount = 0, then Salary = 0 Else:
If Month March and Month September:
Salary = Salaryprevious month1 + (Headcountcurrent month - Headcountprevious month1) * (Band Rate + Band Salary Factor)
If Month = March:
Salary = [Salaryprevious month1 + (Headcountcurrent month - Headcountprevious month1) * (Band Rate + Band Salary Factor)] * (100% + Band Annual Increase + Band Annual Increase Factor)
If the application has been compressed or optimized, it will not get any record for that particular headcount and will directly go into the "else" loop. Though, its not correct.
I hope you got my point.

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

How to auto-update of script logics after adding new dimension members?

Hi Experts,
Just wanna ask if BPC has a functionality that would automatically update/validate and save my script logic whenever I add new dimension members. I've added new PL accounts but they are not automatically added to my calculated BS Net Income. I had to re-validate and save my logic for it to be included in my logic and for the amounts to be computed correctly.
Thanks,
Marvin

Hi Marvin,
There is no functionality as such. we need to configure the script as and when we make any changes in the dimension members.
Regards
Raman

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

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.

BPC 7.5 MS SP5 wrong numbers multiplying GET (A)*GET(B) in script logic

Hi experts,
We are migrating from BPC 5.1 MS to 7.5 MS SP5 and there have some scripts that are using GET function that retrieve wrong numbers. Particularly, it does not record the decimals figures.
Example1 (multiply): when A=2,3 and B=4,4, then AB=10,12. But doing this in script logic GET(A)GET(B)=10. It does not write the decimal figures.
Example2 (addition): when A=2,3 and B=4,4, then AB=6,7. But doing this in script logic GET(A)GET(B)=6. It does not write the decimal figures.
Particularly, the script we are executing is the following. This script worked ok at 5.1 but not at 7.5:
*XDIM_MEMBERSET ACCOUNTL= INFLA_AUX,INFLA_ACUM
*XDIM_NOSCAN ACCOUNTL = INFLA_ACUM
*XDIM_MEMBERSET CATEGORY=%CATEGORY_SET%
*XDIM_MEMBERSET CURRENCY=LC
*XDIM_MEMBERSET TECHNOLOGY = %TECHNOLOGY_SET%
*XDIM_MEMBERSET PEM=DESCENDANTS([PEM].[PEMTOT],999,LEAVES)
*XDIM_MEMBERSET TIME=DESCENDANTS([TIME].[XXXX.TOT],999,LEAVES)
*CALC_EACH_PERIOD
*WHEN ACCOUNTL
*IS INFLA_AUX
     *WHEN TIME.YEAR
     *IS = PEM.YEAR
*REC(EXPRESSION=1,NOADD,ACCOUNTL=INFLA_ACUM)
            *IS < PEM.YEAR
*REC(EXPRESSION=0,NOADD,ACCOUNTL=INFLA_ACUM)
            *IS > PEM.YEAR
*REC(ACCOUNTL=INFLA_ACUM,NOADD,EXPRESSION=GET(ACCOUNTL="INFLA_ACUM",TIME=PRIOR) * GET(ACCOUNTL="INFLA_AUX",TIME=PRIOR))     //in this sentence!!!!!!
          *ENDWHEN
*ENDWHEN
*COMMIT
We have SIGNED_DATA_FORMAT (25,10) in the application parameters.
Many thanks for your attention.
Best regards,
Arkaitz
Edited by: arkaitz_orozko81 on Apr 28, 2011 4:31 PM
Edited by: arkaitz_orozko81 on Apr 28, 2011 4:33 PM

Hello,
We have solved this issue.
First, we have change the script:
*SELECT(%PEM_APLICA%,[ID],PEM,"APLICA='Y'")
*XDIM_MEMBERSET ACCOUNTL=PROD_AUX,DISP_INP,HORA_AUX,CAPAC_AUX
*XDIM_NOSCAN ACCOUNTL= PROD_AUX
*XDIM_MEMBERSET CATEGORY=%CATEGORY_SET%
*XDIM_MEMBERSET CURRENCY=LC
*XDIM_MEMBERSET TECHNOLOGY=DESCENDANTS([TECHNOLOGY].[RENOVABLES],999,LEAVES)
*XDIM_MEMBERSET PEM=%PEM_APLICA%
*XDIM_MEMBERSET TIME=<ALL>
*WHEN ACCOUNTL
*IS CAPAC_AUX
//*IS *
     *WHEN SIGNEDDATA
     *IS <> 0
REC(ACCOUNTL="PROD_AUX",NOADD,EXPRESSION=GET(ACCOUNTL="CAPAC_AUX")* GET(ACCOUNTL="DISP_INP")* GET(ACCOUNTL="HORA_AUX"))
     *ELSE
*REC(ACCOUNTL="PROD_AUX",NOADD,EXPRESSION=0)
*ENDWHEN
*ENDWHEN
*COMMIT
And we have change the regional settings to "English (United States)".
Many thanks for your answer.

Script Logic - YTD Salary

Similar Messages

Maybe you are looking for