SAP BPC Concepts
SAP Business process consolidation
SAP Business objects overview
SAP Consolidation overview
from Verity Solutions
http://www.verity-sol.com
2. 2
Key Terms
Models – transaction data tables. For example: LegalCons, Sales Planning
HR Planning, Rates. A BPC application = a BW Infocube.
Dimensions - master data. For example: Legal Subs, Accounts, Version. A BPC
dimension = a BW characteristic.
Environment – an environment contains models and dimensions.
Business Process Flow – a set of steps and sub steps for a process such as
planning or consolidations. Used to track progress and provide guided navigation.
EVDRE – Everest Dynamic Range Exchange. The primary reporting function
in BPC 7.5 Excel. An array based reporting function. In 10.0, it is replaced by the EPM
Report Designer.
Work Status – used to set work states which control data input. For example,
after the period close is complete, ‘approve’ the period … which turns off any
further data changes.
Business rules – tables with parameters used to perform consolidation tasks such as
balance carry forward, reclassifications, eliminations, etc.
6. Processing Dimension Members From Member Sheet
Business
User
Add new
members
Dimension Member Sheet
Process Dimension
from member sheet(1)
BW Master Data
BW Application
Server (shortcut UJFS)
(1) Appset can be taken offline during ‘processing’. Offline mode makes the applications ‘unavailable’ for tran. data input but
users can still report in read mode. 6
7. Processing Dimension Members From Server
Business
User
Add new
members
Dimension Member Sheet
Process Dimension
From Server (‘From Member
Sheet ‘is an option as well)
BW Master Data
BW Application
Server (shortcut UJFS)Save to Server(2)
(2) Save to Server is a good option when entering in a significant amount of master data. 7
9. ACCTYPE Property
Account type dimensions require the property ACCTYPE.
There are four delivered ACCTYPES:
AST – Assets
EXP – Expense
LEQ – Liability and Owners Equity
INC – Income
ACCTYPES control the sign of the values in reports for example:
Value in db Value displayed in Reports
AST 125 125
EXP 125 125
LEQ -125 125
INC -125 125
ACCTYPES also control aggregation behavior of balance sheet accounts for example:
Value in db set to periodic storage Value displayed in Reports set to YTD
Jan Feb Mar Jan Feb Mar
AST 125 125 125 125 125 125
EXP 125 125 125 125 250 375
LEQ -125 -125 -125 125 125 125
INC -125 -125 -125 125 250 375
9
A BW query on a BPC InfoCube does not read the acctype property.
10. Example of a YTD Application
Consolidation apps are frequently set to YTD to facilitate a YTD ‘cumulative’ data load from source systems. That
way, any prior period adjustments are included.
Note: The shortcut / tcode LISTCUBE was used for the data view above. 10
11. Planning Logic Summary
Type Trigger Stored in Cube Features
Excel Formulas Enter Data, etc No MNU commands, normal
Excel, native macros
Dimension Refresh Data No On the fly calculations
Formulas The receiver has a calc
property of ‘Y’, MDX
Script Logic Data Sends(default) Yes Custom script, Trigger
or User runs a Business Add Ins
package
11
13. Integrating Script Logic & User Interface - BCF
Business User
Note: The push button ‘Run Pack’ is a macro MNU_EDATA_RUNPACKAGE.
Data Manager Package:
Script:
1
ABAP Program
2
Process Chain
3
13
14. Security Summary
Task Profile (what)
Default function tasks:
- sys admin
- primary
- secondary
Tasks by Interface: BPC Excel, Journals,
Documents, Data manager, Web, etc
Assign to users and/or Teams
Member Access Profile (where)
By Application: Finance, Sales, Cost, HR
Access Dimension Member
Read Entity All
Read/Write Cat Budget
Read Cat All
-Read all entities any category
-Write (budget) all entities
Note: Entity & Cat set as ‘Secure’
dimensions at the Application level
Teams (optional)
Team1
User A
User B Team Lead (rights for team
folders)
Assignments:
Task Profile
Member Access Profile
Users (who)
User1
Email and or Instant Messenger
Assignments:
Teams
Task Profiles
Member Access Profiles
14
15. 15
How to do a flat file import
1. Upload flat file on to the BPC Server
2. Opt: Preview
3. Opt: Create conversion file
4. Create transformation file
5. eData > Validate & Process trans file
6. Run import package
7. Opt: View status
8. Opt: Run report
How to do an improvider import
1. Opt: Create conversion file
2. Create transformation file with mapping of characteristics to dims
3. dData > Validate & Process trans file
4. Run infoprovider package
5. Opt: View status
6. Opt: Run report
16. ECC
Data Load Architecture – Flat File Scenario
BPC Transformation
Sheet for possible sign
change, assignment of
BW characteristics to
Dimensions, Selection
criteria to filter the import
etc. (1) (Required)
BPC Import
Data Manager Package
BPC Application
(Real Time
InfoCube)
Non SAP
Systems
Why consider this scenario:
- Quick and Easy
(1) The selection option can only be used with the Infoprovider import.
(2) Real time InfoCubes can receive data via BPC in ‘Plan’ mode or from BW Data Loads
in ‘Load Mode’.
System to System or
Flat File BW Load
•In Plan Mode (2)
16
Flat File(s)
BW
BPC Conversion
Sheet for External
to Internal mapping
17. BPC Imports of Master
Data
BBPC Char BPC Dim
BBW Char
BW Data Load(1)
Notes:
BW Data Loads can be carried out by BW Administrators.
Master data includes descriptions, attributes, and hierarchies.
BW Characteristics such as ‘0COSTCENTER’ can be used as a source for BPC Master Data.
BPC Characteristics are generated by the system when BPC Dimensions are created and have the ‘CPMB’ prefix.
System to System
or Flat File
ECC or
External
System
17
For Example: 0costcenter
- Text, Attributes,
Hierarchies
Scenario: BW Master
Data is in place and
you want to use it!
For Example:
/CPMB/ABCXYZ
BPC Conversion
Sheet for External
to Internal mapping
BPC
Transformation
18. Process Chain Merge Replace & Clear Comment
/CPMB/IMPORT_APPEND
(BPC:Import transaction Data
from Flat File (Aggregated
Overwrite)
Data in the source will first
be aggregated by all
dimensions. Then data in the
target will be overwritten by
source data by all dimensions
The target data will first be
cleared by E/C/T/D in the
source. Then data in the source
will be aggregated by all
dimensions and overwrite the
target by all dimensions.
/CPMB/APPEND
(BPC: Import transaction Data
from Flat File (Append Mode)
n/a n/a No "merge" option and
"Replace&Clear". The
source data will be
appended into the BPC
cube. Key figure will be
aggregated.
/CPMB/IMPORT
(BPC:Import Transaction Data
from Flat File (Last Overwrite)
Data in the target will be
overwritten by source data
by all dimensions. In case
there are entries with the
same dimensions from
source, only the last entry
will be considered.
The target data will first be
cleared by E/C/T/D in the
source. Then data in the target
will be overwritten by the data
from the source. In case there
are multiple entries with the
same dimensions, only the last
entry will be considered.
Flat File Data Manager Packages
19. ECC
Data Load Architecture – BW > BPC Scenario
BW Standard
InfoCube
BW Load with
transformation
Options (BW)
BPC Conversion
Sheet for External
to Internal mapping
BPC Transformation
Sheet for possible sign
change, assignment of
BW characteristics to
BPC Import InfoProvider
Data Manager Package
BPC Application
(Real Time
InfoCube)
•InfoCubes
•Data Store Objects
•MultiProviders
Non SAP
Systems
BW
Why consider this scenario:
- Use actual data in an existing InfoCube
- Use the BW Cube for data homogenization
- BPC Business User can import data
Note: version 10, delta is provided.
System to System or
Flat File BW Load
•In Plan Mode (2)
19
(1) The selection option can only be used with the Infoprovider import.
(2) Real time InfoCubes can receive data via BPC in ‘Plan’ mode or from BW Data Loads
in ‘Load Mode’.
22. 22
KEY FIGURE MODEL
ACCOUNT BASED MODEL CHAR’S KF1 KF2 KF3
ACCT1
ACCT2
ACCT3
KEY FIGURE TO ACCOUNT BASED MODEL
23. 23
Key figure cube to BPC Cube
Note: this is an illustration23. The accounts
shown on the left are not all the same.
24. 24
Key figure based cubes
multiple kf’s
wider / shorter
Account based cubes
one / two kf’s
narrow / long
There is no right or wrong model
You can use BPC transformation files to share data
Modeling InfoCubes
25. 25
Entity Dim: Implied
Entity Parent Owner Reviewer Manager
US Pete Pete
Store1 US Joe Nadine Pete
Store2 US Sachi Nadine Pete
Owners & Managers
Reviewers used to ‘review’ BPF steps ie to approve / reject.
Include multiple users: user1,user2, and you can include teams also!
26. Work Status Architecture
App Set: Work States
Work Data Status
State Manager Journals Manual Documents Comment Controlled By
In Process All All All All All Both
Submitted Locked MAN Owner All All Owner
Approved Locked Locked Locked Locked Locked Manager
- Manager is an owner of a member’s parent.
Application: Work Status
Dimension WorkState
Account No
Category Yes
DataSource No
Entity Owner
Report Cur No
Time Yes
-Only one owner per application
-Workstate dims are ‘variables’
User: Excel > ESubmit > Modify W. Status
If work state is submitted, the owner of the entity
can create a journal. The Manager of the entity
in the data region can change the work state to approved.
If you attempt to input data in the above region, the sys
message is ‘submission status does not allow it’.
26
27. Entity Dim: Implied
Entity Hier Owner Reviewer Manager
US WW Pete Pete
Store1 US Joe Nadine Pete
Store2 US Sachi Nadine Pete
Task Profile:
Run Report ‘Act/Bud’
Run Input Template
Data Manager Package
Import, Copy
Data Access Profile
Finance App:
R/W Budget
R Store1
BPF: Entity = Drive Dim
Step1 Import Actuals
Step2 Copy to Budget
Step3 Input manual changes
Step4 Report Results
Sub Step A Run Report
Sub Step B Review Required
Step5 Lock Budget via Work
Status
User Actions: Joe
launches Planning BPF for
Data Region:
Store1
Budget
2009.Jan
(This will be the default
CV which can be changed)
Joe carries out Steps 1,2,3
And 4a,b , Nadine reviews
The report (4) on the
%Change and approves it!
Pete Locks the Budget
category by setting the
work status to ‘Approved’
for Store1, 2009.Jan
Work Status
Data Region:
Store1
Budget
2009.Jan
Pete
Work Data Status
State Manager Journals Manual Documents Comment Controlled By
In Process All All All All All Owner
Submitted Locked Owner Owner All All Both
Reviewed Locked Manager Locked Locked Locked Manager
Approved Locked Locked Locked Locked Locked Manager
BPF, Work Status, Security
Integration
27
33. 33
If you need to revise your BPF Template
Change the template
Inactivate the existing instance
Archive the instance
Create and activate a new instance
Note: you can only have one instance for a give data region
per template.
36. Result of Cur Tsl & US Elimination
Data Load
Currency Translation
Run US Elim
11301100 is Intercompany AR
21171000 is Intercompany AP
Time Flow Account D.Src Entit Intco Group Category Cur Amount
36
37. Result of Cur Tsl & US Elimination – Using Groups
Note: this elimination is at 100%
Time Flow Account D.Src Entit Intco Group Category Cur Amount
38. 38
How To Set Up Multiple Group Currencies
Add the currencies to the G – Type dimension:
Run Consolidation:
41. Consolidation Business Rules
The Consolidation business rules use 3 accounts primarily: METHOD, POWN, AND
PCON.
METHOD is used to store the assignment of the parent method code (90) or purchase
method code (86) to an entity and intercompany member for example.
POWN is used to store the ownership % for a parent’s subsidiary and is used in a
formula to calculate a value to be booked . Ownership elimination could be achieved
with only POWN. However, both POWN and PCON can be used to reduce the number
of rules that are needed.
PCON also has its (% consolidation) values stored in the ownership cube. PCON for a
purchase entity is usually 1 but PCON for an equity member is usually equal to POWN
since the equity subs books are not fully included in the group.
Therefore, if you store a value of 100% for entities using the purchase method and
PCON(.30 for example) equals POWN(.30) for entities using the Equity method, the
same rule could be used for both.
For example, to calculate a minority share account with an equity sub, minority Interest
should be zero (PCON(.3))=POWN(.30)) but with purchase sub, minority share should
be 80% ie (PCON(1.00) – POWN(.30)).
Note: PCTRL - Percent Control can also be used to have the system generate
proposed methods, PCON, and POWN values.
43. 43
Ownership Transaction Data
Note: The o_acct member ‘pgroup’ is used to identify which entities are included
in the consolidation group. The ownership calculation counts the members in each
cons group and assigns the number to each one. For example, C2000 is the 2nd
member
in the G_CG2 group. In our example in class, the ownership calculation will also calculate
the POWN values for G_CG1.
44. Here’s how the ownership values and org structure relate:
1. The two entities in cons group CG2 are C1000 and C2000 (they both have a value
in the pgroup account.)
2. The parent(90) of CG2 is C1000. The sub owned by C1000 is C2000 @ 80%
and is using the purchase method (86).
45. POWN data is initially entered for the NON_GROUP member of the group
dimension.
The ownership calc package copies the POWN data to groups id’s such as G_CG2,
calculates the pown values for CG1, and numbers the members in each group:
46. ample 1: Purchase method for C1000 & C2000 (BPC 7.5 SP 3)
You could use ‘PCON’ here as well since is stored as 1 in this case.
You can use PCON-POWN or 1-POWN
The ‘ALL’ account will receive a value w/ the opposite sign of the source
account.
The Group/Minority account will receive a value w/ the same sign as the source
account.
47. Example 1:
This is the test data file in LC:
This is the result: (values in USD group currency)
In this example, only two business rules were used to generate 3 postings.
54. Result of IC AP AR via ‘Automatic Adjustments’
Data Load
Currency Translation
Run Consolidation
Time Flow Account D.Src Entity Intco Group Category Rpt Cur Amount
54
55. Result of COI PUR METHOD via ‘Automatic Adjustments’
Data Load
Currency Translation
Run Consolidation
Time Flow Account Src Entity Intco Group Category Rpt Cur Amount
55
72. 72
Number of Appsets: Criteria
•Appsets have their own dims and apps
•BPC reporting is within an Appset
•BW reporting is truly global however(1)
•Task security is by Appset: for example the task ‘dimension’ allows a user to
to add, delete, change properties/members for any dim in an Appset.
•Member access security is by Application by member
•You can do cross application planning within an Appset
•In a production environment, you can have multiple Appsets
•Each Appset is an ‘InfoArea’ in BW
•Master data is unique per Appset > sync issues?
(1) BW reporting on BPC Infocubes is not supported in most cases
since revenue would be displayed as negative values for example.
Also, balance sheet values could be double counted with regard to time.
74. 74
Process Chain(Package)
Run Calcaccount
Fx Restatement
IC Booking
Consolidation
Opening Balances
IC Elimination
Validations
Script Logic
Calcaccount
FXTrans
IC Booking
Consolidation
Opening Balances
IC Elimination
Validations
Bus Rule / P.Chain / Logic Naming
75. 75
Who does what
Basis – installation, transports
BW security – SAP security people
BPC security - SAP security people or Project Team
BW developers – BW data staging and loading
BPC Admin – work in the Admin Console, maintain apps, dims, etc
BPC Excel users / analysts – use the Interface for Excel
Business Requirements & Modeling – Consultants and BPC super users
Separate consultants for planning vs. consolidation
Templates – Consultants, BPC super users
Logic – Consultants, BPC super users
ABAP - Consultants
76. 76
Any script in the default logic file runs whenever data is input, written via
data manager package, and journal entry (if there is no journal.lgf file)
Journal.lgf file only runs for journals to do example, offsetting entries for cross
entity journals.
A Note About Default Logic
77. 77
MS - Data Import Options
1. Flat Files
2. SQL table to table packages
3. Pure sql import w/o using bpc, with SSIS (DTS) packages
4. Data Services: came w/ BOBJ can be along FIM (financial int management)
Etl tool very flexible, use this to feed data to MS w/o flat files
BPC App
3 ways to write data to an application via BPC
1.Data manager package
2.Manual input
3.BPC Journal entries
BPC supports identical id’s across dim’s … but it should be avoided.
cc_sales pc_sales
94. 94
Eliminations made easy
All legal subs are 100% owned
Import trial balances
Run cur tsl
Matching
Run US Elims
Full Blown Consolidations
Legal subs mix of ownership %’s
Import trial balances
Run cur tsl
Matching
Run Eliminations and Adjustments
97. Result of Cur Tsl & US Elimination
Data Load
Currency Translation
Run US Elim
11301100 is Intercompany AR
21171000 is Intercompany AP
Time Flow Account D.Src Entit Intco Group Category Cur Amount
97
98. Result of Cur Tsl & US Elimination – Using Groups
Note: this elimination is at 100%
Time Flow Account D.Src Entit Intco Group Category Cur Amount
This slide illustrates the SAP Business Planning and Consolidation, version for the Microsoft platform architecture.
SAP Business Planning and Consolidation, version for the Microsoft platform has the same architecture as SAP Business Planning and Consolidation 5.x.
BPFs, Work Status, and Security can’t be built in a vacuum. The developer needs to know about all three. For example, if an action is put into a BPF, then the user will need to have rights to perform that task in security.
UJ_VALIDATION – Set up characteristic validation.
UJ00 – View data locking parameters. (It is not recommended to change the delivered settings)
UJBPCTR – Create transport request.
UJBR – Use this to create a backup for an appset including master data and tran data. (if you need to copy an appset and ‘paste’ it into another server). This does not replace the transport mechanism.
UJFS – The file system for bpc reports, logic files etc.
UJKT – The debug program for script logic.
UJQ0 / UJR0 – settings for the lock mechanism. Not recommended to change the delivered settings.
UJSTAT – The screen to analyze bpc statistics.
UJUT_DATA – This is a new program. Used to test file uploads/downloads.
Parity with Microsoft, but in addition, we support the display of multiple hierarchies in a comparison way.
Parity with Microsoft, but in addition, we support the display of multiple hierarchies in a comparison way.
Mention that some industry and functional-focused separately priced apps are also built out on BW-IP ex MAP and PBF, and will be built on the new advanced planning platform ex. TPM
