Script Logic Keyword in BPC NW 7.0

Hi All,
As per the doc in SAP NW 7.0 version the stored procedures will not work and they are to be replaced with some related script logic key word.
I searched for finding the same but i could not. Can any one help me in providing the equivalent script logic keywords for the stored procedures like SPRUNCONVERSION,SPICDATA,etc used in MS version.
Is there any file containing the stored procedures and their equivalent script logic keyword or we need to search for it.
Please Help me in this issue,
Thanks in Advance,
Regards,
G.Vijaya Kumar.

Vijay,
Please take a look at the documentation for running business rules in script logic at the help.sap.com site ([link|http://help.sap.com/saphelp_bpc70sp02/helpdata/en/66/ac5f7e0e174c848b0ecffe5a1d7730/frameset.htm]). Every business rule type includes an example of a script logic section that will call the business rules.
You may also want to do a search for information on programming custom script logic BADIs, which are the equivalent of custom stored procedures in the MS version ([one example|https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e04b5d24-085f-2c10-d5a2-c1153a9f9346]).
Thanks,
Ethan
Edited by: Ethan Jewett on Sep 3, 2009 7:27 AM

Similar Messages

Line numbers in Script Logic editor

Hi everybody,
when using the default Script Logic editor in BPC NW I can not see any Line Numbers (or Column Numbers) in the edited script.
When an error is detected by the system after validating the script, the error message sometimes refers to a certain Line Number where the error occured.
Is there a better way than manually counting the lines from the top (which can be quite a task when editing, say 500 lines) ?
Do I miss something here or are you all using alternative editors ?
Please give me some input.
Regards.
Wolfgang

Hi Nilanjan,
thanks for the quick answer.
That would mean that I always need to switch from BPC frontend Script Editor into BW and start a transacion and program there. I would have hoped, that simole line numbers would be a standard feature in the BPC frontend editor itself. Nevertheless...
Best regards.
Wolfgang

Script logic not working for GL account with Zero balance

Dear Experts,
I have a scenario where the GL account balance in ECC is 0 and when a script logic runs in BPC the same should capture a closing balance as "1".
Though I have written the below logic, this is not getting executed and writing back the value as "1".
Kindly help me on the same.
*WHEN ENTITY
*IS "ABC"
*WHEN ACCOUNT
*IS "20300000"
*REC(EXPRESSION = 11, ACCOUNT = 20300000,FLOW = F99, ENTITY = ABC, PROFITCENTER = 130010 , INTERCO = I_NONE , CONSOSCOPE = G_NONE, CURRENCY = LC ,CATEGORY = ACTUAL, AUDITID = INPUT)
*ENDWHEN
*ENDWHEN
*COMMIT
Regards,
Shilpa

Hello Vadim Kalinin,
Thanks for the very swift help.
Merger of the client happened in 2007. ECC is using the " 20300000- change in fair value " account to record both pre-acquisition and post-acquisition values.
Since the treatment of pre-consolidation and post consolidation reserves is different the split of the amount between pre and post-acquisition values has to be done. For the same post acquisition value is reduced from this account using a script logic as below.
WHEN FLOW
*IS "F99"
*WHEN ENTITY
*IS "ABC"
*REC(EXPRESSION = ([ACCOUNT].[20300000] -3258603),ACCOUNT = 20300000,FLOW = F99, INTERCO = I_NONE , CONSOSCOPE = G_NONE ,CURRENCY = LC ,CATEGORY = ACTUAL )
This logic worked when the account has a figure, but in July 2014 in ECC the account had a transaction and the balance has become Zero. Until this account has a figure this pre acquisition logic is not working.
For making this work, I am trying to write a new logic to make the balance of this account as "1" in BPC through the script logic.
Kindly suggest me on the same.
Regards,
Shilpa

Rounding in NW BPC Script Logic

Hi,
BPC MS version has a keyword "ROUND" to round the numbers through script logic.
What is the replacement to Round the amounts in NW BPC Script Logic.
I tried using the same keyword "Round" but it did not work.
Appreciate your help.
Thanks
Anjali

There is a HowTo guide showing how to implement this functionality as a BADI - [http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50daa919-5b80-2c10-babd-b75c6c64feed]
Please make sure to search SCN and look through the HowTo guides before asking questions in the forums. HowTo guides can be found here: [http://wiki.sdn.sap.com/wiki/display/BPX/EnterprisePerformanceManagement(EPM)How-to+Guides]
Ethan

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.

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.

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

Send parameter from one script logic to another. SAP BPC 7.5 NW.

Hello!
Before i start, want to apologize for my English.
We work on SAP BPC 7.5 for NetWeaver.
In general, we want to send parameter from one Script logic file to another script logic file.
I will explain why :
1. We have parametr like %C_CATEGORY_SET% (and another four parameter, like groups, currency and etc.) that work on one script(next, i will named it A_Script).
       We will send this parametr from BPC EXCEL (we will create button, then use command MNU_eData_SelectPackage(we also set parameters) and run package that we need, also before we set script for this package by the SAP Guide. We send some data, and this A_Script work good. Everything that we want from this script work correctly. )
2. Next we create another script(B_Script) , and we want use %C_CATEGORY_SET%, but we don't know how use this parametr, if we will just write this parametr on Script Logic, apears error ("C_CATEGORYDATAVALUE" is not assigned to the Data Administrator). We try to solve this problem by using System_Constants.lgf, but we get error.
Code:
*DIM C_CATEGORY          WHAT=%C_CATEGORY_SET%;             WHERE=<<<;                   USING=<<<;    TOTAL=<<<
*DIM C_ENTITY                 WHAT=%ENTITYSET%;                         WHERE=<<<;                  USING=<<<;      TOTAL=<<<
*DIM GROUPS                   WHAT=%GROUPS_SET%;                    WHERE=<<<;                  USING=<<<;     TOTAL=<<<
*DIM RPTCURRENCY         WHAT=%RPTCURRENCY_SET%;         WHERE=<<<;                  USING=<<<;      TOTAL=<<<
*DIM TIME                          WHAT=%TIME_SET%;                          WHERE=<<<;                  USING=<<<;     TOTAL=<<<
If we will change %C_CATEGORY_SET% for ACTUAL, and also change another parameters, script will work, package will run correctly. But we need using parameters, because we didn't exactly what will choose our client.
Our question have BPC Script Logic some kind of Globar Parameter(Variable), that we will set in A_Script, and then use them on B_Script?
How can we define parameter from another script logic, maybe we should send it?
Should we use System_Constants for solving this problem, if yes, how?
Any help will be appreciated
Best Regards,
Erlan Kadraliev
Edited by: Erlan Kadraliev on Feb 8, 2011 4:50 PM
Edited by: Erlan Kadraliev on Feb 8, 2011 4:58 PM
Edited by: Erlan Kadraliev on Feb 8, 2011 4:59 PM

Hi Ethan Jewett
1. About %ENTITYSET% it is normal. Before this line i write :
*SELECT(%ENTITYSET%, "ENTITY", GROUPS, "[ID]=%GROUPS_SET%")
So it is not this problem. %ENTITYSET% just parameter, that i used.
2. Are you running the scripts using the same data manager package? I am running two different package for 2 different Script.
For example aPackage for aScript, and bPackage for bScript.
My questions was how can i send parametr from one script to another, for example i can run another script by using BADi command Runlogic, but how can send parameter that i need to used on another script. I have for example parameter %GROUPS_SET% (CG001) on aScript, but i can't get this parameter on another script, if i write %GROUPS_SET% i will get error ("GROUPSDATAVALUE" is not assigned to the Data Administrator)
OR
Maybe if you will answer for next question, i will be able solve problem , How can i send parameter CG001 (this is %GROUPS_SET%, for example it stay in EXCEL in cell A5) from excel to script logic by running package. Maybe i can get cell value on Dynamic Script Data Management?
My Dynamic Script on bPackage
PROMPT(RADIOBUTTON,%CHECKLCK%,"u0412u044Bu0431u043Eu0440 u0431u0430u0437u043Eu0432u043Eu0433u043E u043Fu043Eu043Au0430u0437u0430u0442u0435u043Bu044F.",1,{"u0412u0441u0435u0433u043E u0410u043Au0442u0438u0432u044B","u0421u043Eu0431u0441u0442u0432u0435u043Du043Du044Bu0439 u043Au0430u043Fu0438u0442u0430u043B","u0412u044Bu0440u0443u0447u043Au0430 u043Eu0442 u0440u0435u0430u043Bu0438u0437u0430u0446u0438u0438","u0414u043Eu0445u043Eu0434 u0434u043E u043Du0430u043Bu043Eu0433u043Eu0431u043Bu0430u0436u0435u043Du0438u044F u043Eu0442 u043Fu0440u043Eu0434u043Eu043Bu0436u0430u044Eu0449u0435u0439 u0434u0435u044Fu0442u0435u043Bu044Cu043Du043Eu0441u0442u0438"},{"BPAST_ALL","BPEQ","BPPROCE","BPOPIN_GO"})
INFO
(%EQU%,=)
INFO
(%TAB%,;)
TASK
(/CPMB/DEFAULT_FORMULAS_LOGIC,SUSER,%USER%)
TASK
(/CPMB/DEFAULT_FORMULAS_LOGIC,SAPPSET,%APPSET%)
TASK
(/CPMB/DEFAULT_FORMULAS_LOGIC,SAPP,%APP%)
TASK
(/CPMB/DEFAULT_FORMULAS_LOGIC,REPLACEPARAM,CHECKLCK%EQU%%CHECKLCK%%TAB%)
TASK
(/CPMB/DEFAULT_FORMULAS_LOGIC,LOGICFILENAME,MYTEST_145.LGF)
Best Regards,
Kadraliev Erlan

BPC 7.5 Upgrade - Script Logic Toolbar missing

Hello,
We are moving from BPC 5.0 to 7.5. In the process of testing we found that the script logic window no longer has the toolbar that allows us to change the font type, font size, do pretty print...
Is there a setting to get this?
Also, we have noticed that the 'Administration Help' link on the bottom right hand corner of the BPC Admin screen no longer shows up.
On BPC for Excel, the e-Analyze, e-Publish, e-Submit.. no longer have their own 'help'....
Please let me know if you need additional information...
Regards,
Venkat

Help is a separate icon on top of Action Pane right now.
But the hellp still exist and can be reach from any section.
Regarding the scriptlogic we are speaking about text files.
So for print you just can copy into notepad or any other editor addyour format and you will be able to print.
Regards
Sorin Radulescu

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

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

BPC Script Logic - XDIM_FILTER results in error

I am writing a Script Logic in BPC and I need it to include all records where the DESTINATION dimension member has the Dimension Property of PLANDEST = "Y"
This approach works:
*SELECT(%DestinationMbrs%,"[ID]","Destination","[PlanDest] = 'Y'")
*XDIM_MEMBERSET DESTINATION = %DestinationMbrs%
This approach does not work:
*XDIM_MEMBERSET DESTINATION = <ALL>
*XDIM_FILTER DESTINATION=[DESTINATION].PROPERTIES("PlanDest")="Y"
It results in the error message at runtime:
Error in step 1 of QueryCubeAndDebug: -2147467259 Query (1,156) The PLANDEST dimension attribute was not found.
The reason I would like to use the second approach is that the first approach relies on the SELECT statement. The documentation on the SELECT statement says:
The *SELECT statement is executed at the time the logic is validated, and the expanded result is
written in the LGX file. This means that if the related dimension is modified, it may be necessary
to re-validate the rules.
So if I change the DESTINATION dimension members PLANDEST flags, I need to re-validate the script logic. That is a maintenance nightmare and a problem waiting to happen.
How do I solve this so that the dimension attribute is evaluated at runtime, not at logic validation time?

As Yuan Said, if you are using MDX logic and want to use property, you should check Inapp at the 'manage property' menu of admin console.
Usually, InApp sholud not be selected for better performance of MDX query. (SAP recommendation)
But. Here are two cases that you should select.
1. MDX logic in the logic script.
2. Dimension formula.
I hope it will make clear for all.
James Lim

BPC 7.0 MS Script-Logic problem: New values used, old values written?

I am trying to using BPC Script logic to update my Sales cube, specifically Revenue=Units*Price and Price=Revenue/Units using the "Price" stored in a seperate Price cube.
Inside default.lgl, I am *INCLUDE-ing my own script:
*LOOKUP PRICES
*DIM PREIS:ACCOUNT="Price"
*ENDLOOKUP
*WHEN ACCOUNT
*IS "Units"
*REC(FACTOR=LOOKUP(PREIS),ACCOUNT="Revenue")
*IS "Revenue"
*REC(EXPRESSION=%VALUE%/LOOKUP(PREIS),ACCOUNT="Units")
*ENDWHEN
*COMMIT
Now, when I insert new "Units" values using the std. Excel template, strange things happen:
- The Revenues seems to be computed and updated correctly in the cube (if I check them using excel templates, they show up).
- The Units seem to have the values they had before... seems they get old values ?!
E.g. if I have several write operations say, I write units=2,3,4 and price is constant 10,
the values in the cube seem to be (table):
value written, units in cube, revenue
3 , 2 , 30
4, 3 , 40
The new value is somewhere in the MS Analysis cube, otherwise, how could later be the new value be shown, although the excel templates seem to show old values?
Any explanation for that strange behaviour?

I simplified and wrote the prices in the same cube as I send the data from with the excel template.
I tried using:
*WHEN ACCOUNT
*IS "Units"
[Account].[#Revenue]=[Account].[Units]*[Account].[Price]
*ENDWHEN
*COMMIT
*WHEN ACCOUNT
*IS "Revenue"
[Account].[#Units]=[Account].[Revenue]/[Account].[Price]
*ENDWHEN
*COMMIT
Now, if units are send from the excel template, revenue is calculated correctly.
If I enter revenue instead, seems that the 1st block is executed as well (why????!!!/how to avoid - I use *WHEN - what else should I do? ) which would explain the behaviour I get the old values for Units and Account again...
Related: How can I use "*WRITE_TO_FILE"? I tried both
*WRITE_TO_FILE Mylog.txt
*WRITE_TO_FILE "Mylog.txt"
But I can't find these file after sending data through the excel template... Do I have to create the files manually first or give full Path Names?
Thanks!

Script Logic in BPC is not working properly

Hi All,
I have the BPC Microsoft version 7.0.114. I am trying to create a script logic to calculate price x units.
I have an application called GYP with the following dimensions:
PL (Account type) in this dimension are the units
Time
Category
Entity
Product
RptCurrency
I have another application called PRICE with the following dimensions:
Price (Account type) in this dimension are the prices
Time
Category
Entity
Product
RptCurrency
The script logic i created in the GYP application is as follows:
*XDIM_MEMBERSET PL="Units"
*XDIM_MEMBERSET PRODUCT=<ALL>
*XDIM_MEMBERSET ENTITY=<ALL>
*XDIM_MEMBERSET CATEGORY="Budget"
*LOOKUP PRICE
*DIM PR:PRICE ="PRICES"
*ENDLOOKUP
*WHEN PL
*IS "Units"
*REC(FACTOR=LOOKUP(PR), PL="Revenues")
*ENDWHEN
*COMMIT
I also put in the default.lgf :
*INCLUDE UnitsxPrice.LGF
*COMMIT
I have loaded data for units and price only for one product to validate the script logic but I'm not getting any calculated value in the revenues element.
I have read a lot of documentation about script logic but i haven't found which could be the problem.
Please, could you help me to know what i am missing to?
Thanks in advance for all your help.
Regards,
Luisana

Hi,
Your script logic looks fine to me. However, I would request you to make a small change in your default logic.
Lets say that you created the script logic with the name CALCULATION.LGF, then the default logic should look like below:
*INCLUDE CALCULATION.LGF
Notice that the name of the script logic should be consistent (and I have removed the commit statement from the default logic).
Hope this helps.

SAP Bpc: automate script logic validation

Is there a way to automate the validation of the SAP BPC script logics?
I ask you that because I have daily SSIS packages and, actually, if I don't manually vaildate the logics every time, using SAP BPC administration interface, the new members are not cosidered into the application.
I tryed the BPC SSIS "Adimin Task" (using Validate Logic mode) but it only checks if the syntax of the logic is correct or not.

Thanx for the replay but, unfortunatly, I think it's not useful for my case.
I use SSIS packages to populate dimensions (such as Employees). In these packages I have BPC Admin Task (in create dimension mode) and it works fine.
The problem is > if I don't go into SAP BPC Administration Console to "Validate and Save" the script logics manually > inside the .lgx file there aren't into XDIM_MEMBERSET the new data I previously imported throught the SSIS packages above (in the exemple the new Employees).
Beeing not into the XDIM_MEMBERSET, the script logic executed by the users excel input schedules cannot manage the new set of data... until I "Validate and Save" the logic manually.
Edited by: Francesco Andolfi on May 26, 2010 4:22 PM
Edited by: Francesco Andolfi on May 26, 2010 4:22 PM

Script Logic Keyword in BPC NW 7.0

Similar Messages

Maybe you are looking for