1. Changes of the
IDoc Interface
Release 4.5
compared w/ Release 3.1
Thomas Becker
SAP AG
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 1

2. Content
 IDoc Interface Administration
 Interface w/ (EDI) Subsystems
 IDoc Interface Development
 Procurement (Application MM) & Sales (Application SD)
 SBU Automotive
 SBU Retail/CP
 Financials (Application FI)
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 2

3. Global Changes
 Menu path to transaction WEDI changed.
Tools
Business Communication
IDoc
IDoc Basis
 Transaction WE46 gives access to new IDoc interface profile
 From the IDoc interface profile access to Workflow
verification and auto-customizing is granted.
 Notifications for batch of IDocs that failed in report
RSEOUT00 are merged to one single notification assigned to
process code EDIP.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 3

4. Partner Profile
 The table class for all
tables is changed.
 The transport is removed.
General
Partner
Recipient of notifications
 This allows maintenance
also in a production system.
Outbound
Inbound
Partner
Logical message
NAST-Key
Partner
Message
Partner
Logical message
Port
IDoc type
EDI structure
Recipient of notifications
Process code
Recipient of notifications
Process code
Logical message
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 4

5. Partner Profile, add/ functions
 Default values for partner profiles.

Maintenance in IMG (Customizing).

Maintenance dependent on partner type and logical message.

At partner profile maintenance these default values can be
selected by logical message. The values are copied to the partner
profile.
 Selection of processes enhanced.

Process code, logical message and IDoc type are checked
against each other for consistency.

This allows easier and faster access by value-help (F4 help).
 Output of single profile or list of profiles.

Paper print / ABAP list

IDoc message SYPART
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 5

6. Port Definition
 Port definitions are client-dependent for all port types.
 The transport is removed.
 This allows maintenance also in a production system.
 Beside physical pathnames logical pathnames for port type
file can be choosen. The logical pathnames are maintained by
transaction FILE. The function is important for heterogenous
application server environments.
 Mnemonic names for port type tRFC can be choosen.
 All port types got version-field for envelope version

„1“
envelope as defined in releases 2.1/2.2 (file only)

„2“
envelope as defined in releases 3.0/3.1

„3“
envelope as defined in releases 4.0/4.5/4.6
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 6

7. Content
 IDoc Interface Administration
 Interface w/ (EDI) Subsystems
 IDoc Interface Development
 Procurement (Application MM) & Sales (Application SD)
 SBU Automotive
 SBU Retail/CP
 Financials (Application FI)
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 7

8. Port Types
 The port type „Programming Interface“ or ABAP is available
to leverage IDoc for project-specific formatting.
SAP Application
IDoc Interface & ALE Services
IDoc &
status
File
+ RFC
IDoc
EDI
Any
ALE
Any
IDoc
CPI-C
tRFC
2.1 on
IDoc &
status
3.0 on
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 8
MIME
3.0 on
R/2
Internet
IDoc
ABAP
4.5 on
3.1 on
Any

9. Record Types, i.e. Envelopes
Envelope = changed
Control Record, EDIDC
Data Records, EDIDD
E1HDDOC
M
E1TLSUM
1
C
E1HDADR
C
5
E1ITDOC
M
1
E1ITSCH
Tree of Segments
Status Records, EDIDS
IDoc type = unchanged
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 9
C
99
C
5
1

10. Changes in Version 3
 Control record, external tag EDI_DC40

Logical message
MESTYP
6 to 30 char

Basistype
IDOCTYP
8 to 30 char

Extension
CIMTYP
8 to 30 char

IDoc type
DOCTYP
removed
 Data record, external tag by segment name

Segment name
SEGNAM
10 to 30 char

Table name
TABNAM
removed
 Status record, external tag EDI_DS40

Fields related w/ workbench increased
 All fields are resorted, so they are grouped again from a
logical point of view, e.g. sender fields in the control record
and T100 parameter fields in the status record.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 10

11. Changes in Outbound
 In outbounds the sender in the control record, i.e. the SAP
system itself, is now uniquely identified by

SNDPRN = „logical system“

SNDPRT = „LS“
 This is an ALE requirement!
 See OSS note #111342.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 11

12. CA-EDI (Re-)Certification
 Certified process

Purchase Order, out

Customer order, in

Order confirmation, out

P.O. Acknowledgement, in
 Certified functionality

file interface w/ RFC

outbound IDoc

status report

inbound IDoc
Document
System R/3
System R/3
IDoc
Subsystem
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 12
IDoc
Transaction
Subsystem

13. Content
 IDoc Interface Administration
 Interface w/ (EDI) Subsystems
 IDoc Interface Development
 Procurement (Application MM) & Sales (Application SD)
 SBU Automotive
 SBU Retail/CP
 Financials (Application FI)
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 13

14. Tools to Develop an IDoc Type
Tool to define the
IDoc type with its segments
Tool to define the
segment with its fields
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 14
E1HDDOC

15. IDoc Type Editor
 Customer extensions become easier, because IDoc types are
identified by basis type (IDOCTP) and extension type
(CIMTYP) only.
The IDoc type (DOCTYP) as a "hashed" alias name for
IDOCTP and CIMTYP is not any longer required.
 Customer developments are supported by new naming
conventions.
 Partner developments are supported by new naming
conventions.
 Transport (Workbench Organizer) of IDoc types becomes
more robust by

defining a development class.

defining a logical object (TLOGO) for the workbench organizer.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 15

16. Segment Editor
 Customer developments are supported by new naming
conventions.
 Partner developments are supported by new naming
conventions.
 Transport (Workbench Organizer) of segments becomes more
robust by

defining only E1-structure and Z1-structure (segment type) in
Data Repository and generate the E2-/Z2- and E3-/Z3-structures.

handle each segment and its components as an entity for the
workbench organizer.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 16

17. API for external Development Workbenches
 The output formats provided for EDI subsystems require
initiation of transfer inside SAP prior to runtime.
 The new API is a set of function modules to be invoked
via RFC from outside SAP by an external development
workbench prior to or at runtime.
 The function modules are

IDOC_RECORD_READ

IDOCTYPES_FOR_MESTYPE_READ

IDOCTYPE_READ_COMPLETE

SEGMENT_READ_COMPLETE
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 17

18. IDoc View Concept
 An IDoc view is a selection of segments of a given IDoc
type and is compatible with the IDoc type‘s syntax.
 IDoc views are applied in outbound processing of
selected applications.
 Advantages of views:

Enhancing the performance by restricting the number of
tables read

Reducing the data volume in internal tables at run time
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 18

19. Content
 IDoc Interface Administration
 Interface w/ (EDI) Subsystems
 IDoc Interface Development
 Procurement (Application MM) & Sales (Application SD)
 SBU Automotive
 SBU Retail/CP
 Financials (Application FI)
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 19

20. Procurement & Sales
Customer
Vendor
REQOTE
QUOTES
ORDERS/ORDCHG
IMPINV
ORDRSP
DESADV
EXPINV
INVOIC
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 20

21. Request for Quotation (REQOTE)
 ANSI X12 840 - EDIFACT REQOTE
 New IDoc type versions ORDERS03 and ORDERS04
 Outbound

No functional changes
 Inbound

No functional changes

4.0 uses 3.1 transaction VA11 as VA11X

4.5 option between former and current transaction by MESCOD


MESCOD = SDO uses VA11X
MESCOD <> SDO uses VA11
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 21

22. Quotation (QUOTES)
 ANSI X12 843 - EDIFACT QUOTES
 New message for IDoc types ORDERS01, ORDERS02,
ORDERS03 and ORDERS04
 Outbound

New functionality

Supports the IDoc view concept
 Inbound

Not available
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 22

23. Purchase Order, Sales Order (ORDERS)
 ANSI X12 850 - EDIFACT ORDERS
 New IDoc type versions ORDERS03 and ORDERS04

ORDERS03 for SBU Automotive

ORDERS04 for additional data, payment method and A.F.S.
 Outbound

For 3rd party order customer order is read w/ order head, text and
terms of delivery
 Inbound

New functionality, see separate slides

4.0 uses 3.1 transaction VA01 as VA01X

4.5 option between former and current transaction by MESCOD


MESCOD = SDO uses VA01X
MESCOD <> SDO uses VA01
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 23

24. Sales Order (ORDERS) 1/2
 New Fcode „PAPO“ to maintain partner screens.
 New order document types

Credit memo request

Debit memo request

Returns
 Customizing VOED is split up with

VOE2, table EDSDC

VOE3, table EDPVW

VOE4, table EDPAR
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 24

25. Sales Order (ORDERS) 2/2
 ASUG-3LLT7K reference to quote and contract in inbound

Reference with contract at header

Reference with quote at header

Reference with contract at line item

Reference with quote at line item

Combination of contract, quote and standard order type at
line item.

Combination of references at header and line item. Change in
line item if header-reference and line item-reference matches.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 25

26. P.O. Change, Sales Order Change (ORDCHG)
 ANSI X12 860 - EDIFACT ORDCHG
 New IDoc type versions ORDERS03 and ORDERS04

ORDERS03 for SBU Automotive

ORDERS04 for additional data, payment method and A.F.S.
 Outbound

For 3rd party order customer order is read w/ order head, text and
terms of delivery
 Inbound

New Fcode „PAPO“ to maintain partner screens.

New order document types credit memo request, debit memo
request, returns.

4.0 uses 3.1 transaction VA02 as VA02X

4.5 option between former and current transaction by MESCOD
 MESCOD = SDO uses VA02X
 MESCOD <> SDO uses VA02
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 26

27. Order Acknowledgement (ORDRSP)
 ANSI X12 855 - EDIFACT ORDRSP
 New IDoc type versions ORDERS03 and ORDERS04

ORDERS03 for SBU Automotive

ORDERS04 for additional data, payment method and A.F.S.
 Outbound

Functionality enhanced for conditions. Segments E1EDK05 and
E1EDP05 are populated.

Supports the IDoc view concept
 Inbound

Change of net price

Change of vendor‘s material ID
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 27

28. Despatch Advice (DESADV)
 ANSI X12 856 - EDIFACT DESADV
 Delivery

New IDoc types DELVRY01, DELVRY02

Precondition for enhanced functionality

Supports the IDoc view concept in outbound

A migration from IDoc type DESADV01 is strongly recommended

Message EDLNOT stays w/ IDoc type DESADV01
 Transport

New IDoc types SHPMNT02, SHPMNT03

New functionality. Delivery is included as substructure
 Comprises dangerous goods data for SBU EH&S.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 28

29. Invoice w/ Logistics Verification (INVOIC)
 ANSI X12 810 - EDIFACT INVOIC
 (IDoc type INVOIC02 for intercompany billing only)
 Outbound

No functional changes
 Inbound

New application in inbound, process code INVL w/ function
module IDOC_INPUT_INVOIC_MRM

Enhancement component is MRMH002

Former process code INVM, w/ function module
IDOC_INPUT_INVOIC_MM still available
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 29

30. Customs Declaration (EXPINV, IMPINV)
 EDIFACT CUSDEC
 Export Invoice, also A.E.S.

Outbound only

New IDoc type EXPINV02

Functional enhancements
 Import Invoice

Outbound only

New IDoc type IMPINV01

New functionality
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 30

31. Content
 IDoc Interface Administration
 Interface w/ (EDI) Subsystems
 IDoc Interface Development
 Procurement (Application MM) & Sales (Application SD)
 SBU Automotive
 SBU Retail/CP
 Financials (Application FI)
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 31

32. Automotive Procurement & Sales
Manufacturer
OEM
DELINS
Supplier
DELORD
DESADV
ACCSTA
TRXSTA
GSVERF/SBINV
INVOIC
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 32
ACCSTA

33. Delivery Instruction (DELINS)
 Planning Schedule: ANSI X12 830 - EDIFACT DELFOR
 Shipping Schedule: ANSI X12 862 - EDIFACT DELJIT
 IDoc type DELFOR01
 Outbound

Planning schedule: enhanced functionality RM06ELAB

Shipping schedule: New functionality RM06EFAB

Planning schedule: new functionality RM06EFLB, single IDoc per
call-off possible
 Inbound

Enhanced functionality

4.0 uses 3.1 transaction VA32 as VA32X

4.5 option between former and current transaction by MESCOD


MESCOD = SDO uses VA32X
MESCOD <> SDO uses VA32
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 33

34. Delivery Order (DELORD)
 EDIFACT DELJIT (GM MAIS Pick-up sheet)
 New IDoc type ORDERS03
 Outbound

Not available
 Inbound

New functionality reference to delivery plan

New order document type delivery order

4.0 uses 3.1 transaction VA01 as VA01X

4.5 option between former and current transaction by MESCOD


MESCOD = SDO uses VA01X
MESCOD <> SDO uses VA01
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 34

35. Account Statement (ACCSTA)
 ACCSTA - Account Statement Returnable Packaging Logistics
 New IDoc type ACCSTA01
 Outbound

not available
 Inbound

New functionality
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 35

36. Tracking Status ASN (TRXSTA)
 ANSI X12 214 - EDIFACT IFTSTA
 New IDoc type TRXSTA01
 Outbound

not available
 Inbound

New functionality
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 36

37. Invoice (GSVERF/SBINV)
 Credit/debit memo: ANSI X12 812 - EDIFACT CREADV/DEBADV
 Self-billing Invoice: ANSI X12 810 - EDIFACT INVOIC
 IDoc type GSVERF01
 Outbound

Enhanced functionality

New functionality credit memo
 Inbound

Enhanced functionality

New functionality self-billing
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 37

38. Content
 IDoc Interface Administration
 Interface w/ (EDI) Subsystems
 IDoc Interface Development
 Procurement (Application MM) & Sales (Application SD)
 SBU Automotive
 SBU Retail/CP
 Financials (Application FI)
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 38

39. EDI Price Catalog
 New IDoc Type: PRICAT01
 Product Catalog Information


Price and product information
( Packaging Information )
ANSI
832
 Price Calculation Carried Out


General calculation; valid for all customers
Individual customer-specific calculation
 Transmit Condition Record Information

Condition types, tax, subtotals and scales
 Initial Supply of Data to Partner

As a complete and subsequently as a partial version
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 39

40. EDI Price Catalog - Customers / Materials
Assortment: Price Catalog: Key Accounts
Customer
Deal Markets
Star Center
Valid from
06/06/1998
06/06/1998
Valid to
12/31/1999
12/31/1999
Big Buyer
06/06/1998
12/31/1999
Module: Coffees
Material
Valid from
Dark Roast
06/06/1998
French Blend
06/06/1998
Valid to
12/31/1999
12/31/1998
Irish Creme
12/31/1998
06/06/1998
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 40

41. VMI - Exchange of Product Activity Data
ANSI 852
Manufacturer
Retailer
• Maintains stock
• Sends stock and
data of his products
at the retailer site.
• Tracks sales history
sales data at a
regular basis to the
manufacturer
 Data transfer via EDI using new IDoc type PROACT01
 Article and data selection is controlled by profiles in the
vendor master (stock and on-order quantity, sales history)
 Customer Stock updated in database, Customer Sales Data
in LIS Info Structure S130.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 41

42. VMI - Generation of Sales Documents
Order Response
Manufacturer
Retailer
• Calculates replenishment
• Creates purchase order
requirements
for order acknowledgement
received by EDI.
• Generates sales order
Order Changes
Manufacturer
Retailer
• Updates sales order with
• Sends PO number back to
PO number from retailer
system
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 42
vendor system

43. Content
 IDoc Interface Administration
 Interface w/ (EDI) Subsystems
 IDoc Interface Development
 Procurement (Application MM) & Sales (Application SD)
 SBU Automotive
 SBU Retail/CP
 Financials (Application FI)
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 43

44. The ‘financial cycle’ using EDI messages
Customer
Payment order
Bank
Payer
Debit advice
El. bank statement
Paym. Advice
Check
Bank transfer
Invoice
Vendor
Direct Debit
Credit Advice
El. bank statement
Lockbox Info
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 44
Bank / Lockbox
provider
Beneficiary

45. FEDI Messages
Invoice
INVOIC01/INVOIC
Credit Advice
PEXR2002/CREADV
Debit Advice
PEXR2002/DEBADV
Remittance Adv
PEXR2002/REMADV
Account Stmt
FINSTA01/FINSTA-FST
Lockbox
FINSTA01/LOCKBX
Account Info
FINSTA01/FINSTA-ACP
Remittance Adv
PEXR2002/REMADV
Payment Order
PEXR2002/PAYEXT
Direct Debit
PEXR2002/DIRDEB
Paymt Control
IDCREF01/EUPEXR
SAPSystem
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 45
Accounting
Advices
Bank Data
Buffer
Treasury
Advices
Payment
Database
Documents

46. FI-EDI Certification
Customer/
Vendor
Payment order
Direct Debit
Bank
Payer
Credit Advice
Debit advice
El. bank statement
 Certification is available for all banks.
 The bank will be certified not an EDI subsystem itself.
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 49

47. Questions ...
 IDoc Interface Administration
 Interface w/ (EDI) Subsystems
 IDoc Interface Development
 Procurement (Application MM) & Sales (Application SD)
 SBU Automotive
 SBU Retail/CP
 Financials (Application FI)
© SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 50