SAP SCM 7.2 Support Pack 8 and HANA 1.00.74.390550 (NewDB100_REL)
This document gives an insight into configuring function to replicate planning data (transaction data) from your SAP APO Live Cache to an SAP HANA system through a secondary database connection. Download and Install the HANA content model for Business Analysis.
Master data is replicated using SAP Landscape Transformation (SLT) but that is not possible for planning data as it does not store in database tables, but in SAP liveCache.
We run the reports or schedule the delta to push the planning data in Demand Planning (DP) and Supply Network Planning (SNP) to be available HANA system for Business to analysis.
Author: Santanu Bose
Company: Wipro Ltd.
Created on: 26 July 2014
Table of Contents
Step 1: Install HANA DB Client in APO system.
Need to install HANA Database client in SCM (APO) System.
Step 2: Setup Secondary DB Connection with HANA
Create Secondary DB connection (/ndbco)
Step 3: Set up a replication model and activate it.
Create Replication model (SAPAPO/REPL_MOD_VIE)
Define the Key Figures:
Activate Replication Mode (/n/SAPAPO/REPL_MOD_MNG)
Upon activation the tables should be created in HANA database.
Step 4: Run Full Replication.
Replication of Planning Data to SAP HANA (/SAPAPO/REPL)
Step 5: Run Delta Replication and Scheduling
Schedule delta replication (/SAPAPO/REPL_DELTA )
The table’s data should be available in HANA database.
Step 6: HANA Content Model installation
Download HANA Content Model (/SAPAPO/REPL_REPLICATION_MODE)
Install the HANA Content Model using import function in HANA Studio
Step 7: Run Business Analysis on data in HANA
Run analysis on the data in Calculation view been installed.
Disclaimer and Liability Notice
This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,
and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or
code sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.