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.

Similar Messages

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

How to use total elements in a script logic?

Hi All,
I am using BPC 7.0 MS. I need to create a calculation using script logic as follows:
The application name is GYP and it is composed by the following dimensions:
PL (Account type) in this dimension are the units
Time
Category
Entity
Product
RptCurrency
I would like to make a calculation like this:
UNITS of any product (base element) and any entity (base element) for the BUDGET category and LC currency divided by UNITS of TotalEntity.
Also, I would like to check before the calculation if UNITS have any value to proceed with that calculation.
Best Regards,
Luisana

Hi Robert,
Thank you for your reply.
Let me explain better what i would like to do. I have an application called GYP, it is composed for the following dimensions:
PL (Account type)
Time
Category
Entity
Product
RptCurrency
In the PL dimension i have an element called UNITS and another one called UNITSBYX. I would like to get a calculation like this:
For the BUDGET category and LC currency.
UNITSBYX = UNITS for each ENTITY / UNITS for ALL_ENTITIES
Let's say I have three entities:
Units for Entity1 = 50
Units for Entity2 = 100
Units for Entity3 = 300
Units for All_Entities = 450
The calculation should be like this:
UNITSBYX = Units for Entity1 / Units for All_Entities
UNITSBYX = 50 / 450
UNITSBYX = 0.11
UNITSBYX = Units for Entity2 / Units for All_Entities
UNITSBYX = 100 / 450
UNITSBYX = 0.22
I hope you get my point.
Kind regards,
Luisana

Script Logic - Calculated Members

Hello:
Im trying to build a script member using calculated members:
*WHEN CUENTA
*IS U4000
*ENDWHEN
*COMMIT
U4000 is a calculated member in the account dimension member. I tried using another account, that is not a calculated member and it works.
How can use calculated member in this sintax?
Thanks in advance.
Luciana

I would like to mention few things:
1. OLAPLOOKUP it doesn't work anymore into 7.5. James can you double check. My tests is showing that OLAPLOOKUP is not even validate into 7.5
2. Calc_Dummy_Org it is an option to get the values of calculate members
3. It is strange that kind of condition because into script logic you are doing input for base members.
So that condition to test when an account is a an account which is not base member for me doesn't seems to be right.
I can understand if you are looking about the value of that account but not testing if an account it is an account which is not base member.
So if you want to record something with value of your calculate member just use:
*BEGIN
ACCOUNT.#basememberforinput = ACCOUNT.Calculatemember
*END
*COMMIT
Edited by: Sorin Radulescu on Nov 9, 2010 4:04 PM

Calculating sum in script logic

Dear all.
I am having a script which should be moving values from one parent account to another base account in default logic, but only if posted on certain other dimension, that is when not posted on a certain Brand in my brand dimension.
Sounds pretty much simple..
*WHEN CATEGORY
*IS ACTUAL
*WHEN BRAND
*IS <> B_2600
*WHEN ACCOUNT
*IS BAS(GROSS_PREORDER)
*REC(EXPRESSION=([ACCOUNT].[GROSS_PREORDER]) ,ACCOUNT=GROSS_PREORDER_NOST)
*ENDWHEN
*ENDWHEN
*ENDWHEN
So if any values are posted on a base member of "GROSS PREORDER"-account, then put it onto GROSS_PREODRE_NOST, but only if CATEGORY = ACTUAL and BRAND different from B_2600.
The above script works fine, as long as I only post one record at a time, but that's not realistic. The users necessarily need to be able to input data on all base members of GROSS_PREORDER and then send data.
When you post eg. on three separate accounts below GROSS_PREORDER the result is posted three times onto GROSS_PREORDER_NOST.
I cannot seem to find a good solution for this, but I don't think I'm the first facing this issue..?
Best regards
Mogens
PS. I am using BPC NW 7.5 SP05

Hi Nilanjan.
That works.
I don't really see why it should work compared to my first script, but isn't that just the irony of script logic..?
In order to not put every and all data into my sum account I modified
*WHEN ACCOUNT
*IS *
to
*WHEN ACCOUNT
*IS BAS(GROSS_PREORDER)
Thank you very much for your help..
Br.
Mogens

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

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.

FOR loop in script logic

Dear Gurus,
This is the logic I am working with:
*FOR %MONTH% = 2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP
//CHECK IF THE VALUE OF THE ACCUMULATED DEPRECIATION IS GREATER THAN THE CAPITALIZED ASSET VALUE//
[ACCOUNT].[#AccumDepr] = (([ACCOUNT].[AccumDepr]+[ACCOUNT].[Depreciation])>[ACCOUNT].[EQUIPMENT1]? [ACCOUNT].[EQUIPMENT1] : ([ACCOUNT].[AccumDepr]+[ACCOUNT].[Depreciation]))
*NEXT
I am trying to execute the above script logic, but the system is throwing an error that says
"Duplicate formula found: [ACCOUNT].[#AccumDepr] = (([ACCOUNT].[AccumDepr]+......."
Any idea why this is happening?
Also, could you please suggest a better way of writing the above code?
Thanks,
Vijay.

As a testing scenario, I have calculated the depreciation in a different part of the same logic. Here it is:
//This logic calculates the accumulated depreciation amount for the time period specified in the logic
//NOTE: This logic is not very dynamic and is only valid for the accounts specified in the logic
//A FUTURE ENHANCEMENT TO THIS LOGIC WOULD BE TO MAKE THE "LIFE" OF THE ASSET A $DATAMANAGER VARIABLE$
//AND WRITE A CUSTOM SCRIPT LOGIC
//BEGIN SCRIPT LOGIC FILE//
//CONSTANTS
*XDIM_MEMBERSET CATEGORY=ACTUAL
*XDIM_MEMBERSET ACCOUNT=Depreciation,AccumDepr,NBV_EQUIPMENT1,EQUIPMENT1
*XDIM_MEMBERSET ENTITY=STORE1
*XDIM_MEMBERSET TIME=2008.JAN,2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP
//BEGIN: POPULATE NET BOOK VALUE FROM CAPITALIZED ASSET VALUE //
*WHEN ACCOUNT
*IS EQUIPMENT1
     *WHEN TIME
     *IS 2008.JAN
          *REC(FACTOR=1,ACCOUNT="NBV_EQUIPMENT1")
     *ENDWHEN
*ENDWHEN
*COMMIT
//END: POPULATE NET BOOK VALUE FROM CAPITALIZED ASSET VALUE   //
//BEGIN: CALCULATE DEPRECIATION //
*WHEN ACCOUNT
*IS EQUIPMENT1
     *REC(EXPRESSION=(%VALUE%/6),ACCOUNT="Depreciation")
*ENDWHEN
*COMMIT
//END: CALCULATE DEPRECIATION   //
//BEGIN: CALCULATE ACCUMULATED DEPRECIATION AND NET BOOK VALUE //
*FOR %MONTH% = 2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP
//CHECK IF THE VALUE OF THE ACCUMULATED DEPRECIATION IS GREATER THAN THE CAPITALIZED ASSET VALUE//
*WHEN CATEGORY
*IS ACTUAL
*REC(EXPRESSION=IIF((([ACCOUNT].[AccumDepr] + [ACCOUNT].[Depreciation])>[ACCOUNT].[EQUIPMENT1]), [ACCOUNT].[EQUIPMENT1], [ACCOUNT].[AccumDepr]+[ACCOUNT].[Depreciation]))
*ENDWHEN
*NEXT
//*FOR %MONTH% = 2008.FEB,2008.MAR,2008.APR,2008.MAY,2008.JUN,2008.JUL,2008.AUG,2008.SEP
//CHECK IF THE NET BOOK VALUE OF THE ASSET IS LESS THAN ZERO//
//*[ACCOUNT].[#NBV_EQUIPMENT1] = (([ACCOUNT].[NBV_EQUIPMENT1]-[ACCOUNT].[Depreciation])>0? ([ACCOUNT].[NBV_EQUIPMENT1]-[ACCOUNT].[Depreciation]) : 0)
//*NEXT
*COMMIT
//END: CALCULATE ACCUMULATED DEPRECIATION AND NET BOOK VALUE   //
//END SCRIPT LOGIC FILE//
Please let me know if there is a better way to write this code.
Thanks for all your help.

Lookup Script Logic

Dear Freinds,
I am trying to write script logic for learning LOOKUP fuction of script logic and written the below code in BPC 7.5 NW its not working. Please let me know my mistake .
*XDIM_MEMBERSET TIME =2009.APR
*XDIM_MEMBERSET P_ACCT=CE0004010
*XDIM_MEMBERSET CATEGORY=ACTUAL
*LOOKUP RATE
*DIM TIME="2009.APR"
*DIM CATEGORY="ACTUAL"
*DIM R_ACCT="AVG"
*DIM R_ENTITY="GLOBAL"
*DIM RATEEUR:INPUTCURRENCY="INR"
*DIM MEASURES="PERIODIC"
*ENDLOOKUP
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/LOOKUP(RATEEUR), RPTCURRENCY="INR")
*ENDWHEN

below is the UJTK log but I am not getting result. Please help me .
LOG:
FILE:\ROOT\WEBFOLDERS\BPC_Demo \ADMINAPP\MGT_CONSO\TEST.LGF
USER:PARAGONDNS\BPC_CON
APPSET:BPC_Demo
APPLICATION:MGT_CONSO
[INFO] GET_DIM_LIST(): I_APPL_ID="MGT_CONSO", #dimensions=8
CATEGORY,MEASURES,P_ACCT,P_ACTIVITY,P_CC,P_DATASRC,RPTCURRENCY,TIME
#dim_memberset=3
TIME:2009.APR,1 in total.
P_ACCT:CE0004010,1 in total.
CATEGORY:ACTUAL,1 in total.
REC :%VALUE%/LOOKUP(RATEEUR)
CALCULATION BEGIN:
QUERY PROCESSING DATA
QUERY TIME : 1535.45 ms. 2 RECORDS QUERIED OUT.
QUERY REFERENCE DATA
QUERY LOOKUP DATA FROM APPLICATION: RATE
QUERY TIME : 416.49 ms. 1 RECORDS QUERIED OUT.
CALCULATION TIME IN TOTAL :123.38 ms.
1 RECORDS ARE GENERATED.
CALCULATION END.
SCRIPT RUNNING TIME IN TOTAL:2.42 s.

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 - 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.

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.

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.

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

Calculations in Script Logic

Similar Messages

Maybe you are looking for