Expert Guided Implementation

SAP HANA® Profitability Analysis

Day 2

© 2013 SAP AG. All rights reserved. Customer 1

Agenda
1. Day one
Expert Guided Implementation Methodology and Motivation
Check of prerequisites

2. Day two
Replication via CO-PA program
Configuration of CO-PA acceleration scenario

3. Day three
Alternative Replication (SLT)
Demonstration –before and after

4. Day four
Modeling using SAP HANA
© 2013 SAP AG. All rights reserved. Customer 2
5. Day five
Configuration of CO-PA
scenario
SAP CO-PA Accelerator Customizing
Sequence of configuration steps – Use case 1

© 2013 SAP AG. All rights reserved. Customer 4

SAP CO-PA Accelerator Customizing
Sequence of configuration steps – Use case 2

You should perform configuration in the following sequence (for reporting directly
out of SAP HANA):
Replicate metadata and activate continuous data replication of tables CE1xxxx,
CE2xxxx, CE4xxxx and relevant master data tables using your replication tool (e.g.
SLT). Transaction KEHA will help you identify the necessary tables.
Generate your reporting model either manually in the SAP HANA modeling studio or
semi-automated via transaction KEHA.
Build your reports on SAP HANA.

© 2013 SAP AG. All rights reserved. Customer 5

Choose your replication
approach
Choose your replication approach

© 2013 SAP AG. All rights reserved. Customer 7

Replication via CO-PA
program
User for secondary database connection

Create at least one dedicated user on the SAP 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 essential to separate data and structures from different source systems by
database user and respectively by schema.
We suggest creating database users on the SAP 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.
© 2013 SAP AG. All rights reserved. Customer 9
User for secondary database connection

© 2013 SAP AG. All rights reserved. Customer 10

Configure secondary database connection

Use transaction DBCO or

SM30 on table DBCON to
create the database
connection.

© 2013 SAP AG. All rights reserved. Customer 11

Test secondary database connection

© 2013 SAP AG. All rights reserved. Customer 12

Replication via CO-PA program

If your primary interest is in the acceleration of CO-PA reporting and allocations, you
should choose to replicate via CO-PA program. You will need to schedule program
RKE_HDB_WRITE_DATA periodically. Please choose option “Using CO-PA
program” as your replication mode. The safety buffer for CO-PA replication is the
time latency the system will add as a safety interval to allow for any update
processes to finish. Therefore, when running the replication from the traditional
database to SAP HANA, the program will only fetch data records with a timestamp
of 1800 sec ago. 1800 sec is the default value used for the build up of aggregation
levels. You may change this value.

© 2013 SAP AG. All rights reserved. Customer 13

Replication via CO-PA program
Replication Programs

2 replication programs are available

Regular CO-PA replication program
Transaction KEHW / report
RKE_HDB_WRITE_DATA
Transfers line items (CE1xxxx, CE2xxxx) and
segment data (CE4xxxx) if realignment has been
included in customizing (Transaction KEHC)
Generates tables in SAP HANA & inserts data
To be scheduled periodically
Realignment replication program
Transaction KEHD / report
RKE_HDB_WRITE_REALIGNMENT_DATA
Transfers only CE4xxxx data which could not be
© 2013 SAP AG. All rights reserved. Customer 14
transferred during realignment run execution
Replication via CO-PA program
Transaction KEHW

Operating concern

Server group for parallel processing in

batch mode

Number of parallel processes to be

used in batch mode: start with 2-8
Package size for read from traditional
database: start with 10.000 – 100.000
Force initial load. If blank, delta
replication is performed

Actual and plan line items are always transferred (CE1xxxx and CE2xxxx)
Realignment data (CE4xxxx) are transferred if customized in transaction KEHC.
© 2013 SAP AG. All rights reserved. Customer 15
Replication via CO-PA program
Transaction KEHW
If you are using replication via CO-PA program, you will need to schedule the
replication job with transaction KEHW / report RKE_HDB_WRITE_DATA.
We recommend to run this report once or twice per day. Although the replication job
generates some load on the system, the more frequent your data is in SAP HANA,
the less data still needs to be selected from the traditional database for read access
in CO-PA. The replication job will only select data since the last time it has been
executed (delta selection) and allow for a safety buffer as specified in the
configuration (transaction KEHC). The delta data is identified by the timestamp of
the line items.

© 2013 SAP AG. All rights reserved. Customer 16

Replication via CO-PA program
Performance and Frequency Considerations

Initial load can take substantial time

Measurements are showing 3-20 mio CE1xxxx records per hour. Bottleneck is on reading the
traditional database
Example: 60 mio records in CE1xxxx + 4 mio records in CE4xxxx => 3 hours processing

No downtime is required
CO-PA reporting and processing can continue, the CO-PA accelerator will not become active
before data has been transferred

Schedule the program frequently to avoid long reading time from traditional database
CO-PA read function module will federate data from SAP HANA and from original tables
The more frequently you run the replication, the less data needs to be read from the original
tables
We recommend to schedule replication program once per day. Analyse performance
© 2013 SAP AG. All rights reserved.
trace. If 17
Customer
read access to original table consumes more time than SAP HANA access, increase the
Replication via CO-PA program
Segment table / Realignment data

Relevant entries in CE4xxx table are automatically transferred during initial load

Changes to existing CE4xxxx entries are transferred at the end of realignment run
automatically
Realignment accelerator status is set to red
Application tries to replicate changed entries to SAP HANA
If successful, CO-PA accelerator becomes operational again
If not successful, a message will be shown and status stays red until program
RKE_HDB_WRITE_REALIGNMENT_DATA has been run successfully

© 2013 SAP AG. All rights reserved. Customer 18

Replication via CO-PA program
Safety Instructions

If there are any issues:

re-execute KEHW with “force initial load” option
This will drop the tables on SAP HANA side
Everything is regenerated
Fresh data load happens
… however, you need time

We recommend customers continue to maintain and build up traditional

summarization levels for 3-6 months after CO-PA accelerator adoption. This
will allow to set the accelerator inactive anytime falling back to the situation
before.

© 2013 SAP AG. All rights reserved. Customer 19

Replication via CO-PA program
Reconciliation Program

The number of records in CE1xxx and CE2xxxx tables are automatically

reconciled with each replication run
You can manually start the reconciliation with program
RKE_HDB_RECONCILIATION
The program allows to transfer entries missing in SAP HANA (not vice versa) and
offers different details of log display.

© 2013 SAP AG. All rights reserved. Customer 20

Replication via CO-PA program
General Considerations

The data provisioning via CO-PA program is meant to be the easy-to-

implement, low TCI solution as it builds on the connection required for read
access. It also provides built-in support & status handling for the CO-PA
scenario.

Using SLT, there is no dedicated mechanism for transferring the object table
(CE4xxxx). Changes are simply replicated when they happen.

© 2013 SAP AG. All rights reserved. Customer 21

Configuring CO-PA
Acceleration scenario
Transaction KEHC

© 2013 SAP AG. All rights reserved. Customer 23

Read mode settings

Read mode settings allows

you to fine-tune the
performance of your CO-PA
acceleration depending on
specific runtime findings in
your system. You should only
make changes to these
settings based on SAP advice
or after thorough analysis of
runtime impact. You may use
these settings to switch on the
acceleration mode for
selected users only.

© 2013 SAP AG. All rights reserved. Customer 24

Status

You can access the data in the

SAP HANA database either
directly or via so-called column
views which generally yield
better performance.
You can find the column view
names on the status tab of the
configuration (transaction
KEHC).

© 2013 SAP AG. All rights reserved. Customer 25

Replication job (transaction KEHW)

If your replication job fails, the status for data replication will be set to red (see
status tab in configuration transaction KEHC).

© 2013 SAP AG. All rights reserved. Customer 26

Planned Maintenance

If you need to perform maintenance activities on your SAP HANA database but
want to continue ERP processing during this time, you can put the accelerator into
maintenance status via program RKE_HDB_SET_MAINTAINANCE_MODE. You
may set a single operating concern or a secondary database connection (with all
accelerated operating concerns) into maintenance mode. During maintenance
mode, the ERP system will behave as if no accelerator was present. In contrast to
switching off the acceleration in configuration (transaction KEHC), this program
allows to apply changes in a scheduled way and per database connection instead
of a single operating concern.

© 2013 SAP AG. All rights reserved. Customer 27

Planned Maintenance

© 2013 SAP AG. All rights reserved. Customer 28

SAP ERP Reporting
Transaction KE91 / KE30

Make sure to use the

aggregation in SAP HANA and
not in the application server
when navigating in the report
(option „read upon each
navigation step“). The settings
for summarization data will be
ignored if CO-PA accelerator is
active.

© 2013 SAP AG. All rights reserved. Customer 30

Transaction KE91 / KE30

In order to have the highest

benefit, please make sure you are
using the following setting “Read
upon each navigation step” in the
CO-PA reports.

If necessary implement SAP Note

1624750.

© 2013 SAP AG. All rights reserved. Customer 31

Transaction KE24 Line item reporting

© 2013 SAP AG. All rights reserved. Customer 32

Accelerated Transactions

© 2013 SAP AG. All rights reserved. Customer 33

Accelerated Transactions

© 2013 SAP AG. All rights reserved. Customer 34

Accelerated Transactions

© 2013 SAP AG. All rights reserved. Customer 35

Accelerated Transactions

© 2013 SAP AG. All rights reserved. Customer 36

SQL trace to verify data is being read from SAP HANA

© 2013 SAP AG. All rights reserved. Customer 37

Deployment Considerations
Transport of configuration

The configuration of the HANA accelerator (transaction KEHC) cannot be

transported. The reason is to avoid any inconsistencies if an identical database
connection is used for access e.g. from the ERP development and production
system. Development data could then overwrite or mix up with data from
production. Due to the very limited amount of configuration options, the customizing
is non-transportable and belongs to current settings of each system.

© 2013 SAP AG. All rights reserved. Customer 39

Sizing recommendations

The typical compression between traditional database and the storage in SAP
HANA is 5-10. This means that 200 Gigabyte of uncompressed ERP data will likely
lead to 20 – 40 GB memory consumption in SAP HANA. 200 Gigabyte could
translate into 80 million line item records with a record length of 2,5 KB, which is not
unusual for large customers.
The necessary tables are
CE1xxxx… transaction data actuals
CE2xxxx… transaction data plan (if customer is storing budget data in CO-PA)
CE4xxxx… profitability segments (required for realignment, not relevant to all
customers)
Master data is required for reporting directly on top of SAP HANA. Typically, the
CE1xxxx table
© 2013 SAP AG. All will account for 80% of the data.
rights reserved. Customer 40
System landscapes (for replication via CO-PA program)

© 2013 SAP AG. All rights reserved. Customer 41

Limitations

The EGI SAP HANA Profitability Analysis only supports costing-based CO-PA. It
does not support account-based CO-PA.
It cannot handle period block factors different from 1. This may affect the access to
plan data in table CE2xxxx. In case you use period block not equal 1, refer to SAP
Note 18775 for options to reorganize your ERP CO-PA data to remove this
constraint.
In case you want to use an alternative replication process, e.g. SLT, make sure to
use different database users for SLT and for the CO-PA replication program. It is
normally not required to use both methods in parallel. In case you are using SLT, we
recommend to use the same database user with SAP HANA configuration for the
SLT data replication and to set the replication mode to alternative replication.

© 2013 SAP AG. All rights reserved. Customer 42

Summarization Levels

Currently, many customers are using CO-PA summarization levels to persist sub-
totals on the traditional database (similar to BW aggregates). This helps keeping
reporting performance acceptable but requires some planning and maintenance.
The EGI for SAP HANA Profitability Analysis with SAP HANA will make traditional
summarization levels obsolete in most cases. For reasons of contingency, we
recommend customers to continue building summarization levels at least during a
transition period to keep performance under control even in case SAP HANA is not
available.

© 2013 SAP AG. All rights reserved. Customer 43

Execution

Check Prerequisites
Consider what replication approach to use
Review customizing settings

To be able to follow the session in the

next days please make sure that you
completed all tasks for today.
© 2013 SAP AG. All rights reserved. Customer 44
Outlook

Next steps - Day 3

Alternative Replication (SLT)

Demonstration – before and after

© 2013 SAP AG. All rights reserved. Customer 45

Expert Guided Implementation
How to get help

How to get help

+353 1 4717205
Customer SAP Expert
susana.serrano.ruiz@sap.
com

During the execution part you have direct access to the Expert via
telephone number to solve questions quickly. Please ensure that the
necessary support connections are open and that we can logon to your
system.
© 2013 SAP AG. All rights reserved. Customer 46
Thank You!
Please don’t forget to send us the daily feedback form.
© 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or
warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

© 2013 SAP AG. All rights reserved. Customer 48