SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – Project Planning

Agenda

• General Information
• Customizing
• Data provisioning
• Allocations
• ERP Reporting and Acceptance and Performance Test in CO-PA

SAP HAHA appliance software (SAP HANA^TM)

SAP HANA is a data source agonistic in-memory appliance that enables organizations to analyze business operations in real-time based on large volumes of data

SAP HANA appliance software (SAP HANA ^TM)

Preconfigured Analytical  Appliance

In-Memory software + hard ware’s (HC, IBM, Fujitsu, Cisco)

In-Memory Computing Engine Software

Data Modeling and Data Management Real-time Data Replication via Sybase  Replication Server

Data Services for ETL capabilities from SAP Business Suite, SAP BW and 3^rd party Systems

Capabilities Enabled

Analyze information in real-time at unprecedented speeds on large volumes of non-aggregated data

Create flexible analytic models based on real-time and historic business data

Foundation for new category of applications

(e.g.planning, simulation) to significantly outperform current applications in category

 Minimizes data duplication inter

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA

CO-PA, powered by SAP HANA is an extension of you existing landscape

• Primary data storage stays in ERP and the underlying database
• SAP HANA platform hosts a derived data set for fast aggregations and data retrieval

   No Change to you existing CO-PA configuration required

• Existing reports can be used as-is enjoying significant acceleration
• Existing allocations will be accelerated

     Additional Usage patterns are optional for an additional service cost

• Use SAP HANA to report on CO-PA data and other data sets via Business Objects frontends
• Enrich your ERP reporting by connecting Business Objects frontends
• Extend your level of detail in Co-PA to take full advantage of the power of SAP HANA platform

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA   SAP In-Memory Computing

Typical Business                                  Needs                                                   Expected benefits

Challenges                                      

Business performance can         Accelerated reporting and                  Better commercial decision

be impacted by long                      month-end closing processes            making pricing, discounts, sales

reporting and month-end                                                                                   strategy etc.

closing runtimes

Limited profitability insight      Flexible CO-PA reporting, not           Optimized month end close

and root-cause under-                  limited in data scope

standing due to large data

sets

SAP ERP rapid-deployment solution for profitability Analysis with SAP HANA Today

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA Today – many customers using BW for Co-PA reporting

SAP ERP rapid – deployment solution for profitability analysis with SAP HANA The solution

Accelerated

Accelerated Co-PA Reporting  Accelerated ERP CO-PA Allocations

Improved Reporting

 Business User driven data analysis  instant response times

Eliminated data boundaries

No pre-defined data aggregation  levels  Complete life-time, line-item analysis

Deeper Insight

 High-volume and ad-hoc data queries   No limitations to  reporting dimensions

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA overview

In-scope:

• Costing-based CO-PA
• Enhanced CO-PA read module using SAP HANA as secondary database for

  • Acceleration of ERP reporting
  • Acceleration of ERP allocations reading data from CO-PA tables (i.e. variable reference base in CO-PA) by accelerating the selection during allocation

• Customizing transaction for activating acceleration
• Application-specific data provisioning into SAP HANA (transaction data only)
• Generation of required table and views in SAP HANA automatically by ERP w/o manual activation in the SAP HANA studio 

Out-of-scope:

• Account-based CO-PA
• Additional functionality in application
• Changes to allocation functionality or processing logic

SAP ERP rapid-deployment solution for profitability analysis with HANA

Agenda

• General Information
• Customizing
• Data Provisioning
• Allocations
• ERP Reporting and Acceptance and Performance Test in CO-PA

SAP ERP Rapid-deployment solution for profitability analysis with

SAP HANA – customizing

Introduction

CO-PA accelerator has been built with 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 (SLT, Sybase, BO Data Services)

You will find customizing transaction kehc in the CO-PA branch of IMG (transaction SPRO).

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Prerequisite – creating the database connection

Before customizing the CO-PA accelerator, you will need to create a secondary database connection

• Create database user in HANA
• Table DBCON can be maintained via transactions SM30 DBCO

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Proposed naming conventions for DB user + DB connection

For the data base user on HANA database

You will need to create at least one dedicated user on the HANA database. Please make sure that the DB user is different for each ERP system and ERP client you use. The DB user will determine the database schema where the tables and content will be created. It is thus essential to separate data and structures from different source systems by database user respectively schema.

We suggest creating database users on the HANA database according to the following template:

ERPACC+<XXX> with XXX being the logical system name of your ERP system

Example: your ERP system’s identifier is AAA, your logical system for client 001 is likely to be called AAACLNT001, so please create a database user ERPACC_AAACLNT001 with a default schema ERPACC_AAACLNT001. This user will be used in the secondary database connection defined in the ERP system.

For the database connection / DBCON entry

For the database connection name in table DBCON, please use the following naming convention:

<SID of HANA database>_<Username for connection>

Example: Your HANA system’s identifier is HA1, your ERP’s logical system name is AAACLNT001, then you should call the database connection HA1_ERPACC_AAACLNT001.

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Transaction kehc – basic settings

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Transaction kehc – optional read mode settings

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Excursus: understanding the read access/1

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Excursus: understanding the read access/2

You can fine-tune the read behavior and selectively use HANA as data source.

• Applicable if processes run faster on the traditional database
• Applicable for phased go-live so only pilot users will be redirected to HANA
• As a safely measure to define some reports to show data from traditional database instead of HANA

When reading from HANA, the CO-PA read function module will not access the copied tables directly but rather a runtime object (column views).

• This access method has been chosen for optimum performance.
• You can force access to copied tables in the read mode settings (useful if read access breaks).

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Understanding safety buffers

The CO-PA read function module will combine data from HANA with data from the original line item table.

• Idea: Data replicated to HANA is selected from there, data out yet replicated to HANA is selected from the original table
• Decision criterion is the read access timestamp of the last ------- run
• You can switch off this data federation in the bash settings and only read from HANA.

When using an alternative replication mechanism, the CO-PA application does not know the last timestamp transferred into HANA.

• You have to manually set a safety buffer

  (= maximum time you expect the replication to take).

• Any data before will be read from HANA
• Any more recent data more will be read from the original tables.

If replication gets stuck for longer than the safety buffer, you will miss data in your reporting!

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Safety buffer for alternative replication

The safety buffer for alternative replication determines the interval granted for replication to finish / not selected in read access.

No further timestamp information is known.

Safety buffer for alternative replication

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – Customizing

Safety buffer for Co-PA replication

Safety buffer for CO-PA replication

The safety buffer for CO-PA replication determines the interval granted for update processes to finish / not selected in replication run. The timestamp of the read access timestamp in last replication run determines which data is read from HANA and which from the original table

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

How to decide which replication is right for you?

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – Customizing

Checklist

The 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 alternative replication):

• Connect HANA with ERP at DB connection
• Replicate metadata and activate continuous data replication of tables CE1xxxx, CE2xxxx, CE4xxxxusiing 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)

SAP ERP rapid-deployment solution for profitability analysis with SAP HANA – customizing

Background information

Transporting your customizing

• Transports currently not supported to avoid interference between different systems in landscape

Relevant tables for customizing & status:

• TKEHACC for basic settings
• TKEHDBLCR for status and replication time
• TKEHDB_RANGES for read mode settings

Agenda

• General information
• Customizing
• Data Provisioning
• Allocations

ERP Reporting and Acceptance and performance Test in CO-PA

SAP ERP RDS for profitability analysis with SAP HANA – data provisioning

Prerequisite for using CO-OP replication program

2 replication programs are available

Regular CO-PA replication program

• Transaction KEHW / report RKE_HDB_WRITE_DATA
• Transfers the items (CE1, CE2) and segment data (CE4) if realignment has ------- in customizing (transaction Kehc)
• Generates tables in HANA and inserts data
• To be scheduled periodically

Realignment replication program

• Transaction KEHD / reportRKE_HDB_WRITE_REALIGNMENT_DATA
• Transfers only CE4 data which could not be transferred during realignment run execution
• To be executed on demand only

SAP ERP RDS for profitability analysis with SAP HANA – data provisioning

Using the CO-PA replication program / transaction KEHW

Actual and plan line items are always transferred (CE1 and CE2)

Realignment data (CE4) are transferred if customized in kehc – basic settings

SAP ERP RDS for profitability analysis with SAP HANA – data provisioning

Performance & frequency considerations

Initial load can take substantial time

Measurements are showing 3-20 mio CE1 records per hour. Bottleneck is rather on reading the traditional database.

Example: 60 mio records in CE1 + 4 mio records in CE4 => --  hours processing

NO downtime is required

CO-PA reporting and processing can continue, HANA accelerator will not become active before data has been transferred

Schedule the program frequently to ---- id long reading time from traditional database

CO-PA read function module will federate data from HANA and from original tables The more frequent you run the replication, the less data needs to be read from the original tables

Proposal: Schedule replication program once per day. Analyze performance trace. If read access to original table consumes more time than HANA access, increase the frequency.

CO-PA accelerator should decrease total load on traditional database.

SAP ERP RDS for profitability analysis with SAP HANA – data provisioning

Segment table / realignment data

Relevant entries in CE4 table are automatically transferred during initial load

Changes to existing CE4 entries are transferred at the end of realignment run automatically

• Realignment accelerator status is set to red
• Application tries to replicate changed entries to HANA
• If successful, CO-PA accelerator becomes operational again
• If not successful, a message will be shown and status ------- red until program RKE_HDB_WRITE_REALIGNMENT_DATA has been run successfully