Opebal script logic issue

Hi All
The below logic is used to calculate opening and closing balances.
The logic works fine for 1st month.
ex: for acct TI if i capture 2 in my first month and run the logic its posts closing bal for 1st mnth as 2 which is right
and from feb to dec it posts opening bal as 2 which is right.(we run for whole year)
But for acct To if i capture 5 in 2nd month and run the logic its posting wrong opening bal for accout chc.
for feb my opening bal should be 2. it showing as 7.
please tell me where i am doing wrong.
i cann't use calc_dummy_org.
*SELECT(%Year%,"[YEAR]","Z_Version","[ID]='BUD'")
*SELECT(%Months%,"[ID]","Z_Time","[YEAR]=%Year% AND [LEVEL] = 'MONTH'")
*XDIM_MEMBERSET Z_TIME=%Months%
*XDIM_MEMBERSET Z_VERSION = BUD
*XDIM_MEMBERSET EB_DATASOURCE = MANUAL
*XDIM_MEMBERSET EB_ACCT = CHC,TI,TO,AP,RT
*XDIM_MEMBERSET Z_CC = DEF_CC
*XDIM_MEMBERSET Z_PCC = PCC_DEF_CC
       *WHEN EB_ACCT
           *IS CHC,TI,TO,AP,RT
              *FOR %MonthCopy% = %Months%
                  *REC(FACTOR=1,EB_ACCT="CHC",Z_TIME=TMVL(1,%MonthCopy%))
               *NEXT
        *ENDWHEN

Nilanjan,
Thanks for your prompt reply as always. Somehow I was able to get this thing working, please don't ask me how. It was just a piece of bigger logic code.
I have awarded you full points..
Thx,
Rockdy

Similar Messages

SAP BPC 5.1 Script Logic Issue

Hi Guys,
I have a problem with Inventory Days script logic at the moment. Basically what the logic should do is:
1. Copy the required data across to a calculation category (SQL)
2. Calculate the last 12 months Cost of Sales for every entity in the selection for 3 years (MDX)
3. Use the Cost of Sales number and multiply it with the inventory days number (SQL)
The calc works fine for some of my smaller brands (200 - 500 entities), but when i run the logic for my big brand (2000 entities) the last step doesn't calculate correctly. I have done the following to try and fix the problem.
1. Every step has it's own COMMIT
2. I clear the data before writing anything
3. I use XDIM_MAXMEMBERS Entity = 500
Any ideas why the logic is acting like this? I don't know if I am allowed to post my code here, but if it will help i will
Regards,
Andries van den Berg

Hi,
I only sent you the step that is giving me a problem at the moment. I broke the logic up into different packages to check where the problem lies and narrowed it down to this one.
It seems like the code didn't copy across correctly, it is supposed to be when EXTRAP.BRAND "<>" "". I'll just paste the code again, just so that we are all on the same page.
Regarding the FAC2, the client was running the code a lot of times and the WB table was getting huge. So, i started posting the records to the FAC2 table and processing it in the SSIS package. And i did confirm that they are posting there.
I just tried to run the script for half of the entities and it didn't work. I then tried to run is for 25 entities and it worked. Could the *XDIM_MaxMembers Entity = 50 be giving me the problem? This is all i get over and over in the formula log:
RPTCURRENCY,ACCOUNT,CATEGORY,DATASRC,ENTITY,INTCO,TIME,SIGNEDDATA
LC,80500,BUDGET,INPUT,P71559,NON_INTERCO,2010.AUG, 0
The other thing that bugs me is that i have similar script that never gives me issues for the same client.
Regards,
AvdB
//Step 4 -- Calculate the Inventory per month for all the entities selected
*SELECT(%BUDGET_YEAR1%,"[BUDGET_YEAR1]","CATEGORY","[ID]='BUDGET'")
*SELECT(%BUDGET_TIME_SET1%,"[ID]","TIME","[YEAR]=%BUDGET_YEAR1% AND [CALC] = 'N'")
*SELECT(%BUDGET_YEAR2%,"[BUDGET_YEAR2]","CATEGORY","[ID]='BUDGET'")
*SELECT(%BUDGET_TIME_SET2%,"[ID]","TIME","[YEAR]=%BUDGET_YEAR2% AND [CALC] = 'N'")
*SELECT(%BUDGET_YEAR3%,"[BUDGET_YEAR3]","CATEGORY","[ID]='BUDGET'")
*SELECT(%BUDGET_TIME_SET3%,"[ID]","TIME","[YEAR]=%BUDGET_YEAR3% AND [CALC] = 'N'")
*XDIM_Memberset Time = %BUDGET_TIME_SET1%,%BUDGET_TIME_SET2%,%BUDGET_TIME_SET3%
*XDIM_Memberset Category = TOPDOWN, BUDGET
*XDIM_Memberset Entity = %Entity_Set%
*XDIM_MaxMembers Entity = 50
*XDIM_ADDMemberset ENTITY = CLKS,MUS,BS // Add global entities
*XDIM_Memberset ACCOUNT = Last12FSCoS,Last12DispCoS, InventoryFSDays, InventoryDispDays //Add the caculated CoS account from the previous step and the Global Driver for days
*WHEN ENTITY.EXTRAP_BRAND
*IS <> ""
*WHEN CATEGORY
*IS TOPDOWN
*REC(EXPRESSION=(GET(ACCOUNT="Last12FSCoS",CATEGORY="TOPDOWN")*GET(ACCOUNT="InventoryFSDays",ENTITY=ENTITY.EXTRAP_BRAND,CATEGORY="BUDGET")/365)*-1,NOADD,ACCOUNT="80500",CATEGORY="BUDGET")
*REC(EXPRESSION=(GET(ACCOUNT="Last12DispCoS",CATEGORY="TOPDOWN")*GET(ACCOUNT="InventoryDispDays",ENTITY=ENTITY.EXTRAP_BRAND,CATEGORY="BUDGET")/365)*-1,NOADD,ACCOUNT="80510",CATEGORY="BUDGET")
*ENDWHEN
*ENDWHEN
*WRITE_TO_FAC2
*COMMIT

SP 12 upgrade and script logic issue

Hi All,
We upgraded to BPC 10 SP 09 to SP 12. The system was stable for some days but after 15 days it seems like script logic has got corrupted.
Please find the images below, Any ideas what is the problem

Hello,
Please clarify what you mean by copy, did you copy the script (text) from one open client session to another or did you use back up and restore to copy the environment or any other method.
I recommend checking if this is a client or server side problem. You can verify this either by opening the logic on a different client machine or by checking the logic directly on the server using UJFS.
If this has occurred on the server level I recommend just rewriting the content, through BPC web client, validate and save again and check if that fixes the problem or if the problem occurs again.
Best Regards,
Leila Lappin

Having issue using TMVL in script logic

Hello experts,
We need to replicate the behaviour of the copy opening Bal through script logic.
Below is my code:
where user selects only entity when he runs package,time is derived from property.
// Year from version property
*SELECT(%YEAR%,"[YEAR]","Z_VERSION","[ID]='BUD'")
// Months
*SELECT(%MONTHS%,"[ID]","Z_TIME","[YEAR]=%YEAR% AND LEVEL='MONTH'")
*XDIM_MEMBERSET Z_TIME=%MONTHS%   (for ex:My first month is 2009.jan(ope month)
   *WHEN ACCT
           *IS CHC
        *REC(FACTOR=1, ACCT="CHC",Z_TIME=TMVL(1,%MONTHS%)) ( for ex:2009.feb,nxt month)
    *ENDWHEN
When i run the above logic in debugger TMVL doesn't show next month.
If i hardcode time in my xdimmemberset to (*XDIM_MEMBERSET Z_TIME=2009.JAN) and change my TMVL in my REC statement to TMVL(1,2009.JAN)).Logic works fine.
Please tell me how can we pass dynamic variables to TMVL.
*REC(FACTOR=1, ACCT="CHC",Z_TIME=TMVL(1,%MONTHS%))
Thanks

copying closing bal of prev month to nxt month.
for ex:
Account     jan 2009    Feb 2009    Mar 2009
HC_PLAN     10.00      11.00      21.00
CHC          10.00      11.00        11
TI                     1.00                      1.00
TO                      2.00      1.00          2.00
AP                      3.00                       3.00
RT                       4.00                        4.00
My logic needs to copy values from HC_PLAN (parent) to CHC. I have written ope_bal logic in MS version.
In NW i cannot use next (i am using TMVL),calc_dummy_org,calc_each_period.
Please tell me how can i get values from a parent (HC_PLAN).
Is Calculate_Difference is supported in BPC7.5NW?
Below is my updated code
*SELECT(%Year%,"[YEAR]","Z_Version","[ID]='ACTUAL'")
*SELECT(%Months%,"[ID]","Z_Time","[YEAR]=%Year% AND [LEVEL] = 'MONTH'")
*XDIM_MEMBERSET Z_TIME=%Months%
*XDIM_MEMBERSET EB_ACCT = CHC,TI,TO,AP,RT
*WHEN EB_ACCT
           *IS CHC,TI,TO,AP,RT
                  *FOR %MonthCopy% = %Months%
                       *REC(FACTOR=1,EB_ACCT="CHC",Z_TIME=TMVL(1,%MonthCopy%))
                    *NEXT
             *ENDWHEN

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

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

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.

How to copy applications using script logic with conditions

Hi,
I have two copy data between application A to application B, but only i want to copy the March's Data of Application A. Dimensions are the same in both applications
I'm going to use this script logic, ¿this script will work?
*WHEN TIME
*IS "2009.MAR"
*DESTINATION_APP=B
Thanks in advance
Regards,
Juan

Hi all,
Finally I solved the issue, the problem was that i haven't add this line in the script logic:
TASK(Execute formulas,USER,%USER%)
But now i need to pass in the script logic as an input: entity and time. Below is the code I prepare, it has no error but it doesn't work. ¿any idea?
Thanks in advance
Regards,
Juan
*SSIS PACKAGE *
'DEBUG(ON)
PROMPT(RADIOBUTTON,%CHECKLCK%,"Select whether to check work status settings when running logic.",1,{"Yes, check for work status settings before running logic","No, do not check work status settings"},{"1","0"})
PROMPT(SELECTINPUT,,,"Please select entity and time to copy data from LegalAppNceu to LegalApp",%ENTITY_DIM%%TIME_DIM%)
TASK(Execute formulas,USER,%USER%)
TASK(Execute formulas,APPSET,%APPSET%)
TASK(Execute formulas,APP,%APP%)
TASK(Execute formulas,LOGICFILE,%APPPATH%..AdminApp%APP%CopyApplication.lgx)TASKTASK(Execute formulas,RUNMODE,1)
TASK(Execute formulas,LOGICMODE,1)
TASK(Execute formulas,CHECKLCK,%CHEKCLCK%)
SCRIPTLOGIC
*DESTINATION_APP=LEGALAPP
*SKIP_DIM= COSTCENTER
*WHEN ENTITY
*IS "%ENTITY_DIM%"
*WHEN TIME_DIM
*IS "%TIME_DIM%"
*REC(FACTOR=1)
*ENDWHEN
*ENDWHEN
*COMMIT

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

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

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.

Script Logic: How to test the sign of data

Hi Forum,
I'm looking for a function to test if the amount of an account is positive or negative.
This test is necessary to choose the target account where transfer the amount.
In MS version there is the TEST_WHEN function, but doesn't work in NW (not implemented).
I'm trying to use an algorithm but I don't know the sintax in BPC of Square Root.
I'm working with BPC NW S04.
Have someone suggestion about it.
Thanks a lot in advance.
Gianluca Orlandi

Hey Gianluca,
Looks like this is a known issue and is not supported in NW....
check this thread...
Script Logic: chek the sing of the amount of an account
Hope this helps...

Display entire log in script logic?

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

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

Fetching property value in script logic!!

Hello Experts,
We are using BPC 7.5 M, I am working on a script logic and need to fetch a value of a property of a dimension member where dimension member is itself defined in some property.
We have a Org dimension which has a property "FORECAST_UNIT" and this property contains a member Id of Org dimension itself, In my script logic I need to fetch value of "Currency" property for the Org dimension member defined in "FORECAST_UNIT" property.
Please Advice.
Thanks & Regards,
Rohit

Hi Roberto,
Attached code (In Image) is of our Aggregate Forecast Unit logic, Every Org (Entity) has an forecasting unit defined in Forecasting unit property in Org dimension and Forecasting unit is also a member of Org dimension, below logic aggregates the data at Forecasting unit level:
The issue is that I need to check before the code marked in Red executes that if Org-- Forecasting unit -- Currency is USD then only Red part of logic should execute.
Thanks & Regards,
Rohit

Script Logic choice SQL or MDX in NW release?

Hi experts,
I have encountered some opposite arguments in forum. Please can you clarify NW release script logic choice should be as MS release?
In [Script Logic BPC MS (SQL) vs. NW (ABAP); Tim Klem states
- "Write the logic using BPC SQL script logic syntax (not MDX) for performance reasons" but this opinion based on MS version. How about NW release is it really smarter to select SQL Script rather than MDX.
There is another statement in [Re: BPC 7 NW; Deppak mentions that:
- "In BPC 5.1 the script formula approach suggests to use SQL based logic instead of MDX.
Whereas in Teched,08, I learnt that MDX & ABAP (using BADIs) would be used for it. Thats why I am slightly confused...."
But second statement is far beyond NW relase date and I am sure this is not true but I would like you to confirm that.
If you were a project responsible and want that all scripts will be held in one language, what would you choose??
Thanks in advance,
ergin ozturk

Hi Ergin,
I can understand your approach not to use ABAP hence you miss the skills witin your project team.
However, you (or you client) has chosen the NetWeaver version for whatever reason. I'm sure a thorough decisions process has lead to this decision. In choosing the NetWeaver version with SAP BI you will sooner or later come to the point that you will have to use ABAP if you like it or not. Especially when you start using further capabilities within NetWeaver and the BI solutions. So from my point of view ABAP knowledge is an essential skill you need in a project based on SAP NetWeaver anyway.
Additionally I heared some statements that MDX is causing some performance issues on the NetWeaver version. This may have been fixed in the meantime with some SPs.
As the SQL within the NetWeaver verison does not have the full functionality than it has in MS Version SQL is not an option for me.
I do also not see the cost impact hence someone need to do the support anyway. In case of MDX you need an MDX developer, in case of ABAP and ABAP developer. Or a technical BPC consultant able to do the development (which I would recommend you should have in your project team anyway).
So coming back to your original question, I would recommend to do as much as possible using ABAP BADIs.
Cheers,
Steffen

Opebal script logic issue

Similar Messages

Maybe you are looking for