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

Similar Messages

Script Logic wrong results in migration to BPC 7.5M

Hi Experts,
We have an issue with Script Logic calculation after migration of BPC 7.0M to BPC 7.5M. At the beginning we thought that was the issue mentioned in SAP note 1515973, because we had SP03.
Now we have SP07 and the problems persist. The result of a simply product between two numbers is wrong. For example in the next Default Script Logic:
*WHEN TIME.GROUP
   *IS INPUT
*WHEN CATEGORY
     *IS <> "ACTUAL","B_ACTUAL"
          *WHEN ACCOUNTP
                *IS "M_SALES"
                    *REC(FACTOR=GET(ACCOUNTP="PRCT_SALES_BASIC"),ACCOUNTP="700200")
                    *REC(FACTOR=GET(ACCOUNTP="PRCT_SALES_PROMO"),ACCOUNTP="700230")
                    *REC(FACTOR=GET(ACCOUNTP="PRCT_SALES_LIMITED"),ACCOUNTP="700235")
          *ENDWHEN
*ENDWHEN
*ENDWHEN
*COMMIT
Input:      M_SALES =           -195,75933
Input:      PRCT_SALES_BASIC =      1
Result: 700200 =           -195
Are there some application parameter that defins de presicion of logic calculations?
Some ideas? Thanks in advance.
Best Regards
Albert

Hi Jörg,
We changed to a new server with a multi-server architecture 64 bit (BPC Server and DB Server).
Did you have the same problem? How do you resolve it?
Thanks in advance.
Best regards,
Albert

BPC Logic Script: Copy from calculated members (non-base) to base members

Hi experts,
I want to copy some values from some calculated members to base members in the same dimension. It appears I have a hard time scoping the calculated members.
This is my C_ACCOUNT dimension:
And this is the COPYCALC.LGF script I am running:
LGX:
*XDIM_MEMBERSET C_ACCOUNT = 450
*WHEN C_ACCOUNT
*IS 450
*REC( EXPRESSION = %VALUE%, C_ACCOUNT = 50)
*ENDWHEN
LOG:
LOG BEGIN TIME:2014-02-26 17:21:12
FILE:\ROOT\WEBFOLDERS\STEP_UNIT_TEST \ADMINAPP\BUDGET_CASH\TEST.LGF
USER:KAROLISB
APPSET:STEP_UNIT_TEST
APPLICATION:BUDGET_CASH
[INFO] GET_DIM_LIST(): I_APPL_ID="BUDGET_CASH", #dimensions=16
AA_NUMBER,AUDITTRAIL,BUDGET_OBJECT,BUDGET_TYPE,CATEGORY,COFOG,CURRENCY,C_ACCOUNT,C_ACCOUNT_DT,ENTITY,FLOW,GRANTS,MEASURES,TIME,TIME_DT,VERSION
#dim_memberset=4
CATEGORY:RES,1 in total.
CURRENCY:LC,1 in total.
TIME:2012,1 in total.
C_ACCOUNT:450,1 in total.
SCRIPT RUNNING TIME IN TOTAL:1.00 s.
LOG END TIME:2014-02-26 17:21:12
My model structure:
So as you can see I am trying to copy from account 450 (which is non base) to account 50 ( which is base member). Also you can see that in the previous example no record was generated.
Whereas, if I replace the account 450 with 4500 I get record generated in order:
LGX:
*XDIM_MEMBERSET C_ACCOUNT = 4500
*WHEN C_ACCOUNT
*IS 4500
*REC( EXPRESSION = %VALUE%, C_ACCOUNT = 50)
*ENDWHEN
LOG:
LOG BEGIN TIME:2014-02-26 18:26:26
FILE:\ROOT\WEBFOLDERS\STEP_UNIT_TEST \ADMINAPP\BUDGET_CASH\TEST.LGF
USER:KAROLISB
APPSET:STEP_UNIT_TEST
APPLICATION:BUDGET_CASH
[INFO] GET_DIM_LIST(): I_APPL_ID="BUDGET_CASH", #dimensions=16
AA_NUMBER,AUDITTRAIL,BUDGET_OBJECT,BUDGET_TYPE,CATEGORY,COFOG,CURRENCY,C_ACCOUNT,C_ACCOUNT_DT,ENTITY,FLOW,GRANTS,MEASURES,TIME,TIME_DT,VERSION
#dim_memberset=4
CATEGORY:RES,1 in total.
CURRENCY:LC,1 in total.
TIME:2012,1 in total.
C_ACCOUNT:4500,1 in total.
REC :%VALUE%
CALCULATION BEGIN:
QUERY PROCESSING DATA
QUERY TIME : 0.00 ms. 1 RECORDS QUERIED OUT.
QUERY REFERENCE DATA
CALCULATION TIME IN TOTAL :0.00 ms.
1 RECORDS ARE GENERATED.
CALCULATION END.
ENDWHEN ACCUMULATION: 1 RECORDS ARE GENERATED.
DATA TO WRITE BACK:
AA_NUMBER AUDITTRAIL BUDGET_OBJECT BUDGET_TYPE CATEGORY COFOG CURRENCY C_ACCOUNT C_ACCOUNT_DT ENTITY FLOW GRANTS TIME TIME_DT VERSION SIGNEDDATA
AA_NONE LIM NONE 10 RES FA_NONE LC 50 CAD_NONE A00 F99_1 NONE 2012 TD_NONE CURRENT 222.00
1 RECORDS HAVE BEEN WRITTEN BACK.
WRITING TIME :1.00 ms
Why can I not copy value from 450 ? How do I solve this problem ?
PS: currently I am testing this as a DM package run script but in the future I would like to make it a Default.lgf functionality.
I am working on:
BPC 10 SP5 for NW, calculation engine ABAP, BW 7.4

Sorry to keep you in darkness. My code has developed since I have started this thread:
*SELECT(%ADMISSIBLE%, "[ID]", C_ACCOUNT, " [THIERARCHY]<>'' AND [ACCTYPE]<>INC ")         // DEFINE THE SET OF REAL(ACTUALY EXISTING), NON-REVENUE AND NOT ANCIENT CASH ACCOUNTS HERE.
*SELECT(%INADMISSIBLE%, "[ID]", C_ACCOUNT, " [ID] <> %ADMISSIBLE% ")
*SELECT(%L1%, [ID], C_ACCOUNT, "[ID] = %C_ACCOUNT_SET%")       // DEFINE BASE LEVEL ACCOUNTS
*SELECT(%L2%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L1% ")       // DEFINE FIRST(COUNTING FROM BASE) LEVEL PARENTS
*SELECT(%L3%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L2% ")       // DEFINE SECOND(COUNTING FROM BASE) LEVEL PARENTS
*SELECT(%L4%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L3% ")
*SELECT(%L5%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L4% ")
*SELECT(%L6%, "[THIERARCHY]",C_ACCOUNT, "[ID] = %L5% ")
*SELECT(%LALL%, "[ID]", C_ACCOUNT, "[ID] = %L1%,%L2%,%L3%,%L4%,%L5%,%L6%") //UNION OF ALL LEVELS
*XDIM_MEMBERSET AUDITTRAIL = INPUT
*XDIM_MEMBERSET VERSION = CURRENT
*XDIM_MEMBERSET AA_NUMBER = AA_NONE
*XDIM_MEMBERSET TIME_DT = TD_NONE
*XDIM_MEMBERSET C_ACCOUNT_DT = CAD_NONE
*XDIM_MEMBERSET C_ACCOUNT = %INADMISSIBLE%     //SCOPE LEAVES ALL POTENTIAL DESTINATIONS FOR MEMBERS IN %PARS%
*FOR %A% = %PARS%    //LOOP OVER ALL ADMISSIBLE PARENTS
*WHEN C_ACCOUNT
*IS L_C_%A%
*REC( EXPRESSION = [C_ACCOUNT].[%A%], C_ACCOUNT = L_C_%A%)         //SUM UP THE VALUES OF LEAVES AND WRITE THE SUM TO DESTINATION ACCOUNT
*ENDWHEN
*NEXT
screen shot of part of member table for C_ACCOUNT:
continuation in next reply (I have problems with my text editor)

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

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.

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

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

Use of prompted hierarchy's base members in Script Logic

Hello all,
I have a data manager package which prompts the user for a dimension called P_BUDGET_MODEL. The prompt is SELECT hence the user selects a hierarchy node on this dimension.
In the relevant Script Logic I have a variable %P_BUDGET_MODEL_SET%, which is automatically created by the system. I would like to run the logic for the basemembers of the hierarchy node.
Please note - the basemembers are not direct children of the selected hierarchy node (i.e. the selected node is the "grandparent" of the basemembers).
I tried the following simple logic command:
*XDIM_MEMBERSET P_BUDGET_MODEL = BAS(%P_BUDGET_MODEL_SET%)
It yielded a message that "Member BAS() does not exist".
I have also noticed the following thread:
[BPC 7.5 NW - HIER NODE in PROMPT using Formule in Package ?;
If I understood properly it is not relevant to my case because the hierarchy is more that 2 levels deep.
Any ideas?
TIA
Avihay

Hi,
As it seems after further investigation the problem is that I use "_" in the dimension names and variable names. This creates a problem to BPC in some cases.
For example here there is no problem:
*SELECT(%MODEL%,ID,P_BUDGET_MODEL,ID="%P_BUDGET_MODEL_SET%")
Here there is a problem hence the use of [ ]
*XDIM_MEMBERSET P_MONTH = BAS([%P_VERSION_SET%.YEAR].TOTAL)
Here there is not "_" so the code is fine:
*XDIM_MEMBERSET P_BUDGET_MODEL = BAS(%MODEL%)
Strange yet seems that this was the problem...
Avihay

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.

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.

Problems when using RUNLOGIC Keyword in Script Logic

Hello experts,
I have a problem using RUNLOGIC keyword within Script logic. Both scripts are mentioned below.
Following scenario:
- combination of DESTINATION_APP and LOOKUP to multiply values from two source applications in order to to write results in target application
- data volume in source application VALCHAIN are approx 187.000 records; source app SALES = 500 records
- created data records in target application QUANTITIES are approx 204.000 records
Running LOGIC01_QUANTITIES.LGF without "RUNLOGIC" keyword:
- time to execute logic and write records: 10-12 minutes
- created records 204.000
Running LOGIC01_QUANTITIES.LGF via CALL_RUNLOGIC.LGF
- script does not finish; system produces dumps
- Tcode ST22 shows error messages called "TSV_TNEW_PAGE_ALLOC_FAILED" as well as "SYSTEM_NO_ROLL" as well as "CALL_FUNCTION_SEND_ERROR"
Does anybody have a guess for that? Any answer appreciated.
Thanks a lot!
==================================================
CALL_RUNLOGIC.LGF
*START_BADI RUNLOGIC
QUERY=OFF
WRITE=ON
LOGIC=LOGIC01_QUANTITIES.LGF
APPSET=FINPLAN_PERFORM
APP=VALCHAIN
CHANGED=PRODUCT
DEBUG=OFF
*END_BADI
===========================================
LOGIC01_QUANTITIES.LGF
*XDIM_MEMBERSET DATASRC=ITEMIZED
*XDIM_MEMBERSET VERSION=%VERSION_SET%
*XDIM_MEMBERSET TIME=%TIME_SET%
*LOOKUP SALES
*DIM DATASRC="OUTPUT"
*DIM ITEM="IM_M02"
*DIM QUANTU="QU_TO"
*DIM MEASURES="PERIODIC"
*FOR %LOOP_CENTER%=PC_1000,PC_2000,PC_3000,PC_4000,PC_5000,PC_6000
*DIM C_%LOOP_CENTER%:PCENTER=%LOOP_CENTER%
*NEXT
*ENDLOOKUP
*DESTINATION_APP=QUANTITIES
*ADD_DIM COSELE=CE_NONE
*WHEN PRODUCT.LG
*IS "1"
*WHEN MATERIAL
*IS "MA_NONE"
    *FOR %LOOP_CENTER%=PC_1000,PC_2000,PC_3000,PC_4000,PC_5000,PC_6000
    REC(EXPRESSION=%VALUE%LOOKUP(C_%LOOP_CENTER%), PCENTER=%LOOP_CENTER%, ITEM="IM_M08", DATASRC="CALCULATED")
    *NEXT
*ELSE
    *FOR %LOOP_CENTER%=PC_1000,PC_2000,PC_3000,PC_4000,PC_5000,PC_6000
    REC(EXPRESSION=%VALUE%LOOKUP(C_%LOOP_CENTER%), PCENTER=%LOOP_CENTER%, ITEM="IM_M05", DATASRC="CALCULATED")
    *NEXT
*ENDWHEN
*IS "1000"
*WHEN MATERIAL
*IS "MA_NONE"
    *FOR %LOOP_CENTER%=PC_1000,PC_2000,PC_3000,PC_4000,PC_5000,PC_6000
    REC(EXPRESSION=%VALUE%LOOKUP(C_%LOOP_CENTER%)/1000, PCENTER=%LOOP_CENTER%, ITEM="IM_M08", DATASRC="CALCULATED")
    *NEXT
*ELSE
    *FOR %LOOP_CENTER%=PC_1000,PC_2000,PC_3000,PC_4000,PC_5000,PC_6000
    REC(EXPRESSION=%VALUE%LOOKUP(C_%LOOP_CENTER%)/1000, PCENTER=%LOOP_CENTER%, ITEM="IM_M05", DATASRC="CALCULATED")
    *NEXT
*ENDWHEN
*ENDWHEN
*COMMIT

Hello,
This error comes up when there is no enough memory.
How many members do you have in PRODUCT and how many parallel processes did you set up in PARALLELSCRIPT?
Also, I'd suggest to put *XDIM_MEMBERSET PRODUCT = %PRODUCT_SET% in your LOGIC01_QUANTITIES.LGF script.
Did you get anything in RUNLOGIC log? In UJFS you can find logs for every parallel process ran, name if it is just it's time stamp.
Can you see from those what scripts ran and with what parameters?
This should simplify resolution of your issue.
Regards,
Gersh

Calculated members in Data Manager when run package

Hi All
Do you know why calculated members in C_ACCT dim (which has child and are calculated by hierarchy) are not available in data manager when I want to run package. I want copy this calculated members to another account by using script logic and run it by data manager.
Below is my script
*XDIM_MEMBERSET C_ACCT = IC_BSAS05
*WHEN ENTITY
*IS 1013
*REC(FACTOR=2,C_ACCT="ICX_BSCS02")
*ENDWHEN
*COMMIT
IC_BSAS05 is caclulated by hierarchy.
It works for non-calculated, please tell me if it is possible to run script also for calculated members.
Regards!

Hi Justyna,
When you say that IC_BSAS05 is "calculated by hierarchy" do you mean that IC_BSAS05 is hierarchy node?
If this is true then try replacing the first line of your script with
*XDIM_MEMBERSET C_ACCT = BAS(IC_BSAS05)
Regards,
Gersh

Script Logic EDI

Hi!
Does anyone know if there is script logic (sap bpc) EDI?
Thankxx!!

HI,
I don't know what is EDI.
But SAP BPC has a script logic used to create calculation for aggreate members.
Regards
Sorin Radulescu

Simple Script Logic

Hi all,
Is it possible execute a script logic when i execute the import package? i added in the DEFAULT.LGF the code:
WHEN *
is *
REC(Expression=get(account="ccp0001")*get(account="ccq0001"), account="ccv0001")
endwhen
commit
The idea is calculate value = price * quantity and put in a new rec when i load the data.
value =ccv0001
price = ccp0001
quantity = ccq0001
i dont know whats wrong but thats calculate nothing.

Unfortunately you really don't exactly know if a scope is exactly right, unless you work out the tuples specific to each calculation and the define independent script calcs for each tuple set. A fancy way of saying, breaking down the calculation to each basic account by all the other dimension members that are to get together in a calculation.
There is a way of testing the script starting in version 7.0SP4 ithink, called the logic debugger. This process actually has you define some form of scope in order to test the calculations as a dry run, but not run based on an import, rather based on your request to run.
There are also various rules used during the logic calculation process, such as the engine will query all Accounts for values in the DB that match your inbound data set, or scope. Category, Time and Entity play an critical role in any caluclation, and the processing of values. And remember that logic that works in default may not look the same as when data is loaded, based onthe sets of data that are used during the passing of inbound detals to the engine for the logic processing.
hope this helps.

Script Logic - Calculated Members

Similar Messages

Maybe you are looking for