Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Creating the Custom Idoc for Inbound Processing

Former Member
0 Kudos

Deal All,

Please any body can send the docs/links to create the Custom Idoc for Inbound processing step by step.

Regards

Sridhar

3 REPLIES 3

former_member480923
Active Contributor
0 Kudos

Here are the Steps for the same

1) Create segment (WE31)

Of course it will have naming convention for different company. Here are some tips:

If you copy from existing or std segment eg: Z1E1EDP01_01.

If not you can just put Z1u2026.but this is only the example.

2) Create IDOC Types (WE30)

3) Create message type (WE81)

4) Link message type with basic type (WE82)

5) Create FM

In the FM all the attributes should be the same for Inbound or Outbound. Basically you can get an example from the std FM eg: Inbound - IDOC_INPUT_DELVRY

Outbound - IDOC_OUTPUT_SHPMNT.

6) Create Process Code (Inbound - WE41/ Outbound - WE42)

IMPORTANT: Before you key in the FM, you are required to add the FM in this table V_TBD51.

7) Link FM with Basic Type

For testing go to WE19.

Here are some of the std program that you can use for IDOC:

1) RSNAST00 - Issuing Output type

2) RBDINPUT - Processing Inbound idocs

3) RBDAPP01 - Processing Idocs that already processed before

4) RBDSEMAT- Stand alone program to generate IDocs (Send Material)

5) RBDMIDOC - Outbound triggered from change pointer

6) RSEINB00 - Convert file to IDOC in status 64

Hope that Helps

Anirban M.

0 Kudos

HI,

Thank you for helping in ther creation of Custom Idoc.

Regards

Goli Sridhar

Former Member
0 Kudos

Hi,

As Anirban discussed follow the steps to create Idoc. But get the message type and IDoc type information from the senders end. Create the message type and idoc type same as the senders. As you have to create an inbound processing.

Regards,

Naresh.