SAP IDOC (Intermediate Document)

Uplatz offers this comprehensive training on SAP IDOC module. This is video-based online course (self-paced training). You will be awarded Course Completion Certificate at the end of the course.

IDOC (intermediate document) is a standard data structure used in SAP applications to transfer data to and from SAP system applications and external systems. Using IDocs, companies with SAP ERP systems, for example, can exchange data with external entities like their partners or customers. IDOC is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. It exchanges data using Application Link Enabling (ALE) processes.

In summary, IDoc is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. Using IDocs, companies with SAP ERP systems, for example, can exchange data with external entities like their partners (Customers, Suppliers, Logistic Providers etc.).

The transfer from SAP to non-SAP system is done via EDI subsystems whereas for transfer between two SAP systems, ALE is used. The transfer between SAP systems is done through SAP's Application Link Enabling (ALE) system, while the transfer from an SAP system to an external system happens through electronic data interchange (EDI). This allows data to be exchanged between the different systems without having to convert data from one format to another.

IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. By comparison, another SAP mechanism, the Business Application Programming Interface (BAPI), is used for synchronous transactions. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.

IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.

An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. In other words, an IDOC is like a data file with a specified format which is exchanged between 2 systems which know how to interpret that data.

Each IDOC is assigned a unique number for tracking and future reference. IDOC consists of several segments, and segments contain several fields.

Key Features of IDoc:

IDOCs are independent of the sending and receiving systems.(SAP-to-SAP as well as Non-SAP)

IDOCs are based on EDI standards, ANSI ASC X12 and EDIFACT. In a case of any conflict in data size, it adopts one with greater length.

IDOCs are independent of the direction of data exchange e.g. ORDERS01: Purchasing module: Inbound and Outbound

IDOCs can be viewed in a text editor. Data is stored in character format instead of binary format.

In IDOCs the following terms are to be known:

Port

Port is used in the outbound process to determine the name of the EDI subsystem program, the directory path where the IDOC file will be created at the operating system level, the IDOC file names and the RFC destinations.

RFC Destination

Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.

Partner Profile

Partner profile specified the various components used in an outbound process (Partner number, IDOC type, message type, Port, Process code), the mode in which it communicates with the subsystem (batch or immediate) and the person to be notified in case of errors.

Message Control

Used in pricing, account determination, material determination, and output determination. The message control component enables you to encapsulate business rules with out having to write ABAP programs.

Certificate of completion

Digital certificate - Included

Reed courses certificate of completion

Digital certificate - Included

• SAP IDOC - all lectures 10:09:05

  • 1: SAP IDoc Introduction 1:15:34
  • 2: IDOC Type 40:53
  • 3: Logical Systems in IDOC 26:06
  • 4: Configuration of RFC Connection in IDOC 11:35
  • 5: Creating port in IDOC System 06:13
  • 6: Configuration of Partner Profile in IDOC System 08:05
  • 7: Control Record of an IDOC 29:45
  • 8: Logical System in IDOC - Revision 20:33
  • 9: Partner Profile in IDOC 37:03
  • 10: Outbound and Inbound Parameters 55:06
  • 11: How to work with the IDOC System 51:37
  • 12: Function modules to generate IDOCs 34:52
  • 13: MASTER_IDOC_DISTRIBUTE function module 17:30
  • 14: IDOC Lists 33:28
  • 15: Working with Functional Modules in IDOC 58:51
  • 16: Activating Change Pointers 41:50
  • 17: Summary of the SAP IDOC Tutorial 1:00:04

SAP IDOC Course Syllabus

1. EDI and ALE Basics (Introduction)

2. ALE/IDOC Basics

• What is an IDOC and Segment (Anatomy of an IDOC)

• Why ALE and IDOC

• IDOC Type and Message Type (creation)

• IDOC and its Extension (creation)

• What is a Standard IDOC and Custom IDOC

3. Different Ways of Triggering IDOCs

• Standalone (Master and Transactional Data)

• Message Control (Transactional Data)

• Change Pointer (Master Data)

4. Outbound IDOC Processing

a. Connection Configurations in Outbound Systemà

• Logical System

• RFC Destination

• Message Type Creation

• Port Creation

• Partner Profile

b. ALE/IDOC configuration

• Segment Creation

• IDOC Type Creation

• Message Type creation

• Linking IDOC Type to Message Type

5. Inbound IDOC Processing

a. Connection Configurations in Inbound System

b. ALE/IDOC Configuration

• Inbound Function Module

• Inbound Process Code

• Linking Function Module with Basic Type and Message Type.

6. Distribution Model (BD64)

a. Complete scenario to Send IDOC via this model

b. Filters

• IDOC Level (via BD64) ( do not send entire idoc if it does not match with the filter)

• Segment Level (BD56) ( Do not send this SEGMENT if condition is not met)

c. Reduced Message Type Basics (BD53)

7. Complete End-End Standalone Scenario by Using Topics 4 and 5 above

a. Standalone

• Creating and Sending a Standard IDOC from One Application Server to another Application Server

• Creating and Sending a Custom IDOC from One Application Server to another Application Server

b. Custom Program to create the IDOC by using standard FMs

• Message Control

• Nace Configuration

• Selection Programs

• Creating and Sending a Sales Order / Purchase Order IDOC from One Application Server to another Application Server via Message Control

c. Change Pointers

• TCodes and Tables related to Change Pointers

• Scenario to Trigger IDOC automatically whenever there is a change in the Master Data.

8. Re-processing of IDOC (02 ways)

9. Enhancements to standard IDOC ( OPTIONAL Topic )

• a. Enhancing the standard Table and capturing the values.

• b. Extending IDOC and transfer the enhanced field Contents via enhancement techniques (User Exits SMOD/CMOD)

10. Important TCodes, Tables, Statuses and Programs

11. Trouble shooting OutBound / InBound IDOCs

In this IDoc training, the system demonstration will help you clear the concepts used in the management and execution of IDoc.

Record Types in SAP IDoc

1. Control Record contains administrative information such as the IDoc type, message type, current status, sender and receiver.

2. Data Record contains all the IDoc data, which is stored in groups called segments. Each IDoc may contain standard segments and custom segments.

3. Status Record provides information about the various stages the IDoc has passed through.

Types of IDocs

IDocs can be triggered in the SAP system or in the EDI subsystem. An IDoc coming into an SAP system is called an Inbound IDoc, while an IDoc going out of a system is called an Outbound IDoc. An Outbound IDoc is triggered through document message control to the EDI subsystem. EDI then converts the IDoc data into XML or an equivalent format and sends the data to the outside system via the internet. For Inbound IDocs, EDI converts the outside system data and the IDoc is created in SAP. An application document is then posted in the SAP system after it processes the IDoc.

IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.

Advantages of SAP ALE IDOCs?

• It is the tool that it transfer the data

• The very precise it will save the time of end-users

• It will also minimize the paperwork

• It will minimize also manual mistakes

• It is the Structured data exchange

• There is any mistakes it is Error handling

How IDoc is used in SAP

An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest.

After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an S/4HANA, R/3, or other external system.

Ensure that your SAP system is configured to send and receive IDocs from SAP Data Services. To ensure configuration in your SAP system is correct, refer to your SAP application documentation for more information. When you check your configuration, if your SAP system supports it, set the communication type to Unicode.

Configure IDoc message sources, which are SAP outbound IDocs, in the SAP Data Services Designer and in the RFC client branch in the Administrator application of SAP Data Services Management Console. Do not configure RFC clients for IDoc message targets, which are SAP inbound IDocs.

Save IDoc-type settings in the IDoc target editor in a Data Services data flow. IDoc settings for sending messages to SAP applications by transaction remote function calls (tRFC) include:

• Partner number

• Partner type

• Message type

• IDoc type

What are the main advantages of IDOC?

IDoc is the data Format used by the SAP in data transfer using ALE /EDI methods. They provide more data security. An IDoc is an intermediate document used to send data in two ways, that is internal and the external point for you.

In BW, IDoc is a transfer mode, when you create a Infosource you can select the transfer mode as PSA or IDOC. Its the method provided for backward compatibility. In older version the hirerchies where loaded using IDOC transfer method. Now its possible with PSA but still that method is available to load the hierarchies.

Everyone

Passion and determination to achieve your goals!

SAP IDOC Consultant and/or Power User

EDI Developers - SAP iDOC

SAP SD & ABAP Consultant

SAP PI/PO Consultant

EDI Consultant

SAP Programmer Interface Specialist

SAP & ERP Consultant & Manager

Technical Architect

Application Developer

System & Network Designer

Engineering Manager & Program Manager

Currently there are no Q&As for this course. Be the first to ask a question.