IDOC

IDOC stands for an intermediate document where data will be transferred and received in receiver
system through EDI (electronic data interchange). IDOC is an interface

Where data exchange between 2 systems takes place with help of IDOC on the basis of
requirement.

Methodologies in IDOC

1. ALE IDOC will be use for transferred data between SAP to SAP systems

2. EDI IDOC will be use for transferred data between SAP to non SAP systems

In this document we will learn the below listed content:

 What is an IDOC? Data transfer types through IDOC

 IDOC Types
 Structure of IDOC
 What is a Segment?
 What is Port
 Process Code
 Message Types
 Partner Profiles
 The Outbound Process
 The Inbound Process

Data Transfer types through IDOC

1. Inbound 2. Outbound

Inbound Outbound

1. The process of data transfer into your SAP 1. The process of data transfer out of your SAP
system is called Inbound process. system is called the Outbound process.
2. Ex: Order confirmation from vendor 2. Ex: Sending PO copy to vendor
3. Business  Vendor 3. Business Vendor

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
IDOC types
1. Basic

SAP provides many a pre-defined Basic IDOC Types which cannot be modified.

2. Extension

In case you want to add more data to this restricted basic type you may use an extension type.
Most of the times you will NOT use extension

T code: WE30

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
The IDOC itself is made up of three tiers
Tier 1 – The Control Record
The control record shows you the direction, basic type and message type of the IDOC. It also
shows you the sender and recipient partners.

Display IDOC  WE02

Tier 2 – The Data Records

The data records houses all the segments of the IDOC. Each segment contains data which is used in
the recipient system to fulfil the process in question.

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
Tier 3 – The Status Records
Shows all the status records which the IDOC has gone through in its lifetime, in reverse
chronological order.

What is segment?
A Segment defines the format and structure of a data record in IDOC, where you will save all type of
fields called as segment.

Ex: we are sending a PO copy to vendor that PO copy consist of some fields like material number,
description and quantity etc these all fields we are saving in segment.

Types of segment

1. Parent (Basic type)

SAP standard segments which can’t be modified

2. Child (Extension type)

Customized segment where we can change fields

Note: not recommended to create extension type segment for Functional consultants It’s always
created by EDI experts or Basis consultants

T code: WE31

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
What is PORT?
The port defines the technical characteristics of the connection between your SAP system and the
other system you want to transfer data with (subsystem). The port defines the medium in which
data is exchanged between the 2 systems

Port number contains the receiver details where we are sending the data to partner port number
contains the IP address of the receiving partner to flow the data

Port number has to provide by basis team

T code: WE21

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
Process code
Process code is to convert the message type to receiving tool language, it’s a piece of code where
we have mentioned segments for fields and sending PO through electronic message and now
technical team will prepare code for this it’s just a code which convert the message type form SAP
language to other receiving format language.

Types of receiving systems

1. Vendor (during Procurement)

2. Customer (during sales)

3. Logical system (during data transfer within organization)

T code: WE60

Message type
A message represents a specific type of document that is transmitted between two partners Ex.
Orders, orders responses, invoices etc. An IDOC type can be associated with many message types
also a message type can be associated with different IDOC types.

T code: WE81

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
Partner Profiles
A partner is defined as a business partner with whom you conduct business and exchange
documents In the partner profile of a partner that we exchange IDOC with, we maintain the
parameters that are necessary for exchanging the data.

T code: WE20

We have different types of partner profiles

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
Vendor LI

Customer KU

Logical system LS

Let’s Take an Example and try to understand process of creating IDOC

 Whenever a Purchase Order (PO) is created we want to send the IDOC to a vendor.
 The PO is sent in the form of an IDOC to the vendor (partner). That partner has to be EDI
enabled in that system. SAP should realize that it could send doc to this vendor
electronically.
 The PO sent as an outbound IDOC by the customer will be inbound IDOC for the vendor. The
SAP system on the vendor’s side can process this to create an application document (a sales
order) on their system.
 Quotation, RFQ, PO, SO, Invoice, delivery note etc are some of the commonly exchanged
documents through IDOC

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
Outbound Process in IDOC

Steps Involved

1. Create segments (WE31)

2. Create an IDOC type (WE30)
3. Create a message type (WE81)
4. Associate a message type to IDOC type (WE82)
5. Create a port (WE21)
6. Create a partner profile (WE20) with the necessary information in the outbound parameters
for the partner you want to exchange the IDOC.

1. Create segments (WE31)

2. Create an IDOC type (WE30)

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
3. Create a message type (WE81)

4. Associate a message type to IDOC type (WE82)

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
5. Create a port (WE21)

6. Create a partner profile (WE20)

Before creating partner profile lets create a vendor in XK01

Vendor 0000100826 has been created

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
Partner profile creation in WE20

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
Partner profile has been created

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)
The Inbound Process
Steps Involved

1. Creation of basic IDOC type (Transaction WE30)

2. Creating message type (Transaction WE81)
3. Associating the Message type to basic IDOC type (Transaction WE82)
4. Allocate the inbound function module to the message type(WE57)
5. Defining process code (Transaction WE42)
6. Creation of partner profile (Transaction WE20)

6360959192 www.tagskills.com support@tagskills.com

Linked In | Ameersuhil Dafedar

(SAP MM Associate)