EDI

SAP AG 1999 ASUG EDI/EC (Thomas Becker) page 1

Thomas BeckerSAP AG

Changes of theIDoc Interface

Release 4.5compared w/ Release 3.1


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)


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.

Global Changes


PartnerMessage

NAST-Key

Process codeLogical message

PartnerLogical message

Process codeRecipient of notifications

Inbound

Partner

Recipient of notifications

General

PartnerLogical message

PortIDoc typeEDI structureRecipient of notifications

Outbound

The table class for alltables is changed.

The transport is removed.

This allows maintenancealso in a production system.

Partner Profile


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


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


Content





SBU Automotive

SBU Retail/CP



Port Types

The port type „Programming Interface“ or ABAP is available to leverage IDoc for project-specific formatting.

SAP Application

IDoc Interface & ALE Services

IDocIDoc

MIME

Internet

CPI-C

IDoc &IDoc &statusstatus

R/2

IDocIDoc

tRFC

ALEAny

IDoc &IDoc &statusstatus

File+ RFC

EDIAny

IDocIDoc

ABAP

Any

2.1 on 3.0 on 3.0 on 3.1 on 4.5 on


Record Types, i.e. Envelopes

Control Record, EDIDC

Status Records, EDIDS

Data Records, EDIDD

Tree of Segments

E1HDDOC

M 1

E1TLSUM

C 1

E1HDADR

C 5

C 99

E1ITSCH

C 5

E1ITDOC

M 1

Envelope = changed

IDoc type = unchanged


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.


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.


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 System R/3 System R/3

Document

IDoc

SubsystemSubsystemTransaction

IDoc


Content





SBU Automotive

SBU Retail/CP



Tools to Develop an IDoc Type

Tool to define the segment with its fields

E1HDDOC

Tool to define theIDoc type with its segments


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.


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.


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


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


Content





SBU Automotive

SBU Retail/CP



Procurement & Sales

CustomerCustomer

IMPINV

VendorVendor

EXPINV

REQOTE

ORDRSP

QUOTES

ORDERS/ORDCHG

DESADV

INVOIC


Request for Quotation (REQOTE)

ANSI X12 840 - EDIFACT REQOTE

New IDoc type versions ORDERS03 and ORDERS04

Outbound

No functional changes

Inbound


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


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


Purchase Order, Sales Order (ORDERS)

ANSI X12 850 - EDIFACT ORDERS


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






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


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.


P.O. Change, Sales Order Change (ORDCHG)

ANSI X12 860 - EDIFACT ORDCHG




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.






Order Acknowledgement (ORDRSP)

ANSI X12 855 - EDIFACT ORDRSP




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


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.


Invoice w/ Logistics Verification (INVOIC)

ANSI X12 810 - EDIFACT INVOIC

(IDoc type INVOIC02 for intercompany billing only)

Outbound


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


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


Content





SBU Automotive

SBU Retail/CP



Automotive Procurement & Sales

SupplierSupplierManufacturerManufacturerOEMOEM

DELORD

DELINS

DESADV

GSVERF/SBINV

INVOIC

TRXSTA

ACCSTAACCSTA


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






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






Account Statement (ACCSTA)

ACCSTA - Account Statement Returnable Packaging Logistics

New IDoc type ACCSTA01

Outbound

not available

Inbound

New functionality


Tracking Status ASN (TRXSTA)

ANSI X12 214 - EDIFACT IFTSTA

New IDoc type TRXSTA01

Outbound

not available

Inbound

New functionality


Invoice (GSVERF/SBINV)

Credit/debit memo: ANSI X12 812 - EDIFACT CREADV/DEBADV

Self-billing Invoice: ANSI X12 810 - EDIFACT INVOIC

IDoc type GSVERF01

Outbound


New functionality credit memo

Inbound


New functionality self-billing


Content





SBU Automotive

SBU Retail/CP



EDI Price Catalog

New IDoc Type: PRICAT01

Product Catalog Information Price and product information ( Packaging Information )

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

ANSI 832


EDI Price Catalog - Customers / Materials

Assortment: Price Catalog: Key Accounts

Customer Valid from Valid to

Deal Markets 06/06/1998 12/31/1999 Star Center 06/06/1998 12/31/1999 Big Buyer 06/06/1998 12/31/1999

Module: Coffees Material Valid from Valid toDark Roast 06/06/1998 12/31/1999 French Blend 06/06/1998 12/31/1998 Irish Creme 06/06/1998 12/31/1998


VMI - Exchange of Product Activity Data

Manufacturer

• Maintains stock data of his products at the retailer site.

• Tracks sales history

Retailer

• Sends stock and sales data at a regular basis to the manufacturer

ANSI 852

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.


VMI - Generation of Sales Documents

Manufacturer

• Calculates replenishment requirements

• Generates sales order

Retailer

• Creates purchase order for order acknowledgement received by EDI.

Order Response

Retailer

• Sends PO number back to vendor system

Order Changes

Manufacturer

• Updates sales order with PO number from retailer system


Content





SBU Automotive

SBU Retail/CP



The ‘financial cycle’ using EDI messages

CustomerCustomer BankBank

InvoiceInvoice

Paym. AdvicePaym. Advice

Payment orderPayment order

Debit adviceDebit advice

Bank transferBank transfer

VendorVendor Bank / Lockbox providerBank / Lockbox provider

Credit AdviceCredit AdviceBeneficiaryBeneficiary

PayerPayer

El. bank statementEl. bank statement


CheckCheck

Lockbox InfoLockbox Info

Direct DebitDirect Debit


FEDI Messages

PaymentPayment

DatabaseDatabase

Bank DataBank DataBufferBuffer

InvoiceInvoice

Documents

Debit AdviceDebit Advice

Credit AdviceCredit Advice

Remittance AdvRemittance Adv

Account StmtAccount Stmt

LockboxLockbox

Account InfoAccount Info

Payment OrderPayment Order


Paymt ControlPaymt Control

INVOIC01/INVOICINVOIC01/INVOIC

PEXR2002/DEBADVPEXR2002/DEBADV

PEXR2002/CREADVPEXR2002/CREADV

PEXR2002/REMADVPEXR2002/REMADV

FINSTA01/FINSTA-FSTFINSTA01/FINSTA-FST

FINSTA01/LOCKBXFINSTA01/LOCKBX

FINSTA01/FINSTA-ACPFINSTA01/FINSTA-ACP

PEXR2002/PAYEXTPEXR2002/PAYEXT

IDCREF01/EUPEXRIDCREF01/EUPEXR

PEXR2002/DIRDEBPEXR2002/DIRDEB

Treasury Treasury AdvicesAdvices

Accounting Accounting AdvicesAdvices

SAP-SystemSAP-System

Remittance AdvRemittance Adv PEXR2002/REMADVPEXR2002/REMADV


FI-EDI Certification

Customer/Customer/ BankBankPayment orderPayment order

Debit adviceDebit advice

VendorVendor

Credit AdviceCredit Advice

PayerPayer



Certification is available for all banks.

The bank will be certified not an EDI subsystem itself.






SBU Automotive

SBU Retail/CP


Questions ...

Education

EDI