Steps to create a basic type Idoc

Creation of a new basic type of IDOC consists of several steps. Here is the detail explanation and steps to do for that.

Step 1: Creation of Segments

Here are the steps to define segments

  • Enter Transaction code WE31
  • Select Utilities -> Requests (Organizer)
  • Specify segment type and choose create
  • Enter a short description of the segment and enter the corresponding field names and data elements associated with that segment.
  • Goto -> Documentation and describe the segment type
  • Come back to segment editor
  • Save and Enter the segment in a transport request

Step 2: Define a basic Idoc Type

  • Enter transaction code WE30
  • Enter a name for the basic IDoc type and mark basic type as the development object. And choose create
  • Enter a description for the basic Idoc type and choose tick mark button.
  • Position the mouse on header and choose create button
  • Enter the segments.
  • Save

Step 3: Assigning Message types

We need to create new message types only if the existing message not matching with our requirements.

Steps to create a new message type

  • Enter Transaction WE81
  • Choose edit button and then new entries
  • Enter the message type with description
  • Save

Steps to assign basic Idoc type to message type

  • Enter transaction WE82
  • Choose edit button and then new entries
  • Enter the message type, basic type and SAP release in their corresponding columns.
  • Save data

Step 4: Create function Module for outbound processing

The steps for creating a function module have been described in our earlier posts. Here is a brief about the steps.

  • Open the function builder to create our new function module
  • Create the segments as global data and code the function module to pass the application data to the corresponding segments.
  • Activate the function module


Step 5: Maintaining the Attributes of a Function Module

Use transaction code BD51 to maintaining the Attributes of a Function Module (Like the settings for dialog possible etc)

Step 6: Assign function module to the basic Idoc

Use Transaction code WE57 and then assign the function module to various objects as per our requirements. This step is the ALE registration for the function module.

Step 7: Assigning a Process Code

This step is used to assign a new process code to the new function module. This enables the function module to be identified from the partner profiles defined in the IDoc Interface when an IDoc of the new message type is received.

  • Enter transaction code WE42
  • Enter process code and a description. Choose the Processing with ALE and Processing by function module options and save your entries. In the maintenance screen assign the inbound function module to the process code.
  • Choose new entries
  • In the detail screen enter Process code, Module fame, Idoc fame, Application Object fame etc
  • Save
  • Enter transaction code WE42 again
  • Go back to maintain the inbound process codes and choose the Logical message navigation.
  • Choose change mode and select new entries
  • Enter the message type and process code
  • Save

Step 8: Defining a partner

The new basic type must be entered in the partner profiles before being used. Use transaction code WE20 to create partner profile. Partner number, partner type, Partner function, message type, permitted agent and process code are the important fields to maintain in inbound partner profiles.


These are the common steps involved in creating a new basic type Idoc. The other steps you need to do after this may be

  • Create Logical System
  • Create RFC destination
  • Using of test tool for IDOC
Also Read : IDoc Structure -> IDOC status codes