7/14/2019 idoc[1]

1/14

SAP IDOC Application Link Enabling

SAP IDOC Technology allows two different systems to talk to each

other.

The Communication is established using ports

Flat File,

Middleware

Another SAP systems

Message Types are type of IDOC that is used to send and receive

data.

Message Type point to IDOC type that describes the

communication structure

7/14/2019 idoc[1]

2/14

SAP IDOC Business Application

Send Purchase Order to Vendor

Vendor has capability to accept 850/860 EDI

SAP System will create IDOC ORDERS upon save of PO

(Message Control in ME22N will be used to send IDOC)

SAP ALE interface will send the IDOC to preconfigured PORT that

could be a file, middleware or SAP system

Middleware will convert IDOC message into EDI 850 and send it to

the Vendor

7/14/2019 idoc[1]

3/14

SAP PO created:

ME21N

Issue PO Output:

ME22N

Issue PO Output:

ME9F

IDOC Created:

WE05

IDOC Sent to

Middleware

Middleware sends

850 to Vendor

How Purchase Order Is Sent From Sap to Vendor?

7/14/2019 idoc[1]

4/14

IDOC Monitoring Tools

BD87: IDOC Status Monitor

You will see list of all IDOC searched along with their current status. You couldeither display the IDOC data or process them further for posting into application

WE05: IDOC ListQuick tool to see list of IDOC moving into and out of system. It is only a list so you

cant do anything with the IDOC list displayed.

WE09: IDOC Search based on Segment ContentTool to search IDOC based on date, time, segment content, receiver port etc

WE19: IDOC DebugTool to process a single IDOC and debug inbound and outbound functions

WE08: IDOC file statusMonitor size of IDOC file configured in port

WE11: Delete IDOC Data

7/14/2019 idoc[1]

5/14

Configure IDOC Model

Create RFC destination for the receiving system

SM59: Create RFC Destination for SAP systems and middleware systems

Configure Port to point to RFC destination WE21: Maintain communication ports for file, middleware and sap systems

SALE: IDOC Interface Configuration

Define Logical System Assign Logical System to client

Maintain Distribution Model

Generate Partner Profiles

Distribute the model

Maintain Partner Profiles WE20 Partner Profile

Assign inbound and outbound messages

Partners are customer, vendor and logical systems

7/14/2019 idoc[1]

6/14

Transaction WE20: LI : Send PO to Vendor : Outbound

WE20 [ Maintain Partner Profiles ]:

Select Node Partner type LICreate New Partner

Partner No: Vendor NumberPartner Role: VNMessage type: ORDERS (new Order) or ORDCHG (order change)

Outbound OptionsBasic Type: ORDERS03Receiver Port (one of the following):

FilePort pointing to SAP System

Port pointing to Middleware System

Message ControlApplication: EFMessage Type: NEUProcess Code: ME10

7/14/2019 idoc[1]

7/14

Send PO IDOC to Vendor

Configure Vendor as a partner in WE20

Change PO using ME22N

Go to Messages

Select following options

Output : NEU

Medium: EDIPartner function: VN

Partner: [Vendor Number ]

Click on further options

Dispatch Time: Send Immediately (When Saving The Application)

Save the PO

Check WE05 to see IDOC has been sent(Check NAST table for processing date, if date is present then the IDOC is sent)

7/14/2019 idoc[1]

8/14

Transaction WE20: LI : Receive Order Confirmation from Vendor

WE20 [ Maintain Partner Profiles ] [ Inbound ] :

Select Node Partner type LICreate New Partner

Partner No: Vendor Number

Partner Role: VN

Message Type: ORDRSP

Process Code: ORDR

[ Background Function: IDOC_INPUT_ORDRSP ]

Go inside the ORDR process code to find object and event in order

to link it to a workflow in case of error

7/14/2019 idoc[1]

9/14

Transaction WE20: LI : Receive ASN from Vendor

WE20 [ Maintain Partner Profiles ] [ Inbound ] :

Select Node Partner type LICreate New Partner

Partner No: Vendor Number

Partner Role: VN

Message Type: DESADV

Process Code: DELS

[ Background Function: IDOC_INPUT_DESADV1 ]

If you like your own processing code then create one coping

IDOC_INPUT_DESADV1 to a new Z Function module

7/14/2019 idoc[1]

10/14

How to send Delivery Shipping Notification to Vendor?

Send Delivery Advise to Vendor [ Outbound ]

Partner Role: DP

Message Type: DESADV

Receiving Port: File

Basic Type: DELVRY03Extension: ZDELVR03

Message Control

Application: V2

Message Type: ZMSG

Process Code: ZDELR [ point to copy of

ZZ_IDOC_OUTPUT_DELVRY ]

ZZ_IDOC_OUTPUT_DELVRYwould process the normal segments withIDOC_OUTPUT_DELVRY & you could perform your custom task with rest of the

segment

7/14/2019 idoc[1]

11/14

How to receive Invoice from Vendor?

Receive Billing Document from Vendor [ Inbound ]

Partner Role:

Message Type: INVOIC

Message Code: FI

Process Code: INVF [ Background Function:IDOC_INPUT_INVOIC_FI ]

Receive Logistics Invoice from Vendor [ Inbound ]

Partner Role:

Message Type: INVOIC

Message Code: MM

Process Code: INVL

[ Background Function:IDOC_INPUT_INVOIC_MRM ]

7/14/2019 idoc[1]

12/14

850 PO

IDOC: ORDERS

860 PO Change

IDOC: ORDCHG

855 PO ConfirmationIDOC: ORDRSP

865 PO Change ConfirmationIDOC: ORDRSP

810 Invoice/Bill

IDOC: INVOIC820 EFT PaymentIDOC: REMADV/

PEXR2002

856 Adv Shipment NotificationIDOC: DESADV

Note 104606 - Mapping IDOC types to ANSI X12

MIDDLEWARE

Send Purchase Order to Vendor

Send PO Change to Vendor

Send Payment to Vendor

Vendor Sends Order Confirmation

Vendor Sends Change Acknowledgement

Vendor Sends Delivery Shipment Notice

Vendor Sends Invoice for Payment

Purchasing EDI Integration SAP Landscape

7/14/2019 idoc[1]

13/14

Direction Document

Partner

Role

Message

Type Basic Type

Receiver

Port App

Message

Type

Process

Code

Outbound PO VN ORDERS ORDERS05 File EF NEU ME10

Outbound PO CHG VN ORDCHG ORDERS05 SAP EF ZNEU ME11

Outbound ASN DP DESADV DELVRY03 Middleware V2 ZMSG ZDELR

Message ControlOutbound OptionsParameters

Direction Document

Partner

Role

Message

Type Basic Type

Process

Code

Inbound PO CONF VN ORDRSP ORDERS05 ORDRInbound ASN VN DESADV DELVRY03 DELS

Inbound INVOICE MM INVOIC MM INVL

Inbound INVOICE FI INVOIC FI INVF

IDOC_INPUT_ORDRSPIDOC_INPUT_DESADV1

IDOC_INPUT_INVOIC_MRM

IDOC_INPUT_INVOIC_FI

Function ModuleParameters Inbound Options

Purchasing EDI Integration Outbound

Purchasing EDI Integration Inbound

7/14/2019 idoc[1]

14/14

Why do we need Middleware?

Most of the Supplier systems are not SAP systems.

We need to convert SAP IDOC into EDI compatible format

SAP IDOC can be sent to Middleware system like XI or Websphere

Middleware will phrase the IDOC and make a EDI packet

EDI packet is delivered to Supplier

It is a confirmed delivery. The middleware will keep trying sending

the message until it is delivered to Supplier.