Learn how to gain enhanced analysis capability with US Eliminations in SAP BPC Paul Rafferty, eBay PayPal Vish Arunachalam, Perceptive Technologies
[ Todays speakers
Paul Rafferty
SAP Functional Lead
Vish Arunachalam
Principal, EPM AdvantageFinance
eBay PayPal
prafferty@ebay.com
Perceptive Technologies
vish@perceptinc.com
www.ebayinc.com
www.perceptinc.com
AdvantageFinance
[ Learning Points
Learn what it takes to enable enhanced analysis capability with US eliminations in BPC Get real-world tips and lessons learned with designing US Eliminations in BPC Understand typical challenges faced during intercompany elimination analysis while using US eliminations in BPC
ECC - ERP
NonSAP Data
[ US Eliminations
BPC US Elimination process addresses simple intercompany requirements in financial application, where a full legal consolidation application is not required Multiple lower level legal entities related data is eliminated at first common parent Consolidation Task US widely used Intercompany Elimination uses:
Process Chain /CPMB/IC_ELIMINAT ION Script Logic ICELIM.LGF Business Rule Table US Elimination
[ US Eliminations - Prerequisites
The application must include a dimension of type I, Intercompany The Intercompany dimension must include the property ENTITY, whose values are entity names The account dimension must include the property ELIMACC, whose values are account names The entity dimension must include the property ELIM, whose values are Y or blank. The appropriate business rule table and DTS must be set up
[ Illustration: IC Elimination
Parent A
Elimination Entity A Legal entity X Legal entity Y
Legal entity M
Legal entity N
All eliminations between X, Y, M and N are eliminated at Elimination Entity A Reconciliation is a challenge when too many children roll up under a single parent elimination entity
Real Experience. Real Advantage.
9
INPUT
2011.SEP
250000
-5000
10
Note: To simplify scenario, the ELIMACC records are excluded in above table
11
Note: Data Model includes additional user defined dimension Z Legal Entity
13
Amount $ -50000
A
A A A A
ELIM
ELIM ELIM ELIM ELIM
Y
M Y N Y
2011.SEP
2011.SEP 2011.SEP 2011.SEP 2011.SEP
250000
122000 250000 122000 250000
X
Y M Y N
50000
-23000 23000 -5000 5000
Note: To simplify scenario, the ELIMACC records are excluded in above table
14
[ Demo
BPC NW with Basic US elimination and US elimination with enhanced analysis enabled
15
Note: Extract of BW Data in CPMB info cube shown to illustrate granularity of data under both scenarios
Real Experience. Real Advantage.
16
17
Adding additional user defined dimension for Entity will allow retention of granularity at Elimination Entity, Trading Partner and User Defined Entity
18
[ Best Practices
IC Reconciliation is often a challenge in close process, address this upfront Consider post IC elimination review and analysis process and pain areas as critical input for designing optimal data model for BPC consolidation Consider all possible dimensions required for Consolidation (Legal and Management)
What views of data do you need supported at the underlying ledger? Consider system performance implications with adding dimensions? Define and activate all potentially required dimensions on day one to avoid complex and costly changes later
Real Experience. Real Advantage.
19
[ Key Learnings
Deficiency in data model could adversely impact close process Facilitate reconciliation by addressing granularity of IC Elimination data Dont lose granularity post IC elimination. More detail and granularity is appropriate Optimal data model for consolidation will minimize reporting and analysis challenges during financial close
20
[ Q&A
21
[ Thanks!
Paul Rafferty
SAP Functional Lead, eBay PayPal
prafferty@ebay.com
22
]
23