El ectroni c Data Interchange /

I Doc I nterface (SD-EDI )

H
E
L
P
.
S
D
E
D
I
Rel ease 4. 6C
Electronic Data Interchange / IDoc Interface (SD-EDI) SAP AG
2 April 2001
Copyright

Copyright 2000 SAP AG. All rights reserved.
No part of this brochure may be reproduced or transmitted in any form or for any purpose without
the express permission of SAP AG. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft

, WINDOWS

, NT

, EXCEL

, Word

and SQL Server

are registered trademarks of

Microsoft Corporation.
IBM

, DB2

, OS/2

, DB2/6000

, Parallel Sysplex

, MVS/ESA

, RS/6000

, AIX

, S/390

,
AS/400

, OS/390

, and OS/400

are registered trademarks of IBM Corporation.

ORACLE

is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX

-OnLine for SAP and Informix

Dynamic Server
TM
are registered trademarks of
Informix Software Incorporated.
UNIX

, X/Open

, OSF/1

, and Motif

are registered trademarks of The Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C

, World Wide
Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of
Technology, 545 Technology Square, Cambridge, MA 02139.
JAVA

is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto,
CA 94303 USA.
JAVASCRIPT

is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.
SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com
Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP
Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management
Cockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in several
other countries all over the world. All other products mentioned are trademarks or registered
trademarks of their respective companies.
SAP AG Electronic Data Interchange / IDoc Interface (SD-EDI)
April 2001 3
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Tip
Electronic Data Interchange / IDoc Interface (SD-EDI) SAP AG
4 April 2001
Contents
Electronic Data Interchange / IDoc Interface (SD-EDI) ............................................... 5
Outbound Message Processing (SD) .........................................................................................................7
IDoc Types for Outbound Messages (SD) .................................................................................................8
IDoc Types for Outbound Messages (LE)................................................................................................10
Inbound Message Processing (SD) ..........................................................................................................11
IDoc Types for Inbound Messages (SD) ..................................................................................................12
SAP AG Electronic Data Interchange / IDoc Interface (SD-EDI)
Electronic Data Interchange / IDoc Interface (SD-EDI)
April 2001 5
Electronic Data Interchange / IDoc Interface (SD-EDI)
Purpose
The Electronic Data Interchange (EDI) [Ext.] component in Sales and Distribution consists of an
Intermediate Document (IDoc) [Ext.] interface. You can use this interface to
send messages (outbound processing) such as an order confirmation through Electronic
Data Interchange (EDI)
receive messages (inbound processing) such as a sales order through EDI
Integration
Many large companies (such as automotive suppliers) require their vendors to use EDI.
For information on EDI in the components supplying industry, refer to Intermediate Documents
for Scheduling Agreements [Ext.].
In Sales and Distribution, output determination is initiated during outbound processing.
For information on output determination in Sales and Distribution, see Output Determination (SD)
[Ext.].
For information on output (or message) control in general, see CA - Message Control [Ext.] in
Cross-Application Components.
Features
During outbound processing in Sales and Distribution, the system determines output using the
output determination component. The system converts the data into an IDoc and issues it using
the IDoc interface.
During inbound processing, the sender converts the data into IDocs and passes it on to the IDoc
interface. These IDocs are stored in the SAP System. In a second step, the system creates the
document data.
Electronic Data Interchange / IDoc Interface (SD-EDI) SAP AG
Electronic Data Interchange / IDoc Interface (SD-EDI)
6 April 2001
SAP does not provide EDI converters.
For more information on the IDoc interface in general, see IDoc-Interface / Electronic Data
Interchange [Ext.] in the cross-application documentation The IDoc Interface (BC-SRV-EDI).
SAP AG Electronic Data Interchange / IDoc Interface (SD-EDI)
Outbound Message Processing (SD)
April 2001 7
Outbound Message Processing (SD)
Purpose
This component is used to send EDI messages. In outbound processing, document data is
written to IDocs and sent to the receiving system.
Features
The following outbound EDI messages are available in Sales and Distribution:
quotations
order confirmation
order changes
delivery notes
shipping notifications
invoices
Standards such as EDIFACT, ANSI, ODETTE and VDA are supported.
For more information on outbound processing in general, see Outbound Processing [Ext.] in the
cross-application documentation The IDoc Interface (CA-EDI).
Electronic Data Interchange / IDoc Interface (SD-EDI) SAP AG
IDoc Types for Outbound Messages (SD)
8 April 2001
IDoc Types for Outbound Messages (SD)
The following outbound EDI (Electronic Data Interchange) messages are available in the
standard system.
EDI standard term Output type IDoc type
Quotation QUOTES ORDERS01
ORDERS02
ORDERS03
ORDERS04
Sales order confirmation ORDERSP ORDERS01
ORDERS02
ORDERS03
ORDERS04
Invoice INVOIC INVOIC01
INVOIC02
Invoice list INVOIC INVOIC01
INVOIC02
Foreign trade billing document INVOIC EXPINV01
EXPINV02
The IDoc type is the version number. The highest number always represents the latest version.
In the list above, ORDERS04 is the most up-to-date IDoc type for sales orders.
The segments available in the IDoc are defined in the IDoc type. The following segments have
been added for the IDoc types below:
IDoc type / newly added segments
for:
Segments Description
ORDERS02
Inbound orders with configurable
products
E1CUREF
E1CUCFG
E1CUINS
E1CUPRT
E1CUVAL
Order item reference
Configuration data
Instance data
Part of data
Characteristic valuation
SAP AG Electronic Data Interchange / IDoc Interface (SD-EDI)
IDoc Types for Outbound Messages (SD)
April 2001 9
ORDERS03
Delivery order
E1EDL37
E1EDL38
E1EDL39
E1EDL44
Shipping unit header
Control segment for shipping units
Shipping unit header descriptions
Shipping unit item (delivery)
ORDERS04
Payment cards, additional data
E1EDK35
E1EDK36
E1EDP35
Document header, additional data
Document header, payment cards
Document item, additional data
Electronic Data Interchange / IDoc Interface (SD-EDI) SAP AG
IDoc Types for Outbound Messages (LE)
10 April 2001
IDoc Types for Outbound Messages (LE)
The following outbound EDI (Electronic Data Interchange) messages are available in the
standard system.
EDI standard term Output type IDoc type
Shipping notification DESADV DELVRY01
Shipment notification SHPMNT SHPMNT01
SHPMNT02
The IDoc type is the version number. The highest number always represents the latest version.
SAP AG Electronic Data Interchange / IDoc Interface (SD-EDI)
Inbound Message Processing (SD)
April 2001 11
Inbound Message Processing (SD)
Purpose
If you receive external EDI messages in your SAP System, you need this component to convert
these messages, so that your system can understand them. In inbound processing, IDocs are
transferred to the IDoc interface and stored in the SAP System. The document data is generated
in a second step.
Features
The following inbound EDI message types are available in Sales and Distribution:
inquiries
sales orders
order changes
forecast delivery schedules
JIT delivery schedules
credit memos
pick-up sheets
external agent delivery notes
The system carries out the following tasks:
performs technical and application-specific checks on the data transferred in the IDoc
automatically determines the information which is not present in the IDoc and which is
essential for processing in the SAP System
- determination of the SAP material number on the basis of the customer material number
- determination of organizational data
assigns a status record [Ext.] to the IDoc
For more information on inbound processing in general, see Inbound Processing [Ext.] in the
cross-application documentation The IDoc Interface (CA-EDI).
Electronic Data Interchange / IDoc Interface (SD-EDI) SAP AG
IDoc Types for Inbound Messages (SD)
12 April 2001
IDoc Types for Inbound Messages (SD)
The following inbound EDI (Electronic Data Interchange) messages are available in the standard
system.
EDI standard term Output type IDoc type
Inquiry REQOTE ORDERS01
ORDERS02
ORDERS03
ORDERS04
Sales order ORDERS ORDERS01
ORDERS02
ORDERS03
ORDERS04
Sales order change ORDCHG ORDERS01
ORDERS02
ORDERS03
ORDERS04
Delivery order
(Pick-up sheet)
DELORD ORDERS03
ORDERS04
Forecast delivery schedule DELINS DELFOR01
Just-in-time delivery schedule DELJIT DELFOR01
Self billing procedure GSVERF GSVERF01
External agent delivery note EDLNOT DESADV01
The IDoc type is the version number. The highest number always represents the latest version.
In the list above, ORDERS04 is the most up-to-date IDoc type for sales orders.
For more information on inbound messages in the component supplier industry, see the following
documentation in Scheduling Agreements for Component Suppliers:
Controlling Inbound EDI [Ext.]
Intermediate Documents for Scheduling Agreements [Ext.]
Intermediate Documents for Delivery Orders [Ext.]