Show TOC

Background documentationData Transfer of Supplier Master Data


Data transfer allows you to move master data between systems. These systems can be client or your main Master Data Governance systems.

If MDG-S is used on a productive ERP system in the same client no further initial import is required.

If MDG-S is used on a standalone ERP system supplier data that is not available on the ERP hub needs to be imported from one of the following sources:

  • Another ERP system

  • An SRM system

  • A CRM system

  • A non-SAP system

Data Export from Source System

To be able to export supplier master data, you can use the Export Master Data service (SAP ERP 6.0, EHP6) or the File Export (EHP5) which will create XML files in the SOA format. For exporting supplier master data from systems with ERP releases lower than SAP Business Suite Enhancement Package 5, use the existing functions in that release. For more information, see Extraction of Supplier and Customer Master Data (Earlier ERP Releases). In this case you need to configure the logical system for IDoc-XML. The steps are as follows:

  1. Create an XML-file port

    Use transaction WE21 to create an XML-file port for IDoc processing. Ensure that you have network access from your local client to the directory configured in the XML-file port. Enter the port name, description, and the physical directory. Enter the function module EDI_PATH_CREATE_CLIENT_DOCNUM. On the Outbound Trigger tab enter the RFC destination LOCAL_EXEC.

  2. Create Logical System

    Open transaction SALE and then go to Start of the navigation path Basic Settings Next navigation step Logical Systems Next navigation step Define Logical System End of the navigation path to create a new logical system.

  3. Maintain Distribution Model

    Open transaction SALE and then go to Start of the navigation path Modeling and Implementing Business Processes Next navigation step Maintain Distribution Model and Distribute Views End of the navigation path. You can also use transaction BD64 for this.

    1. Switch to change mode and choose Create Model View to create a new entry. Enter a short text and a technical identifier.

    2. Choose Add Message Type for the newly created model. Enter a logical source system name and a destination system name and choose the message type CREMDM.

  4. Create Partner Profile

    Run transaction SALE and then go to Start of the navigation path Modelling and Implementing Business Processes Next navigation step Partner Profiles Next navigation step Generate Partner Profiles End of the navigation path. Alternatively you can use transaction BD82.

    1. Select the newly created model using the input help for the technical name and then select the logical destination system.

    2. Enter the authorized user and the following values:

      • Version: 3

      • Pack.Size: 100

      • Output Mode: Immediate Transfer

      • Inbound. Processing: Immediately

    3. Choose Execute. You can ignore the port error that appears.

  5. Call transaction WE20 and make the following settings:

    1. Open the Partner Type LS folder and select the partner profile you created above.

    2. Update the message type CREMDM in the Outbound Parameters section. The Receiver Port is the XML-file port from the first step above. In the Basic Type field enter CREMDM04 for CREMDM.

  6. Test creation of IDOC XML

    1. Generate the IDoc-XML for supplier using transaction BD14.

    2. Check the newly generated IDocs using transaction WE02 or BD87. You can use the receiver port as the filter criteria in the Partner Port field.

    3. Use transaction AL11 to find the XML files on the directory of your XML-file port.

    4. To download the file for analysis purposes to local directory use transaction CG3Y.

Data Cleansing in NetWeaver MDM

In an optional step data cleansing, that means matching, merging, validation, and enrichment of data can be done with SAP NetWeaver MDM. The files from the data extraction process have to be converted in a first step and then can be imported into SAP NetWeaver MDM.

After data cleansing steps the supplier data can be extracted again in order to import them into the MDG Hub. Additionally key and value mapping information might be created and uploaded with the supplier data.

To convert the data for consumption in NetWeaver MDM you can use the WebDynpro Application MDG_TRANSFORMER_FPM_CMP which can be called from the work center for MDG-S under (Start of the navigation path Data Exchange Next navigation step Data Transfer Next navigation step Convert Master Data End of the navigation path

Use transaction FILE to create the logical directory MDG_TRANS_SOURCE to be able to use the File Converter.

Data Import into Target System (MDG Hub)

Note Note

To perform an initial load of master data, we recommend to use the functions described in the following documents:

End of the note.

If you want to use parallel processing for data import it is recommended that you register your queue name prefixes in the QIN Scheduler so that they are executed automatically and do not have to be manually activated each time. To register the queue name follow these instructions:

  1. Run transaction SMQ2.

  2. Choose Execute. This shows the list of current queues.

  3. ChooseStart of the navigation path Goto Next navigation step QIN Scheduler End of the navigation path.

  4. Choose the Registration.

  5. In the Queue Name field, enter a prefix for your queues. Add an asterisk after the name to allow you to add additional text to the prefix when scheduling the export or import. Enter additional details as required.

  6. Press OK.

Your new queue has been registered and will execute automatically. You should inform those working with the Data Import service what the queue name is so they can use it.

The IDoc-XML files contain the following fields in the header section:

Field Name

Field Description






Sender Partner Number

Defined in step 3 below.


Sender Port

Defined in step 1 below.





Receiver Partner Number

Defined in step 3 below.


Receiver Port

Defined in step 1 below.

To be able to import IDoc-XML files the following set up activities need to be carried out:

  1. Use transaction IDX1 to create two ports in the IDoc adapter, one for sending and the other for receiving. Enter the port, client, description, and RFC destination for each port. Both ports should have the RFC destination of the MDG hub. Check that the port names match the names in your IDoc-XML file for the SNDPOR and RCVPOR, see table above for details.

  2. In transaction WE21 enter the receiver XML port using the same name as in step 1 above. Enter the port name under the folder XML File, and enter a description and a physical directory. In the function module field enter EDI_PATH_CREATE_CLIENT_DOCNUM. On the Outbound:Trigger tab, in the RFC destination field, enter LOCAL_EXEC.

  3. In transaction BD54 enter the sender and receiver partner numbers as logical system names.

  4. In transaction FILE create the logical file name. Enter a Logical File and a Name. In the Physical File field enter <PARAM_1>. In the data format field enter BIN. In the Application Area field enter CA. In the Logical Path field enter the logical file path

  5. In transaction AL11 make sure that the IDoc-XML files are stored under the logical path and that there are no other files stored in that directory. Double-click on the path to view the existing iDoc-XML file. You can use transaction CG3Z to copy a local IDoc-XML file to the path.

  6. To test the data import, open Start of the navigation path Data Exchange Next navigation step Data Transfer Next navigation step Import Master Data End of the navigation path in the SAP NetWeaver Portal or in the SAP NetWeaver Business Client. For more information, see Importing Master Data.

You can use the Monitor Data Transfer application to get an overview of your data transfer processes.