Configuring Custom Objects: Data Transfer

Components:

• Export Master Data
• Import Master Data
• Convert Master Data
• Monitor Data Transfer

XML-based transfer of data (business objects). Supports mainly the initial load scenarios into an active area.

Each business object needs implementation coding.

Related Components:

• File Download
• File Upload

CSV*-based transfer of data (entities) for load scenarios into the staging area supports the processing of multiple objects for all data models (and also Custom Objects). This covers initial load scenarios for Financials and Custom Objects. A master data object usually spans several entities, which must be uploaded separately. Dependencies are not covered by the system and limit the use case especially for complex objects like Business Partner, Vendor, Customer, and Material.

Although MDG delivers a new SOA-based framework with ERP EhP5, other technologies for extraction and load are still available and can be considered if appropriate (for example, pure ALE technology (using transaction BD10 or BD14), LSMW, or SAP BusinessObjects Data Services). These are sufficient for loading data in non-SOA based formats (for example, CSV files or IDoc-XML formats) into the active area. The new framework also allows for direct load of data in the SOA-format into an active area or staging (which is not available using other technologies).

Be aware that master data (and key- and value-mapping) can be exported from clients as well as from the MDG system. Exporting data from MDG is used to allow Consolidation and Data Quality Services through additional components (like NW MDM or SBOP Data Services). See "Data Quality".

SAP MDG stores data in one of two persistence areas: Staging Area or Active Area. Data in the staging area is not ready for consumption and usually has to be approved by a Master Data Steward to be sent to the Active Area.

Enterprise Service Bus (ESB); Middleware, NW MDM (NetWeaver Master Data Management), or SBOP DS (SAP BusinessObjects Data Services) are optional components. Additional implementation steps are necessary to build scenarios based on these components.

Depending on the release versions of the SAP client systems, different scenarios are possible. The following figures cover three common scenarios.

Further explanations about the scenarios:

1. Be aware that MDG-F does not use the Data Export/Data Import Framework. It uses the File Upload/File Download functionality. See Initial Load of the MDG-F System and the documentation for further information.
2. Documentation: Working with Master Data Governance/Financials/File Upload and File Download.
3. Be aware that for Business Partners, transaction BUPA_SEND is available, which includes full address data.

File Download and File Upload are components that can also be used to transfer multiple objects from and to the MDG system.

Unlike the XML-based components, these components offer a CSV*-based transfer of data (entities) for load scenarios into a staging area. This supports processing of multiple objects for all data models (and Custom Objects also).

This covers initial load scenarios for Financials and Custom Objects. Be aware that a master data object usually spans several entities that must be uploaded separately. Dependencies are not covered by the system and limit the use case especially for complex objects like Business Partner, Vendor, Customer, and Material.

• File Download WebUI: USMD_FILE_DOWNLOAD

• File Upload WebUI: USMD_FILE_UPLOAD

Data Transfer allows you to move master data between systems. These systems can be clients or your main Master Data Governance (MDG) system.

The first step of a data transfer is the export of the master data to an IDoc-XML file, which you can save locally or on your application server.

In the second step, you import the data into your central MDG system. During the import step, you can decide if you want the new master data to appear directly in the active area, or if you want to work with change requests and import the data to the staging area.

For more details on the data transfer, follow the detailed steps described in the configuration guide.

Master Data Governance for Materials uses existing technologies for the replication of the materials and related data to other connected business systems, including:

• SOA to connect to 3rd Party systems, but also to import data.
• ALE for connected SAP ERP or 3rd Party systems.
• CIF to connect to SAP SCM.
• Middleware to connect to SAP CRM or SAP SRM.

• Data Model
• Change Request Type (several Change Request Types can be assigned to one Business Activity. In that case, the user has to select the Change Request Type that he wants to use).

Export master data from SAP business systems to import them to the MDG system.

Beside generic options like "Data Migration Workbench" or LSMW, MDG leverages the MDMGX tool originally built for SAP NW MDM.

The tool is used in MDG for Financial Data and Custom Objects/Reference data.

To set up MDMGX for MDG-F, perform the following:

1. Apply the SAP Notes 1783851 and 1880169 to the target systems.
2. Download the required MDMGX configuration text file from SAP Note 1882127. The note includes a detailed how-to document about MDMGX setup and execution.

In addition: check the Community Network for SAP Master Data Governance http://scn.sap.com/community/mdm/master-data-governance/content and read the SAP how-to guide for MDG-F 'Use MDMGX for Initial Load'.

The figure shows the Import Master Data and Mapping Information. Advantages compared to File Upload are monitoring, scheduling, and usability.

The figure explains the first part of change request process configuration of data replication.

The figure explains the customizing settings for Generate Data Model-Specific Structures.

The figure shows the references to the Business Object Types, which you can find throughout SAP Master Data Governance customizing.

The screenshots shows the mappings and filters customizing for the Data Replication.

The figure explains the Define Filter Objects area in the customizing tree for Data Replication.