SAP StackFICOHRMMSDPMPSABAPNetWeaverTablesTcodes ☰MENU

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

Step 2: Define a basic Idoc Type

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

Steps to assign basic Idoc type to message type

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.

 

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.

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

Also Read : IDoc Structure -> IDOC status codes

SAP ALECRMSCMSRMSAP Solutions SAP ReferencesSAP BasicsPP ModuleWMSAP Partners
HomeContact & Privacy PolicyTwitter
All of the product names here are trademarks of their respective companies. The site sapstack.com is not affiliated with SAP AG.
©2018 sapstack.com