Conventional IDOC

Posted on Mar. 17, 2010 at 02.56 PM - Kuala Lumpur, Malaysia

BAPI Based IDOC is a way to go for most of the new IDOC development. However, sometime we might just want to create new conventional IDOC just because we can copy most of the stuff from SAP standard conventional IDOC. Following is the step by step required:

1. Create segment type using transaction WE31

2. Create IDOC type and attach all the segments to it, using transaction WE30

3. When you are satisfied with your IDoc structure and segments, you can release them formally to signify their

completion and make them available for transport to the test and production systems. First, you release the

segments; then, you release the basic IDoc type.

4. Changes to basic IDoc types and segments are recorded in a change request. After you transport the objects,

you can also manually re−transport them from the segment editor and IDoc editor screens by choosing

Segment, Transport and Development Object, Transport, respectively. Transporting a segment transports all

the segment definitions and documentation, but transporting an IDoc does not automatically transport all the

segments.

5. Create a new message type using transaction WE81

5. Link the message type with the IDOC type using transaction WE82

6. Create new process code, using transaction WE41 for outbound or WE42 for inbound

7. Link the message type with the function module using transaction BD60

8. Link the message type, IDOC type and function module using transaction WE57

9. Define setting for the function module (Inbound) using transaction BD51

10. Congratulations! The new IDOC is ready. Create ALE configuration and test the new IDOC!

We have not discussed on how to create the conventional IDOC posting FM, so far, I will show you what needs to be done in another blog.

Life is beautiful! Let's make it meaningful and colorful!