Show TOC

Background documentationSet Up Data Transfer

 

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.

Data Export from Source System

To be able to export material master data, you need to configure the logical system for IDoc-XML export to the application server file system. 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 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 types MATMAS and CLFMAS.

  4. Create Partner Profile

    Run transaction SALE and then choose Start of the navigation path Modeling 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 (Generate Partner Profiles).

    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 types MATMAS and CLFMAS in the Outbound Parameters section. The Receiver Port is the XML-file port from the first step above. In the Basic Type field enter MATMAS05 for MATMAS and CLFMAS02 for CLFMAS.

  6. Test creation of IDOC XML

    1. Generate the IDoc-XML for material using the transaction BD10.

    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 Import into Target System (MDG Hub)

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 the Execute button. This shows the list of current queues.

  3. From the Goto menu, select QIN Scheduler.

  4. Choose the Registration button.

  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. Choose OK.

Your new queue has been registered and will execute automatically. You should inform those working with the Import Master Data service of the new queue name so that they can use it when creating new imports.

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

Field Name

Field Description

Value

SNDPRT

Partnertyp

LS

SNDPRN

Sender Partner Number

Defined in step 3 below.

SNDPOR

Sender Port

Defined in step 1 below.

RCVPRT

Partnertyp

LS

RCVPRN

Receiver Partner Number

Defined in step 3 below.

RCVPOR

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 path 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. Open the Configuration activity Start of the navigation path General Settings Next navigation step Data Transfer Next navigation step Define File Source and Archive Directories for Data Transfer End of the navigation path and assign your new logical file path name as a directory for data transfer.

  6. 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.

  7. To test the data import, open the Data Import service from the Material Governance work center in the SAP NetWeaver Portal or SAP NetWeaver Business Client. For more information, see Data Import.

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

More Information

For more information on data transfer see How to Use the Data Import Framework for Material http://scn.sap.com/docs/DOC-47519Information published on SAP site.