Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1of 1

Points to remember:

In SAP Outbound Idoc is represented by �1� Inbound is represented by �2�.

Staus of Idoc can check in WE02 & WE05

Partner type is KU for customer, LI for vendor and LS for Logical System.

Idocs are assigned to Message output types of application documents in T.code NACE

Idoc consists of control reocords(technical configuration), Data Records(Segements


and field names) & Status records (status messages) (t.code we02)

Status messages of outbound Idocs


01: IDoc generation successful
30: IDoc is ready to be processed by IDoc Processing job
03: IDoc data is passed to the Port
18: IDoc successfully triggered EDI subsystem
06: IDoc data translated to EDI format
12: IDoc is dispatched successfully to the partner
16: Partner has received the IDoc successfully

Status messages of Inbound Idocs


50: IDoc received successfully in the system
64: IDoc is ready to be processed by IDoc processing job
53: Application document created and saved successfully

Background jobs to process Idocs


RBDAPP01 - Inbound IDocs
RSEOUT00 - Outbound IDocs

Standard tables of Idoc EDIDC, EDID4 and EDIDS.

If Idoc fails then Re-processing of Idocs is done manually in BD87.

Standard IDoc types for Purchase order


Basic Type: ORDERS04, ORDERS05
Message Type: ORDERS - Purchase Order
Message Type: ORDCHG - Purchase Order Change

Standard Idoc types For Invoice


Basic Type: INVOIC01
Message Type: INVOIC

You might also like