Hi,
This document contains end to end scenario to replicate data from ECC system to SAP HANA system (Replication is real time). SAP HANA Studio is used for modelling purpose. Views are created in data modelling. This document is divided into 3 parts. Please find the link to the next part at the end of the page.
Prerequisite for this scenario is to have SLT configured.
For SLT Configuration : http://scn.sap.com/docs/DOC-63548
Following are the step involved in integration of ECC to HANA and HANA modelling :
In SAP HANA STUDIO, we need to login for data provisioning.
SAP HANA Studio Version SP09 (Latest).
NOTE : Data Provisioning used for selecting the source metadata and importing metadata and data into SAP HANA System. SLT is (trigger-based) type of data provisioning which is used in current scenario.
Here EH7(EHP7_EH7_07) is source system and Target Schema is ECC_NEW_HANA
This tables contents the description and structure details about all tables in ECC system.
Replication of tables will be real time.
NOTE : Load will load only the current data and not any other data that is changed afterwards (no delta support). Load is advantage if you think you won't have any updates in any table and this will not create any triggers or logging table in the source system which are primarily required for delta (and hence replicate creates and uses them)
Replicate will load the data till the current state and also all the changes that happen then on (Replicate = Load + Delta).Replicate is advantage if you want real-time data always in HANA and which would enable you for real-time reporting.
This starts the replication of EKKO table.
NOTE : EKKO is Purchasing Document Header table. For table structure check below link
http://www.stechno.net/sap-tables.html?view=saptable&id=EKKO
NOTE : Catalog represents SAP HANA’s data dictionary, i. e. all data structures, tables, and data which can be used. The physical tables and views will be placed in the Navigator tree under the Default Catalog node. This node contains a list of Schemas which is used to categorize tables according to user defined groupings.
NOTE : Schema is a logical place for creating / maintaining Tables / views / DB objects. Whenever a DB USER is created, he is assigned a DEFAULT schema for his id.
Here we have used EKKO table.
SELECT TOP 1000 * FROM “ECC_NEW_HANA”.”EKKO”
NOTE : SQL SELECT Query takes top 1000 records by default. This may change.
NOTE : The node Content represents the design-time repository which holds all information data models created with the Modeler. Physically these models are stored in database tables which are also visible under Catalog. The Information Model nodes navigate to Attribute Views, Analytic Views and Calculation Views. The Information Models are organized in Packages. The Contents node just provides a different view on the same physical data.
EBELN purchasing document number is used for join between both tables.
NOTE : Package is a procedure for grouping together the related information objects in a structured way.
Go to http://saphanatutorial.com/build-your-first-sap-hana-model/ for details.
For Next Steps : End to end integrated Scenario of ECC, HANA and BO : HANA Modelling to IDT (Part 2)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 | |
2 | |
2 |