BAPI based IDOC

Posted on Mar. 15, 2010 at 02.28 PM - Kuala Lumpur, Malaysia

There are 2 types of IDOC based on how it's created, those are:

1. Conventional IDOC and,

2. BAPI based IDOC.

SAP has hinted that its future direction is to provide more BAPI based IDOC. The advantages are quite obvious, if we compare it to the conventional IDOC:

1. BAPI can be used in any RFC scenario with ABAP or any external programming language through connector

2. BAPI can become promoted as method of a business object which later can be used in workflow, or external communications, etc

3. Through SAP standard transaction BDBG, BAPI can be promoted as an IDOC. All necessary segment, IDOC type and other configuration will be automatically populated, unlike the conventional IDOC where we have to do all these things manually

This time I would like to discuss on how to create BAPI based IDOC.

1. Create BAPI using transaction SE37. Make sure you follow any BAPI naming convention & standards

2. Promote BAPI as method of a business object type using transaction SWO1

Over here you can create a new business object, create a subtype, or copy from SAP standard business object type

3. Create message type, IDOC type, segments, and its necessary configurations using transaction BDBG

4. Create necessary ALE configuration to test the new generated IDOC. Check it out with transaction WE02 or WE05 :)

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