Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Infosys

Introduction To IDoc And Configuration Of

Outbound IDoc Interface
March 2014

INFOSYS LIMITED

Bangalore

Document No. Ver. Rev. :

Authorized by: Signature/:

Date:

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

COPYRIGHT NOTICE

©2014 Infosys Limited, Bangalore, India. All rights reserved. Infosys believes the information
in this document is accurate as of its publication date; such information is subject to change
without notice. Infosys acknowledges the proprietary rights of other companies to the
trademarks, product names and such other intellectual property rights mentioned in this
document. Except as expressly permitted, neither this document nor any part of it may be
reproduced, stored in a retrieval system, or transmitted in any form or by any means,
electronic, mechanical, printing, photocopying, recording or otherwise, without the prior
permission of Infosys Limited and/or any named intellectual property rights holders under
this document.

Infosys Limited
Hosur Road
Electronic City, 3rd Cross
Bangalore 560 100
India.
Telephone: (91) (80)28520 261-270
Fax: (91) (80) 8520 362
Website: http://www.infosys.com

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Authors: Sandeep Nomula, Hina Gandhi

Date written: 03/06/14

Project Details

Project(s) involved: SYNBUHYD

H/W Platform: Acer

S/W Environment: SAP ECC 7.1, Windows 7

Application Type: ABAP

Project Type: Support

Target readers: -
SAP ABAP

Prerequisites: -

Basic Knowledge of SAP ABAP.

Keywords: -
SAP, ABAP, IDoc

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Introduction

IDoc means “Intermediate Document”. IDocs are repository used for purpose of data
exchange between two systems. It transfers data from SAP to non-SAP system and vice
versa through EDI (Electronic Data Interchange). IDocs are useful in transferring data
between two SAP systems through ALE (Application Link Enabling). IDoc can be triggered in
SAP system or in EDI subsystem. Each IDoc contain one unique number for tracking and
future reference. IDoc consists of several segments and segments consists of several fields.

In simple language IDoc is an interface used to:

Send messages (Outbound processing)

Receive messages (Inbound processing)

There are three types of records in every IDoc:

Control Record

It contains information like IDoc number, sender’s name, receiver‘s name, channel it is
using, port number etc.

Data Record

It contains the identity of the IDoc, a sequential segment number, a segment type
description and field containing the actual data segment.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Status Record

It has information regarding the processed stages and encountered errors/messages.

Introduction to EDI

EDI is Electronic Data interchange. SAP supports EDI with the help of IDocs. EDI is an
electronic exchange of business documents between the computer systems of business
partners, using a standard format over a communication network. EDI standard data format
can be understood as the common platform to exchange data between different companies.

EDI has two process

1. Outbound process
2. Inbound process

Outbound Process:
1.Application document is created.
2. IDoc is generated
3.Idoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.EDI document is transmitted to the business partner
6.The EDI Subsystem report status to SAP

Inbound Process:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.

Introduction to ALE

ALE is Application link enabling. It is used to exchange data between two SAP systems or
between SAP and non-SAP system e.g. FTP, web services etc. It is used to exchange
messages between different distributed systems.

The distributed systems are coupled in two ways:

Narrow coupling: It involves synchronous communication where both systems are needed
to be available at the time of communication.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Loose coupling: It involves asynchronous communication where called and the calling
system need to be present at the time of communication.

Difference between ALE and EDI

 The basic difference between ALE and EDI is that ALE is used for internal
communication while EDI is used for external communication.
 ALE uses IDoc format to exchange data between two systems so both systems
should understand IDoc format while EDI is for exchanging transaction data between
two business partners. EDI is all about the standards that one has to follow while
exchanging data.
 ALE transfers data using memory buffers while EDI uses ports to transfer data.

 With EDI technology one always need a translator to convert the IDOC to X12
(Outbound), X12 to IDOC (Inbound).But with ALE one does not need a translator.
 EDI is used to communicate with Partner Systems, while ALE is used to communicate
between Logical Systems. However observe that a Partner System could also be a
logical system.

Advantages of IDocs over RFC and Proxy

 IDoc provides asynchronous mode of communication so it is excellent in error

handling than RFC.
 In IDoc there is no need for configuration in XI therefore its processing is faster as
compared to RFC and Proxy.
 Fast to load, easy processing, low programming for standard IDocs in comparison to
Proxy and RFC.

Steps to setup outbound IDoc Interface:

Find the fields from FMD those are available in standard IDoc or not. If any fields are not
available in standard IDoc you should create extension IDoc or new IDoc by adding new
segments.

This is the procedure to create a new custom IDoc.

Step 1: Create segments

Go to transaction we31 to create segment.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Step 2: Create IDoc type.

Go to transaction we30 to create IDoc type.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Step 3: Create the message type.

The message is created using transaction we81.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Step 4: Associating message type with IDoc type using transaction we82.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Step 5: Create port number using transaction we21.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Step 6: Creating the function module without message control to create IDoc.

We are creating a standalone program so function module ‘MASTER_IDOC_DISTRIBUTE’ is

called to create IDoc and the required partner values are properly filled in the code.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Step 7: Creating partner profile using transaction we20.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

The partner number, partner type, partner role, message type, message code, receiver port
etc. all are outbound parameters.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

The partner number, partner type, partner role, message type, message code, process code
all are inbound parameters.

Step 8: triggering the IDoc by running the standalone program.

©2014 Infosys Limited, India

Infosys Introduction to IDoc and configuration of outbound IDoc Interface

Step 9: check the status of the IDoc. If it is 03 this means data passed to port.

Reference:

NA

©2014 Infosys Limited, India