Contents

1. IDoc Introduction................................................................................................................................................................................................. 1
2. Standard Inbound/Outbound IDoc......................................................................................................................................................................3
a. Sample Scenario for Standard Inbound/Outbound IDoc..................................................................................................................................3
b. Inbound Standard (Sales Order ORDERS against customer - KU).....................................................................................................................3
c. Outbound Standard (Sales Order INVOIC customer - KU)................................................................................................................................5
d. Test cases created in D19 System for standard Inbound / Outbound IDoc....................................................................................................12
3. Change Pointers (Example Material Master – Message Type MATMAS)...........................................................................................................12
4. Custom Inbound / Outbound IDoc..................................................................................................................................................................... 15
a. Sample Scenario for Custom Inbound / Outbound IDoc................................................................................................................................15
b. Custom Inbound IDoc.................................................................................................................................................................................... 15
c. Custom Outbound IDoc.................................................................................................................................................................................. 17
d. Test cases created for custom Inbound & Outbound IDoc in D19 system.....................................................................................................20
5. Miscellaneous T-codes & useful points for IDocs...............................................................................................................................................20
6. EDI standards..................................................................................................................................................................................................... 20
7. Miscellaneous.................................................................................................................................................................................................... 21

1. IDoc Introduction

1. IDoc - Intermediate Document to transfer data from one system to another.

2. Methods of transfer:
 a. ALE - ALE stands for Application Link Enabling. Application Link Enabling is a very common technology used in SAP to transfer
master and transactional data between different Logical Systems. ALE is a proprietary SAP technology.

b. EDI - EDI stands for Electronic Data Interchange. EDI is a much older term and has been used in existence much before SAP. EDI
is a generic technology that has been standardized using ANSI and EDIFACT standards. EDI is a very standard Industry standard
used for business communication across partners.

Note: EDI is used to communicate with Partner Systems, while ALE is used to communicate between Logical Systems. Please do
however observe that a Partner System could also be a logical system.

3. Message type: A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A
message type characterizes the data sent across systems and relates to the structure of the data called an IDOC type. For example,
MATMAS is a message type for Material Master, and INVOIC is a message type for an Invoice (Billing Document).

4. Basic type (IDoc Type): Basic/IDoc type represents the structure and sequence of the data transferred from one system to another
system.

5. IDoc structure
a. Control Record
b. Data Record
c. Status Record

6. Types of IDoc:
a. Outbound
b. Inbound
2. Standard Inbound/Outbound IDoc

a. Sample Scenario for Standard Inbound/Outbound IDoc

b. Inbound Standard (Sales Order ORDERS against customer - KU)

1. Identify the appropriate Message type

WE81 - Message Type (ORDERS)

2. Identify the appropriate IDoc/Basic type

WE82 - Link between Message Type & IDoc type (ORDERS -> ORDERS05)

3. Display the IDoc/Basic type

WE30 - Basic Type (ORDERS05)

4. IDoc/Basic type Documentation

WE60 - IDoc Documentation (Explain Qualifier segments too)
5. Identify the inbound process code and see the FM attached to the process code for IDoc processing
WE42 - Inbound Process Code (ORDE)

6. To set up the partner profile for receiving the IDoc

WE20 - Partner Profile (Partner No. 100003 & Partner Type: KU)

7. Creation logical system

SALE - IMG for IDoc Interface / Application Link Enabling (ALE)

8. To process IDoc which are in status 64 - IDoc ready to be transferred to application

BD20 - Inbound Processing of IDocs Ready for Transfer (Program: RBDAPP01)
 9. To edit an inbound IDoc and reprocess it.
a. WE02 - To edit IDoc (Double click the segment -> Data Record -> Change) - On save, Original IDoc will be set with status 69 -
'IDoc was edited' and a new duplicate IDoc will be created with status 70 - 'Original of an IDoc which was edited' with
original IDoc.
b. WPIE - Reprocessing of Edited IDocs (Program: RBDAGAIE) with status 69

10. Additional T-codes needed and points to be noted for Inbound IDoc with extension
a. WE31 - To create segment (ZE1EDK01)
b. WE30 - To create extension (ZORDERS05)
c. WE82 - To link the extension to the existing standard message type and IDoc/Basic type (ORDERS -> ORDERS05 ->
ZORDERS05)
d. WE42 - To create new custom process code if needed. The new custom FM to be attached should have same parameters as
of any standard inbound IDoc processing FM.
- If going with standard process code, check the attached FM to the process code and see the customer exits available to
read the data from the Z segment and implement the necessary functionality

c. Outbound Standard (Sales Order INVOIC customer - KU)

1. Identify the appropriate Message type

WE81 - Message Type (INVOIC)

2. Identify the appropriate IDoc/Basic type

WE82 - Link between Message Type & IDoc type (INVOIC -> INVOIC02)

3. Display the IDoc/Basic type

WE30 - Basic Type (INVOIC02)

4. IDoc/Basic type Documentation

WE60 - IDoc Documentation (Explain Qualifier segments too)

5. Identify the outbound process code and see the FM attached to the process code for IDoc processing
WE41 - Outbound Process Code (SD09)
6. Decide on the method of IDoc triggering
a. Report/FM/Module Pool Program - Write the logic to fill the IDoc control data and IDoc data and
i. call the Standard FM to send the IDoc - IDOC_OUTPUT_INVOIC identified from the process code
ii. call the FM: MASTER_IDOC_DISTRIBUTE followed by FM's: DB_COMMIT (to change the status of IDoc from 30 to 03),
EDI_DOCUMENT_DEQUEUE_LATER (call inside the loop of date received in table parameter
COMMUNICATION_IDOC_CONTROL from FM: MASTER_IDOC_DISTRIBUTE) and commit and wait to send the IDoc.

b. Via Output Type - Identify the right output type and do the necessary NACE configuration with the help of functional

7. To set up the partner profile for receiving the IDoc

WE20 - Partner Profile
Note: Message control tab to link output type and outbound process code.
8. Creation logical system
SALE - IMG for IDoc Interface / Application Link Enabling (ALE)

9. Port creation and maintain the RFC destination

WE21 – Port
SM59 - RFC destination
10. To process IDoc which are in status 30 - IDoc ready for dispatch (ALE service)
WE14 - Process All Selected IDocs (EDI) (Program: RSEOUT00)

11. Additional T-codes needed and points to be noted for Inbound IDoc with extension
a. WE31 - To create segment (ZE1EDK01)
b. WE30 - To create extension (ZINVOIC02)
c. WE82 - To link the extension to the existing standard message type and IDoc/Basic type (INVOIC -> INVOIC02 -> ZINVOIC02)
d. WE20 - Partner Profile
e. WE41 - To create new custom process code if needed. The new custom FM to be attached should have same parameters as
of any standard outbound IDoc processing FM.
- If going with standard process code, check the attached FM to the process code and see the customer exits available to fill
the data in the Z segment
 d. Test cases created in D19 System for standard Inbound / Outbound IDoc

Sales Order: 1336 (Inbound IDoc: 0000000000019028)

Delivery: 80001091
Invoice: 90001043 (Outbound IDoc: 0000000000019029)

Inbound IDoc with extension: 0000000000019032

Outbound IDoc with extension: 0000000000019034

3. Change Pointers (Example Material Master – Message Type MATMAS)

Material Master Material Master

SAP Bi/BW
D19
system

1. BD61 - Activate Change Pointers generally

2. BD50 - Activate change pointer for message type (MATMAS)
3. BD52 - Activate change pointer per change document item
4. BD64 - Maintenance of Distribution Model (IMG is SALE) – Mandatory for change pointers (Filter group is optional)
 5. BD21 - Create IDOC type from change pointers (Program: RBDMIDOC)
6. BD22 - Delete Change Pointers (Program: RBDCPCLR)
7. BD59 - Assignment of Object type to Message (for additional Filters in BD64)
8. BD95 - ALE Object Type (for additional Filters in BD64)

Use the t-codes listed in standard inbound/outbound case to identify the correct message type, IDoc type and do the necessary partner
profile set up before triggering the change pointer IDocs.

Partner Profile set up

Test IDoc’s created in D19 system: 0000000000019043, 0000000000019044, 0000000000019045
4. Custom Inbound / Outbound IDoc

a. Sample Scenario for Custom Inbound / Outbound IDoc

Budget (Reward)

EDI Service Customer 1 (text)

Provider System
D19 Customer 2 (PDF)

Customer 3 (Excel)
SEEBURGER

Budget Utilization

b. Custom Inbound IDoc

1. Create Segments
WE31 - Create Segments (ZBUDGET_HDR)

2. Create Basic type

WE30 - Create Basic type (ZBUDGET_IN)
3. Create Message type
WE81 - Message Type (ZBUDGET)

4. Identify the appropriate IDoc/Basic type

WE82 - Link between Message Type & IDoc type (ZBUDGET -> ZBUDGET_IN)

5. Create FM to process the inbound IDoc. The new custom FM to be attached should have same parameters as of any standard
outbound IDoc processing FM.
SE37 - FM to process the inbound FM. (ZBUDGET_IDOC_INPUT)

6. Create an entry of the above FM in BD51 so that the function Module can be attached to process code in WE42.
BD51 - Characteristics of Inbound FM. (ZBUDGET_IDOC_INPUT)

7. Create an entry of the Function Module in WE57. This step attaches the FM with Inbound IDoc type and the message type.
WE57 - Assignment of FM to Message and IDoc Type (ZBUDGET_IDOC_INPUT -> ZBUDGET_IN -> ZBUDGET)

8. Create new inbound process code and attach the new custom FM to the process code for IDoc processing and the message type
under logical messages.
WE42 - Inbound Process Code (ZBUD)
 9. To set up the partner profile for receiving the IDoc
WE20 - Partner Profile

c. Custom Outbound IDoc

1. Create Segments
WE31 - Create Segments (ZBUDGET_HDR, ZBUDGET_UTIL)

2. Create Basic type

WE30 - Create Basic type (ZBUDGET_OUT)
3. Create Message type
WE81 - Message Type (ZBUDGET)

4. Identify the appropriate IDoc/Basic type

WE82 - Link between Message Type & IDoc type (ZBUDGET -> ZBUDGET_OUT)
5. To set up the partner profile for sending the IDoc
WE20 - Partner Profile
 6. Create a custom report to fill the segments and trigger the IDoc
SE38 - To create the report (ZBUDGET_UTILIZATION_OUTPUT)

d. Test cases created for custom Inbound & Outbound IDoc in D19 system

1. Inbound IDoc: 0000000000019046

2. Outbound IDoc: 0000000000019050, 0000000000019049
3. Z Tables: ZBUDGET_HEADER, ZBUDGET_UTILIZE

5. Miscellaneous T-codes & useful points for IDocs.

1. WE11 - To delete IDocs

2. WE09 - To search IDoc content
3. Report: RC1_IDOC_SET_STATUS - To change the status of an IDoc
4. Error IDoc processing
a. BD87 - To reprocess error IDoc
b. WE19 - To reprocess error IDoc but will create a fresh one
5. WE02 - More options in the t-code
a. To see status of IDoc one by one or for more IDocs in one going (message type wise/status wise) - Second last button on
application toolbar
b. To see data in a segment of IDoc one by one or for more IDocs in one going (message type wise/status wise) - Last button on
application toolbar
6. BADI: IDOC_CREATION_CHECK - this is last point before actual Outbound IDoc processing which can be utilized to stop IDoc creation as
per your requirement.

6. EDI standards
  Refer the below link to know more about each EDI standards
https://www.edibasics.com/edi-resources/document-standards/#ansi

 Refer the blow line to know about top EDI third service providers
https://www.youredi.com/blog/25-great-edi-service-providers

 EDI Notepad - Choose Express Edition for free access

https://liaison-edi-notepad.software.informer.com/8.1/

 EDI Transaction Set for ANSI & EDIFACT

 Sample 850 file

o ANSI X12

o EDIFACT

7. Miscellaneous

 Output Management via BRF+ - With SAP S/4 HANA a new Output Management approach is in place.
The complete configuration differs from the configuration that is used when output management is based on NAST (condition
technique). The configuration is based on BRF+.
https://blogs.sap.com/2016/04/01/output-management-via-brf/
 Table Used -
o APOC_D_OR_ITEM - Output Request Item (replacement for NAST)
o APOC_I_OUTP_TYPE - Output Type

 T-code to trigger output type against billing document - VF31F