You are on page 1of 9

Business Rules

SAP Business Planning and Consolidation

SAP Product Support
March 20,2008

US Eliminations (Elim) – Controls where in an Entity dimension member the results of eliminations are stored. (Valid) – Allows user to check integrity and correctness of entered . Validations values. Intercompany Eliminations (AutoElim) – Performs intercompany eliminations.Types of Business Rules Account Transformation (CalcAccount) – Performs a straight summarization of a group of accounts Carry – Forward (CopyOpening) – Summarizes a group of activity accounts and copies the value into an opening balance account Currency Translation (FX) – Performs standard currency translation.

Business Rules (also known as table based logic)  Encrypted  Written SQL Stored procedures that are shipped with the product by product development and cannot be modified by users  Parameters are defined in BPC Administration and then executed through scripting logic  Parameters are application specific but procedures are in all applications .

When are Business Rules Used © SAP 2007 / Page 4 Uses Business Rules Reporting Values Yes Creating Records Yes Moving Data Yes Calculations on base records Yes Calculations on parent levels Yes .

How and when is logic executed  Business Rules  Executed by using the *RUN_STORED_PROCEDURE script logic command in a script logic file.  Business rule is executed when the script file is executed .

tables are not well documented and can be difficult to understand .Pros and Cons  Business Rules  Pros  Code is centrally stored and parameters are maintained by the application administrator  Execution  Typically can be setup to run on-demand or automatically fastest execution because it works in the relational database using SQL Server memory  Cons  If product development hasn’t written it. it cannot be done with BR  Stored  Rules procedures cannot be customized to fit unique client needs.

application administrators during implementation but can be modified anytime business processes change. .Who typically writes logic and when  Business Rules  Implementation  Typically consultants.

Business Rules Syntax .

 You might see cases where logic directly calls the stored procedure (*RUN_STORED_PROCEDURE) directly rather than using the wrapper function. The SP name can change so the best practice is to always call the wrapper which stays the same.  Make sure the name of the rule there calling is correct. there isn’t anything you can do to check for code errors. .Business rules troubleshooting  Most likely issue is with the parameters in the table.  Because the procedures are encrypted.