No | BW | BPC |
1. | Infoarea | Appshell |
2. | Cube | Application |
3. | Multiprovider | Application |
4. | Infoobjects – costcenter,cocode | Dimensions |
5. | Master data | Members |
6. | Navigational Attributes – Material color , size,etc | Properties |
7. | Key Figures – Quantity or Amount | Signed data/Amount(Please check below notes) |
8. | Bex Query | EVDRE Reports |
9. | Process Chains | Data Manager Packages |
Jul 20, 2011
BPC Vs BW
Jul 14, 2011
Structure of Script Logic
Logic can be broken down into 3 components
BPC for Excel Scoping
Modification of Scope (i.e.:*XDIM_MEMBERSET)
Allocation Logic and Stored Procedures
Custom BADIs
BPC version for Netweaver Script Logic Overview
*XDIM_MEMBERSET O_CUENTA = ESP001111
*XDIM_MEMBERSET T_TIME = 2011.FEB
*WHEN O_CUENTA
*IS ESP001111
*REC (EXPRESSION = 311)
*ENDWHEN
*COMMIT
- Scoping - What am I running the data on?
BPC for Excel Scoping
Modification of Scope (i.e.:*XDIM_MEMBERSET)
- Body/Code – What do I want to do with the scopedrecords?
Allocation Logic and Stored Procedures
Custom BADIs
- Writing the record
BPC version for Netweaver Script Logic Overview
*XDIM_MEMBERSET O_CUENTA = ESP001111
*XDIM_MEMBERSET T_TIME = 2011.FEB
*WHEN O_CUENTA
*IS ESP001111
*REC (EXPRESSION = 311)
*ENDWHEN
*COMMIT
Parameter *INCLUDE... more Script logic
Multiple files can be combined into one logic file by the use of the instruction INCLUDE. During the LGX generation of the script logic execution step, the statements in INCLUDE file are combined with main file.
Working with *INCLUDE will facilitate debugging since you can debug each Include separately.
The file has the extension .LGF, which can be called at validation by using the INCLUDE function in your logic file.
Working with *INCLUDE will facilitate debugging since you can debug each Include separately.
The file has the extension .LGF, which can be called at validation by using the INCLUDE function in your logic file.
Use the *INCLUDE command to have one logic file call another logic file.
Types of Script Logic
Default logic is a special logic statement that is executed on every write back
to an application.
All logic in Default.LGF is run after data sends. Data is first committed to cube and then, Default.LGF is run on cube data. All other Logic is not executed during Send Data!
Script Logic allows you to create files containing instructions for performing calculations with special requirements on Planning and Consolidation data. You can perform logic calculations on base level members only. In addition, logic is application-specific.
Script Logic Files
You have the following two files for each piece of script logic you create:
1.- An .LGF file, which is an ASCII file you create and edit when setting up logic calculations. You access the .LGF file through the Script Logic editor in the Admin Console.
2.- An .LGX file, which is the compiled logic file created by the system when you validate and save your logic. This is an executable version of the .LGF file that is not stored in Planning and Consolidation.
to an application.
All logic in Default.LGF is run after data sends. Data is first committed to cube and then, Default.LGF is run on cube data. All other Logic is not executed during Send Data!
Script Logic allows you to create files containing instructions for performing calculations with special requirements on Planning and Consolidation data. You can perform logic calculations on base level members only. In addition, logic is application-specific.
Script Logic Files
You have the following two files for each piece of script logic you create:
1.- An .LGF file, which is an ASCII file you create and edit when setting up logic calculations. You access the .LGF file through the Script Logic editor in the Admin Console.
2.- An .LGX file, which is the compiled logic file created by the system when you validate and save your logic. This is an executable version of the .LGF file that is not stored in Planning and Consolidation.
Jun 28, 2011
10 Key Value add from SAP EPM 10
Articulo muy interesante,
While EPM10 is the most significant release that SAP has made from the day SAP become serious about EPM in 2007 , I often get asked what are those key use cases that has been addressed in EPM 10. Here is my attempt to crack some top use cases that brings significant value from SAP Business Objects Enterprise Performance Management 10.0 release.
LINK
While EPM10 is the most significant release that SAP has made from the day SAP become serious about EPM in 2007 , I often get asked what are those key use cases that has been addressed in EPM 10. Here is my attempt to crack some top use cases that brings significant value from SAP Business Objects Enterprise Performance Management 10.0 release.
- Our top exec own ipads – manage strategy on the move
- We all love Excel, but there are too many of them – unify them
- Need budgeting and consolidation rolled out to 10K+ users across 100 locations
- Its takes a while to report financials to stakeholders and what’s this XBRL
- Our setup is diversified, hard to get consistency on the financial notes
- Our Legal consolidation is too complex and needs effective monitoring
- Not interested in just analysis of output costs, need drill down to inputs
- This variance analysis kills lot of my time - need some quick indicators
- Would like to deep dive into GL to analyze variance by transaction
- What’s this TCO, I am finance, can you explain
LINK
Subscribe to:
Posts (Atom)