saphelp afs50 en 009

SalesPDF download from SAP Help Portal:http://help.sap.com/saphelp_afs50/helpdata/en/7c/b6cee70a0411d4b311005004394c29/content.htm

Created on June 17, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

NoteThis PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AGand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC 2014 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 49

Table of content1 Sales1.1 Sales Order1.1.1 Customizing: Sales Order1.1.2 Technical Information: Sales Order1.1.2.1 Document Header: General Data (Segment E1EDK01)1.1.2.1.1 Document Header: Organizational Data (Segment E1EDK14)1.1.2.1.2 Document Header: Date Segment (Segment E1J3K03)1.1.2.1.3 Document Header: Taxes (Segment E1EDK04)1.1.2.1.4 Document Header: Conditions (Segment E1EDK05)1.1.2.1.5 Document Header: Partner Info (Segment E1EDKA1)1.1.2.1.6 Document Header: Partner Info Additional Data (Segment E1EDKA3)1.1.2.1.7 Document Header: Reference Data (Segment E1EDK02)1.1.2.1.8 Document Header: Terms of Delivery (Segment E1EDK17)1.1.2.1.9 Document Header: Terms of Payment (Segment E1EDK18)1.1.2.1.10 Document Header: Additional Data (Segment E1EDK35)1.1.2.1.11 Document Header: Payment Cards (Segment E1EDK36)1.1.2.1.12 Document Header: Text Identification (Segment E1EDKT1)1.1.2.1.13 Document Header: Texts (Segment E1EDKT2)1.1.2.1.14 Document Header: MSO Header (Segment E1J3AHO)1.1.2.2 Document Item: General Data (Segment E1J3P01)1.1.2.2.1 Document Item: Date Segment (Segment E1J3P03)1.1.2.2.2 Document Item: Schedule Lines (Segment E1EDP20)1.1.2.2.3 Document Item: Schedule Lines Additional Data (Segment E1J3P20)1.1.2.2.4 Document Item: Conditions (Segment E1J3P05)1.1.2.2.5 Document Item: Configuration Data (Segment E1CUCFG)1.1.2.2.6 Document Item: Service Specifications Data (Segment E1EDC01)1.1.2.2.7 Document Item: Terms of Delivery (Segment E1EDP17)1.1.2.2.8 Document Item: Multi-Store Order (Segment E1J3AIO)1.1.2.2.9 Document Item: Object Identification (Segment E1EDP19)1.1.2.2.10 Document Item: Object Identification (Segment E1J3AIM)1.1.2.2.11 Document Item: Partner Info Additional Data (Segment E1EDPA3)1.1.2.2.12 Document Item: Partner Information (Segment E1EDPA1)1.1.2.2.13 Document Item: Reference Order Item (Segment E1CUREF)1.1.2.2.14 Document Item: Reference Data (Segment E1EDP02)1.1.2.2.15 Document Item: Taxes (Segment E1J3P04)1.1.2.2.16 Document Item: Totals Segment (Segment E1EDS01)1.1.2.2.17 Document Item: Texts (Segment E1EDPT2)1.1.2.2.18 Document Item: Text Identification (Segment E1EDPT1)1.1.2.2.19 Document Item: Additionals (Segment E1ADDI1)1.1.2.2.20 Document Item: Shipping Unit Header (Segment E1EDL37)1.1.2.2.21 Document Item: VAS Ticketing/Labeling (Segment E1J3AIT)1.1.2.2.22 Document Item: VAS Ticketing/Labeling Text (Segment E1J3AIX)1.1.2.2.23 Document Item: VAS Special Services (Segment E1J3AIS)1.1.2.2.24 Document Item: VAS Packing (Segment E1J3AIP)1.1.2.2.25 Document Item: Terms of Payment (Segment E1EDP18)1.1.2.2.26 Document Item: Additional Data (Segment E1EDP35)1.1.3 User Exits in the Incoming Order1.2 Contract1.2.1 Customizing: Contract1.2.2 Technical Information: Contract1.2.2.1 Document Header: Organizational Data (Segment E1EDK14)1.2.2.2 Document Header: Date Segment (Segment E1J3K03)1.3 Quotation1.3.1 Technical Information: Quotation1.4 Order Change1.4.1 Customizing: Order Change1.4.2 Technical Information: Order Change1.4.2.1 Document Item: General Data (Segment E1J3P01)1.4.2.2 Document Item: Multi-Store Order (Segment E1J3AIO)1.4.2.3 Document Item: VAS Ticketing/Labeling (Segment E1J3AIT)


Page 2 of 49

1.4.2.4 Document Item: VAS Ticketing/Labeling Text (Segment E1J3AIX)1.4.2.5 Document Item: VAS Packing (Segment E1J3AIP)1.4.2.6 Document Item: VAS Special Services (Segment E1J3AIS)1.4.2.7 Document Item: Partner Information (Segment E1EDPA1)1.4.2.8 Document Item: Texts (Segment E1EDPT2)1.4.2.9 Document Header: Organizational Data (Segment E1EDK14)1.4.2.10 Document Header: Partner Information (Segment E1EDKA1)1.4.2.11 Document Header: Reference Data (Segment E1EDK02)1.4.2.12 Document Header: Payment Cards (Segment E1EDK36)1.4.2.13 Document Header: Texts (Segments E1EDKT2)1.4.2.14 Document Header: MSO Header (Segment E1J3AHO)1.4.2.15 User Exits in the Incoming Order Change1.5 Order Confirmation1.5.1 General Data for the Order Confirmation (Segment E1J3P01)1.5.1.1 Multi-Store Order (Segment E1J3AIO)1.5.1.2 VAS Ticketing/Labeling (Segment E1J3AIT)1.5.1.3 VAS Ticketing/Labeling Text (Segment E1J3AIX)1.5.1.4 VAS Packing (Segment E1J3AIP)1.5.1.5 VAS Special Services (Segment E1J3AIS)1.5.1.6 Object Identification (Segment E1J3AIM)1.5.1.7 Reference Data (Segment E1EDP02)1.5.1.8 Date Segment (Segment E1J3P03)1.5.1.9 Taxes (Segment E1J3P04)1.5.1.10 Conditions (Segment E1J3P05)1.5.1.11 Schedule Lines (Segment E1EDP20)1.5.1.12 Schedule Lines Additional Data (Segment E1J3P20)1.5.1.13 Partner Information (Segment E1EDPA1)1.5.1.14 Partner Info Additional Data (Segment E1EDPA3)1.5.1.15 Object Identification (Segment E1EDP19)1.5.1.16 Terms of Delivery (Segment E1EDP17)1.5.1.17 Terms of Payment (Segment E1EDP18)1.5.1.18 Additional Data (Segment E1EDP35)1.5.1.19 Text Identification (Segment E1EDPT1)1.5.1.20 Texts (Segment E1EDPT2)1.5.1.21 Totals Segment (Segment E1EDS01)1.5.1.22 User Exits in the Outgoing Order Confirmation1.5.2 Document Header: General Data (Segment E1EDK01)1.5.2.1 Document Header: Organizational Data (Segment E1EDK14)1.5.2.2 Document Header: Date Segment (Segment E1J3K03)1.5.2.3 Document Header: Taxes (Segment E1EDK04)1.5.2.4 Document Header: Conditions (Segment E1EDK05)1.5.2.5 Document Header: Partner Info (Segment E1EDKA1)1.5.2.6 Document Header: Partner Info Additional Data (Segment E1EDK02)1.5.2.7 Document Header: Reference Data (Segment E1EDK02)1.5.2.8 Document Header: Terms of Delivery (Segment E1EDK17)1.5.2.9 Document Header: Terms of Payment (Segment E1EDK18)1.5.2.10 Document Header: Additional Data (Segment E1EDK35)1.5.2.11 Document Header: Text Identification (Segment E1EDKT1)1.5.2.12 Document Header: Texts (Segment E1EDKT2)1.6 IDoc Error Handling for Inbound IDocs


Page 3 of 49

!--a11y-->

1 Sales

Available Document TypesThe following table shows an overview of the supported document types, their assigned logical messages, and the IDoc type to be used.

Remember that this documentation always refers to the most recent version of an IDoc type, unless specified otherwise. SAP recommends,therefore, that you use the most recent IDoc type version.

Document Type Direction Logical Message IDoc Type Output Type Process CodeOrders Inbound ORDERS /AFS/ORDERS04 J3AAContracts (CQ) Inbound ORDERS /AFS/ORDERS04 J3AAOrder Change Inbound ORDCHG /AFS/ORDERS04 J3ACOrder Confirmation Outbound ORDRSP /AFS/ORDERS04 BA00 SD10Quotations Outbound QUOTES /AFS/ORDERS04 AN00 J3AJ

!--a11y-->

1.1 Sales Order

FeaturesSales orders can be created and updated using IDoc interfaces. In contrast to the standard IDoc process, the AFS-specific enhancements are primarily in theareas of dimension processing, processing of VAS data, and MSO processing. The decisive technical difference from standard processing is the implementationof the data transfer to the application with standardized "Direct Input Modules". On the one hand, this allows for a significantly better runtime for the process. Onthe other hand, it also prevents the possibility of running the data processing "visibly" as is normally possible in an inbound process when using Batch Input.An order can also be created as a contrast release order for an existing quantity contract using the IDoc interface. Individual contracts or contract items can thenbe directly referenced. The corresponding dependencies are documented in the document flow. A reference to an existing quantity contract in the incoming ordervia the IDoc interface can only be automatically implemented when two customer enhancements are used. For more information about the procedure, see the SAPNotes on customer enhancements EXIT_SAPLJ4AS_601 and EXIT_SAPLJ4AS_701.

To use enhanced error handling options, see section " Error handling in ORDERS Inbound ".The current release uses IDoc type /AFS/ORDERS04. This IDoc type is now in the fourth version (after J3AORD01, J3AORD02, /AFS/ORDERS03).Note that you should always use the most recent version of an IDoc type.

AFS RestrictionsWhen creating an MSO explosion, the splitting of the created order into individual documents is not automatically triggered.The delivery order is not supported.Conditions in the incoming sales order cannot be changed at the header level, item level or dimension level. Read the Notes in the documentation for

segments E1EDK04, E1EDK05, E1EDP04 and E1EDP05.You cannot use the IDoc interface to automatically copy contracts to a sales document as an attachment with reference to a contact. A contract reference can

be made for each individual item or dimension.VAS data or MSOs cannot be changed in AFS.AFS does not support adding individual components by means of an order change IDoc (ORDCHG) to a bill of material (BOM) that has already been

exploded in a sales document.Creating MSOs with VAS dataIn order changes per IDoc, the partner functions AG, RE, RG, and SB cannot be changed (this is also valid when adding new items and/or dimensions).Only the partner functions RE, WE and RG are processed at item level.AFS does not support changes to the material number or the dimension of an already existing stock keeping unit (SKU). SKUs can only be flagged with one

deletion indicator.Contracts: AFS does not support the transfer or additional contract data (table VEDA) using the IDoc interface.


Page 4 of 49

!--a11y-->

1.1.1 Customizing: Sales Order The workflow basic settings for error handling must be maintained (transaction SWU3).You must assign the EDI pricing conditions JED1 and JED2 to the pricing procedure of the respective document type of the sales area. These pricing

conditions serve to transfer the expected customer price / customer value to the sales document.You must maintain the translation of EDI internal item categories into SD item categories in Customizing (transaction code VOE1) in the table EDPST (see

also notes for the documentation for segment E1EDP01, Field PSTYP).IMG: Sales and Distribution Electronic Data Interchange EDI Messages Convert SAP Item Category to IDoc Item Category.Using the table EDPAR, you can convert external partner numbers into internal partner numbers as needed. Maintain the table using transaction VOE4.

Read also the notes in the documentation for the segments E1EDKA1 and E1EDPA1.IMG: Sales and Distribution Electronic Data Interchange EDI Messages Configure EDI Partners Convert External to Internal Partner Numbers.You can control the determination of the sales area data (sales organization, distribution channel, division) with the table EDSDC. Since an EDI partner will

only rarely transmit this data (see notes for the documentation on segment E1EDK14), the sales area can be determined for the transfer to the applicationdepending on the customer and vendor number. To do this call the transaction VOE2.

IMG: Sales and Distribution Electronic Data Interchange EDI Messages Configure EDI Partners Assign Customer/Vendor To Sales OrganizationData.

!--a11y-->

1.1.2 Technical Information: Sales Order The following document provides descriptions of the functionality of each field and explains how the essential elements are used. Note that documentation isavailable for the IDoc segments and fields in SAP system. Call up this documentation in transaction we60. The respective segment hierarchy (interdependency ofthe segments) can also be found in the documentation.

!--a11y-->

1.5.2 Document Header: General Data (Segment E1EDK01) Mandatory segment: YES

Field Explanation Processingaction Action code that concerns the entire EDI message No processingkzabs Order acknowledgment requirement indicator No processingcurcy Currency code Here you transfer an ISO currency code that is

converted in the SAP internal currency code. If theconversion is not successful, error VG014 appears.

hwaer EDI local currency No processingwkurs Exchange rate Is transferred to the documentzterm Term of payment Is transferred to the documentkundeuinr VAT registration number No processingeigenuinr VAT registration number No processingBSARt Document type No processingBELNR IDoc document number No processingntgew Net Weight No processingbrgew Gross weight No processinggewei Weight Unit No processingfkart_rl Remuneration list type No processingABLAD Unloading point No processingBSTZD Order number addition of customer Is transferred to the documentVSART Shipping condition Is transferred to the documentVSART_BEZ Description of shipping type No processingrecipnt_no Number of recipient No processingkzazu Indicator: order combination Is transferred to the documentautlf Complete delivery indicator Is transferred to the documentaugru Order reason Is transferred to the documentaugru_bez Description order reason No processingabrvw Is transferred to the document


Page 5 of 49

abrvw_bez No processingfktyp Billing category No processinglifsk Delivery note block Is transferred to the documentlifsk_bez Description: delivery note block No processingempst Receiving point Is transferred to the documentabtnr Department number No processingdelco Agreed delivery time No processingwkurs_m Rate with indirect quotation No processing

!--a11y-->

1.5.2.1 Document Header: Organizational Data (SegmentE1EDK14) Mandatory segment: NO

Field Short text ExplanationQUALF Organization indicator Describes the use of the data sent in field ORGID

(for example 006 for division, 007 for distributionchannel, 008 for sales organization). With thequalifier 012 the order type can also be transferredin the field ORGID.

ORGID Organization ID See field QUALF.

The following indicators are processed in the inbound IDoc:

006 Division007 Distribution Channel008 Sales Organization010 Sales Group012 Order Type016 Sales Office019 Purchase Order Type (SD)J01 Department

If no data for sales organization, distribution channel and/or division is sent in the segment, the determination of the data is called using the table EDSDC.An entry for the key sold-to party (AG) + vendor number (LF) is then searched for. The sold-to party and vendor number are taken from the data from segmentE1EDKA1 for the partner function ,AG (sold-to party from field PARTN, vendor number from field LIFNR). If segment E1EDKA1 is sent for partner function ,LF(vendor) as well, the vendor number is then taken from this segment (field PARTN).If the determination of the sales area data goes wrong, you will see the error message VG204.The sales area data can also be determined via the customer enhancement. The corresponding data is to be transferred to the fields DXVBAK-VKORG (= salesorganization), DXVBAK-VTWEG (= distribution channel) and DXVBAK-SPART (= division). The customer enhancement exit_saplj4as_002 should be used forthis.If the order type (indicator ,012) is not transferred in the IDoc, it will be set as standard order (,OR). The default setting for the purchase order type (indicator 019)is also DFUE. Please note that the valid purchase order types are to be maintained for each order type in the IMG (Sales and Distribution Sales SalesDocuments Sales Document Header Assign Ordering Types (AFS)). If this assignment does not exist, the error message 00058 is displayed.

!--a11y-->

1.5.2.2 Document Header: Date Segment (Segment E1J3K03) Mandatory segment: NO

Field Short text ExplanationIDDAT Indicator for Date Segment Indicator for the use of the date / time entries in the

following fields.DATUM Date Is transferred to the documentUZEIT Time Is transferred to the document


Page 6 of 49

J_3AQUALF Indicator Indicator for the qualification of the use of the date.The field is used for purely informative reasons andfor adding information to the date. The permittedvalue table is J_3AQUALF.

The following date indicators are processed:

003 Requested delivery date005 AFS: value-added service Date006 AFS: Cancellation Date007 Price determination date014 Validity start date for outline agreements022 Date for services023 Pick-up date for delivery order (validity start date)024 Pick-up date for delivery order (validity end date)

The requested delivery date (003) and the cancellation date (006) are checked for validity by the inbound function. This means that if one of these dates is inthe past (the reference date is the current system date), the processing terminates with the error message V1437. However, this error only leads to terminationin the first processing of an IDoc (IDoc is set to status 51). If the incorrect IDoc is processed a second time (for example, with transaction BD87 or reportRBDMANI2), the incorrect date only leads to a warning message which does not interfere with the update of the data.

!--a11y-->

1.5.2.3 Document Header: Taxes (Segment E1EDK04) Mandatory segment: NO

Field ExplanationMWSKZ VAT IDMSATZ Value-added taxMWSBT Sales tax amountTXJCD Tax Jurisdiction CodeKTEXT Text field

Although data sent in the segment E1EDP04 will first be read by the inbound processing, it cannot be transferred to the application. This leads to the errorVG200 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed incorrectly.

!--a11y-->

1.5.2.4 Document Header: Conditions (Segment E1EDK05) Mandatory segment: No

Field ExplanationALCKZ Surcharge or discount indicatorKSCHL Condition type (coded)KOTXT Condition descriptionBETRG Fixed surcharge / discount on item total gross amountKPERC Condition percentage rateKRATE Condition record per unitUPRBS Price UnitMEAUN Unit of measureKOBTR Condition end amountMWSKZ VAT IDMSATZ Value-added taxKOEIN Currency

Although data sent in the segment E1EDP05 will first be read by the inbound processing, it cannot be transferred to the application. This leads to the error


Page 7 of 49

VG201 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed incorrectly.

!--a11y-->

1.5.2.5 Document Header: Partner Info (Segment E1EDKA1) Mandatory segment: NO

Field Short text ExplanationPARVW Partner function (such as sold-to party, ship-to

party,...)Internal (2-character) code for the partner function(such as AG, WE)

PARTN Partner number Internal number of the partnerLIFNR Vendor number at the customer Normally the identification number of the order

recipient at the sold-to party. Using this field aconversion of external partner numbers into internalpartner numbers is also possible (see below).

NAME1 Name 1 The data sent in these fields serves to transferpossibly different address information to the partner.Missing data is transferred from the existing masterrecords.

NAME2 Name 2 Additional fields for partner information. For detailed

information see IDoc documentation on transactionWE60.

KNREF Customized description of the business partner(plant, warehouse)

ILNNR 70 Character fieldPFORT Location of the P.O. BoxSPRAS_ISO Language according to ISO code 639TITLE Form of address

Only those partner functions can be processed in the field PARVW that have been defined in table TPAR (transaction VOPA). The transfer of a non-definedpartner function leads to error message VP450.The following is valid for the determination of the partner number:If the partner number is sent in the field PARTN, it will be transferred as such to the document. If the field PARTN remains empty and if instead a partner numberis sent in the field LIFNR, the external partner number (LIFNR) will be converted into the internal partner number (PARTN) via table EDPAR. The partner numberfrom the sender information of the control record (EDPAR-KUNNR), the partner function (EDPAR-PARVW) transferred in the segment, as well as the externalpartner number (EDPAR-EXPNR) are used as keys for the conversion. If the conversion is not successful, the error message VG140 appears.If data is not sent in PARTN or in LIFNR, the partner number is determined by processing the inferior segment E1EDKA3 (see below).For the partner functions AG (Sold-to party), WE (Ship-to party), RE (Bill-to party) and RG (Payer) address information that has not been transferred is read fromthe respective master data record.

!--a11y-->

1.1.2.1.6 Document Header: Partner Info Additional Data(Segment E1EDKA3) Mandatory segment: NOSuperior segment: E1EDKA1

Field Short text ExplanationQUALP Partner identification Only indicator 001 - International Location Number

(ILN) is processed here.STDPN 70 Character field Identification number

The segment can be used to determine a partner number from the transfer of the International Location Number (ILN).

PrerequisiteA valid partner function has been sent in the superior segment E1EDKA1 and the fields PARTN and LIFNR of the segment E1EDKA1 have been transferredempty. In this case the system determines the partner number via the specifications from the view Control in the customer master record. The complete 13 digitILN must be then be transferred in STDPN. If the conversion could not be successfully carried out, it will lead to error message VG140.


Page 8 of 49

!--a11y-->

1.5.2.7 Document Header: Reference Data (SegmentE1EDK02) Mandatory segment: NO

Field Short text ExplanationQUALF Reference document indicator For the identification of the subsequent document

number.BELNR Document number Document numberPOSNR Item Number No processingDATUM Date Document dateUZEIT Time No processing

The following indicators for reference documents are processed:

001 Order number of customer004 Quotation number of vendor007 Collective number050 Delivery order066 External order number (in external order number assignment)

The document date (field DATUM) is only transferred for reference documents for the indicator 001.

!--a11y-->

1.5.2.8 Document Header: Terms of Delivery (SegmentE1EDK17) Mandatory segment: NO

Field Short text ExplanationQUALF Terms of delivery indicator Permitted values for the indicator are 001 for

Incoterms part 1 and 002 for Incoterms part 2LKOND Delivery condition code Terms of delivery codeLKTEXT Delivery condition text Terms of delivery text

If the text field LKTEXT is filled in addition to the terms of delivery code for the indicator 001 (=Incoterms part 1) in this segment, then this textwill first be interpreted as Incoterms part 2. These entries will, however, be overwritten again as soon as the segment is sent with theindicator 002. For this reason it is very important to make sure that the segment is sent in the correct sequence.

!--a11y-->

1.5.2.9 Document Header: Terms of Payment (SegmentE1EDK18) Mandatory segment: NO

Field ExplanationQUALF Terms of payment indicatorTAGE Number of daysPRZNT Percentage for terms of payment


Page 9 of 49

ZTERM_TXT Text line

Although data for terms of payment sent in the segment E1EDK18 will first be read by the inbound processing, it cannot be transferred to theapplication. This leads to the error VG202 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processedincorrectly.

!--a11y-->

1.5.2.10 Document Header: Additional Data (SegmentE1EDK35) Mandatory segment: NO

Field Short text ExplanationQUALZ Indicator for IDoc additional data Indicator for additional data transferred with CUSADDCUSADD Data element for article number CUSADD_BEZ 40 character field No processing

The following indicators for additional data are processed at document level:

001 to 005 Customer groups 1 - 5006 to 010 Condition groups 1 - 5J01 to J05 AFS customer groups 6 7

!--a11y-->

1.4.2.12 Document Header: Payment Cards (SegmentE1EDK36) Mandatory segment: NO

Field ExplanationCCINS Card typeCCINS_BEZEI DescriptionCCNUM Card numberEXDATBI DateCCNAME Name of cardholderFAKWR Maximum amount

The segment E1EDK36 is not supported in the incoming order.

!--a11y-->

1.5.2.11 Document Header: Text Identification (SegmentE1EDKT1) Mandatory segment: NO

Field Short text ExplanationTDID Text ID Text identification key The permitted values are

dependent on the IMG settings for the respectivedocument category.

TSSPRAS Language key SAP language key of the texts


Page 10 of 49

TSSPRAS_ISO Language according to ISO code 639 ISO language keyTDOBJECT Texts: Application object TDOBNAME Text name

Segment E1EDKT2 must be sent for each text line corresponding to segment E1EDKT1. Remember that the processing of texts has a considerably negativeeffect on the performance of the entire inbound processing.

!--a11y-->

1.5.2.12 Document Header: Texts (Segment E1EDKT2) Mandatory segment: NOSuperior segment: E1EDKT1

Field Short text ExplanationTDLINE Text line Text line for the Text ID used under E1EDKT1. The

individual text line has a maximum of 70 characters.For texts with multiple lines, the segment must berepeated accordingly.

TDFORMAT Tag column The tag column contains format keys which definethe output form of the text or initiate control demands.

!--a11y-->

1.4.2.14 Document Header: MSO Header (Segment E1J3AHO) Mandatory segment: NO

Field Short text ExplanationJ_3AMSOFLG Multi-store order indicator The indicator controls whether the Mix ID should be

generated automatically for an MSO or if it wasalready assigned in the inbound IDoc. If the indicatoris set, there will be no automatic Mix ID generation.

This segment generally does not control if this is a multi-store order or not. Rather, this is determined from the existence of E1J3AIO-segments. When the segmentE1J3AHO is sent with the indicator, the Mix ID from segment E1J3P01, field J_3AMSOM is used for grouping. Remember that the proper assignment of theseMix IDs is not checked. This means that the (external) assignment of the Mix IDs must keep to the rules for grouping. (Only those items can be grouped in oneMix ID, for which the same combination of stores order the same combination of quantities and dimensions respectively for the same material.)

!--a11y-->

1.4.2.1 Document Item: General Data (Segment E1J3P01) Mandatory segment: NO

Field Short text ExplanationPOSEX Item Number Item number of the current document. It is used for

the unique identification of the item. Normally the itemnumber is copied from the customer order.

ACTION Action code that concerns the item. Not relevant for incoming ordersPSTYP Item Category Indicator for the item category. The (one-digit)

numeric indicator is converted in the sales itemcategory depending on the order type, using thetable EDPST. Note, that an entry in this field isalways overridden by the value in field PSTYV.

KZABS Indicator for the order acknowledgment requirement No processingMENGE Quantity Ordered quantity of the item.

Note: The quantity that is relevant for the documentitem is always taken from segment E1EDP20.

MENEE Unit of Measure ISO code of the unit of measure for the order quantityBMNG2 Quantity in Price Unit of Measure No processing


Page 11 of 49

PMENE Price Unit of Measure ISO code of the price unit of measureABFTZ Agreed Cumulative Quantity No processingVPREI Price (net) Customer-expected net pricePEINH Price Unit Price UnitNETWR Value of Item (net) Customer-expected net valueANETW Absolute Net Value of the Item No processingSKFBP Discountable amount No processingNTGEW Net Weight No processingGEWEI Weight Unit No processingEINKZ Indicator: More than one schedule line for the item No processingCURCY Currency Currency codePREIS Gross price No processingMATKL Material class No processingUEPOS Superior item in bill of material structures Link to the related superior item number for bill of

material components. Note that the value must link toa POSEX, existing in the IDoc.

GRKOR Delivery group (items are delivered together) No processingEVERS Shipping Instruction No processingBPUMN Denominator for the Conversion BPRME into BME No processingBPUMZ Numerator for the Conversion BPRME into BME No processingABGRU Reason for item rejection Is transferred to document item.ABGRT Description No processingANTLF Maximum number of permitted partial deliveries per

itemIs transferred to document item.

FIXMG Delivery date and quantity fixed No processingKZAZU Indicator: order combination Is transferred to document item.J_3APOSNR Item Number Internal usageJ_3AMSOM Equal mix of products in a multi-store order The mix key is only then processed, if the flag

J_3AMSOFLG is set in segment E1J3AHO. It isused for the grouping of store and/or distributioncenters that should be delivered.

J_3ABZUS Requirements grouping Dimension requirements for an item are grouped, ifthis indicator is set.

J_3ADEPM Department Is transferred to document item.J_3ASPLIT AFS Split indicator Is transferred to document item.J_3ASEAN Season indicator Is transferred to document item.J_3ASIZE AFS grid value Is transferred to document item or schedule lineJ_3ALNGR AFS Line group ID (schedule lines are delivered

together)Is transferred to document item.

J_4KRCAT Requirements Category Is transferred to document item.J_4KSCAT Stock Category No processingBRGEW Total Weight No processingVOLUM Volume No processingVOLEH Volume Unit No processingJ_3AVASIT VAS Item values ticketing/labeling (E), packing (V),

special service (S)No processing

J_3AEBTYP Order confirmation category No processingJ_3AMSOF AFS Multi-store order: counter for partner The counter for the number of stores that should be

delivered with this item will only be then processed ifsegment E1J3AHO was sent with flagJ_3AMSOFLG. You must enter the total number ofstores per item.

PSTYV Item category sales document The field directly transfers the item category to thedocument item. In contrast to field PSTYP noconversion takes place. Note that the content of fieldPSTYV overrides the value of field PSTYP andsends it directly to the application.

EMPST Receiving point Is transferred to document item.ABTNR Department number No processingABRVW Usage indicator No processingWERKS Plant Is transferred to document item.


Page 12 of 49

LPRIO Delivery priority No processingLPRIO_BEZ Description No processingROUTE Route No processingROUTE_BEZ Description No processingLGORT Storage location No processingVSTEL Shipping point No processingDELCO Agreed delivery time No processingMATNR Material identification No processing

Note: The material identification and determination iscontrolled by using segments E1J3AIM and/orE1EDP19.

The document item segment E1J3P01 starts the transfer of data per item. Below the segment you find further item-related segments with detailed information for therespective item. A prerequisite for correctly processing the segment is that the external item number in field POSEX is uniquely filled. If the field remains initial,error message /AFS/IDOC 018 is displayed. In view of automatic order changes with the message type ORDCHG you must note that the external itemnumber is uniquely transferred to the created document. After the creation of the order, it is the unique identification and reference criterion of an item.Bills of MaterialFor the processing of bills of materials in incoming orders, there are some special features. There are basically two ways of BOM processing:

In the IDoc, only the header material of a BOM is sent.Both header and component materials are sent.

In both cases the BOM is exploded in the sales document, according to the settings in the IMG. Make sure when using item categories that the correct itemcategories are transferred for both header and component items. An automatic item category determination only takes place if neither field PSTYP nor field PSTYVare filled in segment E1J3P01. The sales document contains more items after the transfer of IDoc data than were sent in the IDoc. This has to do with the fact thatduring the BOM explosion in individual components, new items are generated.If both header and item materials are sent as mentioned in the second case, the relation between the two can be created using field UEPOS in segmentE1J3P01. Here, the value of the superior item always refers to the external item number (POSEX) of the header material. We strongly recommend that you sendrelated components and their respective header material as groups in the sequence of the individual E1J3P01 segments.It is possible to send a material as an individual item without reference to a header material, even if it belongs to a BOM as component. In this case you must notfill field UEPOS.

The processing of BOMs in multi-store orders per IDoc interface is currently not supported.Processing of Item SegmentsThere can generally be one of the following situations during the processing of the item segments: A material of the following types is sent:

Standard (= non-AFS) MaterialAFS material with dimensionsAFS material without dimensions (without a grid)

In the first case a 1:1 ratio exists between the sent E1J3P01 segment and the created document item. Normally the item contains a delivery schedule line.In the second case an n:1 relation exists between the sent E1J3P01 segment and the created document item. The ordered dimensions are first grouped bymaterial numbers and combined to items with the same material number. Different dimensions of the same material (for the same recipient) are combined to oneitem. The individual dimension is reflected in a schedule line on the document. All the relevant data is "copied" from the item header to the schedule line for theidentification of the individual purchase order items. That means that the external item number POSEX is not connected to the document item itself, but rather tothe schedule line at dimension level.In the third case (no grid material) the processing is similar to the standard material without combining at item level.Sort CriteriaThe grouping of AFS materials and their dimensions is controlled by the following sort criteria:

Material numberGoods recipientPlantMSO Mix keyRequested delivery dateCancellation dateDepartmentItem Category

If you change one of the criteria, a new document item is created.The values of field VPREI and NETWR are interpreted as customer-expected price or item value. The entries are assigned to the condition types EDI1/EDI2 orJED1/JED2. The assignment to the AFS-specific conditions JED1 and JED2 only takes place, if the condition type is flagged as dimension-relevant in the IMG.When transferring the values, remember that the transferred values are checked in the sales document against the amounts determined by pricing. If there aredifferences, an incompletion log for the document is created according to the settings in the IMG. You can not overwrite the values that are determined by thepricing with the entries of the IDoc. The transfer of conditions both at header and item level is not supported by the inbound processing.

!--a11y-->

1.1.2.2.1 Document Item: Date Segment (Segment E1J3P03) Mandatory segment: NO


Page 13 of 49

Superior segment: E1J3P01


following fields.DATUM Date Is transferred to the documentUZEIT Time No processingJ_3AQUALF Indicator Indicator for the qualification of the use of the date.

The field is used for purely informative reasons andfor adding information to the date. The permittedvalue table is J_3AQUALF.

The following date indicators are processed at item level:

001 Purchase order date003 Requested delivery date006 AFS Cancellation Date007 Price determination date020 Fixed value date

The indicator J_3AQUALF is only used for the date indicators 003 and 006.

!--a11y-->

1.1.2.2.2 Document Item: Schedule Lines (Segment E1EDP20) Mandatory segment: YESSuperior segment: E1J3P01

Field Short text ExplanationWMENG Schedule line quantity Ordered quantityAMENG Previous schedule line quantity No processingEDATU Date Schedule line dateEZEIT Time Delivery timeEDATU_OLD Date No processingEZEIT_OLD IDoc: Time No processing

The meaning of the E1EDP20 segment reflects one of the AFS special features of incoming orders via the IDoc interface: The ordered quantities are transferredsolely from this segment for the AFS material as well as for standard material. Quantity entries from the E1J3P01 segment are not taken into account as far as thisis concerned. The only exception is the processing of multi-store orders: The ordered quantity of the respective dimension or of the material are calculated from thequantity entries of the segment E1J3AIO.

!--a11y-->

1.1.2.2.3 Document Item: Schedule Lines Additional Data(Segment E1J3P20) Mandatory segment: NOSuperior segment: E1EDP20

Field ExplanationJ_3AABGRU Reason for rejection for quotations and ordersJ_4KRCAT Requirements CategoryJ_4KSCAT Stock CategoryJ_3AETENR Schedule lineJ_3AVASIT VAS item values: E labeling, V packing, S special service


Page 14 of 49

The segment is not processed in the incoming order.

!--a11y-->

1.1.2.2.4 Document Item: Conditions (Segment E1J3P05) Mandatory segment: NOSuperior segment: E1J3P01

Field ExplanationALCKZ Surcharge or discount indicatorKSCHL Condition type (coded)KOTXT Condition descriptionBETRG Fixed surcharge / discount on item total gross amountKPERC Condition percentage rateKRATE Condition record per unitUPRBS Price UnitMEAUN Unit of measureKOBTR Condition end amountMENGE Quantity of the pricing scale (SPEC2000)PREIS Price per unit of measure (SPEC2000)MWSKZ VAT IDMSATZ Value-added taxKOEIN CurrencyCURTP Currency type and valuation view

Although data sent in the segment E1EDP05 will first be read by the inbound processing, it cannot be transferred to the application. Thisleads to the error VG201 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed incorrectly.

!--a11y-->

1.1.2.2.5 Document Item: Configuration Data (SegmentE1CUCFG) Mandatory segment: NO

Field ExplanationPOSEX 6 Character fieldCONFIG_ID 6 Character fieldROOT_ID 8 Character fieldSCE CU: Only information for the configuration transferred by SCE

The segment E1CUCFG (including the subsegments E1CUINS, E1CUPRT, E1CUVAL and E1CUBLB) is not processed in the incoming order.

!--a11y-->

1.1.2.2.6 Document Item: Service Specifications Data(Segment E1EDC01) Mandatory segment: NOSuperior segment: E1J3P01


Page 15 of 49

Field ExplanationSGTYP Service specifications segment typeZLTYP Service specifications line categoryLVALT Service specifications alternativesALTNO Alternative number for service specificationsALREF Assignment number for service specificationsZLART Service specifications line typePOSEX Line numberRANG Hierarchy level of the groupEXGRP Outline levelUEPOS Superior item in bill of material structuresMATKL Material classMENGE QuantityMENEE Unit of MeasureBMNG2 Quantity in Price Unit of MeasurePMENE Price Unit of MeasureBPUMN Denominator for the Conversion BPRME into BMEBPUMZ Numerator for the Conversion BPRME into BMEVPREI Price (net)PEINH Price UnitNETWR Value of Item (net)ANETW Absolute Net Value of the ItemSKFBP Discountable amountCURCY CurrencyPREIS Gross priceACTION Action code that concerns the item.KZABS Indicator for the order acknowledgment requirementUEBTO Overfulfillment toleranceUEBTK Unlimited overfulfillmentLBNUM Description of the service typeAUSGB Output of the service typeFRPOS Lower limitTOPOS Upper limitKTXT1 Short textKTXT2 Short textPERNR Personnel numberLGART Wage typeSTELL JobZWERT Total value totals segment

The segment E1EDC01 (including the subsegments E1EDC02, E1EDC03, E1EDC04, E1EDC05, E1EDC06, E1EDC07, E1EDCA1, E1EDC19, E1EDC17,E1EDC18, E1EDCT1 and E1EDCT2) is not processed in the incoming order.

!--a11y-->

1.1.2.2.7 Document Item: Terms of Delivery (SegmentE1EDP17) Mandatory segment: NOSuperior segment: E1J3P01

Field Short text ExplanationQUALF Terms of delivery indicator Permitted values for the indicator are 001 for

Incoterms part 1 and 002 for Incoterms part 2LKOND Delivery condition code Terms of delivery code


Page 16 of 49

LKTEXT Delivery condition text Terms of delivery textLPRIO Delivery priority No processing

If the text field LKTEXT is filled in addition to the terms of delivery code for the indicator 001 (=Incoterms part 1) in this segment, then this textwill first be interpreted as Incoterms part 2. These entries will, however, be overwritten again as soon as the segment is sent with theindicator 002. For this reason it is very important to make sure that the segment is sent in the correct sequence.

The terms of delivery at item level do not belong to the sort / grouping criteria according to which AFS dimensions are combined to formitems. This means that different terms of delivery at dimension level might not be completely transferred to the document. The only possibilityof controlling different terms of delivery at dimension level for the same material is to transfer different ship-to parties or another groupingcriterion named in the notes on segment E1J3P01.

!--a11y-->

1.4.2.2 Document Item: Multi-Store Order (Segment E1J3AIO) Mandatory segment: NOSuperior segment: E1J3P01

Field Short text ExplanationJ_3APARVW Partner function Partner function of the ship-to partyJ_3ASTORE MSO stores Partner number of the ship-to partyJ_3ADICE Customer distribution center Identification number of the customer distribution

centerJ_3AWMENG Schedule line quantity Ordered quantityJ_3ABMENG Delivered quantity in sales unit No processingJ_3ADEPM Department Department number (is transferred to the document)J_3ASTCU Customer store / distribution center number Identification of the store / the customer distribution

center at the customerJ_3ABSTNK Order number of customer Order number of customerJ_3AILNNR 70 Character field International Location Number of the storeJ_3AUPDKZ Update Indicator No processing

With the segment E1J3AIO the necessary data for the creation of MSOs is transferred to the document. Using the specification of the partner function it iscontrolled whether the store itself is the ship-to party or if the delivery first goes to a customer distribution center. If the store itself is the ship-to party, use thepartner function WE for the ship-to party. The partner number that was maintained in the system as the ship-to party is to be transferred in the field J_3ASTORE.If this field is not filled, you can trigger a conversion of the partner number from the specifications for the International Location Number (J_3AILNNR) (see alsosegment E1EDKA3).The customer store number can be transferred in the field J_3ASTCU. If this number is maintained in the AFS additional data for the customer master, it will beconverted into a valid partner number. The original customer store number is then transferred to the document.For further documentation of MSOs, please see the information inMulti-Store Orders.The quantity (J_3AWMENG) transferred in this segment is assigned to the respective store as the ordered quantity. Take note that the quantity specification insegment E1EDP20 is not included in this case.The segment can occur multiply under an E1J3P01-segment, depending on the number of stores that order the product described under this item. All furtherspecifications in sub-segments are then valid for all stores respectively.The system assigns a mix ID for a group of stores (exception: in segment E1J3AHO the indicator J_3AMSOFLG has been set). With the automatic assignment ofthe mix ID, a numerical numerator is used. This means that a maximum of 999 mix IDs can be assigned. The stores are grouped according to the number of thesame combinations of stores that order the same combination of dimensions and quantities for the same date. The following graphic illustrates the logic for theautomatic generation of the mix IDs.Example of Mix ID assignments in MSOs


Page 17 of 49

!--a11y-->

1.1.2.2.9 Document Item: Object Identification (SegmentE1EDP19) Mandatory segment: NOSuperior segment: E1EDPA1

Field Short text ExplanationQUALF IDoc object identification (such as material number,

customer, and so on)Indicator for material identification in field IDTNR

IDTNR Material identification Material numberKTEXT Short text Material short textMFRPN Manufacturer part number No processingMFRNR Manufacturer number No processing

The following indicators in the field QUALF are processed in the specified sequence:

002 internal material number003 EAN/UPC number001 Customer material number

See the note for segment E1J3AIM. The segment E1EDP19 should no longer be used for object identification because AFS specific datacannot be transferred here.

!--a11y-->

1.1.2.2.10 Document Item: Object Identification (SegmentE1J3AIM) Mandatory segment: NOSuperior segment: E1J3P01

Field Short text ExplanationJ_3AOBIDQF Indicator for object identification Indicator for material identification in field J_3AIDTNRJ_3AIDTNR Material identification Material identificationJ_3ASIZE AFS grid value Grid value / dimension for materialJ_3AKTEXT Material short text Is transferred to the documentJ_4KRCAT Requirements Category Is transferred to the documentJ_4KSCAT Stock Category No processing

The following indicators in the field J_3AOBIDQF are processed in the specified sequence:


Page 18 of 49

002 internal material number003 EAN/UPC number001 customer material number

Take note that with this segment the object identification can also be controlled via the standard segment E1EDP19. We recommend that youalways use E1J3AIM instead of E1EDP19.

If no material number is sent to indicator 002, a material determination procedure is triggered which first looks for a material number based on the specifications ofthe EAN/UPC number (indicator 003). The AFS specific table J_3AMEAN must be maintained for this via transaction J3A^ ( Logistics AFS Central Functions Material Master UPC/EAN Numbers). An incorrect UPC/EAN number leads to error message 8J308.The material determination according to IMG settings is triggered via the customer material number. If the internal material number is already sent in the IDoc or ifit was determined using the EAN/UPC number, then the customer material number is transferred as information to the document. No further check takes place.The transfer of a grid value in J_3ASIZE is only necessary if, for example, it is not already determinable via the EAN/UPC number or customer material number.The grid value must, however, always be sent in connection with the internal material number, in order to guarantee the correct setting of the document item or itsdimensions.The additional check for eligibility of a transferred material number is carried out within the document creation. Similar to the dialog entry, error messages canoccur here that put the complete IDoc in the error status 51. This means that even if, for example, only one piece of material information could not be correctlytransferred to the document, the creation of the entire document will be terminated.

!--a11y-->

1.1.2.2.11 Document Item: Partner Info Additional Data(Segment E1EDPA3) Mandatory segment: NOSuperior segment: E1EDPA1

Field Short text ExplanationQUALP IDoc partner identification (for example

Dun&Bradstreet number)Only indicator 001 - International Location Number(ILN) is processed here.

STDPN 70 Character field Identification number

The segment can be used to determine a partner number from the transfer of the International Location Number (ILN).The prerequisite is that a valid partner function has been sent in the superior segment E1EDPA1 and the fields PARTN and LIFNR of the segment E1EDPA1have been transferred empty. In this case the system determines the partner number via the specifications from the view Control in the customer master record.The complete 13 digit ILN must be then be transferred in STDPN. If the conversion could not be successfully carried out, it will lead to error message VG140.

!--a11y-->

1.4.2.7 Document Item: Partner Information (SegmentE1EDPA1) Mandatory segment: NOSuperior segment: E1J3P01

Field Short text ExplanationPARVW Partner function (such as sold-to party, ship-to party,

and so on)Internal (2-character) code for the partner function(such as AG, WE)


recipient at the sold-to party. Using this field aconversion of external partner numbers into internalpartner numbers is also possible.

NAME1 Name 1 The data sent in these fields serves to transferpossibly different address information to the partner.

NAME2 Name 2 KNREF Customized description of the business partner

(plant, warehouse)


Page 19 of 49

ILNNR 70 Character field PFORT Location of the P.O. Box SPRAS_ISO Language according to ISO code 639 TITLE Form of address

Only the following partner functions are transferred at item level:

WE Goods recipientRE Bill-to partyRG Payer

You can find further information under segment E1EDKA1.

!--a11y-->

1.1.2.2.13 Document Item: Reference Order Item (SegmentE1CUREF) Mandatory segment: NOSuperior segment: E1J3P01

Field ExplanationPOSEX 6 Character fieldCONFIG_ID 6 Character fieldINST_ID 8 Character field

The segment is not used in the incoming order.

!--a11y-->

1.1.2.2.14 Document Item: Reference Data (SegmentE1EDP02) Mandatory segment: NOSuperior segment: E1J3P01


number.BELNR Document number Reference document numberZEILE Item Number Processing only for indicator 044 (purchase order of

the ship-to party)DATUM Date Document dateUZEIT Time No processingBSARK Organization IHREZ Your initial (from partner) Reference number of the customer

The following indicators are processed:

001 Order number of customer044 Purchase order of ship-to party052 Sequence number for delivery orderJ30 internal use in ALE


Page 20 of 49

!--a11y-->

1.1.2.2.15 Document Item: Taxes (Segment E1J3P04) Mandatory segment: NOSuperior segment: E1J3P01

Field ExplanationMWSKZ VAT IDMSATZ Value-added taxMWSBT Sales tax amountTXJCD Tax Jurisdiction CodeKTEXT Text field

Although data sent in the segment E1EDP04 will first be read by the inbound processing, it cannot be transferred to the application. Thisleads to the error VG200 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed incorrectly.

!--a11y-->

1.1.2.2.16 Document Item: Totals Segment (SegmentE1EDS01) Mandatory segment: NO

Field ExplanationSUMID Indicator: totals segment for shipping notificationSUMME Total value totals segmentSUNIT Unit total value totals segment shipping notificationWAERQ Currency

The totals segment E1EDS01 is not processed in the incoming order.

!--a11y-->

1.4.2.8 Document Item: Texts (Segment E1EDPT2) Mandatory segment: NOSuperior segment: E1EDPT1

Field Short text ExplanationTDLINE Text line Text line for the Text ID used under E1EDPT1. The



!--a11y-->

1.1.2.2.18 Document Item: Text Identification (SegmentE1EDPT1) Mandatory segment: NO


Page 21 of 49

Superior segment: E1J3P01

Field Short text ExplanationTDID Text ID Text identification key The permitted values are

dependent on the IMG settings for the respectivedocument category.

TSSPRAS Language key SAP language key of the textsTSSPRAS_ISO Language according to ISO code 639 ISO language key

Segment E1EDPT2 must be sent for each text line corresponding to segment E1EDPT1. Remember that the processing of texts has a considerably negativeeffect on the performance of the entire inbound processing. The correct processing of texts at item level requires that the external item number be transferreduniquely in the field POSEX (segment E1J3P01) for the entire document.

!--a11y-->

1.1.2.2.19 Document Item: Additionals (Segment E1ADDI1) Mandatory segment: NOSuperior segment: E1J3P01

Field ExplanationADDIMATNR Material number for additionalADDINUMBER Number of additionalsADDIVKME Sales unit of the materialADDIFM Procedure for additionalsADDIFM_TXT Additionals: Description for the procedure for additionalsADDIKLART Class type displayed when editing additionalsADDIKLART_TXT Description of class typeADDICLASS Class with additionals assigned to its elementsADDICLASS_TXT KeywordsADDIIDOC Indicator which refers to separate additionals IDoc

The segment is not used in the incoming order.

!--a11y-->

1.1.2.2.20 Document Item: Shipping Unit Header (SegmentE1EDL37) Mandatory segment: NO

Field ExplanationEXIDV External shipping unit IDTARAG Tare weight of shipping unitGWEIT Weight unit tareBRGEW Total weight of shipping unitNTGEW Loading weight of shipping unitMAGEW Maximum allowed loading weight of the shipping unitGWEIM Weight UnitBTVOL Total volume of shipping unitNTVOL Loading volume of shipping unitMAVOL Permitted loading volume of shipping unitVOLEM Volume UnitTAVOL Tare volume of shipping unitVOLET Volume unit tare


Page 22 of 49

VEGR2 Shipping unit group 2 (freely definable)VEGR1 Shipping unit group 1 (freely definable)VEGR3 Shipping unit group 3 (freely definable)VHILM Shipping materialVEGR4 Shipping unit group 4 (freely definable)LAENG LengthVEGR5 Shipping unit group 5 (freely definable)BREIT WidthHOEHE HeightMEABM Unit of dimension for length/width/heightINHALT Description of shipping unit contentVHART Shipping material typeMAGRV Material group: shipping materialsLADLG Length of loading platform in length of loading platform measurement unitsLADEH Unit of measure to measure the length of the loading platformFARZT Travel timeFAREH Unit of travel timeENTFE Distance traveledEHENT Unit of distanceVELTP Shipping unit categoryEXIDV2 2. External identification of shipping unitLANDT Country providing means of transportLANDF Drivers nationalityNAMEF Driver's nameNAMBE Passenger's nameVHILM_KU Customer shipping materialVEBEZ Description of shipping unitSMGKN SMG identification for material tagKDMAT35 Customer shipping materialSORTL Sort fieldERNAM Name of person who created objectGEWFX Weight and volume fixedERLKZ Status

The segment E1EDL37 (including the subsegments E1EDL39, E1EDL38 and E1EDL44) is not processed in the incoming order.

!--a11y-->

1.4.2.3 Document Item: VAS Ticketing/Labeling (SegmentE1J3AIT) Mandatory segment: NOSuperior segment: E1J3P01

Field Short text ExplanationJ_3ASTORE MSO stores The store for which there is ticketing/labeling.J_3ATLTYP VAS Ticketing/label type Is transferred to the documentJ_3ATLMAT VAS Ticketing/labeling material Is transferred to the documentJ_3ACHARC VAS charge code Is transferred to the documentJ_3AFIELD1 VAS User-Defined Field 1 Is transferred to the documentJ_3AFIELD2 VAS User-Defined Field 2 Is transferred to the documentJ_3AFIELD3 VAS User-Defined Field 3 Is transferred to the documentJ_3AVASPQ Quantity Is transferred to the documentJ_3AUPDKZ Update Indicator No processing


Page 23 of 49

J_3AUPDKZ Update Indicator No processingJ_3AVASPO VAS generated sub-item number No processingJ_3AVASETE VAS Generated Sub-Schedule Line Number No processing

The segment is connected to the item segment E1J3P01. The data sent here is transferred to the document according to the created item. Independent of the datasent here, an automatic determination of VAS data can also be triggered during the creation of a sales document.

!--a11y-->

1.4.2.4 Document Item: VAS Ticketing/Labeling Text (SegmentE1J3AIX) Mandatory segment: NOSuperior segment: E1J3AIT

Field Short text ExplanationJ_3ATLTXT Additional text for ticketing/labeling Is transferred to VAS itemJ_3ATLORD Order level Indicates from where in the document the entries for

the text information should be assigned in order to beprinted on the label.

J_3ATLITEM Item level J_3ATLSIZE Dimension level J_3AUPDKZ Update Indicator No processing

Corresponding to the previous E1J3AIX segment, additional texts can be transferred here for ticketing/labeling.

!--a11y-->

1.4.2.6 Document Item: VAS Special Services (SegmentE1J3AIS) Mandatory segment: NOSuperior segment: E1J3P01

Field Short text ExplanationJ_3ASTORE MSO stores The store for which there is special service

information.J_3ASSTYP VAS Special Services: Category Is transferred to the documentJ_3ASSMAT VAS Special Services: MaterialJ_3ACHARC VAS charge codeJ_3AFIELD1 VAS User-Defined Field 1J_3AFIELD2 VAS User-Defined Field 2J_3AFIELD3 VAS User-Defined Field 3J_3AVASPQ Quantity Internal usageJ_3AUPDKZ Update Indicator No processingJ_3AVASPO VAS generated sub-item number No processingJ_3AVASETE VAS Generated Sub-Schedule Line Number No processing

!--a11y-->

1.4.2.5 Document Item: VAS Packing (Segment E1J3AIP) Mandatory segment: NOSuperior segment: E1J3P01


Page 24 of 49

Field Short text ExplanationJ_3ASTORE MSO stores The store for which there is packing information.J_3APTYP VAS packing type Is transferred to the documentJ_3APMAT VAS packing material J_3ACHARC VAS charge code J_3AINCREM VAS Packing Increment J_3AMIXIND VAS Packing Mix Indicator J_3AFIELD1 VAS User-Defined Field 1 J_3AFIELD2 VAS User-Defined Field 2 J_3AFIELD3 VAS User-Defined Field 3 J_3AVASPQ Quantity Internal usageJ_3AUPDKZ Update Indicator No processingJ_3AVASPO VAS generated sub-item number No processingJ_3AVASETE VAS Generated Sub-Schedule Line Number No processing

!--a11y-->

1.1.2.2.25 Document Item: Terms of Payment (SegmentE1EDP18) Mandatory segment: NOSuperior segment: E1J3P01

Field ExplanationQUALF Terms of payment indicatorTAGE Number of daysPRZNT Percentage for terms of paymentZTERM_TXT Text line

Although data for terms of payment sent in the segment E1EDP18 will first be read by the inbound processing, it cannot be transferred to theapplication. This leads to the error VG202 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processedincorrectly.

!--a11y-->

1.1.2.2.26 Document Item: Additional Data (SegmentE1EDP35) Mandatory segment: NOSuperior segment: E1J3P01

Field Short text ExplanationQUALZ Indicator for additional data Indicator for additional data transferred with CUSADDCUSADD Additional data CUSADD_BEZ Text for additional data No processing

The following indicators for additional data are processed at item level:

001-005 Customer groups 1 5006-010 Condition groups 1 5

The customer groups and condition groups at item level do not belong to the sort / grouping criteria according to which AFS dimensions arecombined to form items. This means that different customer / condition groups at dimension level might not be completely transferred to the


Page 25 of 49

document. The only possibility of controlling different customer/condition groups at dimension level for the same material is to transfer differentship-to parties or another grouping criterion mentioned in the notes on segment E1J3P01.

!--a11y-->

1.1.3 User Exits in the Incoming Order A series of customer enhancements are available in the incoming order via the IDoc interface. To activate the customer enhancement, first create a project. Thecustomer enhancements of the inbound processing are summarized in the SAP enhancement J_3AEDS0.

!--a11y-->

1.2 Contract

UseInbound processing for contracts is implemented using the IDoc interface for the incoming order. Basically, there is no difference between the data processing andthe incoming order process. A sales document type for the sales document category G (= contract) is to be transferred in the IDoc as the order type (seeCustomizing).

FeaturesThe automatic referencing of contracts for contract release orders is controlled using two customer enhancements (EXIT_SAPMJ3AS_601 andEXIT_SAPMJ3AS_701) (for more information, see the documentation for the appropriate function modules).

AFS RestrictionsAFS does not support the transfer of additional contract data (table VEDA) using the IDoc interface.

!--a11y-->

1.2.1 Customizing: Contract Contracts must be flagged in Customizing as a sales document type for the document category contracts (G). Choose in Customizing Sales and Distribution Sales Sales Documents Sales Document Header Define Sales Document Types.

!--a11y-->

1.2.2 Technical Information: Contract The following document provides descriptions of the functionality of each field and explains how the essential elements are used. Note that contract handling isalmost identical to the method used when handling incoming orders. This section therefore only details the segments and fields that are used differently than inincoming orders.

!--a11y-->


Field Short text ExplanationQUALF Organization Indicator Describes the use of the data sent in field ORGID


ORGID Organization Indicator See field QUALF.


006 Division


Page 26 of 49

006 Division007 Distribution Channel008 Sales Organization010 Sales Group012 Order Type016 Sales Office019 Purchase Order Type (SD)J01 Department

For the creation of contracts the order type flagged as sales document category contract (G) in Customizing must be transferred with the indicator 012. If the ordertype is not sent directly with the IDoc, it can also be changed using the customer enhancement exit_saplj4as_002. The default setting for the purchase ordertype (indicator 019) is also DFUE for contracts. Please note that the valid purchase order types are to be maintained for each order type in Customizing. If thisassignment does not exist, the error message 00058 is displayed.

!--a11y-->

1.5.2.2 Document Header: Date Segment (Segment E1J3K03) Mandatory segment: NO


following fields.DATUM Date Is transferred to the documentUZEIT Time Is transferred to the documentJ_3AQUALF Indicator Indicator for the qualification of the use of the date.

The field is used for purely informative reasons andfor adding information to the date. The permittedvalue table is J_3AQUALF.

The following date indicators are relevant for contracts:

006 AFS Cancellation Date014 Validity start date for outline agreements

Please note that the AFS cancellation date for contracts is interpreted as the validity end date.The validity start date (014) and the validity end date (006) are checked by the inbound function. This means that if one of these dates is in the past (the referencedate is the current system date), the processing terminates with the error message V1437. However, this error only leads to termination in the first processing ofan IDoc (IDoc is set to status 51). If the incorrect IDoc is processed a second time (for example, with transaction BD87 or report RBDMANI2), the incorrect dateonly leads to a warning message which does not interfere with the update of the data.If the end date is earlier than the start date, the error message V1444 appears. If this occurs, please correct the date entries.

!--a11y-->

1.3 Quotation Requests for quotations can be sent to the vendors via the IDoc interface. The general conditions are sent in the IDoc so that the vendor can specifically create aquotation.

!--a11y-->

1.3.1 Technical Information: Quotation The IDoc outbound processing for quotations is essentially identical to that of theorder confirmation The following exceptions and special features are valid for quotations:Segment E1EDK02 Document Header Reference Data



Page 27 of 49

number.BELNR Document number Document numberPOSNR Item Number Item number of the documentDATUM Date Document dateUZEIT Time Time of the document

The indicator 004 is used for the quotation number.This also applies for the item segment E1EDP02.Segment E1EDP19 Document Item Object Identification

Field ExplanationQUALF IDoc object identification (such as material number, customer, and so on)IDTNR Material identificationKTEXT Short textMFRPN Manufacturer part numberMFRNR Manufacturer number

The segment is not used in the outbound quotation. The object identification is sent with the segment E1J3AIM.Document Item General Data

Field Short text ExplanationPOSEX Item Number Item number from a customer order.ACTION Action code that concerns the item. 000 - item unchanged

001 - item changed003 - item deleted

PSTYP Item Category One-digit numerical indicator for the item category.The indicator is converted into the sales itemcategory depending on the order type, using thetable EDPST.

KZABS Indicator for the order acknowledgment requirement N/AMENGE Quantity Ordered quantity of the item.

Please note: for AFS materials with dimensions, thequantity ordered is per dimension.

MENEE Unit of Measure ISO code of the unit of measure for the order quantityBMNG2 Quantity in Price Unit of Measure N/APMENE Price Unit of Measure ISO code of the price unit of measureABFTZ Agreed Cumulative Quantity N/AVPREI Price (net) Price per price unit. Please note: for AFS materials

with dimensions, the price here is per dimension.PEINH Price Unit Price UnitNETWR Value of Item (net) Net value. For AFS materials with dimensions, the

value here is per dimension.ANETW Absolute Net Value of the Item N/ASKFBP Discountable amount N/ANTGEW Net Weight Is copied from the document.GEWEI Weight Unit ISO code of the weight unitEINKZ Indicator: More than one schedule line for the item X, if more than one schedule line exists for the item.CURCY Currency ISO code for currencyPREIS Gross price N/AMATKL Material class Is copied from the document.UEPOS Superior item in bill of material structures Is copied from the document.GRKOR Delivery group (items are delivered together) Is copied from the document.EVERS Shipping Instruction N/ABPUMN Denominator for the conversion BPRME into BME N/ABPUMZ Numerator for the conversion BPRME into BME N/AABGRU Reason for item rejection Is copied from document item or schedule line.ABGRT Description Text for reason for rejection ABGRUANTLF Maximum number of permitted partial deliveries per

itemIs copied from the document.

FIXMG Delivery date and quantity fixed Is copied from the document.KZAZU Indicator: order combination N/A


Page 28 of 49

J_3APOSNR Item Number Schedule line number of dimensionJ_3AMSOM Equal mix of products in a multi-store order Mix ID for multi-store order.J_3ABZUS Requirements grouping Is copied from the document.J_3ADEPM Department Is copied from the document.J_3ASPLIT AFS Split indicator Is copied from the document.J_3ASEAN Season indicator Is copied from the document.J_3ASIZE AFS Grid Value N/AJ_3ALNGR AFS Line group-ID (schedule lines are delivered

together)Is copied from the document.

J_4KRCAT Requirements Category N/AJ_4KSCAT Stock Category N/ABRGEW Total Weight Is copied from the document itemVOLUM Volume N/AVOLEH Volume Unit N/AJ_3AVASIT VAS Item values ticketing/labeling (E), packing (V),

special service (S)Is copied from the document.

J_3AEBTYP Order confirmation category N/AJ_3AMSOF AFS Multi-store order counter for partner N/APSTYV Item category sales document N/AEMPST Receiving point Is copied from the document itemABTNR Department number N/AABRVW Usage indicator N/AWERKS Plant N/ALPRIO Delivery priority N/ALPRIO_BEZ Description N/AROUTE Route N/AROUTE_BEZ Description N/ALGORT Storage location N/AVSTEL Shipping point N/ADELCO Agreed delivery time N/AMATNR Material identification N/A

In contrast to the order confirmation, the dimension values and category values are not transferred in segment E1J3P01 (J_3ASIZE, J_4KRCAT, J_4KSCAT) in theinbound quotation.

!--a11y-->

1.4 Order Change

FeaturesThe same special features and restrictions that apply to the incoming sales order processing via EDI apply here. In addition, please note that AFS does notsupport an order change via IDoc for multi-store orders (MSO) and for value-added service (VAS) data.

AFS RestrictionsA change in MSOs and in orders with VAS data via IDoc is not supported.Conditions in the incoming sales order cannot be changed at the header level, item level or dimension level. Please also read the documentation of the

segments E1EDK04, E1EDK05, E1EDP04, E1EDP05.AFS does not support changes to the material number or the dimension of an already existing stock keeping unit (SKU). SKUs can only be flagged with one

deletion indicator.AFS does not support adding individual components by means of an order change IDoc (ORDCHG) to a bill of material (BOM) that has already been

exploded in a sales document.

!--a11y-->


Page 29 of 49

1.4.1 Customizing: Order Change Basically the same settings are valid as for the incoming orders.A partner profile and inbound parameters for the output type ORDCHG must be maintained (transaction WE20) for the partner.

!--a11y-->

1.4.2 Technical Information: Order Change The following document provides descriptions of the functionality of each field and explains how the essential elements are used. Please note that the processingfor order change is for the most part identical to the processing for incoming orders. This section therefore only details the segments and fields that are useddifferently than in incoming orders.

!--a11y-->

1.4.2.1 Document Item: General Data (Segment E1J3P01) Mandatory segment: NO

Field Short text ExplanationPOSEX Item Number Item number of the current document. It is used for

the unique identification of the item. Normally the itemnumber is copied from the customer order.

ACTION Action code that concerns the item. 001 item was added002 = item was changed003 = item was deleted

PSTYP Item Category See information on incoming order MATNR Material identification

The entry of the action code is decisive for processing the data for the order change. Therefore you must fill this field. If none of the three possible action codes(001, 002 or 003) is sent, the document will not be changed at item level.If you want to change or delete an item, the entry of the external item number (POSEX) is mandatory. It is used for the unique identification of the item that shouldbe changed.The same rules are valid for combining dimensions under items as are described for the incoming orders. That means that dimensions that should be newlycreated can be grouped in an already existing item if the partners at item level are identical (for partner function processing see the note for segment E1EDPA1).Changing a material number or dimension for an already existing item is not supported. If you want to change this data, you must flag the corresponding item orschedule line with a deletion indicator and then you have to create it once more. It is also not possible to add individual components to a bill of material that hasalready been exploded in a sales document.If the action code 003 is sent to delete a dimension, the corresponding entry is not physically deleted from the document table, but flagged with the reason forrejection 00. The schedule line remains in the document, but is not active. You cannot reset this deletion flag via IDoc. If you want to reactivate a schedule line,you can only do so using the dialog transactions for changing an order.Changes in an already rejected dimension result in the error message /AFS/IDOC 019 in the inbound processing. Before you further process the IDoc you mustmanually reset the reason for rejection for the corresponding dimension.

!--a11y-->

1.4.2.2 Document Item: Multi-Store Order (Segment E1J3AIO) Mandatory segment: NOSuperior segment: E1J3P01

Field ExplanationJ_3APARVW Partner functionJ_3ASTORE MSO storesJ_3ADICE Customer distribution centerJ_3AWMENG Schedule line quantityJ_3ABMENG Delivered quantity in sales unitJ_3ADEPM DepartmentJ_3ASTCU Customer store / distribution center number


Page 30 of 49

J_3ASTCU Customer store / distribution center numberJ_3ABSTNK Order number of customerJ_3AILNNR 70 Character fieldJ_3AUPDKZ Update Indicator

This segment is not supported during the order change.

!--a11y-->

1.4.2.3 Document Item: VAS Ticketing/Labeling (SegmentE1J3AIT) Mandatory segment: NOSuperior segment: E1J3P01

Field ExplanationJ_3ASTORE MSO storesJ_3ATLTYP VAS Ticketing/label typeJ_3ATLMAT VAS Ticketing/labeling materialJ_3ACHARC VAS charge codeJ_3AFIELD1 VAS User-Defined Field 1J_3AFIELD2 VAS User-Defined Field 2J_3AFIELD3 VAS User-Defined Field 3J_3AVASPQ QuantityJ_3AUPDKZ Update IndicatorJ_3AVASPO VAS generated sub-item numberJ_3AVASETE VAS Generated Sub-Schedule Line Number


!--a11y-->

1.4.2.4 Document Item: VAS Ticketing/Labeling Text (SegmentE1J3AIX) Mandatory segment: NOSuperior segment: E1J3AIT

Field ExplanationJ_3ATLTXT Additional text for ticketing/labelingJ_3ATLORD Order levelJ_3ATLITEM Item levelJ_3ATLSIZE Dimension levelJ_3AUPDKZ Update Indicator


!--a11y-->

1.4.2.5 Document Item: VAS Packing (Segment E1J3AIP) PUBLIC 2014 SAP AG or an SAP affiliate company. All rights reserved.

Page 31 of 49

Mandatory segment: NOSuperior segment: E1J3AP01

Field ExplanationJ_3ASTORE MSO storesJ_3APTYP VAS packing typeJ_3APMAT VAS packing materialJ_3ACHARC VAS charge codeJ_3AINCREM VAS Packing IncrementJ_3AMIXIND VAS Packing Mix IndicatorJ_3AFIELD1 VAS User-Defined Field 1J_3AFIELD2 VAS User-Defined Field 2J_3AFIELD3 VAS User-Defined Field 3J_3AVASPQ QuantityJ_3AUPDKZ Update IndicatorJ_3AVASPO VAS generated sub-item numberJ_3AVASETE VAS Generated Sub-Schedule Line Number


!--a11y-->

1.4.2.6 Document Item: VAS Special Services (SegmentE1J3AIS) Mandatory segment: NOSuperior segment: E1J3P01

Field ExplanationJ_3ASTORE MSO storesJ_3ASSTYP VAS Special Services: CategoryJ_3ASSMAT VAS Special Services: MaterialJ_3ACHARC VAS charge codeJ_3AFIELD1 VAS User-Defined Field 1J_3AFIELD2 VAS User-Defined Field 2J_3AFIELD3 VAS User-Defined Field 3J_3AVASPQ QuantityJ_3AUPDKZ Update IndicatorJ_3AVASPO VAS generated sub-item numberJ_3AVASETE VAS Generated Sub-Schedule Line Number


!--a11y-->

1.4.2.7 Document Item: Partner Information (SegmentE1EDPA1) Mandatory segment: NOSuperior segment: E1J3P01


Page 32 of 49

Field Short text ExplanationPARVW Partner function (such as sold-to party, ship-to

party,...)Internal (2-character) code for the partner function(such as AG, WE)


recipient at the sold-to party. Using this field aconversion of external partner numbers into internalpartner numbers is also possible.

NAME1 Name 1 The data sent in these fields serves to transferpossibly different address information to the partner.NAME2 Name 2

KNREF Customized description of the business partner

(plant, warehouse)ILNNR 70 Character fieldPFORT Location of the P.O. BoxSPRAS_ISO Language according to ISO code 639TITLE Form of address

In order changes per IDoc, the partner functions AG, RE, RG, and SB cannot be changed (this is also valid for the addition of new itemsand/or dimensions. However, possible partners must be transferred at item level in this segment when you change an item because theyare considered an additional identification criterion of an item.

!--a11y-->

1.4.2.8 Document Item: Texts (Segment E1EDPT2) Mandatory segment: NOSuperior segment: E1EDPT1

Field Short text ExplanationTDLINE Text line Text line for the Text ID used under E1EDPT1. The



To change already existing texts, please note that all of the texts lines must always be transferred. It is not possible to only change individuallines of a text. If the text segments are sent to an already existing Text ID, a text that possibly already exists will be overwritten.

!--a11y-->


Field Short text ExplanationQUALF Organization indicator Describes the use of the data sent in field ORGID


ORGID Organization Indicator See field QUALF.


006 Division


Page 33 of 49

007 Distribution Channel008 Sales Organization010 Sales Group012 Order Type016 Sales Office019 Purchase Order Type (SD)J01 Department

Please read the sections on the incoming order.Sales area data and order type do not necessarily need to be sent in the order change IDoc. Rather, this data is transferred from the existing document after thedetermination of the order number.

!--a11y-->

1.4.2.10 Document Header: Partner Information (SegmentE1EDKA1) Mandatory segment: NO

Field ExplanationPARVW Partner function (such as sold-to party, ship-to party,...)PARTN Partner numberLIFNR Vendor number at the customerNAME1 Name 1NAME2 Name 2 Additional fields for partner information. For detailed information see IDoc

documentation on transaction WE60.KNREF Customized description of the business partner (plant, warehouse)ILNNR 70 Character fieldPFORT Location of the P.O. BoxSPRAS_ISO Language according to ISO code 639TITLE Form of address

Changing the partner at header level is not supported in order changes.

!--a11y-->

1.5.2.7 Document Header: Reference Data (SegmentE1EDK02) Mandatory segment: NO


number.BELNR Document number Document numberPOSNR Item Number No processingDATUM Date No processingUZEIT Time No processing

The following indicators for reference documents are processed:

001 Order number of customer002 Order number of vendor


Page 34 of 49

This segment is extremely important for the processing of the order change. The sales document to be changed in the system is identified via the entry ofreference document numbers. There are two possibilities:

Identification via the customer purchase order numberThis option requires that the customer purchase order number exists once in the system under the respective partner number of the sold-to party. Acustomer order number that exists more than once leads to error message /AFS/IDOC 006 in the inbound processing. An invalid customer ordernumber leads to error message VG151.

Identification via the order numberAs an alternative to the customer order number, the order number stored in the system can also be used for the identification of the document. If thisorder number cannot be determined, you will see the error message /AFS/IDOC 014.

!--a11y-->

1.4.2.12 Document Header: Payment Cards (SegmentE1EDK36) Mandatory segment: NO

Field ExplanationCCINS Card typeCCINS_BEZEI DescriptionCCNUM Card numberEXDATBI DateCCNAME Name of cardholderFAKWR Maximum amount

!--a11y-->

1.4.2.13 Document Header: Texts (Segments E1EDKT2) Mandatory segment: NOSuperior segment: E1EDKT1

Field Short text ExplanationTDLINE Text line Text line for the Text ID used under E1EDKT1. The



To change already existing texts, please note that all of the texts lines must always be transferred. It is not possible to only changeindividual lines of a text. If the text segments are sent to an already existing Text ID, a text that possibly already exists will be overwritten.

!--a11y-->

1.4.2.14 Document Header: MSO Header (Segment E1J3AHO) Mandatory segment: NO

Field ExplanationJ_3AMSOFLG Multi-store order indicator



Page 35 of 49

!--a11y-->

1.4.2.15 User Exits in the Incoming Order Change A series of customer enhancements are available in the incoming order change via the IDoc interface. To activate the customer enhancement, first create aproject. The customer enhancements of the inbound processing are summarized in the SAP enhancement J_3AEDS0.

!--a11y-->

1.5 Order Confirmation All the dimensions of an AFS material (= schedule lines of the sales document) are considered items in the outbound processing of the order confirmation. Thismeans that for each dimension there is one item segment E1J3P01 with corresponding subsegments.

!--a11y-->

1.5.1 General Data for the Order Confirmation (SegmentE1J3P01) Field Short text ExplanationPOSEX Item Number Item number from a customer order.ACTION Action code that concerns the item. 000 - item unchanged

001 - item changed003 - item deleted

PSTYP Item Category One-digit numerical indicator for the item category.The indicator is converted into the sales itemcategory depending on the order type, using thetable EDPST.

KZABS Indicator for the order acknowledgment requirement N/AMENGE Quantity Ordered quantity of the item.

For AFS materials with dimensions, the orderedquantity here is per dimension.

MENEE Unit of Measure ISO code of the unit of measure for the order quantityBMNG2 Quantity in Price Unit of Measure N/APMENE Price Unit of Measure ISO code of the price unit of measureABFTZ Agreed Cumulative Quantity N/AVPREI Price (net) Price per price unit. For AFS materials with

dimensions, the price here is per dimension.PEINH Price Unit Price UnitNETWR Value of Item (net) Net value. For AFS materials with dimensions, the

value here is per dimension.ANETW Absolute Net Value of the Item N/ASKFBP Discountable amount N/ANTGEW Net Weight - is cop