Project DISHA - Phase 2

Profitability Analysis
CO-PA
Reporting & Planning
COPA Reporting
CO PA – Profitability Reporting
COPA – Reporting
•CO PA is tool for cost margin calculation & cost allocation derivation based business requirement, It prepares only profit margin Data for reporting. It is used for real time cost allocation for direct cost. COPA has capability to set up complex rule for allocation logic

•CO PA reporting user experience is very poor, CO PA reporting is not user friendly from start of SAP R3 and ECC Version

•Best approach for deriving COPA reporting is from BW system.

•CONS for Reporting in COPA

•COPA Standard reports are not user friendly & suitable for analysis
•Limited reports KE30 & KE31 – Basic PNL report with Grid view in COPA
•COPA reports does not have the capabilities for dicing/slicing data with required dimensions
•With huge volume of Retail data, COPA reports will get impacted with slow performance
•Customized report formats are not easy to build in COPA system, SSL has all complex formats for Margin reporting requirement

•PROS for Reporting in BW

•BW reporting is very much flexible in analysis, It gives all required functionality for dicing/slicing with required dimensions
•BW reporting is easily manage Huge retail volume data
•As perSSL current landscape & design, mostly all other reports are deriving from BW system only
•BW is capable to use as a Single Repository for all other systems data. Those data can be used for different reporting requirement
•Currently also other systems like CAR, Vistex, S4 & BPC data are flowing to BW system for report designing
•BW system has many capabilities like Direct upload flat file, easy integration with SAP or future Non SAP system for reporting
•BW report designing efforts are lesser compare to ABAP reports in S4 system

•
COPA Planning
CO PA – Profitability Planning
COPA – Planning

•CO PA is part of S4 system and allow better integration with S4 Actual Data for planning comparison, But It is not great in user friendly and reporting part. CO PA typically is performed bottom up planning

•In SSL, we have already implemented BPC for Cost Center & Profit Center level planning. Currently L5 & detail level expense planning is not carried out in SSL

•CO PA planning is required, where profitability segments for analysis are different than BPC measuring planning dimensions.

•CONS for Planning in CO PA

•CO PA has the functionality to allocate planning at L5 level from a higher level planning , but it has lot of limitation and it is very rigid for execution
•Projections & What if analysis are not possible in CO PA module
•Add or Change for any new measuring dimensions are very difficult
•CO PA is very poor in reporting aspects, so Actual vs planning reports are difficult to design in required & complex format
•No SAP standard reports delivered for Planning comparisons, need to design through customization or through report painter

•PROS for Planning in COPA

•BPC is new module from SAP for addressing business planning requirement
•BPC has many advantages over COPA, like User friendliness, excel sheet looks experience, easy to create different planning version, shared reporting tool with multiple users can be working with same time & real time
•BPC is implemented on BW database, so Actual vs Planned data reporting can be achieved easily through BW
•Simple data transfer from CO PA to BPC/BW, S4 to BPC/BW for reporting requirement
•Already implemented BPC solution in current SSL landscape, so no additional licence cost expenses
•Single place for Planning solution, Any future requirement changes like New version, New dimensions & New templates are easy to accommodate in existing BPC system
•SAP Best Approach – BW is for CO PA reporting, BPC is for CO PA planning

•&
Planning – User Experience with BPC
Planning – User Experience with CO
PA