EDI ORDERS TEMPLATE.doc

Analysis of the compatibilityof EDIFACT messages

in the form of SIMPL-EDIwith the IDoc Interface

© SAP AG of 19

SIMPL-EDI August 1998System R/3, Release 4.5

1 Introduction

Tom McGuffog, co-developer of the TRADACOMS EDI-Standards and the UK EDIFACT-Standards, has discussed in a few essays, up to which degree Electronic Commerce and value Chain Management can be combined in order to reduce complexity and a simplify business processes (Business Process Re-engineering).

An introduction to this topic is published in “Managing the Supply Chain with Speed and Certainty“ and “Electronic Commerce and Value Chain Management“, in “SIMPL-EDI, A Vision for the future, linking Value Chain Management and Electronic Commerce“ a concrete solution is given.

McGuffog believes, that the Supply Chain Message can be totally represented by just a small number of elements which are shown in the box below1. His thesis is, that about 80% of needs can be met with approximately “20% of the elements drawn from the existing EDI messages”2:

(1) Location number for Customer

(2) Location number for Supplier

(3) Reference numbers for:- The order, for the type of order – to deliver or to produce etc.- The locations – customer, supplier, agent.- The products – key characteristics, prices, details- The processes – technical, medical etc.- People – employees, patients etc.

(4) Date/Time Delivery/Service Required

(5) Number for Delivery to/from location

(6) Number for Products or Services Required

(7) Quantities of Each

Looking at the “Simple order message“ (ORDERS) described in that document, consisting of segments of the EDIFACT-Standard3 there are some inconsistencies to find in the author’s compilation itself. For example the “processes“ or the “people“ mentioned above are not included; redundancies can be found in the points listed here as well (compare (3) “The products“ and (6)).

A kind of a second version of McGuffog’s proposal for “SIMPLE, STANDARD ORDER MESSAGE“ can be found in his essay “Electronic Commerce and Value Chain Management“:

1 Tom McGuffog, SIMPL-EDI, Version 10, Copyright ANA (UK) Ltd., 27. November 1997, Page 62 Tom McGuffog, SIMPL-EDI, Version 10, Copyright ANA (UK) Ltd., 27. November 1997, Page 93 The version of the EDIFACT-Standard used in McGuffogs documents could not be identified.

© SAP AG of 19


(1) Code for customer

(2) Code for supplier

(3) Code for item being ordered

(4) Code for location of the place to where delivery is required

(5) Order number

(6) Date/time delivery required

(7) Quantity required

It is important to mention, that the first four elements are represented by codes (International Article Number [EAN] or International Location Number [ILN]). Describing information such as names and addresses of the partners or product descriptions are not included. They can be find in so called Master Files, but that was the same in the previous version.

Purpose and aim of this paper is now to investigate, if and how far respectively that reduction of complexity is compatible with the IDoc Interface of the R/3 System. It therefore has to be tested, if the few navigating elements of the SIMPL-EDI message are sufficient, not matching or even too extensive. For the testing SAP R/3 Release 4.5B is taken.

For the beginning it is important to know, that McGuffog sets some assumptions for the demanded standardisation: So the partners need to have a explicit definition about what is meant by each data element; multiple possibilities of interpretation have to be excluded.4 A kind of a “logistic language” has to be established. To realise that, it is necessary to adapt internal systems to the structured form of automatic data exchange represented by SIMPL-EDI.

For the simulation of the scenarios the test tool in R/3 Q45 is used. There differently built EDIFACT messages are tested if they can be recognised and processed correctly by the IDoc Interface. In the IDoc Exit it has to be certain that consistent EDIFACT messages are generated.5

2 The Message Exchange

In this section now follows a description of the messages as they are exchanged between the customer and the supplier i.e. MM-Module and SD-Module. At first the IDoc type ORDERS01 with its messages enquiry (REQOTE), quote (QUOTES), order (ORDERS), order change (ORDCHG) and order response (ORDRSP) is analysed. In the following charts the entry and the exit of the messages are shown; the IDoc segments with their corresponding EDIFACT element and the field in the MM- or SD-Module. Concerning the quote the Entry of the R/3 System has not yet been implemented and therefore cannot be analysed here.

Although McGuffog does not mention the messages enquiry and quote they are considered here, for the IDoc Interface makes it possible to analyse them and they should not be missing in a complete supply chain message.

4 see Tom McGuffog, SIMPL-EDI, Version 10, Copyright ANA (UK) Ltd., 27. November 1997, P. 35 Version D.96A, March 1996 of the EDIFACT-Standard is used.

© SAP AG of 19


SAP AG, 03.01.-1,

SAP AG, 03.01.-1,

In the sections 2.2 and 2.3 we take a closer look at the IDoc type delivery interface (DELVRY01) with the message delivery note (DESADV) and invoice (INVOIC01) with the message INVOIC, which complete the supply chain message.

With the help of the test tool the originally generated messages are modified in a way, that segments necessary for the IDoc entry are added and segments not needed are left out. But this optimisation is done with consideration of McGuffog’s EDI message, so that in some cases segments and fields not necessarily needed are kept. (for example Order Change, segment E1EDKA1 [WE]).

© SAP AG of 19


2.1 ORDERS01

Enquiry (REQOTE) Exit MM

MM-Module

Segments

IDoc Field

Segments

EDIFACT Comment

ekko-bsart

Header data

E1EDK01 BSART BGM – C002 - 1001 AN (Anfrage)

„004“ E1EDK03 IDDAT DTM – C507 – 2005 Last date for quote; Code „144“ (Quota date)

ekko-angdt DATUM DTM – C507 – 2380 Format CCYYMMDD

„AG“ E1EDKA1 PARVW NAD – 3035 Partner role; Code „BY“ (Buyer)

lfb1-eikto PARTN NAD – C082 – 3039 Partner number

„LF“ E1EDKA1 PARVW NAD – 3035 Partner role; Code „SE“ (Seller)

ekko-lifnr PARTN NAD – C082 – 3039 Partner number

„003“ E1EDK02 QUALF RFF – C506 – 1153 Code „AAV“ (Enquiry number)

ekko-ebeln BELNR RFF – C506 - 1154

ekpo-ebelp

Item data

E1EDP01 POSEX LIN - 1082 Item number; normally in 10 steps

ekpo-? MENGE LIN –QTY-C186 -6060 IF ekko-bstyp EQ bstyp-best THEN ekpo-menge ELSE ekpo-ktmng

„001“ E1EDP19 QUALF LIN – C212 – 7143 Customers material; Code „BP“ (Buyer’s part number)

ekpo-? IDTNR LIN – C212 – 7140 IF ekpo-ematn IS INITIAL THEN ekpo-matnr ELSE ekpo-ematn

At the beginning of the complete supply chain message stands the enquiry. As you can see from the chart there are just information about the validity date of the enquiry, the partners and the product in that IDoc message REQOTE. The fields only consist of qualifiers, codes and dates. A message sent in this way however cannot be processed from the IDoc Interface of a SD-Module, because there the qualifiers 006 for the data segment E1EDK03 is mandatory.

© SAP AG of 19


Enquiry (REQOTE) Entry SD

Segments

EDIFACT

Segments

IDoc Field SD-Module Comment

BGM – C002 - 1001

Header data

E1EDK01 BSART AF (Anfrage) – just a Dummy, because not needed, but E1EDK01 is mandatory.

DTM – C507 – 2005 E1EDK03 IDDAT „014“ Enquiry (valid from); if not sent: SY-DATUM

DTM – C507 – 2380 DATUM vbak-angdt Format CCYYMMDD

DTM – C507 – 2005 E1EDK03 IDDAT „006“ Enquiry (valid until); the outgoing enquiry does not give this information

DTM – C507 – 2380 DATUM vbak-bnddt Format CCYYMMDD

NAD – 3035 E1EDKA1 PARVW „AG“ Partner role; Code „BY“ (Buyer)

NAD – C082 – 3039 PARTN vbadr-kunnr

vbak-kunnr

The partner number is put into two fields in the SD-Module

NAD – 3035 E1EDKA1 PARVW „LF“ Partner role; Code „SE“ (Seller)

NAD – C082 – 3039 PARTN Partner number; organisational unit is derived from EDSDC

RFF – C506 – 1153 E1EDK02 QUALF „003“ Code „AAV“ (Enquiry number)

RFF – C506 – 1154 BELNR vbak-bstnk

LIN - 1082

Item data

E1EDP01 POSEX vbap-posex Item number, normal in 10 steps

LIN -QTY –C186 –6060 MENGE vbap-wmeng

LIN – C212 – 7143 E1EDP19 QUALF „001“ Customer’s material number; Code „BP“ (Buyer’s part number)

LIN – C212 – 7140 IDTNR vbap-kdmat SAP material number derived from the Kunden-Material-Infosatz

© SAP AG of 19


Quote (QUOTES) Exit SD

SD-Module

Segments

IDoc Field

Segments

EDIFACT Comment

Control set BGM – C002 - 1001 BGM segment is derived from the control set.

Header data

E1EDK01No data, but segment is mandatory.

„005“ E1EDK03 IDDAT DTM – C507 – 2005 Code „15“ (Promotion start date/time)

vbak-angdt DATUM DTM – C507 – 2380 Format CCYYMMDD

„006“ E1EDK03 IDDAT DTM – C507 – 2005 Code „16“ (Promotion end date/time)

vbak-bnddt DATUM DTM – C507 – 2380 Format CCYYMMDD

„AG“ E1EDKA1 PARVW NAD – 3035 Partner role; Code „BY“ (Buyer)

vbak-kunnr PARTN NAD – C082 – 3039 Partner number

knvv-eikto LIFNRNAD – 3035

NAD – C082 - 3039

Customer’s supplier number; Code „SE“ (Seller) im DE „3035“

„056“ E1EDK02 QUALF RFF – C506 - 1153 Code „AAG“ (Offer number)

vbak-vbeln BELNR RFF – C506 - 1154

vbap-posnr

Item data

E1EDP01 POSEX LIN - 1082 Item number; normal in 10 steps

vbap-kwmeng MENGE LIN –QTY –C186 -6060

LIN – PRI –C509 - 5125 Price qualifier; Code „CAL” (Calculation price)

vbap-netwr NETWR LIN – PRI –C509 - 5118 Value of the item (net)

„001“ E1EDP19 QUALF LIN – C212 – 7143 Customer’s material number; Code „BP“ (Buyer’s part number)

vbap-kdmat IDTNR LIN – C212 – 7140

© SAP AG of 19


Order (ORDERS) Exit MM

MM-Module

Segments

IDoc Field

Segments

EDIFACT Comment

ekko-bsart

Header data

E1EDK01 BSART BGM – C002 - 1001 NB (Normalbestellung)

„012“ E1EDK03 IDDAT DTM – C507 – 2005 Code „4“ (Order date/time)

ekko-bedat DATUM DTM – C507 - 2380 Format CCYYMMDD

„WE“ E1EDKA1 PARVW NAD – 3035 Partner role; Code „CN“ (Consignee)

pekko-werks LIFNR NAD – C082 – 3039 Customer’s factory


ekko-lifnr PARTN NAD – C082 – 3039 SAP supplier number

„001“ E1EDK02 QUALF RFF – C506 – 1153 Code „ON“ (Order number [purchase])


ekpo-ebelp

Item data


E1EDP20 LIN- SCC - 4017 SCC Segment (Scheduling conditions) is mandatory; DE 4017 (Delivery plan status) with Code 26 (Proposed)

eket-menge WMENG LIN – SCC -QTY –C186 -6060

Item quantity

eket-eindt EDATU LIN – SCC -DTM –C507 -2380

Item/Wish delivery date; Format CCYYMMDD

„001“ E1EDP19 QUALF LIN – C212 – 7143 Customer’s material; Code „BP“ (Buyer’s part number)


© SAP AG of 19


Order (ORDERS) Entry SD

Segments

EDIFACT

Segments


BGM – C002 - 1001

Header data

E1EDK01 BSART

TA (Kundenauftrag) – just a Dummy, because not needed, but E1EDK01 is mandatory.

NAD – 3035 E1EDKA1 PARVW „WE“ Partner role; Code „CN“ (Consignee)

NAD – C082 – 3039 LIFNR vbadr-kunnr

Derivation in EDPAR from Debitor (aus EDIDC-SNDPRN) +Rolle (E1EDKA1-PARVW) +Externe ID (E1EDKA1-LIFNR) to Customer number SD


NAD – C082 – 3039 PARTN Suppler number; organisational unit is derived from EDSDC

RFF – C506 - 1153 E1EDK02 QUALF „001“ Code „ON“ (Order number [purchase])

RFF – C506 - 1154 BELNR vbak-bstnk

DTM – C507 – 2005

DTM – C507 - 2380

DATUM vbak-bstdk Format CCYYMMDD; Code „4“ (Order date/time)

LIN - 1082

Item data

E1EDP01 POSEX vbap-posex

Item number; normal in 10 steps

LIN - SCC - 4017 E1EDP20 SCC Segment (Scheduling conditions) is mandatory; DE 4017 (Delivery plan status) with Code 26 (Proposed)

LIN –SCC -QTY – C186 –6060

WMENG vbep-wmeng

Item quantity

LIN –SCC -DTM –C507 –2380

EDATU vbep-edatu

vbap-lfdat

Format CCYYMMDD;

IF vbap-lfdat IS INITIAL THEN vbap-lfdat =vbep-edatu


LIN – C212 – 7140 IDTNR vbap-kdmat

SAP material number derived from the Kunden-Material-Infosatz

© SAP AG of 19


Order Change (ORDCHG) Exit MM

MM-Module

Segments

IDoc Field

Segments

EDIFACT Comment

ekko-bsart

Header data

E1EDK01 BSART BGM – C002 - 1001 NB (Normalbestellung)

„012“ E1EDK03 IDDAT DTM – C507 – 2005 Code „4“ (Order date/time)

ekko-bedat DATUM DTM – C507 - 2380 Format CCYYMMDD

„WE“ E1EDKA1 PARVW NAD – 3035 Partner role; Code „CN“ (Consignee)

pekko-werks LIFNR NAD – C082 – 3039 Customer’s factory


ekko-lifnr PARTN NAD – C082 – 3039 SAP supplier number



ekpo-ebelp

Item data


E1EDP20 LIN- SCC - 4017 SCC Segment (Scheduling conditions) is mandatory; DE 4017 (Delivery plan status) with Code 26 (Proposed)

eket-menge WMENG LIN – SCC -QTY –C186 -6060

Item quantity

eket-eindt EDATU LIN – SCC -DTM –C507 -2380

Item/Wish delivery date; Format CCYYMMDD



The order change (ORDCHG) corresponds to the order (ORDERS) in the exit, but only that data is given away in which changes have been made or which where added or deleted. Unchanged items are not sent.

© SAP AG of 19


Order Change (ORDCHG) Entry SD

Segments

EDIFACT

Segments

IDoc Field SD-Module Erläuterungen

BGM – C002 - 1001

Header data

E1EDK01 BSART TA (Kundenauftrag) – just a Dummy, because not needed, but E1EDK01 is mandatory.

NAD – 3035 E1EDKA1 PARVW „WE“ Partner role; Code „CN“ (Consignee)

NAD – C082 – 3039 LIFNR vbadr-kunnr


NAD – C082 – 3039 PARTN Supplier number; organisational unit is derived from EDSDC


RFF – C506 - 1154 BELNR vbak-bstkd

LIN - 1082

Item data

E1EDP01 POSEX vbap-posex Item number; normal in 10 steps

LIN - SCC - 4017 E1EDP20 SCC Segment (Scheduling conditions) is mandatory; DE 4017 (Delivery plan status) with Code 26 (Proposed)

LIN –SCC -QTY –C186 –6060

WMENG vbep-wmeng Item quantity

LIN –SCC -DTM –C507 –2380

EDATU vbep-edatu

vbap-wldat

Format CCYYMMDD

IF vbap-wldat IS INITIAL THEN vbap-wldat =vbep-edatu


LIN – C212 – 7140 IDTNR vbap-kdmat SAP material number derived from the Kunden-Material-Infosatz.

In the entry the order change is different from the order in that way, that the reference numbers from the E1EDK02 segment and the wish delivery date from the E1EDP20 segment are put into other fields of the SD-Module. The date of the original order is derived from the reference number. The E1EDKA1 [WE] segment is not mandatory.

© SAP AG of 19


Order Response (ORDRSP) Exit SD

SD-Module

Segments

IDoc Field

Segments

EDIFACT Comment

vbak-bsark

Header data

E1EDK01 BSART BGM – C002 - 1001 DFUE (Datenfernübertragung)

„012“ E1EDK03 IDDAT DTM – C507 – 2005 Order response date; Code „8“ (Order received date/time)

vbak-audat DATUM DTM – C507 - 2380 Format CCYYMMDD


vbak-bstnk BELNR RFF – C506 - 1154 Order number MM

„002“ E1EDK02 QUALF RFF – C506 – 1153 Code „VN“ (Order number [vendor])

vbak-vbeln BELNR RFF – C506 - 1154 Order number SD

vbap-vrkme

Item data

E1EDP01 MENEE LIN -QTY –C186 -6063 Quantity unit

„001“ E1EDP02 QUALF LIN -RFF –C506 -1153 Code „ON“ (Order number [purchase])

vbak-bstnk BELNR LIN -RFF –C506 -1154 Order number MM

vbap-posex ZEILE LIN - 1082 Item number; normal in 10 steps

E1EDP20 LIN – SCC - 4017 SCC Segment (Scheduling conditions) is mandatory; DE 4017 (Delivery plan status) with Code 26 (Proposed)

vbep-bmeng WMENG LIN –SCC -QTY –C186 – 6060 Item quantity

vbep-edatu EDATU LIN –SCC -DTM –C507 - 2380 Format CCYYMMDD


vbap-kdmat IDTNR LIN – C212 – 7140

© SAP AG of 19


Order Response (ORDRSP) Entry MM

Segments

EDIFACT

Segments

IDoc Field MM-Module Comment

BGM – C002 - 1001

Header data

E1EDK01 BSART DFUE (Datenfernübertra-gung) – just a Dummy, because not needed, but E1EDK01 is mandatory.


RFF – C506 - 1154 BELNR ekko-ebeln Order number MM

RFF – C506 - 1153 E1EDK02 QUALF „002“ Code „VN“ (Order number [vendor])

RFF – C506 - 1154 BELNR ekpo-labnr Order number SD

LIN -QTY –C186 -6063

Item data

E1EDP01 MENEE ekpo-meins Quantity unit

LIN -RFF – C506 –1153 E1EDP02 QUALF „001“ Code „ON“ (Order number [purchase])

LIN -RFF – C506 -1154 BELNR idoc_ebeln Field „idoc_ebeln“ must be like „ekko-ebeln“

LIN - 1082 ZEILE fekpo-ebelp Item number; normal in 10 steps

LIN – SCC - 4017 E1EDP20 SCC Segment (Scheduling conditions) is mandatory; DE 4017 (Delivery plan status) with Code 26 (Proposed)

LIN –SCC -QTY –C186 –6060 WMENG uekes-menge Item quantity

LIN –SCC -DTM –C507 -2380 EDATU uekes-eindt Format CCYYMMDD


LIN – C212 – 7140 IDTNR fekpo-matnr

© SAP AG of 19


2.2 DELVRY01

Delivery Note (DESADV) Exit SD

SD-Module

Segments

IDoc Field

Segments

EDIFACT Comment

likp-vbeln

Header data

E1EDL20 VBELN BGM - 1004 Delivery note number

„007“ E1EDT13 QUALF DTM – C507 - 2005 Code „69“ (Delivery date/time, promised for)

vbddl-ntanf NTANF DTM – C507 - 2380 Format CCYYMMDDItem data

E1EDL24 CPS - 7164 CPS Segment (Consignment packing sequence) is mandatory; DE 7164 (Hierarchical id. number)

lips-posnr POSNR CPS -LIN - 1082 Item number of delivery note

lips-kdmatKDMAT

CPS -LIN – C212 – 7143

CPS -LIN – C212 - 7140

Customer’s material number; Code „BP“ (Buyer’s part number) in DE „7143“

lips-lfimgLFIMG

CPS-LIN–QTY–C186-6063

CPS-LIN–QTY–C186-6060

Quantity delivered; Code „12“ (Despatch quantity) in DE „6063“

lips-vrkme VRKME CPS -LIN–QTY–C186-6411 Quantity unit

„001“

Reference data

E1EDL41 QUALI CPS -LIN–RFF–C506 -1153 Code „ON“ (Order number [purchase])

vbkd-bstkd BSTNR CPS -LIN–RFF–C506–1154

vbap-posex POSEX CPS -LIN–RFF–C506–1156 Item number from the corresponding order

© SAP AG of 19


Delivery Note (DESADV) Entry MM

Segments

EDIFACT

Segments

IDoc Field MM-Module Comment

BGM – 1004

Header data

E1EDL20 VBELN dlgn-rfbel, dlgn-verur, dlgn-lifex

Delivery note number; number is put into three fields in the MM-Module

DTM – C507 – 2005 E1EDT13 QUALF „007“ Code „69“ (Delivery date/time, promised for)

DTM – C507 - 2380 NTANF dlgn-lfdat Format CCYYMMDD

CPS - 7164

Item data

E1EDL24 CPS Segment (Consignment packing sequence) is mandatory; DE 7164 (Hierarchical id. number)

CPS - LIN – 1082 POSNR dlgn-lifexpos, dlgn-rfpos, dlgn-vupos

Item number of delivery note; number is put into three fields in the MM-Module

CPS -LIN – C212 – 7143

CPS -LIN – C212 – 7140

KDMAT dlgn-matnr, dlgn-ematn

Customer’s material number; Code „BP“ (Buyer’s part number) in DE „7143“; number is put into two fields in the MM-Module

CPS -LIN–QTY–C186–6063

CPS -LIN–QTY–C186-6060

LFIMG dlgn-lfimg Quantity delivered; Code „12“ (Despatch quantity) im DE „6063“

CPS -LIN-QTY–C186 -6411 VRKME dlgn-vrkme Quantity unit

CPS -LIN-RFF- C506- 1153

Reference data

E1EDL41 QUALI „001“ Code „ON“ (Order number [purchase])

CPS –LIN-RFF-C506 -1154 BSTNR dlgn-vgbel

CPS –LIN-RFF-C506 -1156 POSEX dlgn-vgpos Item number from the corresponding order.

© SAP AG of 19


2.3 INVOIC01

Invoice (INVOIC) Exit SD

SD-Module

Segments

IDoc Field

Segments

EDIFACT Comment

vbdkr-waerk

Header data

E1EDK01 CURCY Currency

BSART BGM – C002 - 1001 INVO (Invoice)

„RS“ E1EDKA1 PARVW NAD – 3035 Partner role; Code „II“ (Issuer of invoice)

vbdkr-kunre PARTN NAD – C082 – 3039

„RE“ E1EDKA1 PARVW NAD – 3035 Partner role; Code „IV“ (Invoicee)

PARTN NAD – C082 – 3039

„009“ E1EDK02 QUALF RFF – C506 – 1153 Code „IV“ (Invoice number)

vbdkr-vbeln BELNR RFF – C506 - 1154

„012“ E1EDK03 IDDAT DTM – C507 – 2005 Code „3“ (Invoice date/time)

vbdkr-erdat DATUM DTM – C507 - 2380 Format CCYYMMDD

„024“ E1EDK03 IDDAT DTM – C507 – 2005 Value date; Code „288“ (Price base date/time)

fkdat DATUM DTM – C507 - 2380 Format CCYYMMDD

vbdpr-fkimg

Item data

E1EDP01 MENGE LIN –QTY –C186 -6060 Quantity

vbdpr-vrkme MENEE LIN –QTY –C186 -6411 Quantity unit

„001“ E1EDP02 QUALF LIN - RFF- C506 - 1153 Code „ON“ (Order number [purchase])

vbdpr- ? BELNR LIN - RFF- C506 -1154 IF NOT tvbdpr-bstnk IS INITIAL THEN BELNR =vbdpr-bstnk AND ZEILE =vbdpr-posex ELSE BELNR =vbdpr-vbeln_vauf AND ZEILE =vbdpr-posnr_vauf

vbdpr- ? ZEILE LIN - RFF- C506 - 1156 Item number; normal in 10 steps

© SAP AG of 19


continuation Invoice (INVOIC) Exit SD

SD-Module

Segments

IDoc Field

Segments

EDIFACT Comment

„016“ E1EDP02 QUALF LIN –RFF - C506 -1153 Code „ACW“ (Reference number to previous message)

vbdpr-vgbel BELNR LIN –RFF - C506 -1154


vbdpr-idnkd IDTNR LIN – C212 – 7140

„003“ E1EDP26 QUALF LIN –PRI –C509 - 5125 Code „AAA“ (Calculation net)

vbdpr-netwr BETRG LIN –PRI –C509 - 5118

E1EDP04 MWSKZ LIN – TAX - 5283 VAT qualifier; Code „7“ (Tax)

MSATZ VAT rate

MWSBT

LIN – TAX –MOA –C516 -5025

LIN – TAX –MOA –C516 -5004

Code „1“ (VAT, 1st value) aus DE 5025

„011“

Sum segment

E1EDS01 SUMID MOA – C516 - 5025 Code „39“ (Invoice total amount)

SUMME MOA – C516 - 5004 Values of the items are added

© SAP AG of 19


Invoice (INVOIC) Entry MM

Segments

EDIFACT

Segments


Header data

E1EDK01 CURCY i_rbkpv-waers Currency

BGM – C002 - 1001 BSART INVO (Invoice) – just a Dummy

NAD – 3035 E1EDKA1 PARVW „RS“ Partner role; Code „II“ (Issuer of invoice)

NAD – C082 – 3039 PARTN i_rbkpv-lifnr

NAD – 3035 E1EDKA1 PARVW „RE“ Partnerrolle; Code „IV“ (Invoicee)

NAD – C082 – 3039 PARTN i_rbkpv-bukrs

RFF – C506 – 1153 E1EDK02 QUALF „009“ Code „IV“ (Invoice number)

RFF – C506 - 1154 BELNR i_rbkpv-xblnr

DTM – C507 – 2005 E1EDK03 IDDAT „012“ Code „3“ (Invoice date/time)

DTM – C507 - 2380 DATUM i_rbkpv-bldat Format CCYYMMDD

DTM – C507 – 2005 E1EDK03 IDDAT „024“ Value date; Code „288“ (Price base date/time)

DTM – C507 - 2380 DATUM i_rbkpv-zfbdt Format CCYYMMDD

LIN -QTY -C186 -6060

Item data

E1EDP01 MENGE t_drseg-menge

LIN - RFF- C506- 1153 E1EDP02 QUALF „001“ Code „ON“ (Order number [purchase])

LIN - RFF- C506 -1154 BELNR t_drseg-ebeln

LIN - RFF-C506 -1156 ZEILE t_drseg-ebelp Item number; normal in 10 steps

LIN - RFF- C506- 1153 E1EDP02 QUALF „016“ Code „ACW“ (Reference number to previous message)

LIN - RFF-C506 -1154 BELNR t_drseg-lfbnr, t_drseg-lfgja, t_drseg-lfpos

Number is put into three fields in the MM-Module.

© SAP AG of 19


continuation Invoice (INVOIC) Entry MM

Segmente

EDIFACT

Segmente

IDoc Feld SD-System Erläuterungen

LIN – TAX - 5283 E1EDP04 MWSKZ t_drseg-mwskz VAT qualifier; Code „7“ (Tax)

MSATZ VAT rate

LIN – TAX –MOA –C516 -5025

LIN – TAX –MOA –C516 -5004

MWSBT

Code „1“ (VAT, 1st value) aus DE 5025

MOA – C516 - 5025

Sum segment

E1EDS01 SUMID „011“ Code „39“ (Invoice total amount)

MOA – C516 - 5004 SUMME i_rbkpv-rmwwr

© SAP AG of 19


EDI ORDERS TEMPLATE.doc

Documents

Transcript of EDI ORDERS TEMPLATE.doc