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

Similar Messages

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!

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.

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.

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.

Migration V4 to V7 -- script logic problem

Dear all,
I am migrating all the necessary logics but in one logic I have following error
"invalid dimension:AccountL"
The accountL dimension is not a dimension in Version 7
However in the logic is following syntax:
*XDIM_MEMBERSET ACCOUNTDIM <> INVALID
*XDIM_MEMBERSET DATASRC<>INPUT
*XDIM_MEMBERSET INTCODIM <> INVALID
*XDIM_MEMBERSET ACCOUNTDIM <> INVALID
*XDIM_MEMBERSET DATASRC<>INPUT
*XDIM_MEMBERSET INTCODIM <> INVALID
So I think it's something in the system constants file?
But I dont know where to look...
Someone has a solution?
Thx
Br
Benjamin

Hi Benjamin,
you are right, it seems that the Dimension Mapping in SystemConstant.lgl file is not correct.
You can find this file on the Appserver at %InstallDrive%BPCDataWEBFOLDERS%AppSet%ADMINAPP%Application%SystemConstant.lgl.
Another possibility is to directly use the name of the Account dimension in Scriptlogic and not the alias "AccountDim"
Regards
Jörg

Script logic problem

Hi ,
I transfering the data from HR to finance .
HR account dimension : HRM_Account
Finance account dimension : Account
in HR diemnsion , i created one property ( fixgroup ) and value for required accounts is "transfer"
at the same time in account dimension ( account ) in finance application all HR accounts under property ( group ) with value "HR"
i exceuted below code ..but system unable read and write my accounts from HR application .
Pls look at my nbelow code and correct where i am wrong .
*DESTINATION_APP=FINANCE
*SKIP_DIM=HR_POSITION
*SKIP_DIM=HR_VALUE
*SKIP_DIM=HR_WTYPE
*RENAME_DIM DATASRCOTH = DATASRC
*RENAME_DIM HRM_CATEGORY = CATEGORY
*RENAME_DIM HRM_ACCOUNT = ACCOUNT
*SELECT (%ACCTSET%,"[ID]", "HRM_ACCOUNT", "[FIXGROUP] = ' HR ' ")
*XDIM_MEMBERSET HRM_ACCOUNT = %ACCTSET%
*XDIM_MEMBERSET DATASRCOTH = INPUT
*XDIM_MEMBERSET COSTCTR = <ALL>
*XDIM_MEMBERSET HR_POSITION = D_DUMMY
*XDIM_MEMBERSET HR_VALUE = HRVAL
*WHEN *
*IS *
*REC(FACTOR=1)
*ENDWHEN
Regards,
PSR
*COMMIT

Hi Shoba ,
I pasted ur code and after running it reading 636 records and skipped all records .
Actuall in i need ready only 10 accounts under fixgroup property .
but it reading 636 records ...means it is reading all reacords .
pls let me know ur inputs .
Regards,
PSR
Edited by: PSR on Jul 15, 2010 9:09 AM

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

Problems with "GET" in a Script Logic

Hi,
I created a Script Logic in BPC NW with the following code:
*WHEN *
*IS *
   *REC(GET(CONCEPTO=M30121),CONCEPTO=M213)
*ENDWHEN
And I click "Validate and Save" and I get this error:
Validation Error
Unknown Dimension Name in Keyword: "*:
What's happening?
Regards,
Miguel.

Thanks, but my problem is with "GET" function in Script Logic. You don't look at what I do with the code because it's an example. The problem is that the GET function doesn't work.
I created a Script Logic in BPC NW with the following code:
*WHEN CONCEPTO
*IS M30121
   *REC(FACTOR=GET(CONCEPTO=M213),CONCEPTO=M30121)
*ENDWHEN
And I click "Validate and Save" and I get this error:
Validation Error
Unknown Dimension Name in Keyword: "M213):
And if the code is like this:
*WHEN CONCEPTO
*IS "M30121"
   *REC(FACTOR=GET(CONCEPTO="M213"),CONCEPTO=M30121)
*ENDWHEN
The error is this:
Validation Error
Unknown Dimension Name in Keyword: ""M213"):
Regards,
Miguel.

Script logic folder empty!

Hello every body,
After installing Patch1 of BPC MS 7.5 SP04 I had a problem with script logic folder when expanding the Legal application in the Admin console. The folder is empty, no Logic found, even the Default.LGF!!!
When I try to create a new one through the "Create New Logic" link in the Action Pane, I get this error displayed:
System.IO.DirectoryNotFoundException: Could not find a part of the path 'E:\BPC\Data\Webfolders\<AppSet>\AdminApp\Legal(my application)'
When I tried to access this path I didn't find it, I found: 'C:\PC_MS\Data\Webfolders\<AppSet>\AdminApp\Legal' instead.
PS:I performed an update for the client with an Admin Account, after installing the patch.
Any help?
Thank you in advance.

Hello,
Thank you nilanjan for your reply
We have resolved the issue.
The problem was that on the BPC server on OS level the folder E:\BPC was not shared and we have added the everyone group to have access to the folder and now all the users that are using the BPC client can see the content of the Script logic in BPC Admin.
The File Share Server was pointing to E:\BPC\Data but the folder BPC was not shared and we have added the group: Domain Users to access the network path. Now we can see all the files in the appset Production \ Application \Legal\ Script Logic . We can create a new Script logic with success.
Thank you.

How to debug script logic in NW?

Hello,
does anybody know how we can debug script logic in BPC NW? I wasn't able to find anything in the documentation. Without debuger or log the script logic is quite useless.
Thanks for any advice
Jan

Hi Jan,
I am not sure if there is some information on this in SDN but there are RKT materials (which are available in Service market place) detailing this.
But in general, you need to setup a debug user and map it to bpc user using BPC server manager tool and then have a stop point in your ABAP program by logging into the NW system using debug user and run your logic using mapped BPC user.
regards,
Sreedhar

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

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

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

Problem with Script logic logs

Hi Experts,
I am using BPC 7.5M with SQL Server 2008, I am looking into script logic log but found one very strange statement "(More than 300,000 records. Details are not being logged)", Earlier it was not showing this statement and was showing all the entries to be posted, Is there any setting we need to do for having all the entries in the log file.
Status log file showing as of now:
App: HEADCOUNT - Records to be posted are 310875 (calc diff = 0)
(More than 300,000 records. Details are not being logged)
Time to validate records: 100.3 sec.
Post Record Status
Submit count : 100001
Accept count : 100001
Reject count : 0
Post Record Status
Submit count : 200002
Accept count : 200002
Reject count : 0
Post Record Status
Submit count : 300003
Accept count : 300003
Reject count : 0
Post Record Status
Submit count : 310875
Accept count : 310875
Reject count : 0
Posting ok
Time to post records:325.4 sec.
Please Advice
Thanks & Regards,
Rohit

Hi Rohit,
This is not a problem.
If the resultant number of records is more than 300,000, then the records are not logged.
This can be controlled by the UNLIMIT_PRINT_LOG appset parameter. By default, this is set as NO. This will allow only 300k records to be logged.
You can set the above parameter as YES to log all the records for the execution of all logics across the appset in all applications.
Warning:
Of course, it will add slow down the logic execution. Logging the records will always slow down the execution. The system has to open the file and keep writing all the records in the flatfile, which is a slow process. You can increase the speed of your logics by disabling this logging completely by using the CALCULATE_DIFFERENCE statement in your script logic for each commit section. You can reduce the logic execution time by disabling this logging.
Karthik AJ

Script logic problem BPC 7.5

Similar Messages

Maybe you are looking for