COPA reporting challenges and HANA
Download as PPTX, PDF4 likes3,858 views
The document discusses various reporting solutions for companies facing challenges with COPA reporting, emphasizing the use of SAP HANA, BW, and accelerators to enhance performance. It clarifies that while SAP HANA and BW are complementary, significant investments continue to be made in both platforms. Key strategies include building out COPA with enhancements, using HANA Live for direct reporting, and implementing a BW data warehouse for robust data management.
COPA reporting challenges and HANA
- 1. 2/25/2014 www.infogility.org HANA Reporting JOHANNES.LEROUX@INFOGILITY.ORG
- 2. What does other companies with COPA reporting challenges do? 1. Remove the Pain Use - COPA HANA Accelerator (Operational Reporting in ECC) 2. Move to BW to get better Performance - BW on HANA (Transformation, Periodic www.infogility.org 2 Reporting, History) 3. Convert ECC Platform – HANA Integrated (Operational Reporting) Most companies use a Hybrid solution to support corporate historic data for legal & financial reporting
- 3. HANA and BW Q: Is SAP still investing in BW or is BW Dead? A: Yes! Significant investments were made in latest releases of BW and enhancing solutions on the BW platform e.g. BPC 10.1 Q: Does HANA replace BW? A: No! They are different solutions complementing each other Q: Is BW better on HANA? A: Absolutely! Significant performance improvement in run times, www.infogility.org 3 extraction times and data storage
- 4. www.infogility.org 4 Options 1. Build out COPA to maintain calculation and data there (requires prerequisites and accelerator enhancements) 2. HANA LIVE 3. BW Data warehouse and HANA
- 5. 1. Build out COPA to maintain calculation and data Pro’s Con’s IT’s Reporting strategy Allocation of data to correct levels in ECC – This will require COPA enhancements www.infogility.org 5 Optional - No Reporting performance if HANA COPA Accelerators implemented Reports not as flexible – Need to use REPORT PAINTER Will be a good base to support HANA LIVE, and MS data warehouse Performance issue if HANA COPA Accelerators not implemented Us BOBJ reporting directly from ECC to provide one touch and dashboard reporting – Optional Data in ECC – Reporting requirement met and no record limitation issues Required changes needed 1. Optional Implement HANA accelerator to speedup COPA (1-2 month implementation time line) 2. Extend COPA to support ( allocations) – This will include enhancement and development 2. Create reports in ECC COPA - REPORT Painter or BOBJ
- 6. 1. Build out COPA to maintain calculation and data BOBJ REPORTING FRONTEND (Optional) OPTIONAL – COPA HANA Accelerator to help with performance ERP application data (transactional data) www.infogility.org 6 Existing Stack SAP ECC Business Suite (ERP, CRM, SCM,…) AnyDB HANA DB Accelerated read Table replication
- 7. www.infogility.org 7 2. HANA LIVE Pro’s Con’s IT’s Reporting strategy All data in ECC Database / no Long term data storage available One touch reporting capability – If all data is in the same format and levels as required Achieving of ECC data limited to year to year comparisons required in reporting No manual data process to build data set for reporting Microsoft strategy to include achieving data in reporting will be complex because modeling is in HANA and achieved data will be in ECC format Dashboard capability based on each required level of reporting in BOBJ Allocation of data to correct levels in ECC – This will require COPA enhancements No Reporting performance issue due to HANA Allocation of data to correct levels in ECC will impact ECC performance if no COPA HANA accelerator implemented Required changes needed 1. Optional - COPA HANA accelerator will be required to limit any ECC performance impact 2. Extend COPA to support ( allocations) – This will include enhancement and development 3. Create required Modeling structures in HANA LIVE 4. Create required reports and DASHBOARDS in BOBJ 5. Only available 3rd QUARTER 2015 – Finance not on 2015 roadmap
- 8. SAP ECC Business Suite (ERP, CRM, SCM,…) OPTIONAL – COPA HANA Accelerator to help with performance Accelerated read ERP application data (transactional data) www.infogility.org 8 2. SAP HANA Live Sidecar Approach SAP HANA BOBJ Design Studio Crystal Reporting SAP HANA Live BOBJ REPORTING FRONTEND Existing Stack AnyDB HANA DB Table replication Replication
- 9. 3. BW Data warehouse ON HANA Pro’s Con’s www.infogility.org 9 IT’s Reporting strategy Significant Improvement in Performance Significant Improvement in Data Storage Space All data in BW Database / Long term data storage available to do comparison reporting Achieving of ECC data not impacting Profitability reporting No data based record limitation/Performance issues to extract and store data Automated data transformation to build data set for reporting One touch reporting capability Dashboard capability based on each required level of reporting in BOBJ Allocation of data to correct levels can be in done BW Delta load can be done throughout the month to limit impact on ECC Requirements 1. COPA database in BW Data warehouse 2. BW data warehouse 3. Optional - COPA HANA accelerator will be required to limit any ECC performance impact 5. Create required reports and DASHBOARDS on selected front end
- 10. 3. BW Data warehouse ON HANA Existing Stack SAP ECC Business (ERP, CRM, SCM,…) OPTIONAL – COPA HANA Accelerator to help with performance Accelerated read ERP application data (transactional data) www.infogility.org 10 SAP HANA Suite AnyDB Replication BOBJ Design Studio Crystal Reporting SAP HANA Live BOBJ REPORTING FRONTEND BW HANA DB Table replication