Import from IDoc

One of the greatest challenges in creating a data migration mapping project is unfamiliarity with the detailed usage of the IDoc. Which segments and fields are relevant for the desired result?  Answering that question through trial and error is one option, but it can be both time consuming and ultimately unreliable.

A better approach is to create example data in an SAP system using standard T-Codes and then send an outbound message for that data using ALE.  The result is an outbound IDoc, created by the SAP system, which is a very good example (or at least a starting point) for data migration efforts.

MDA Workbench supports this strategy, using Import from IDoc functionality as a time saving alternative to performing some steps in Create a Mapping Project. Import from IDoc functionality enables quickly and accurately creating parts of mapping project based on an example IDoc that has been exported from an SAP system.

By configuring ALE outbound it is  possible to create an outbound IDoc for example master data or transactional data created in an SAP system.  For most master data, ALE outbound can be configured for a given message type.  For some master data, use of change pointers may be required to initiate the outbound IDoc.  Lastly, for some transactional data, such as a Purchase Order, output conditions may be required.

Features

• For the mapping project, you can import the segment and field selections from an existing IDoc.
• For sample data, you can import the data from an existing IDoc.
• Import from IDoc functionality is cumulative; It is possible to use the Import from IDoc functionality repeatedly. For example, if there are 3 flavors of vendors, then create examples of each in the SAP system and then an outbound IDoc for each.  Then use the Import from IDoc functionality to import each IDoc in turn.  The total of all segments and fields in each of the 3 IDocs are made active in the mapping project. The same applies to Sample data.

Options

• n/a

Execution Overview - Import IDoc from SAP

• Create a new Map from SAP

• Choose File and then Map from SAP to create a new Mapping Document window and fill it with the segments and fields of an IDoc.

• Import IDoc segment and field selections.
• Click the Import IDoc button the External Data ribbon in the Map ribbon group.
• Enter the IDoc number.
• Choose the SAP System and Client
• A selection screen is presented. It displays all the segments and fields that are used by the IDoc, and as each segment is click the IDoc data for that segment is displayed in a Grid.
• The segments and fields used in the IDoc are marked Active in the selection screen.  If you want to ignore any Segment or Field then clear the Active check box for that Segment or Field.  
• The system remembers the segments and fields that you've chosen to ignore for this Mapping Project ID.  They will not be flagged as Active with subsequent imports.
• If the apply button is clicked, then Active flags for Segments and Fields in the selection screen will be transferred to the mapping project.  That is to say that this process can only be used to mark non-Active segments and non-Active fields in the mapping project as Active.
• Merge IDoc Segments
• Per the steps in Create a Mapping Project, indicate which segments are to be merged.
• Maintain Primary Key(s).
• Per the steps in Create a Mapping Project, maintain primary keys for each staging table
• Import IDoc to create Sample Data.
• Click the Maintain button the Home ribbon in the Sample Data ribbon group.
• The sample data form is opened.
• Click the Import IDoc button on the Sample Data toolbar.
• Choose the IDoc text file that was exported from SAP.
• The data from the IDoc is imported into the sample data structure of the mapping project.
• Maintain sample data fields as needed.
• For example, if Primary Key fields were added to a segment in a mapping project then these fields do not exist in an IDoc. Consequently these fields will be empty in the sample data and must be maintained.
• Click the Apply button.

Execution Overview - Import IDoc from File

• Export IDoc from SAP
• An existing IDoc is easily exported to a text file from SAP.  Using transaction code WE02 to view the IDoc, Choose IDoc, Print IDoc, and then List, Export, Local File as Unconverted.
• Create a new Map from SAP

• Choose File and then Map from SAP to create a new Mapping Document window and fill it with the segments and fields of an IDoc.

• Import IDoc segment and field selections.
• Click the Import IDoc button the External Data ribbon in the Map ribbon group.
• Choose the IDoc text file that was exported from SAP.
• A selection screen is presented. It displays all the segments and fields that are used by the IDoc, and as each segment is click the IDoc data for that segment is displayed in a Grid.
• The segments and fields used in the IDoc are marked Active in the selection screen.  If you want to ignore any Segment or Field then clear the Active check box for that Segment or Field.  
• The system remembers the segments and fields that you've chosen to ignore for this Mapping Project ID.  They will not be flagged as Active with subsequent imports.
• If the apply button is clicked, then Active flags for Segments and Fields in the selection screen will be transferred to the mapping project.  That is to say that this process can only be used to mark non-Active segments and non-Active fields in the mapping project as Active.
• Merge IDoc Segments
• Per the steps in Create a Mapping Project, indicate which segments are to be merged.
• Maintain Primary Key(s).
• Per the steps in Create a Mapping Project, maintain primary keys for each staging table
• Import IDoc to create Sample Data.
• Click the Maintain button the Home ribbon in the Sample Data ribbon group.
• The sample data form is opened.
• Click the Import IDoc button on the Sample Data toolbar.
• Choose the IDoc text file that was exported from SAP.
• The data from the IDoc is imported into the sample data structure of the mapping project.
• Maintain sample data fields as needed.
• For example, if Primary Key fields were added to a segment in a mapping project then these fields do not exist in an IDoc. Consequently these fields will be empty in the sample data and must be maintained.
• Click the Apply button.