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

Similar Messages

Script Logic Validation Error

Hi experts.
The Script Logic validation is returning an error for this sentence:
.[#BUDGET]=[TIPO_DATO].[PREVISION]+.[AJUSTE]{/code}
The error I'm receiving is:
Member "" not exits
The member BUDGET for TIPO_DATO dimension exits as well as member prevision
¿Any idea?
Thanks a lot
it0

Hi,
Can you process by removing the member and then add budget to dimension tipo_dato and then validate the script logic.thnx.
Sanjeev

SQL functions in Script Logic

I want to build a script logic but the dimensions that I am testing do not have the fields I want in the format I want. In my case I would like to test the "Start" property in the Employee dimension. The property represents the employee start date but is a var char in the format dd.mm.yyyy rather thna a date field. I want to test whether it is five years prior to the date being processed.
My time dimension has a year property and a monthnum property. Each of these are varchar. I can write SQL that would convert these to a date and compare them with the start property on the employee dimension.
Can I do iinsert SQL functions in the When statement. An example would be
*When convert(datetime, substring(employee.start,4,2) + '/' + substring(employee.start,1,2) + '/' + substring(employee.start,7,4))
Can I use SQL functions in the Is statement? An example would be
*Is <DateAdd(YY,-5 , convert(datetime, Time.Monthnum + '/01/'' + time.year)
Finally when I use such techniques and look at the log by using "show log" in the logic debugger I see no reference to the SQL I used. It is as if the generated SQL has not made use of my functions. Instead all I seee are the extract statements from the three fact tables. Is this normal? Is there a way to see what SQL is really being generated and run?
At the moment it seems my only option is to make changes, try running it and hope I get an output. If no records are written I can't be sure whether it is because embedding SQL function is not supported or because I have made some other error.

No, the "BPC SQL" script logic doesn't allow for this extensive use of real SQL within the scripting syntax. As a concept, it's best to think of "BPC SQL" script logic as, "this unique BPC logic syntax will generate real SQL code when it's executed."
There's very little real SQL that you can use within the syntax itself, and definitely not within the WHEN or IF statements. Nothing like cast, convert, substring, etc. (Except you CAN use these, a little bit, in a *SELECT statement. But I don't see how that will solve your current problem.)
Plus, when you consider how the logic engine processes a set of data, it's helpful to think of it in terms of selects & reading through a recordset. So in that regard, a SQL background can be helpful, in understanding the concepts. (Sort of helpful, except when it confuses you, or frustrates you since you don't have all the power you want.)
Anyway, to solve your problem, you might be able to restate the problem, and then use something like this code, which is valid syntax:
*WHEN TIME.TIMEID
*IS >= VERSION.FirstPlanMonthTimeID
In this case, FirstPlanMonthTimeID is set up in the version dimension as, for example, 20090400 (representing 2009.APR). This timeID is set by BPC automatically when processing the time dimension, and I need to ensure that my Version property value is set to match it.
A key point is that in BPC fact tables, the time dimension is stored as TIMEID (not ID, unlike all the other dimensions), and can be used for comparative evaluation in script logic WHEN/IF. The comparison property needs to be stored as an 8-digit integer value. If your time dimension has days in it (along with months), check the TIMEID after processing, and you should see the pattern for assigning values to TIMEID for days and months, etc.
Normally, TIMEID is assigned pretty sensible and stable values. If it doesn't meet your logic requirements, you can create another property (be careful of USERTIMEID, since that has a specific purpose in the system which I've never fully understood) and assign that whatever (integer) values make sense.

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

Automate excel circular references - script logic - BPC

Hi,
I need to automate in BPC the calculation of financial debt that contains excel circular references, so you have to enable the calculation Automatic iterations properly to work.
I would like to automate the process through a script logic.
I appreciate any help or suggestions.
Regards,
Fernando Chávez.

Dear Fernando Chávez,
I just want to give you simple suggestions because I don't know your case exactly. The script logic is similiar with SQL script. You could put your logic script in default.lgf or make new file .lgf through BPC Administration Console. If you put it in default.lgf, the SAP BPC will execute it when user sent values through BPC Excel. You also could run the script logic through Data Manager Packages, its runs depend on user execution.
If we are talking about circular and complex formulas in Ms.Excel, I suggest you put your calculation in another worksheet and send values through BPC Excel. Before you define a script logic, the number one is you should to consider performance because its really critical.
Kind Regards,
Wandi Sutandi

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

SAP BPC 10.0 NW break query in logic script

Hi Experts,
We are facing one issue while copying data from one version to other version.
logic is like the data in target should get cleared first and then copy the data from source to target version (in same model).
But while clearing the data, the package is failing with memory allocation error.
So to break the query we tried maxmembers and xdimpackage but facing performance issue.
please suggest command to break the query in script logic in BPC 10.0 NW.
Regards,
Rachana

Hi Uros,
just to make sure, you have entered FX rates in your rate model for the period you are trying to convert?
Do you need to select an entity when starting the package? If not, could you try to run the script as follows:
*RUN_PROGRAM CURR_CONVERSION
CATEGORY = %CATEGORY_SET%
CURRENCY = %RPTCURRENCY_SET%
TID_RA = %TIME_SET%
R_ENTITY = GLOBAL
*ENDRUN_PROGRAM
BR,
Arnold

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

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

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.

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

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 7.5 NW SP 4 - ERRORVALIDATION SCRIPT LOGIC WITH PROGRAM CURR_CONVERSION

Hi Gurus
I´m copying script logic for currency conversion for consolidation application, but when I want to validate this code
*RUN_PROGRAM CURR_CONVERSION
*ENDRUN_PROGRAM
the system generate this error "run program error, message number:""
is very strange because when i run without "N" or any other letter, the validation is correct, for example:
**RUN_PROGRAM CURR_CONVE
*ENDRUN_PROGRAM
is sensitive when I write CURR_CONVERSION
do you have any idea what happend with this?
thanks in advance

Lucio,
This is not a valid currency conversion call:
*RUN_PROGRAM CURR_CONVERSION
*ENDRUN_PROGRAM
You need to provide the necessary argument parameters. I assume that it is validating "correctly" when you remove letters because it can't find the program and just assumes that it will show up at runtime. These other permutations won't work either.
Please search the forum and take a look at help.sap.com for examples of currency conversion. There are a lot of good examples out there.
Ethan

SAP BPC 5.1 Validation Tolerance in Validation Business Rules

I am trying to use the the validation tolerance field in the validation business rules and I make it work
This is how i understand it:
For example, I am trying to create a control that check that net assets = equity in the balance sheet with a tolerance of 10.
I have set up the following validation rule header and detail:
Header: CTRL1 ;validation operand = ; validation tolerance 10; all other fields are blank
Details: CTRL1; account1=netassets;flow1=F_CLO;SIign1=1;account2=equity;flow2=F_CLO;sign2=1
After running the validation package:
If my netassets-equity=9--> i should see CTRL1=0
If my netassets-equity=-5--> i should see CTRL1=0
If my netassets-equity=15--> I should see CTRL1=15
Is my understanding correct? Has anyone been able to use the validation tolerance?
Regards
Lena

In addition to James comments, I just wanted to add a few additional notes:
1. The Demo application that was presented contains the applications that you described in your question. Historically, the consulting team would either use the ApShell or the demo as the foundation for developing a set of applications for the customer based on the design sessions held with the customer. BAsed on the customer requirements and design, often we start with ApShell and pull in components from the Demo that would support functionality requirements that may go beyond what Apshell has out of the box. Many of these components are covered in an Advanced Training for BPC, including the helpful and not so helpful components.
2. You can pull many of the Demo dimension files, logic scripts and rules from the Application Server file folders for use in an Application set design. Unfortunately, BPF's can not be transfered, since they are built in to an application and reside in tables in SQL. In addition, many BPF's need to be defined to meet a customers requirements, file names, location, users, and dimension structure.
3. Many of the dimensions utilize several supporting properties that may be added via the admin console to any dimension. The properties are a key ingrediaent to a well running application set, supporting reporting, script logic, and business rules.
4. The Performance dashboard is no longer an option that is included out-of -the-box, howvere it is just a shell that was adjustable to the application set designed for the customer.

SAP Bpc: automate script logic validation

Similar Messages

Maybe you are looking for