Hana for copa

SAP ® Customer Solution Adoption

Know-How Network Call Two Use Cases for Accelerated Profitability Analysis and

Reporting on SAP HANA™

Jeffrey Holdeman

October 5, 2011

© 2011 SAP AG. All rights reserved. 2

CO-PA in ERP: Provides Highly Integrated Profitability Analysis for

Customer-defined Product-Market Segments

Financial

Accounting

Production

Overhead

Management

Sales

Product

Costing

Profitability

Analysis

Cost center assessment

Order settlement

Billing doc.

Cost of goods manufactured

Cost allocation

Settlement of production variances

Direct postings from Financial Accounting

FI-GL

MM PP SD

CO-PC

CO-OM

CO-PA


Press Release – SAP ®

CO-PA Accelerator

Use Case 1

SAP CO-PA

Accelerator

Use Case 2

BI Reporting on

CO-PA Data

in SAP HANA


SAP CO-PA Accelerator Basic Architecture

SAP BO BI 4.0 SAP GUI

SAP HANA

SAP ERP

CO-PA application (ABAP AS)

Traditional DB In-Memory DB

CO-PA Drilldown Reporting Dash-

boards Analysis Explorer

Crystal

Reports

Read interface traditional + HANA

Periodic Replication to HANA** Secondary

DB connection

Generated

model**

HANA

reporting on

CO-PA data

XML Reporting Model Generator*

SAP HANA

Modeling Studio**

* Only used for BI/HANA reporting on CO-PA data ** Optional use of LT Replication

CO-PA Read Access Optimizer

LT

Replication**

XML file

Overview

Technical Requirements

Setup

Benefits

Customer Insights

SAP CO-PA Accelerator


Use Case 1 SAP CO-PA Accelerator

Accelerating existing processes:

SAP HANA In-Memory Appliance serves

as secondary database for SAP ERP

CO-PA line item data is replicated / written

into In-Memory in real time for secondary

storage

CO-PA User interface remains unchanged

to ensure non disruptive acceleration

CO-PA application is accelerated by

reading the mass data from the In-Memory

database

Examples:

KE30 Execute Reports

KE24 Display Line Items

KEU5 CCA to CO-PA Assessment

KE28 Top-Down Distribution

SAP HANA

Read

SAP

Business

Suite

SAP UI

Traditional DB

Computing Engine

Data Modeling

Replication


SAP CO-PA Accelerator Understanding the Read Access

All CO-PA functions access data through

a dedicated function module. Generally,

this module determines the best data

source in the traditional database

(similar to an OLAP processor). With CO-

PA accelerator, HANA becomes the best

data source by default.

Sum. Levels Line items Segments Totals HANA objects

K81.x

CO-PA

report

CO-PA read function module

Data source determination

CE1xxxx

CE2xxxx

CE3xxxx K81.x HANA

CE1

HANA

CE2

CE4xxxx HANA

CE4

ColumnView

CO-PA

allocation

CO-PA

planning


Technical prerequisites for the SAP CO-PA Accelerator

Acceleration of ERP reporting and allocations

On ERP side

Application coding

Netweaver

Netweaver Kernel

Database Client

On HANA side

HANA 1.0 SPS 2

Use Case 1 Technical Prerequisites SAP CO-PA Accelerator


SAP CO-PA Accelerator Technical Prerequisites Use Case 1 - Acceleration of ERP Reporting and Allocations

ERP 6.0 ERP 6.01 ERP 6.02 ERP 6.03 ERP 6.04 ERP 6.05

NW 7.00 NW 7.01 NW 7.02

ERP

NetWeaver

ADBC classes + domain values ADBC + .. ADBC + ..

Kernel

Application CO-PA Accelerator Coding

DB client for In-Memory DB to be installed on application server OS

ERP 6.06

NW 7.31

Kernel 7.20 Kernel 7.20 Downward-compatible Kernel 7.20

replacing current Kernel 7.00 / 7.01

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)

Requires upgrade / installation

HANA 1.0 SPS 2 or higher HANA Secondary DB

connection


SAP CO-PA Accelerator Technical Prerequisites Planned Schedule of Deliveries

Delivery of CO-PA Accelerator with support packages

Additional delivery via notes 1614438 and 1559994 through transport has been arranged for

selected customers

Technical prerequisites regarding SAP kernel and HANA-DBSL

SAP Kernel 7.20 (DCK) with minimum patch level 90

Minimum HANA-DBSL patch level 92

ERP EHP EHP0 EHP2 EHP3 EHP4 EHP5 EHP6

08.11.2011 SP21 SP11 SP10 SP10 SP06 SP01

RTC CW15 2012 CW15 2012 CW15 2012 10.10.2011 17.10.2011 08.11.2011

NW EHP 7.00 7.00 7.00 7.01 7.02 7.31

NW SP 26 26 26 10 09 01

RTC 17.02.2012 17.02.2012 17.02.2012 26.08.2011 09.09.2011


SAP CO-PA Accelerator Customizing

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 (LT,

Sybase, BO DataServices)

You will find customizing transaction

KEHC in the CO-PA branch of the

IMG (transaction SPRO). 1

1


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 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)

SAP CO-PA Accelerator Customizing Checklist


ERP w/o

HANA

(benchmark

provided by

xxx)

(1)

ERP with

HANA

(SAP test

installation)

(3)

Acceleration

factor vs.

ERP

(1) / (3)

EBIT with xxxx sales

– initial report

280 sec 7 sec (DB 2,8 sec)*

40

EBIT with xxxx sales

– drilldown by ….


124

Cost allocation analysis

– initial report


9

Cost allocation analysis

– drilldown by cost center


37

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.

Accelerated Profitability Reporting (Use Case 1) Benefits Advanced by SAP In-Memory Computing

1 Operating Concern

8 months of real customer data

~ 85 Mio line items in CE1 table

~ 33,000 customers

~ 27,000 articles


Accelerated Profitability Allocations (Use Case 1) Benefits Advanced by SAP In-Memory Computing

SAP HANA DB

<30 sec reading time for reference data!

(runtime for specific scenario)

<1 sec search time for data w/o product

assignment (to be allocated)

No data aggregation levels required, any

allocation anytime

Classic DB

>1h reading time for reference data (runtime

for specific scenario)

Search only possible with index support or

further “tricks”

Time-consuming optimization of pre-

calculated data aggregation levels

depending on allocation needs

85 Mio. line items, allocation of overhead cost to single products based on sales qty


Use Case 1 Customer Insights

Reporting performance

Activate HANA parameter

force_analyze in

indexserver.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

Overview

Technical Requirements

Setup

Benefits

Customer Insights

BI Reporting on CO-PA Data in SAP HANA


Use Case 2 Overview BI Reporting on CO-PA Data in SAP HANA

Accelerating 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

information models

Note: report models are available as RDS

(Rapid Deployment Solution)

BI frontends are used to display the data

Examples:

SAP BusinessObjects Explorer

SAP BusinessObjects Analysis, Office Edition

SAP BusinessObjects Web Intelligence

Microsoft Excel

SAP HANA

BI Clients

SQ

L

MD

X

BIC

S

3rd Party

Replication

SAP

Business

Suite

Traditional DB

Computing Engine

Data Modeling


BI reporting on CO-PA data in HANA can be implemented based on data of

any 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 1

What 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

Use Case 2 Scope BI Reporting on CO-PA Data in SAP HANA


CO-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

Use Case 2 Data Model CO-PA XML Generator

XML Files

Upload into

Modeling

Studio

Generate

Model

XML Generator report available from SAP Note 1627568


Technical 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)

Use Case 2 Technical Prerequisites BI Reporting on CO-PA Data in SAP HANA


Accelerated Profitability Reporting (Use Case 2) Benefits Advanced by SAP In-Memory Computing

SAP HANA DB

Less than 1 sec (runtime for specific

scenario)

Directly on line item level

No pre-calculated data aggregation levels

required

No limit on drill-downs and details

Data immediately available for reporting, no

waiting on data load processes to data

warehouse

Classic DB

Several minutes (runtime for specific

scenario)

Pre-calculated data aggregation levels

Processing time for next navigation step

depends on if aggregate exists

Parallel drill-down to multiple dimensions

may not be possible anymore

120 Mio. line items, report on product-related dimensions for a single company


Use Case 2 Customer Insights

Reporting performance

Oct-19 KHNC webinar

How to best leverage SAP

BusinessObjects BI 4.0 on SAP

HANA 1.0 by Patrice Le Bihan

Data Provisioning (in POCs)

Extraction Methods

Flat Files

DB Backups

R3LOAD

Physical Delivery

Data Load Methods

Data Services

Scripts

R3LOAD

Dashboards

Reporting

Interactive

Analysis OLAP

Analysis Data

Exploration


Function Module: RKE_FILL_FIELD_TABLE

Transaction SE37

Function Module:

RKE_FILL_FIELD_TABLE

Input:

ERKRS = Operating Concern

PA_TYPE = 1 (Costing-based

CO-PA)

Execute:

Click on F8 Run Single Test

Click on FIELDTAB result to view

contents


FIELDTAB

Master Data

Tables

Shown from

FIELDTAB in

column

CHECKTABLE

Scroll down and

take note of each

of the master

data tables

needed


Accelerated Profitability Analysis and Reporting Which Use Case is Best for my Customer?

Customer wants to …

Acceleration of

ERP reporting

and allocations

BI reporting on

CO-PA data

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

Positioning CO-PA Accelerator and BW / BWA


CO-PA Reporting with SAP BW / BWA or CO-PA Accelerator Positioning

This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.

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.

SAP Business Suite

SAP HANA SAP BW

Enterprise Data Warehouse

Design and Operations

Analytic Engine (Queries)

BW Architected Data Marts

Data Acquisition

(DataSources)

HANA Models

SAP BusinessObjects BI

Corporate View on Information

Company wide Reporting on „standard“ data is key

BW Analytic Engine features required

„Snapshot“ reporting / latency is not an issue

DataSources

1_CO_PA_*

SLT Replication or

2nd DB Connection

Operational View on Information

Agility and Flexibility in local business process is key

Operational Excellence in Closing Process

Reporting on real time data required


Data in InfoCubes on disk need to be

replicated into memory - Compressed into

BWA but inherent duplication.

Realignment

BWA 7.20 last official BWA release

Roadmap

BWA 7.20 Composite Provider can do

some but not all join logic Modeling

HANA

Calculation logic

Many possibilities with

calculation views but deep

technical expertise required

Modeling

More Join types

SQL available for further join

logic

Realignment

No realignment needed

Roadmap

BW on HANA

All SAP Applications on

HANA as “RDBMS”

BW Analytic Engine / BWA offer many

calculation features “out of the box”

Calculation

logic

CO-PA Reporting with SAP BW / BWA or CO-PA Accelerator Technical Considerations

Positioning CO-PA Accelerator and PCM


Customer and Product Profitability Challenges using only CO-PA

Customizing is owned by IT

Integrated planning is difficult and inflexible

Reconciliation between G/L and CO-PA

Adaptability

CO-PA used for only margin reporting

Unassigned characteristic values

Granularity / Performance trade-off

Suitability

Operating concern design depends on

choices made in customizing

Sign handling, cost element types,

mappings

Many allocation methods to transfer costs

in CO

Complexity

PCM

Prebuilt Data Model

Standard model types

Predefined dimensionality

Simple assignment screens

Trust and Visibility of Data

Less IT involvement

Simplified data flow

Trace back of results

Full P&L Reporting

Customer & Product P&L’s

Many built-in best practices

Transactional costing if

needed

Thank You!

Contact information:

Jeffrey Holdeman

Americas Regional Team | Customer Solution Adoption | Solutions GTM

Technology

Hana for copa