Performing the Initial Data Load in SAP MDG, Consolidation

Excerpt from the book SAP Master Data Governance: The Comprehensive Guide to SAP MDG by Homiar Kalwachwala, Sandeep Chahal, Santhosh Cheekoti, Antony Isacc, Rajani Khambhampati, and David Quirk. Used with permission of SAP PRESS. All rights reserved.

In this blog, get an overview of the options available for the initial data load in SAP MDG, consolidation.

To use SAP MDG, consolidation functionalities, master data from the source has to be loaded in the SAP MDG, consolidation application. It’s important to note that data has to be prepared and transformed into the SAP data structures for the successful processing of the initial load.

Various extract, transform, and load (ETL) tools can be used for loading master data in SAP MDG, consolidation tables from various SAP applications as well as non-SAP applications.

SAP has provided several options that can be leveraged for performing initial master data loads in SAP MDG, consolidation: SAP Landscape Transformation Replication Server (SLT), SAP HANA Studio, and CSV files.

1 Source Tables

Following are some source tables in which data has to be loaded from the business partner data model:

  • Table BUT000_SRC: BP General Data-I (required in all cases)
  • Table BUT020_SRC: BP Addresses (required if address relevant data are uploaded)
  • Table BUT_ADRC_SRC: Addresses (Business Address Services)
  • Table BUT_ADR6_SRC: Email Addresses (Business Address Services)
  • Table BUT100_SRC: BP Roles
  • Table KNA1_SRC: SAP ERP Customer Data (required if a customer data model is used)
  • Table LFA1_SRC: SAP ERP Vendor Data (required if a vendor data model is used)

Following are some source tables from the material data model:

  • Table MARA_SRC: Central Material Data (required in all cases)
  • ·Table MARC_SRC: Plant Data for Material (required while working with plant-level material data)
  • Table MVKE_SRC: Sales Data for Material (required if distribution chain data of materials are loaded)

For accessing all SAP MDG, consolidation-specific source tables, you can search for “*SRC” in Transaction SE16N to get a list of all relevant tables.

Report MDC_BP_TRANSFORM_SOURCE_DATA can be used for transforming the customer or vendor data to the business partner data model after the source tables are filled.

Note: Report MDC_BP_TRANSFORM_SOURCE_DATA doesn’t support the transformation of person-related data. Although the SAP MDG, consolidation process supports business partner organizations and business partner persons, it doesn’t support business partner relationships with current versions. Refer to SAP Note 2233142 for more information on how to fill in source tables in SAP MDG, consolidation. In addition, in SAP MDG 8.0, the inbound functionality doesn’t allow you to load the consolidation source tables; however, with SAP MDG 9.0 and based on the SOA service, you can choose whether to load the master data directly to the SAP MDG active area, to the SAP MDG staging area (change request), or to the source tables for SAP MDG, consolidation.

While loading data in SAP MDG, consolidation, the source ID should be a unique identifier for a specific source system. If data are uploaded using customer or vendor data models, ensure that the IDs remain unique. If there are vendor and customer IDs within the same number range, the IDs can be made unique by adding a prefix.

2 SAP Landscape Transformation Replication Server

SAP Landscape Transformation Replication Server (SLT) is a recommended option for initial loads in SAP MDG, consolidation, especially for existing SAP Business Suite models because identical data models are being used. SLT uses a trigger-based replication approach to pass data from source systems to target SAP HANA-based systems. As shown below, with SLT, it’s possible to load as well as replicate data in real time or schedule data to be loaded into an SAP HANA database at a later time.

SLT has the built-in capability to handle and support conversion between non-Unicode and Unicode data formats. With full integration to SAP HANA Studio, SLT also has table settings and some simple transformation capabilities. For any complex transformation, specialized ETL tools should be considered. With the help of SAP Solution Manager for SAP HANA, SLT also has data monitoring functionalities. To access SLT, use Transaction LTR.

SLT-based table data provisions provide the following options:

  • Load (Full): This is normally a one-time event used mainly for initial load purposes from a source application.
  • Replicate (Full and Delta Load): With this option, the initial load is triggered along with any delta changes.
  • Stop Replication: This option removes the database trigger and logging table completely while ensuring the replication process is stopped for a given table.
  • Suspend: This option doesn’t remove the database trigger and logging information but just pauses the replication process.
  • Resume: This option resumes the suspended replication process.

The following are some salient features while establishing a connection between SAP application and an SAP HANA-based system:

  • A read engine is created in the SAP source system.
  • The connection between SAP SLT and SAP HANA-based systems is established as a database connection.
  • The connection between the SAP source applications and SLT is established as an RFC connection.
  • While replicating a table, SLT creates logging tables in the source system.
  • SLT transforms all metadata table definitions from the ABAP source applications to SAP HANA.

Here are some salient features while performing a data load connection between a non-SAP system and an SAP HANA-based system:

  • A read engine is created in SLT.
  • The connection between SLT and the non-SAP legacy system is established as a database connection.
  • The connection between SLT and SAP HANA-based systems is established as a database connection.
  • While replicating a table, SLT does create logging tables in the source system.
  • SLT transforms all metadata table definitions from the legacy source system to SAP HANA.

3 SAP HANA Studio

With SAP HANA Studio, it’s recommended that data be imported in an interim table first, and subsequently, in the next steps, this content from the interim tables can be loaded to source tables using custom ABAP reports or SQL.

4 CSV Files

SAP MDG, consolidation supports uploading data from a file without ETL tools. SAP HANA-based systems support data loads from file types such as CSV (comma-separated values), XLS, and XLSX.

Prior to performing initial data loads using these options, a control file (CTL) should be created. To upload data in SAP MDG, consolidation, a table should already exist; otherwise, a new table needs to be created via a SQL script. The generic steps required when using CSV files for initial loads are as follows:

  1. Select the target system.
  2. Select the import source.
  3. Select the file for upload.
  4. Select the target table.
  5. Manage the table definition and data mapping.
  6. Check the target table.

You should now have a better understanding of the options available for the initial data load in SAP MDG, consolidation.

Excerpt from the book SAP Master Data Governance: The Comprehensive Guide to SAP MDG by Homiar Kalwachwala, Sandeep Chahal, Santhosh Cheekoti, Antony Isacc, Rajani Khambhampati, and David Quirk. Used with permission of SAP PRESS. All rights reserved.

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Sign up for SAP PRESS newsletters to get even more SAP tips and tricks delivered to you monthly!

Like what you read? Give SAP PRESS a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.