Clarification required in Script Logic

Hi All,
I had written a Script logic which copies the data from one dimension member of entity to another entity.
The script that we used is pasted here for reference:
"//Logic for Revenue Transfer for one account to account
*XDIM_MEMBERSET CATEGORY = BUDGET
*XDIM_MEMBERSET P_ACCT = REV000003, REV000007, REV000008
*XDIM_MEMBERSET P_ACTIVITY = P_ACTIVITY_NONE
*XDIM_MEMBERSET P_DATASRC = U
*XDIM_MEMBERSET ENTITY = U_RCL_INP, U_MFG_INP, U_FSI_INP, U_ECS_INP, U_KS_INP, U_INDIA_INP, U_BIZP_INP, U_SI_INP
*XDIM_MEMBERSET INTCO = I_U_RCL, I_U_MFG, I_U_FSI, I_U_ECS, I_U_KS, I_U_INDIA, I_U_BIZP, I_U_SI
//Revenue Transfer from P_ACCT REV000003 to P_ACCT REV000004
*WHEN P_ACCT
*IS "REV000003"
*REC(FACTOR=1,P_ACCT=REV000004 ,INTCO=ENTITY.INTCO,ENTITY=INTCO.ENTITY)
//Revenue Transfer from P_ACCT REV000007 to P_ACCT REV000012
*IS "REV000007"
*REC(FACTOR=1,P_ACCT=REV000012 ,INTCO=ENTITY.INTCO,ENTITY=INTCO.ENTITY)
//Revenue Transfer from P_ACCT REV000008 to P_ACCT REV000009
*IS "REV000008"
*REC(FACTOR=1,P_ACCT=REV000009 ,INTCO=ENTITY.INTCO,ENTITY=INTCO.ENTITY)
*ENDWHEN"
The above script logic is not working if the user doesnt have access to the other entity to which data is copied into.
However, as per our business requirement, we need to restrict the access to the users to thier respective entites.
Hence, i would be glad to know, How can I overcome this limitation, or, how can I bypass the authorization through script logic??
Let me know incase you require any further information about the issue.
Thanks in Advance
Regards,
Chandra

Hi Nilanjan,
As Anurodh said, The command *IGNORE_SECURITY is not recognised in the BPC NW. I tried, but is not validated.
Anurodh,
Thanks for the link. Seems it is helpful.
Regards,
Chandra

Similar Messages

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.

How to use the current view in script logic - %DIMENSIONNAME_SET% not work

Hello,
I have the requirement to use the values from the current view in the script logic. User would like to use the members which were selected from the current view in the calculation.
We are using SAP BPC 7.0 SP06
I have prepared the following scrpit:
*XDIM_MEMBERSET TIME=$YEARS001$.NA
*XDIM_MEMBERSET ACCOUNT=BAS(PLVEH_EXP)
*SELECT(%CBU%,ID,BUSINESSAREA,[ID]='%BUSINESSAREA_SET%'")
*SELECT(%CIO%,ID,INTERNALORDER,[ID]='%INTERNALORDER_SET%'")
*RUNALLOCATION
*FACTOR=USING
*DIM BUSINESSAREA WHAT=BANA;WHERE=%CBU%;USING=<<<
*DIM INTERNALORDER WHAT=IONA;WHERE=%CIO%;USING=<<<
*DIM INDICATORS WHAT=INVEHPRI;WHERE=INPXQ;USING=INVEHQUA
*ENDALLOCATION
I have read in the sdn that it is possible to get the current values using %DIMENSIONNAME_SET% variable and use it but it returns all the members that were selected in the datapackage.
I would like to know if there is any special consideration regarging the use of variable or if there is another way to solve it.
Thanks in advance.

Hi,
If you want the code to be executed for the current view selected, you can place the code in Default logic which executes the logic for what ever current view values you send the data through Input schedule.
The key word you have mentined is for script running through Data Manager which gets the value selected through user promt.
Hope this helps,
Regards,
G.Vijaya Kumar.

Help in script logic - problem in FOR loop

Hi Experts,
We are using BPC 7.5 SP08. I have written a FOR loop in script logic default.lgf which is as follows:
*FOR %TIM_MEM%=%TIME_SET%
*XDIM_MEMBERSET TIME =%TIM_MEM%
*WHEN P_ACCT2
*IS "OSDU"
REC(EXPRESSION=[P_ACCT2].[ASSTCAINVURO][P_ACCT2].[COGSUPRVIPSA]/[P_ACCT2].[ASSTUPRVTAQTY],P_ACCT2="COGSUIPSAO")
*ENDWHEN
*COMMIT
*NEXT
As per my requirement, all this members: [ASSTCAINVURO], [COGSUPRVIPSA], [ASSTUPRVTAQTY] exists for months September to next year's August. But in my input schedule, the months are from August to next year's July(which is the company's fiscal year). Consequently the loop runs for month August to next year's July while I need to run the loop 1 month late(i.e. September to next year's August). This was achieved earlier by hard-coding the time members which we cannot afford as this requires to update these hard-coded member IDs every year.
We have also tried using the "NEXT" property of TIME dimension as follows:
*XDIM_MEMBERSET TIME =%TIM_MEM%.NEXT
but %TIM_MEM%.NEXT doesn't get the month in 'NEXT'.
Please suggest if there is any way out to solve this problem.
Thanks in advance.

Hi Appu,
Even if you restrict the scope using the XDIM statement, your script will just run the number of times as per the for loop. Actually, in reality, the same calculation is happening again and again, in your code; since your calculation is not based on the time member.
To use the for loop effectively, you need to incorporate the time member in your calculation.
Please look at the below sample code:
*XDIM_MEMBERSET TIME = %TIME_SET%
*FOR %TIM_MEM%=%TIME_SET%
   *WHEN P_ACCT2
   *IS "OSDU"
      *REC(EXPRESSION=<CALCULATION>,P_ACCT2="COGSUIPSAO")
   *ENDWHEN
*NEXT
And in your calculation, you can use statements like
([P_ACCT2].[ASSTCAINVURO],TMVL(1, [TIME].[%TIM_MEM%]))
This will ensure that everytime (as per the for loop), the calculation works on separate set of data.
Hope you got the idea.

Syntax in script logic

Hi Friends,
I have input schedule in below format.
Product   Rate/2011.INP Packing/2011.INP QTY/2011.APR AMOUNT/2011.APR QTY/2011.MAY AMOUNT/2011.MAY
PM         3                 3              3               27            4         36
PN        5            2          2          20     3 30
Here Amount= Rate*Packing*QTY. Pls correct below script logic and make it generic for all months.
*XDIMMEMBERSET TIME=2011.APR,2011.MAY,2011.INP
*XDIMMEMBERSET ACCT=QTY,RATE,PACK,AMOUNT
*WHEN ACCT
*IS QTY
*WHEN TIME
*IS 2011.APR,2011.MAY,2011.INP
*REC(EXPRESSION=%VALUE% * ([ACCT].[RATE],[TIME].[2011.INP])
                         * ([ACCT].[PACK],[TIME].[2011.INP]),
                             [ACCT]=AMOUNT,[TIME].[2011.APR])
*ENDWHEN
*ENDWHEN
*COMMIT
Thanks,
Naresh

Hi,
You can simply write this using MDX formula,
[ACCT].[#AMOUNT]=[ACCT].[PACK]*([ACCT].[RATE],[TIME].[2011.INP])*([ACCT].[QTY],[TIME].[2011.INP])
Run this code with required months from DM package it gets executed for defined time periods.
Hope this helps,
Regards,
G.Vijaya Kumar

Distribution in script logic

Hello, all.
I'm new in BPC. Please give advice, how can we realize following logic.
We have a application Sales with following dimensions.
Account, Category, DataSrc, Entity, Department, Prodline, RptCurrency, Time
User send data to the DB in view:
Account | Category | DataSrc | Entity | Department | Prodline | RptCurrency| Time
NetSales | BUDGET | Input | Company_In | Sales | NoProd | LC | 2008.INP
Where each record NetSales, Budget, etc has no child
and user send data in view:
Account | Category | DataSrc | Entity | Department | Prodline | RptCurrency| Time
Coeficient | BUDGET | Input | Company | Sales | NoProd | LC | 2008.INP
Where Entity has 3 childs: Company_1, Company_2, Company_3.
After posting a data to Fact table, it view, is:
Account | Category | DataSrc | Entity | Department | Prodline | RptCurrency| Time | Signed_data
NetSales | BUDGET | Input | Company_In | Sales | NoProd | LC |2008.INP| -20
Coeficient| BUDGET | Input | Company_1 | Sales | NoProd | LC | 2008.INP| -0,1
Coeficient| BUDGET | Input | Company_2 | Sales | NoProd | LC | 2008.INP| -0,3
Coeficient| BUDGET | Input | Company_3 | Sales | NoProd | LC | 2008.INP| -0,6
I want to get new records in db such as:
Account | Category | DataSrc | Entity | Department | Prodline | RptCurrency| Time | Signed_data
NetSales | BUDGET | Input | Company_1 | Sales | NoProd | LC | 2008.INP| -2
NetSales | BUDGET | Input | Company_2 | Sales | NoProd | LC | 2008.INP| -6
NetSales | BUDGET | Input | Company_3 | Sales | NoProd | LC | 2008.INP| -12
Where NetSales distribute by coefficient for each Entity.
I want do something like (Account ="NetSales",Entity ="Company_1")= (Account="NetSales",Entity="Company_In")*(Account="Coeficient",Entity.Company_1) for each Company_n.
How can I write script logic for this.
Thanks

I think there are several options. The easiest option may be simply to construct a template that sends the values directly based on the input of the Coefficients and the Raw data value input of 20. Thus the input process would submit 7 total entries.
Now should you wish to have a repeatable calculation process that updates the Child entities each time either a coefficient or data input point is submit, then you could utilize script logic that was suggested in the thread as an allocation process. Otherwise, you would need to develop sets of properties and script logic for each set of requests such as:
*When Account.ID
*IS COEFFICIENT
*WHEN ENTITY.ID
*IS COMPANY_1
*REC(EXPRESSION = VALUE * GET(ACCOUNT=ACCOUNT.NETSALES,ENTITY=ENTITY.COMPANY_IN), ACCOUNT=ACCOUNT.NETSALES)
*ENDWHEN
*ENDWHEN
*COMMIT
This is not as flexible and there are many approaches that may be taken here, such as using LOOKUP statements and proeprties to manage the calculations and make them more flexible. It will just depend on how much volume there is to calculate, how many statements are required and how often the logic will need to be updated or managed based on hierarchy changes to the entity dimension. Plus, you need to test many options to determine which is the fastest approach during the send process.
Hope this helps.

Use BADI or LGF script logic? Which is good in performance

Hello,
I have a situation wherein a choice is to be made among the "BADI" or "script logic" having DESTINATION_APP which is along with WHEN clause.
Below is the code in which WHEN clause is used:
Code Starts****
XDIM_MEMBERSET CATEGORY=FC_CUR
*DESTINATION_APP=GROSSMARGIN
*SKIP_DIM =WEEK
*ADD_DIM PLAN_PARTNER = PP_NA, RPTCURRENCY = LC
*WHEN CATEGORY
    *IS "FC_CUR"
              *REC(EXPRESSION=%VALUE%)
*ENDWHEN
*****Code Ends****
The business requirement could be changing as we are at initial stage, wherein i may have to incorporate some data mapping logic which can also be handled through scripts instead of using BADI.
The major concern is if BADI would be most prefferable over script logic having WHEN clause to acheive the optimal performance considering large no. of records that needs to be written to the target APPLICATION
from the source application?
OR
The script with WHEN statement is fine if the data mapping is pretty simple and would not have much impact on performance compared to using of BADI even if the records to be moved is huge.

If data mapping is simple you can opt for script logic . If requirement is complex then you can go for BADI . You can check this [How-to|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70187b3e-d5ce-2d10-d780-bb8b1a5b0bdc?QuickLink=index&overridelayout=true] 6 th page on performance considerations of BADI .
A well designed BADI implementation is faster than script logic

Script Logic VS Data Transformation File

Hi all,
   I'm new to SAP BPC. I have knowledge of SAP BW.
   I can see conversion file, which we are referring in data transformation file. which we can use for mapping and conversion of external data into internal data.
How data transformation file different form script logic? Are we going to refer script logis in Data transformation file for each required dimension?
Can any of you give me clarity on how to place script logic and data transformation file in BPC data management flow.
I will really applicate all your help!!!
Thanks
Ben.

Nilanjan,
   I have a another quick question...
suppose my bpc application has 5 dimensions. Out of the 5 dimensions, 4 dimensions data i'm getting directly from SAP BW. assume 1 dim, i need to extract by doing look up at different table which also reside in BW.
   how to populate data for DIM 5.
   I got your point that data transformation file purely for field mapping. suppose DIM5 if i want to populate from script logic, wht do i need map in Transformation file. I hope you got my point.
   My question if how to populate a DIM in BPC using lookup approach.
Thanks,
Ben.

From where i can run script logic file.

Dear All,
I am new to BPC.
I have a code for currency translation in my Script logic (Default.lgf).
From where i should run this file. Can any help me.
thanks a lot in advance,
Regards,
Satish.

Typically the Currency rates are stored in the "RATE" application. This application is what the script logic or Business rule will call during the conversion process. The rates are only stored by MONTH and by TYPE in a typical planning application. If you need more granular rate details, then you may need to make you time dimension by weeks or days, or add more "TYPES" that are assigned to ACCOUNTs in th ecorressponding account dimension.
But in a simple planning world, most companies will use a monthly rate, one for an AVG and one for END account types, enter this into the RATE application, and run the Defualt logic on submission of data to compile the FX value. Whne you wish to view the results, make certain that you select the correct REPORTING CURRENCY in the report. Many time users forget that data is "normally" entered to an ENTITY,, the ENTITY defines the currency it assumes data is entered, so the plan is loaded to the "LC" member, and converted to USD; or entered in LC, and converted to RS.
But the RATE application will store all the rates required and you may need to open the INPUT template in that application to load the data at the correct intersections.
Hope this helps.

Math power function in script logic

Hello all!
Can anybody help me how I can do math "power" function in BPC 5.1 Script Logic?
Thanks

Let's say you have a source account FOO and you want to calculate FOO to the 5th power, posting the result to FOOFIVE.
In BPC SQL scripting, there are no mathematical functions to play with (powers, roots, sine, cosine, etc.) except for add, subtract, multiply and divide -- plus you can round results in your Factor or Expression. So that means, we must use multiplication.
You could certainly do this using a bunch of intermediate accounts, one each for foo squared, foo cubed, foo to the 4th, and foo to the 5th. That would require *GO in between each *WHEN/REC block, and could be slow.
I haven't tried this, but I think this should work, all in one statement:
*XDIM_ACCOUNT = FOO
*WHEN *
*IS *
REC(Factor=GET(Account="FOO")GET(Account="FOO")GET(Account="FOO")GET(Account="FOO")*GET(Account="FOO"),Account=FOOFIVE)
*ENDWHEN
If you want FOO to the 50th power, copy & paste.
If you want square root of FOO, that could be a real challenge. I think to use straight BPC SQL logic it wouldn't be possible. I would probably write a stored procedure using SQL's SQRT(), and call that from the BPC logic file. Likewise for any other geometric functions, complex algebra, etc.
There also may be a way to calculate powers in MDX -- that's more mathematically straightforward -- but as a BPC on MS person, I really never ever use MDX due to performance.
Regards,
Tim

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

Reg: Script Logic - REC Statement Variable usage

hi friends
Pl find enclosed the following code:
*WHEN TIME
*IS TMVL(-1,2011.04)
*WHEN ACCOUNT
*IS "EXP01"
*REC(EXPRESSION = [TIME].[2011.04]-%VALUE%,TIME = 2011.04,ACCOUNT = EXP01A)
*ENDWHEN
*ENDWHEN
The above code is working fine and result is extracted but i have hardcoded , ACCOUNT=EXP01A;
My Query is follows:
I have used
*WHEN ACCOUNT
*IS "EXP01"
In REC i want to use concatenation of "A" To account like EXP01&"A"
i know accunt & i want to concatenate "A" and use in REC statement like assign to variable
var1="EXP01" & "A" and use var1 in REC
*REC(EXPRESSION = [TIME].[2011.04]-%VALUE%,TIME = 2011.04,ACCOUNT = var1)
i am not sure the syntax (Whether we need to put in strings)
Also if EXP02 then var1="EXP02"&"A" and so on
In fact i want to make this for all members in Account Dimenstion as generalised.
Pl. verify and suggest best possibility
Thanx & Rgds
Srinath

Hi Krishna
*XDIM_MEMBERSET ACCOUNT AS %ACC% = EXP01
*WHEN ACCOUNT
*IS %ACC%
REC(EXPRESSION = %VALUE%2,TIME = 2011.04,ACCOUNT = %ACC%A)
*ENDWHEN
Is it required to add EXP01A as below?
XDIM_MEMBERSET ACCOUNT AS %ACC% = EXP01, EXP01A
Also In Generalized code you have mentioned:
Instead of Hard Coding EXP01, EXP02 can i have hierarchy of all EXP , so that if any new account added in dimension, there will be no change in script logic. Pl. can you share how to use the same.
If above code needs to be generalised, *FOR *NEXT can be used .
*XDIM_MEMBERSET ACCOUNT AS %ACC_LIST% = EXP01,EXP02,EXP03,EXP04
*FOR %ACC_MBR% = %ACC_LIST%
*WHEN ACCOUNT
*IS %ACC_MBR%
REC(EXPRESSION = %VALUE%2,TIME = 2011.04,ACCOUNT = %ACC_MBR%A)
*ENDWHEN
*NEXT
Rgds
Srinath

Probelm with Commit in Script logic.

Hi Experts,
I am using NW 7.5, SP 05.
I used commit statement in my script logic and executed it, It didn't given any result.
But, I removed the commit statement and executed it again. the code got executed and got the result.
Here is the code
*WHEN KF_DIM
*IS UNIT
*REC(EXPRESSION=%VALUE%*[KF_DIM].[BASEPRICE],KF_DIM=AVERAGEPRICE)
*ENDWHEN
//*COMMIT
Please some body tell me know why this is happening.
Thanks,
Regards
Maheedhar

Hi Maheedhar,
You dont require COMMIT statement as long as the scope remains same.
Is this the entire script? If not, can you please share the whole script?

ADDITION USING SCRIPT LOGIC

Hi All,
Under 'INCOME' i have 3 accounts.
account1
account2
account3
i want to add the value of these 3 account then i want to multiply with 3
the result i want to display in "account4"
What is the required script logic for this?
Regards,
Phanikumar.

Hi Phani Kumar,
BPC 7.0 NW doesnt support GET, so you cannot have the script as
*WHEN ACCOUNT
*IS "ACCOUNT1"
*REC(EXPRESSION=(%VALUE% + GET(ACCOUNT="ACCOUNT2") + GET(ACCOUNT="ACCOUNT3"),ACCOUNT="ACCOUNT4")
*ENDWHEN
Instead you can modify the script to
*WHEN ACCOUNT
*IS "ACCOUNT1","ACCOUNT2","ACCOUNT3"
*REC(FACTOR = 3, ACCOUNT="ACCOUNT4")
*ENDWHEN
If you want to go with MDX, then you can use as suggested earlier
[ACCOUNT].[#account4]=([ACCOUNT].[account1]+[ACCOUNT].[account2]+[ACCOUNT].[account3])*3
Hope this helps.

Can we run script logic at the time of preparing reports.

Helo Everybody!
I am new to SAP BPC.
Can we run script logic at the time of preparing reports.
Thanks & Regards,
Satish.

If you mean, "Can we run script logic at the time of preparing reports" is equivalent to entering data into the report and sending it to the database, then yes, you may run logic as Marcel indicates. Defualt logic is ALWAYS run for ANY and EVERY set of data that is sent via an input template from the field. You may also run logic when posting a jOURNAL entry as well. But be careful....if default logic attempts to perform to MANY or COMPLEX calculations, the time it takes to complete the process may not be in expectations with the users plans. There is a fine design balance required when planning to run logic at the time of input, as opposed to running in a package or at specific times during the day.
Hope this helps.

Clarification required in Script Logic

Similar Messages

Maybe you are looking for