Script logic: Current ID in lookup

Hello,
I have made a lookup that is called inside a when/endwhen structure. I would like to pas to the lookup first parameter the value of the current id of the dimension GROUPS, but I don't know how to do it. I have tried with GROUPS, %GROUPS%, %GROUPS%.ID and FLD(GROUPS.ID) but nothing worked.
I paste the code to make this more comprehensible:
*XDIM_MEMBERSET GROUPS=%BASMBRS%
*SELECT(%DIVISAS_A_CONVERTIR%,"ID","GROUPS","ID<>'EUR' AND ID<>'EUR_T' AND ID<>'LC' ")
*LOOKUP RATE
   *DIM TipoEntidad="Global"
   *DIM Escenario="REAL"
   *DIM Periodo="%Periodo_SET%"
   *DIM TipoCambio="END"
   *FOR %DIV%=%DIVISAS_A_CONVERTIR%
      *DIM %DIV%: DivisaInput="%DIV%"
   *NEXT
*ENDLOOKUP
*WHEN GROUPS
*IS *
   // In the *????* I would like to introduce the id of the dimensino GROUPS of the current region -- NOT %Groups_SET%
   *REC(FACTOR=-LOOKUP( *????* ),GROUPS=EUR)
*ENDWHEN
Thanks!

Hi,
Look up cannot be used with in when condition.i did't get your requirement???can you explain with your real example.
You can look in to the NOTE:1283600.give discription of lookup in when condition.
Regards,
Naresh.K
Edited by: Naresh Kumar Reddy Kondakindi on Oct 16, 2009 12:32 AM

Similar Messages

Validate my script logic: reference erro LOOKUP is not defined

Dear all,
i want write one script logic. It use LOOKUP using FOR/NEXT.
But when i check stament in my script logic: messesage erro: reference erro LOOKUP is not defined.Can you help me?
My script logic
*XDIM_MEMBERSET ACCOUNT=BS221
*XDIM_ADDMEMBERSET CATEGORY = Actual
*XDIM_ADDMEMBERSET ENTITY = CSO
*SELECT(%TIME%,"[ID]",TIME,"[ID]>=2006.01 AND [ID]<=2006.02")
*XDIM_MEMBERSET TIME = %TIME%
*LOOKUP Rates
*DIM CATEGORY ="Actual"
*DIM R_ACCOUNT ="AVG"
*DIM R_ENTITY ="Global"
*DIM INPUTCURRENCY="USD"
*DIM MEASURES ="PERIODIC"
*FOR %T% = %TIME%
*DIM RATE_%T%: TIME =%T%
*NEXT
*ENDLOOKUP
*WHEN ACCOUNT
*IS "BS221"
*FOR %T1% = %TIME%
*REC(EXPRESSION=LOOKUP(RATE_%T1%),TIME=%T%)
*NEXT
*ENDWHEN
*COMMIT
Thanks,
Hungth

Dear Vadim,
I want test LOOKUP statement using FOR/NEX, then get value per member for member in LOOKUP.
in excel add-in of Rates Model:
Actual - Actual
Average Rate
Global Entity
2006.01 - Jan 2006
31
2006.02 - Feb 2006
30
2006.03 - Mar 2006
30
2006.Q1 - Q1 2006
30
I want run my script logic above to get value from Rates Model ( 2006.01: 31, 2006.02 : 30, 2006.03: 30 ) to current model , to calculate in crurrent model.
BS221 - Long Term Debt
2006.01 - Jan 2006
2006.02 - Feb 2006
2006.03 - Mar 2006
Actual - Actual
31
30
30
How i can write my script logic? My script logic statements is correct??
Thanks,
hungth

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.

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.

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

Script logic problem BPC 7.5

Hi!
We have a script logic that worked fine in BPC 5.1 but after our upgrade to BPC 7.5 it doesn´t work anymore.
I will try to explain the part of or logic that doesn´t work anymore.
We have 2 lines that will pass through the script, each line creates a temporary value on KATEGORI ="#avskr1").
Depending on the value created on u201C#avskr1" it should do calculation A if the value is negative and calculation B if the value is positive. To do this we the following script logic:
*WHEN GET(KATEGORI="#avskr1")
       *IS < 0
*Calculation A
ELS
*Calculation B
And this logic worked fine in BPC 5.1.
If line X had -50 as a value in u201C#avskr1"   and line Y had 75 as a value in u201C#avskr1" , calculation A would be performed on line X and calculation B on line Y
With the same example as above in BPC 7.5 calculation A will be performed on both lines.
But if I change the logic to the following script logic in BPC 7.5:
*WHEN GET(KATEGORI="#avskr1")
       *IS = -50
*Calculation A
ELS
*Calculation B
Calculation A would be performed on line X and calculation B on line Y. It seems like the logic can´t handle <> signs in this script logic anymore.
Regards
Fredrik

Hi!
Unfortunately it didn´t help still the same error.
And I just got an answer from SAP Support that there are a bug in the use of "Get whith When or lookup" in 7.5 SP03 which we currently are using, but it has been fixed in SP04. They just put up a SAP not 1515973 about the issue.
Unfortunately they have no work around for this problem so I don´t know how to solve it untill we have installed SP04.
Regards
Fredrik

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

An error in Script Logic

Hi Experts,
I have a problem with one of the FXTranslation logicu2019s in one of my report can u please help me on that.
The logic works fine for 2 reports out of 3, for the 3rd report I donu2019t know why itu2019s not doing the translation to USD. As far as the design of the report goes the 2 reports for which translation works fine comprises of 2 logics one for percentage allocation and other for translation from LC to USD, whereas the 3rd report needs only translation but doesnu2019t need the allocation logic to be run.
The conversion for the 3rd report happens if I comment out the allocation logic. Both these logics are mapped to Default.LGF file. I am unable to figure out what could be the error.
Below is the Script Logic for Aloocation and Translation:
//Budget Allocation
*SELECT(%CURR%,"[ID]","RPTCURRENCY","[CURRENCY_TYPE]='L' OR [CURRENCY_TYPE]='R'")
*XDIM_MEMBERSET RPTCURRENCY=%CURR%
*RUNALLOCATION
*FACTOR=USING/1
*DIM ACCOUNTB WHAT=[IS_ALLOC]='Y'; WHERE=<<<; USING=ALLOCPER
*DIM PRODUCTM WHAT=NOPRODUCT; WHERE<>NOPRODUCT; USING=<<<
*ENDALLOCATION
*COMMIT
// Currency Translation
*SELECT(%REPORTING_CURRENCIES%, "[ID]", "RPTCURRENCY", "[REPORTING] = 'Y'")
*SELECT(%FX_RATES%, "[ID]", "RATE", "[GROUP] = 'FX RATE'")
// Load the rates from the RATE cube
*LOOKUP RATE
            *DIM CATEGORY="BUDGET"
     *DIM RATEENTITY="GLOBAL"
     *DIM RATE=ACCOUNTB.RATETYPE
     *DIM SOURCECURR:INPUTCURRENCY=LEGALENTITY.CURRENCY
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *DIM %CURR%:INPUTCURRENCY="%CURR%"
     *NEXT
*ENDLOOKUP
// define the translation rule
*WHEN ACCOUNTB.RATETYPE
*IS "NOTRANS"
     // skip
*IS %FX_RATES%
           // translate
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *REC(FACTOR=LOOKUP(%CURR%)/LOOKUP(SOURCECURR),RPTCURRENCY="%CURR%")
     *NEXT
*IS "COPYLC"
     // take as is
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *REC(RPTCURRENCY="%CURR%")
     *NEXT
*ENDWHEN
*COMMIT
// Default
// FX Translation
*include FXTranslation.lgf
// Budget Allocation
*include BudgetAllocation.lgf

Hi Naresh,
One thing that helped me solve the problem was I needed to use different set of Dimension members/property in the Logic i.e What, Where and Using to trigger off the Curency Translation.
But please make sure that you use try to understand a unique dimension (member/property) used and use that to trigger off the translation or anything for that matter. My other two translations were working fine as the parameters i used were unique for them whereas the remaining one needed alteration in the logic only in the parameters used in What, Where and Using, so had to add one more set of Translation Logic for this exclusively.
Another point you need to check in your Rate Application is whether you have your Reporting Currency as value 1, say for eg USD is your reporting currency then the value in Rate Application for USD must be 1, if u by mistake cleared of this value when using the Clear Data Manager Package so the multiplication with 0 results in no conversion.
These were the two points that helped me solve my issue. I hope it helps.
Rgds,
Rizwan
Edited by: Rizwan Mustaffa on Jul 13, 2009 12:09 PM

Substring in script logic

Hi,
We have a customer dimension, where we can extract a lot of information. However the information depends on the sales organization.
Since the client currently have 30 sales organization and we can deduct information like: billing currency, sold-to-country and profitcenter from the combination of sales organization and customer this means I have to create 90 properties to hold this information (30 salesorg * 3 informations pr salesorg).
Therefore I would like to concatenate the information in 1 property per sales organization. This however means I have to be able to make a substring on the property, e.g. in a select statement to retreive the relevant information (it is not possible to do it in the report, since the properties hold information I need to save the data).
Does anyone know if this is possible?
Thanks,
Lars

Hi Lars -
Sorry, string manipulation commands are not available in script Logic. You will need to call a BAdI from script logic and use the rich string manipulation tools available in ABAP.
Regards,
Sheldon

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.

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

Script logic from BPC 5 in BPC 7.5

Hi,
I am trying to use some script logic from an appset in BPC 5 in BPC 7.5. When I validate the logic in 5 it works fine but in 7.5 I get validation errors.
They relate to properties of dimension elements that are not currently used (neither in 5 nor in 7.5) but could well be used in the future. As an example, this bit generates an error
*WHEN ACCOUNTL.RATETYPE
*IS END,ENDFLOW
I currently do not have an account defined with ratetype END but it is quite possible that there will be one in the future. And END is defined as an element in the RATE dimension.
So, why did BPC 5 accept this and BPC 7.5 does not? And, is there a way around other than defining a dummy element in ACCOUNTL that used ratetype END?
Thanks
Edited by: ArnoldWarhonowicz on Aug 5, 2010 4:06 PM

What I havenoticed is that with the new7.5 Script logic, there are more checks and balances performed during the validation. So, if you have only AVG, ENDRATE on RATETYPE property and no END for any member, yet your logic is calling a set of members with this parameter, the logic fails to validate. I assume the process is checking for a set of END members based on the request. Since they don't exist, the error occurs. But I would request that BPC Support verify the behavior as well.
If you remove END, does the logic validate?
Hope this helps.

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.

Script logic: Current ID in lookup

Similar Messages

Maybe you are looking for