Hana for copa


Published on

Published in: Technology, Travel
1 Comment
  • For SAP online training register at http://www.todaycourses.com
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Hana for copa

  1. 1. SAP ® Customer Solution AdoptionKnow-How Network CallTwo Use Cases for Accelerated Profitability Analysis andReporting on SAP HANA™Jeffrey HoldemanOctober 5, 2011
  2. 2. CO-PA in ERP: Provides Highly Integrated Profitability Analysis forCustomer-defined Product-Market SegmentsFinancial Settlement of production variancesAccounting Production Sales Profitability Billing doc. MM PP SD Analysis CO-PA Product Costing Cost of goods manufactured CO-PC Cost allocation Cost center assessment FI-GL Overhead CO-OM Management Order settlement Direct postings from Financial Accounting © 2011 SAP AG. All rights reserved. 2
  3. 3. ®Press Release – SAP CO-PA Accelerator© 2011 SAP AG. All rights reserved. 3
  4. 4. Use Case 1 Use Case 2SAP CO-PA BI Reporting onAccelerator CO-PA Data in SAP HANA
  5. 5. SAP CO-PA AcceleratorBasic Architecture SAP GUI SAP BO BI 4.0 CO-PA Drilldown Reporting Dash- Crystal Analysis Explorer boards Reports SAP ERP HANA CO-PA application (ABAP AS) reporting on CO-PA data XML file XML Reporting Model Generator* CO-PA Read Access Optimizer SAP HANA Periodic Replication to HANA** Secondary DB connection SAP HANA Read interface traditional + HANA Modeling Studio** LT Generated Traditional DB In-Memory DB model** Replication** * Only used for BI/HANA reporting on CO-PA data ** Optional use of LT Replication© 2011 SAP AG. All rights reserved. 5
  6. 6. SAP CO-PA Accelerator Overview Technical Requirements Setup Benefits Customer Insights
  7. 7. Use Case 1SAP CO-PA AcceleratorAccelerating existing processes: SAP HANA In-Memory Appliance serves as secondary database for SAP ERP CO-PA line item data is replicated / written SAP UI into In-Memory in real time for secondary storage CO-PA User interface remains unchanged Data Modeling to ensure non disruptive acceleration SAP Computing Engine Business CO-PA application is accelerated by Read Suite reading the mass data from the In-Memory database Examples:  KE30 Execute Reports Traditional DB Replication SAP HANA  KE24 Display Line Items  KEU5 CCA to CO-PA Assessment  KE28 Top-Down Distribution© 2011 SAP AG. All rights reserved. 7
  8. 8. SAP CO-PA AcceleratorUnderstanding the Read Access CO-PA CO-PA CO-PA report allocation planning All CO-PA functions access data through a dedicated function module. Generally, this module determines the best data source in the traditional database CO-PA read function module (similar to an OLAP processor). With CO- PA accelerator, HANA becomes the best Data source determination data source by default. Segments Line items Totals Sum. Levels HANA objects ColumnView HANA HANA CE4xxxx CE1xxxx CE3xxxx K81.x K81.x CE1 CE4 HANA CE2xxxx CE2© 2011 SAP AG. All rights reserved. 8
  9. 9. Use Case 1 Technical PrerequisitesSAP CO-PA AcceleratorTechnical prerequisites for the SAP CO-PA AcceleratorAcceleration of ERP reporting and allocations On ERP side  Application coding  Netweaver  Netweaver Kernel  Database Client On HANA side  HANA 1.0 SPS 2© 2011 SAP AG. All rights reserved. 9
  10. 10. SAP CO-PA Accelerator Technical PrerequisitesUse Case 1 - Acceleration of ERP Reporting and Allocations ERP ERP 6.0 ERP 6.01 ERP 6.02 ERP 6.03 ERP 6.04 ERP 6.05 ERP 6.06 Application CO-PA Accelerator Coding ADBC classes + domain values ADBC + .. ADBC + .. NW 7.31 NetWeaver NW 7.00 NW 7.01 NW 7.02 Downward-compatible Kernel 7.20 Kernel Kernel 7.20 Kernel 7.20 replacing current Kernel 7.00 / 7.01 OS DB client for In-Memory DB to be installed on application server Initial OS support for SLES 11, SLES 10, Windows 2008, AIX 6.1, HP-UX 11.31 (IA64) und SunOS 5.10 (Sparc und X86) HANA HANA 1.0 SPS 2 or higher Secondary DB connection Requires upgrade / installation© 2011 SAP AG. All rights reserved. 10
  11. 11. SAP CO-PA Accelerator Technical PrerequisitesPlanned Schedule of Deliveries Delivery of CO-PA Accelerator with support packages Additional delivery via notes 1614438 and 1559994 through transport has been arranged forselected customersERP EHP EHP0 EHP2 EHP3 EHP4 EHP5 EHP608.11.2011 SP21 SP11 SP10 SP10 SP06 SP01RTC CW15 2012 CW15 2012 CW15 2012 10.10.2011 17.10.2011 08.11.2011NW EHP 7.00 7.00 7.00 7.01 7.02 7.31NW SP 26 26 26 10 09 01RTC 17.02.2012 17.02.2012 17.02.2012 26.08.2011 09.09.2011 Technical prerequisites regarding SAP kernel and HANA-DBSL  SAP Kernel 7.20 (DCK) with minimum patch level 90  Minimum HANA-DBSL patch level 92© 2011 SAP AG. All rights reserved. 11
  12. 12. SAP CO-PA AcceleratorCustomizingCO-PA accelerator has been builtwith the idea to be as non-disruptive as possible(“plug & play”) Customizing is simple Scenario can be activated by Operating Concern Customizing caters for replication via CO- PA program and alternative replication (LT, Sybase, BO DataServices)You will find customizing transaction 1KEHC in the CO-PA branch of theIMG (transaction SPRO). 1© 2011 SAP AG. All rights reserved. 12
  13. 13. SAP CO-PA Accelerator CustomizingChecklistThe necessary configuration steps depend on your scenario: You should perform configuration in the following sequence (for replication via CO-PA program):  Connect HANA with ERP as DB connection  Maintain configuration in KEHC  Start / schedule replication program You should perform configuration in the following sequence (for alternativereplication):  Connect HANA with ERP as DB connection  Replicate metadata and activate continuous data replication of tables CE1xxxx, CE2xxxx, CE4xxxx using your replication tool (e.g. SLT).  Maintain configuration in KEHC and choose alternative replication with an appropriate safety buffer  Generate Column Views using transaction KEHC (button on status tab)© 2011 SAP AG. All rights reserved. 13
  14. 14. Accelerated Profitability Reporting (Use Case 1)Benefits Advanced by SAP In-Memory Computing 1 Operating Concern ERP w/o ERP with Acceleration HANA HANA factor vs. 8 months of real customer data (benchmark (SAP test ERP provided by installation) ~ 85 Mio line items in CE1 table xxx) (1) (3) (1) / (3) ~ 33,000 customers EBIT with xxxx sales 280 sec 7 sec 40 ~ 27,000 articles – initial report (DB 2,8 sec)* EBIT with xxxx sales 620 sec 5 sec 124 – drilldown by …. (DB 2,9 sec)* Cost allocation analysis 45 sec 5 sec 9 – initial report (DB 3,4 sec)* Cost allocation analysis 260 sec 7 sec 37 – drilldown by cost center (DB 3,3 sec)*  Additional drilldowns are now possible e.g. by customer and article (not feasible before)  Drilldown performance not dependent on availability of suitable aggregation level, selection always on line item level from In-Memory Database  Existing ERP reports are accelerated with no changes to report definitions *DB measurements show the selection runtime on HANA. Non-DB time is likely to decrease if the application server runs on production hardware. © 2011 SAP AG. All rights reserved. 14
  15. 15. Accelerated Profitability Allocations (Use Case 1)Benefits Advanced by SAP In-Memory Computing85 Mio. line items, allocation of overhead cost to single products based on sales qtyClassic DB SAP HANA DB >1h reading time for reference data (runtime  <30 sec reading time for reference data! for specific scenario) (runtime for specific scenario) Search only possible with index support or  <1 sec search time for data w/o product further “tricks” assignment (to be allocated) Time-consuming optimization of pre-  No data aggregation levels required, any calculated data aggregation levels allocation anytime depending on allocation needs© 2011 SAP AG. All rights reserved. 15
  16. 16. Use Case 1Customer InsightsReporting performance Activate HANA parameterforce_analyze inindexserver.ini/parallel  Automatically tries to generate an OLAP model for each query if possible  Caution: can sometimes lead to decreased performance for other HANA use cases (such as SQL joins), if no OLAP model can be constructed© 2011 SAP AG. All rights reserved. 16
  17. 17. BI Reporting on CO-PA Data in SAP HANA Overview Technical Requirements Setup Benefits Customer Insights
  18. 18. Use Case 2 OverviewBI Reporting on CO-PA Data in SAP HANAAccelerating operational reporting: CO-PA data is replicated / written into the SAP HANA In-Memory Appliance for secondary storage SAP HANA Studio client is used to create 3rd Party BI Clients information models BICS MDX SQL  Note: report models are available as RDS (Rapid Deployment Solution) Data Modeling BI frontends are used to display the data SAP Computing Engine Examples: Business Suite  SAP BusinessObjects Explorer  SAP BusinessObjects Analysis, Office Edition  SAP BusinessObjects Web Intelligence  Microsoft Excel Traditional DB Replication SAP HANA© 2011 SAP AG. All rights reserved. 18
  19. 19. Use Case 2 ScopeBI Reporting on CO-PA Data in SAP HANABI reporting on CO-PA data in HANA can be implemented based on data ofany ERP system from R/3 4.6c onwards.You will need: Data provisioning via replication tool (i.e. LT tool), potentially on separate server Attribute views, analytic views, calculation view on HANA (either manually or via transaction KEHA) For generating attribute views and analytic views automatically via transaction KEHA (XML generation), you will need to apply the same support packages / notes as for use case 1What you do not need in this use case: Customizing on ERP side Kernel or Netweaver updates on ERP system (unless required for replication tool) Secondary database connection from ERP to HANA© 2011 SAP AG. All rights reserved. 19
  20. 20. Use Case 2 Data ModelCO-PA XML GeneratorCO-PA XML Generator for SAP HANA 1.0 Dynamic CO-PA Data Models are transformed into an XML file  Transaction KEHA Uploading the XML file into the HANA modeling studio speeds up modeling Upload into Generate XML Files Modeling Model Studio XML Generator report available from SAP Note 1627568© 2011 SAP AG. All rights reserved. 20
  21. 21. Use Case 2 Technical PrerequisitesBI Reporting on CO-PA Data in SAP HANATechnical Prerequisites for the BI Reporting on CO-PA Data in SAP HANA On ERP side  Application coding for automatic XML model generation On HANA side  HANA 1.0 SPS 2 Replication tool (with its own technical prerequisites)© 2011 SAP AG. All rights reserved. 21
  22. 22. Accelerated Profitability Reporting (Use Case 2)Benefits Advanced by SAP In-Memory Computing 120 Mio. line items, report on product-related dimensions for a single companyClassic DB SAP HANA DB Several minutes (runtime for specific  Less than 1 sec (runtime for specific scenario) scenario) Pre-calculated data aggregation levels  Directly on line item level  No pre-calculated data aggregation levels Processing time for next navigation step required depends on if aggregate exists  No limit on drill-downs and details Parallel drill-down to multiple dimensions  Data immediately available for reporting, no may not be possible anymore waiting on data load processes to data warehouse© 2011 SAP AG. All rights reserved. 22
  23. 23. Use Case 2Customer InsightsReporting performance Oct-19 KHNC webinar How to best leverage SAPBusinessObjects BI 4.0 on SAPHANA 1.0 by Patrice Le BihanData Provisioning (in POCs) Extraction Methods  Flat Files  DB Backups  R3LOAD Physical Delivery Interactive OLAP Dashboards Analysis Analysis Data Load Methods Data  Data Services Reporting Exploration  Scripts  R3LOAD© 2011 SAP AG. All rights reserved. 23
  24. 24. Function Module: RKE_FILL_FIELD_TABLETransaction SE37Function Module:RKE_FILL_FIELD_TABLEInput:ERKRS = Operating ConcernPA_TYPE = 1 (Costing-basedCO-PA)Execute:Click on F8 Run Single TestClick on FIELDTAB result to viewcontents© 2011 SAP AG. All rights reserved. 24
  25. 25. FIELDTABMaster DataTablesShown fromFIELDTAB incolumnCHECKTABLEScroll down andtake note of eachof the masterdata tablesneeded© 2011 SAP AG. All rights reserved. 25
  26. 26. Accelerated Profitability Analysis and ReportingWhich Use Case is Best for my Customer? Acceleration of BI reporting on Customer wants to … ERP reporting CO-PA data and allocations in HANA Speed up allocations in month-end process  Keep existing ERP reports / protect investment  Keep existing ERP authorizations & user concept  Eliminate summarization levels in CO-PA  Business-user frontend instead of ERP reporting planned  Real-time access to data instead of waiting for data   warehouse processes to finish Drill-down on lower level w/o performance penalty   Unlimited drill-downs on line item characteristics ()  Combine CO-PA data with other data sources  Avoid any change to ERP system or minimum ERP  and Netweaver levels are not in reach© 2011 SAP AG. All rights reserved. 26
  27. 27. Positioning CO-PA Accelerator and BW / BWA
  28. 28. CO-PA Reporting with SAP BW / BWA or CO-PA AcceleratorPositioning SAP BusinessObjects BI SAP BW SAP HANA Analytic Engine (Queries) HANA Models BW Architected Data Marts Enterprise Data Warehouse Design and Operations Data Acquisition (DataSources) DataSources SLT Replication or 1_CO_PA_* 2nd DB Connection SAP Business Suite  Corporate View on Information  Operational View on Information  Company wide Reporting on „standard“ data is key  Agility and Flexibility in local business process is key  BW Analytic Engine features required  Operational Excellence in Closing Process  „Snapshot“ reporting / latency is not an issue  Reporting on real time data required This presentation and SAPs strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.© 2011 SAP AG. All rights reserved. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. 28
  29. 29. CO-PA Reporting with SAP BW / BWA or CO-PA Accelerator Technical Considerations HANA Calculation logicCalculation  BW Analytic Engine / BWA offer manylogic calculation features “out of the box”  Many possibilities with calculation views but deep technical expertise required  BWA 7.20 Composite Provider can do ModelingModeling some but not all join logic  More Join types  SQL available for further join logic  Data in InfoCubes on disk need to be RealignmentRealignment replicated into memory - Compressed into BWA but inherent duplication.  No realignment needed Roadmap  BW on HANA  BWA 7.20 last official BWA releaseRoadmap  All SAP Applications on HANA as “RDBMS” © 2011 SAP AG. All rights reserved. 29
  30. 30. Positioning CO-PA Accelerator and PCM
  31. 31. Customer and Product Profitability Challenges using only CO-PA  Operating concern design depends on PCM choices made in customizing  Sign handling, cost element types, Prebuilt Data ModelComplexity mappings  Standard model types  Many allocation methods to transfer costs  Predefined dimensionality in CO  Simple assignment screens  Customizing is owned by IT Trust and Visibility of DataAdaptability  Integrated planning is difficult and inflexible  Less IT involvement  Reconciliation between G/L and CO-PA  Simplified data flow  Trace back of results  CO-PA used for only margin reporting Full P&L Reporting  Unassigned characteristic values  Customer & Product P&L’sSuitability  Granularity / Performance trade-off  Many built-in best practices  Transactional costing if needed © 2011 SAP AG. All rights reserved. 31
  32. 32. Thank You!Contact information:Jeffrey HoldemanAmericas Regional Team | Customer Solution Adoption | Solutions GTM