IDoc Basic Overview

ALE

It's stands for application link enabling. it is a technology use for establishing a connection between two or more system.

EDI

It's stands for electronic data interchange. it is used to exchange the data between two systems. Which is sap to sap and sap to non-sap.

IDOC

• It's stands for intermediate document.
• It is a data container.
• It is used to transfer the data between two system.
• IDOC is the collection of segments & each segment is the collection of fields.
• IDoc hold the data in structure format in the fields of segment.

IDOC Structure

There are three structure in idoc.

I. Control Record:

It contains IDOC type & Message type information, Partner information such as partner system number, and the sender & receiver system port number.

It also contains technical & address information of the sender & recipients.

II. Data Record:

These are collections of segments. The data record of an IDOC contains segments.

Segment is a collection of fields that can be distributed the data between the systems.

III. Status record:

It contains the status of the processed IDOC to know where an IDOC has been successful/failed.

The standard table EDIDC contains IDOC information such as control records, different

statuses etc.

Note:

➢ The Sender/Source system is also called an ‘Outbound system’.

➢ The Receiver/Target system is called the ‘Inbound system’.

➢ The T-code ‘WE30’ is used to maintain different types of IDOCs such as Basic IDOCs,

Extended IDOC.

➢ WE02/WE05 T-codes are used to list the generated IDOCs.

➢ The T-code ‘WE19’ is used to test/check the IDOC.

IDOC TYPE

IDoc type is collection of segment.

there are two type of idoc type:

• Basic
• Extension

SEGMENT

• Segment define format and structure of data records.
• It is collection of field.

Custom Segments:

•  The custom segments are starts with Z*/Y* & they are maintained by technical & functional consultants.

Standard Segment:

• These are system-provided segments
• The T-code: WE31 is used to maintain the segments

Message Types:

• A message type indicates what type of data is stored in IDoc. 

for E.g : 

• MATMAS for material master
• CREMAS  for vendor master   
• DEBMAS for customer master

• These are identifiers of the application data to be distributed between the systems.
• The T-code WE81 is used to create & WE82 is to assign the message types to the IDOC (Data carrier).
• EDIDC is standard table that contains all available message type.

LOGICAL SYSTEM

It's unique name assign to each sender and receiver system for identification purpose.

Tcode - BD54 or SALE.

RFC DESTINATION

• it's store the details of receiving system, where idoc has to be send.
• it contains ip/address, client number login credentials.
• it is created only sender system.
• Tcode - SM59
• Table - RFCDES

  Types:

RFC PORT

• it's define medium in which data is exchange.
• It is channel on receiver system through which data is send.

Types:

PARTNER PROFILE

• It store the information about partner system.
• for sender system receiver is the partner and for a receiver system sender is a partner.
• These are used to maintain the partner system details with which data to be distributed such as partner number, Partner type & Message type of outbound parameters.
• For Sender - Receiver logical system + outbound parameter - message type, idoc type, port etc. 
• For Receiver - Sender logical system + inbound parameter - message type, process code.
• Tcode- WE20.
• Table - EDPP1.

MODEL DISTRIBUTION VIEW

• It is used to define a data distribution model to exchange messages between two logical systems (SAP to SAP and SAP to non SAP).
• It is object which stored the sender, receiver information along with message type and filtering condition if maintained.
• The T-code BD64 is used to define/maintain the distribution model.

PROCESS CODE

• It is an identifier for inbound program (FUNCTION MODUEL).
• it's provide a link to the inbound program for reading the incoming IDoc.
• WE41 - OUTBOUND
• WE42 - INBOUND.

FOR E.g:

• ORDR - ORDRSP - PURCHASE ORDER CONFIRMATION.
• ORDE - ORDERS - CREATE SALES ORDER.

IDOC CONFIGURATION STEPS

OUTBOUND

• Define logical system (BD54/SALE)
• Create RFC connection (SM59)
• Port (WE21)
• Segment(WE31)
• Basic Type (WE30)
• Message Type (WE81)
• Assign message type to basic type (WE82)
• Outbound Program / FM.
•  Partner profile (WE20).

INBOUND

• Logical system (BD54)
• Inbound function module (SE37) 
•  BD51 - Register characteristic of inbound function module.
• WE57 - Tcode fro establishing the relationship between function module and message type. 
• Process code (WE42)
• partner profile (WE20).