IDoc Extensions

Introduction to IDoc Extensions

• IDoc extensions are required when standard segments do not fulfil specific business data needs.
• Custom segments allow the inclusion of additional data, such as extra customer quantities.
• This guide explains the steps to create and configure IDoc extensions effectively.

Understanding the Need for Extensions

• Each segment contains fields for data transmission, but when additional fields are required, custom segments must be created.
• Many business require IDoc extensions to meet unique business needs.

Steps to Create IDoc Extensions

1. Creating a Custom Segment

• Use transaction code WE31 to create a new segment.
• Define a segment
• Add a custom field with a Characters.
• Save the segment locally, keeping responsible user and processing details as default.
• Successfully created custom segments ensure that additional business requirements are met.

2. Creating the Extension

• Use transaction code WE30 to create the extension.
• Link the extension to the basic type.
• Add a description for clarity and future reference.
• Include the custom segment under the standard segment to complete the extension setup.

3. Linking Basic Type and Extension

• Use transaction code WE82 to link the basic type with the extension.
• Examine existing configurations and create new entries as needed.
• Modify necessary entries to include the extension in the correct message type.
• Save the changes to complete the linking process.

4. Assigning the Function Module

• Use transaction code WE57 to assign a function module to the basic type and extension.
• Enter change mode to add the function module.
• Ensure correct linkage between the basic type and message type.

5. Creating the Partner Profile

• Use transaction code WE20 to create a partner profile.
• Enter the partner number and type for system communication.
• Navigate to the extension tab and configure necessary settings.
• The partner profile enables smooth data exchange between different systems.

?

Here the things are not finished here as a functional we need to send the Functional logic to the developer and developers should must ensure proper logic handling for seamless IDoc processing and the Custom logic must be implemented using customer exits to retrieve and process data correctly.

?Here the Developer will create the Program with Custom logic with customer exit.

As a functional if we want to know where the mapping in the code level is then with this process you can check.

1.????? Go to your T code, where you are sending the Data.

2.????? Go to System >> Status >> Double Click on Program. ?

3.????? Go to the Call function MASTERIDOC_CREATE_(Your message type) (Double Click )

4.????? Here we need to find call functions MASTERIDOC_CREATE (Double Click )

5.????? Here we need to check the CUSTOMER EXIT

6.????? In Customer Exit there will be CALL CUSTOMER FUNCTION as 0001 or 0002.

7.????? If you double click on that it will take you to function Exit.

8.????? In that function Exit there will be a Z Include Programmed

9.????? If you analyze that Include Program you will get the Mapping Code Details.

Thank You

Amit Kumar Bishoyi

?