6
document.xlsx Page 1 of 6 Generic 850 Inbound Orders Mapping Document MAPPING Segment Field Description Literal ValueValue Description X12 X12 Static Qualifi X12 Description Extras Notes EDI_DC40 TABNAM Name of table structure MANDT Client DOCNUM IDoc number DOCREL SAP Release for IDoc 40B This Value should be the Version of SAP R/3 you have installed STATUS Status of IDoc DIRECT Direction "2" Inbound OUTMOD Output mode EXPRSS Overriding in inbound processin TEST Test flag IDOCTYP Name of basic type "ORDERS03" CIMTYP Name of extension type MESTYP Logical message type "ORDERS" MESCOD Logical message code MESFCT Logical message function STD EDI standard, flag STDVRS EDI standard, version and relea SDTEMES EDI message type SNDPOR Sender port (SAP System, extern The Value in this field is not validated by the system SNDPRT Partner type of sender "KU" Customer "KU" Defines that the IDoc transaction is coming from a customer SNDPFC Partner function of sender "AG" Sold-to Party SNDPRN Partner number of sender This value must be the SAP Partner number. ( ie. Sold-to Party) SNDSAD Sender address (SADR) SNDLAD Logical address of sender RCVPOR Receiver port (SAP System, exte SAPXXX RCVPRT Partner type of recipient "LI" VENDOR RCVPFC Partner function of recipient "VN" RCVPRN Partner number of recipient RCVSAD Recipient address (SADR) RCVLAD Logical address of recipient CREDAT Created on CRETIM Time created REFINT Reference to transfer (EDI inte REFGRP Reference to message group (EDI REFMES Reference to message (EDI messa ARCKEY Key for (external) message arch SERIAL Serialization field E1EDK01 ACTION Action code for the whole EDI message KZABS Flag: order acknowledgment required "000" No Action is Required CURCY Currency HWAER EDI local currency WKURS Exchange rate ZTERM Terms of payment key KUNDEUINR VAT registration number EIGENUINR VAT registration number BSART Document type BELNR IDOC document number NTGEW Net weight BRGEW Net weight GEWEI Weight unit FKART_RL Invoice list type ABLAD Unloading point BSTZD Purchase order number supplement VSART Shipping type VSART_BEZ Description of the shipping type RECIPNT_NO Number of recipient (for control via the ALE model) KZAZU Order combination indicator AUTLF Complete delivery defined for each sales order? AUGRU Order reason (reason for the business transaction) AUGRU_BEZ Description ABRVW Usage indicator ABRVW_BEZ Description FKTYP Billing category LIFSK Delivery block (document header) LIFSK_BEZ Description EMPST Receiving point E1EDK14 Organizational Data Header QUALF IDOC qualifer organization ORGID IDOC organization E1EDK03 Idoc Document Header Date Segment IDDAT Qualifier for IDOC date segment "002" Requested Delivery Date DTM01 "002" DATUM IDOC: Date DTM02 CCYYMMDD UZEIT IDOC: Time E1EDK04 Document Header Taxes Not commonly used for inbound 850 to Orders03 transactions MWSKZ VAT indicator MSATZ VAT rate MWSBT Value added tax amount TXJCD Jurisdiction for tax calculation tax jurisdiction code This is the Idoc Header Segment. A new Idoc is defined by a new EDI_DC40 segment Because and Idoc is used for both inbound and oubound functional purposes this field defines the direction of the If this flag is activiated the system will not allow for the Idoc to posted to the application. This flag should only be activated when checking Idoc Syntax This Field should contain the Names of the IDoc type that is being used. Ie. ORDERS03 This field should contatin the name of the Message type of the IDoc being used. Ie. ORDERS These values are used in the partner profile to define what process code is to be used on the inbound IDoc "AG" Defines that the Idoc is coming from the Sold-to Party. This value must be the same partner function value defined in the partner profile for this customer, SAP SOLD-TO NUMBER This field must contain the value "SAPXXX" where XXX is your three character R/3 system ID This segment is used to define the overall action taken with the IDoc. The only commonly used field in this segment if the "000" is the value entered for new inbound orders. This value states that no particular action is required In this segment allows one to define values such as the SAP sales order type, Distribution channel, sales office etc. It is not commonly used as this information can be defined from within SAP eliminting the need to map this data within the This segement is used to enter header dates into the document. Dates such as the requested delivery date, and pricing date are commonly used. There can be multiple occurances of this field.

Generic 850 Mapping Document

  • Upload
    ag-sri

  • View
    151

  • Download
    16

Embed Size (px)

DESCRIPTION

Generic 850 Mapping Document.xlsx

Citation preview

Ord3Generic 850 Inbound Orders Mapping DocumentMAPPINGSegmentFieldDescriptionLiteral ValueValue DescriptionX12X12 Static QualifierX12 DescriptionExtrasNotesEDI_DC40This is the Idoc Header Segment. A new Idoc is defined by a new EDI_DC40 segmentTABNAMName of table structure MANDTClient DOCNUMIDoc number DOCRELSAP Release for IDoc 40BThis Value should be the Version of SAP R/3 you have installedSTATUSStatus of IDoc DIRECTDirection "2"InboundBecause and Idoc is used for both inbound and oubound functional purposes this field defines the direction of the particular documentOUTMODOutput mode EXPRSSOverriding in inbound processinTESTTest flag If this flag is activiated the system will not allow for the Idoc to posted to the application. This flag should only be activated when checking Idoc SyntaxIDOCTYPName of basic type "ORDERS03"This Field should contain the Names of the IDoc type that is being used. Ie. ORDERS03CIMTYPName of extension type MESTYPLogical message type "ORDERS"This field should contatin the name of the Message type of the IDoc being used. Ie. ORDERSMESCODLogical message code MESFCTLogical message function STDEDI standard, flag STDVRSEDI standard, version and releaSDTEMESEDI message type SNDPORSender port (SAP System, externThe Value in this field is not validated by the systemSNDPRTPartner type of sender "KU"Customer "KU" Defines that the IDoc transaction is coming from a customerThese values are used in the partner profile to define what process code is to be used on the inbound IDocSNDPFCPartner function of sender "AG"Sold-to Party"AG" Defines that the Idoc is coming from the Sold-to Party. This value must be the same partner function value defined in the partner profile for this customer,SNDPRNPartner number of sender SAP SOLD-TO NUMBERThis value must be the SAP Partner number. ( ie. Sold-to Party)SNDSADSender address (SADR) SNDLADLogical address of sender RCVPORReceiver port (SAP System, exteSAPXXXThis field must contain the value "SAPXXX" where XXX is your three character R/3 system IDRCVPRTPartner type of recipient "LI"VENDORRCVPFCPartner function of recipient "VN"RCVPRNPartner number of recipient RCVSADRecipient address (SADR) RCVLADLogical address of recipient CREDATCreated on CRETIMTime created REFINTReference to transfer (EDI inteREFGRPReference to message group (EDIREFMESReference to message (EDI messaARCKEYKey for (external) message archSERIALSerialization field

E1EDK01This segment is used to define the overall action taken with the IDoc. The only commonly used field in this segment if the ACTION field.

ACTIONAction code for the whole EDI message"000" is the value entered for new inbound orders. This value states that no particular action is requiredKZABSFlag: order acknowledgment required"000"No Action is RequiredCURCYCurrencyHWAEREDI local currencyWKURSExchange rateZTERMTerms of payment keyKUNDEUINRVAT registration numberEIGENUINRVAT registration numberBSARTDocument typeBELNRIDOC document numberNTGEWNet weightBRGEWNet weightGEWEIWeight unitFKART_RLInvoice list typeABLADUnloading pointBSTZDPurchase order number supplementVSARTShipping typeVSART_BEZDescription of the shipping typeRECIPNT_NONumber of recipient (for control via the ALE model)KZAZUOrder combination indicatorAUTLFComplete delivery defined for each sales order?AUGRUOrder reason (reason for the business transaction)AUGRU_BEZDescriptionABRVWUsage indicatorABRVW_BEZDescriptionFKTYPBilling categoryLIFSKDelivery block (document header)LIFSK_BEZDescriptionEMPSTReceiving point

E1EDK14Organizational Data HeaderIn this segment allows one to define values such as the SAP sales order type, Distribution channel, sales office etc. It is not commonly used as this information can be defined from within SAP eliminting the need to map this data within the translator over and over again.

QUALFIDOC qualifer organizationORGIDIDOC organization

E1EDK03Idoc Document Header Date SegmentThis segement is used to enter header dates into the document. Dates such as the requested delivery date, and pricing date are commonly used. There can be multiple occurances of this field.

IDDATQualifier for IDOC date segment"002"Requested Delivery DateDTM01"002"DATUMIDOC: DateDTM02CCYYMMDDUZEITIDOC: Time

E1EDK04Document Header TaxesNot commonly used for inbound 850 to Orders03 transactions

MWSKZVAT indicatorMSATZVAT rateMWSBTValue added tax amountTXJCDJurisdiction for tax calculation tax jurisdiction code

E1EDK05Document header ConditionsNot commonly used for inbound 850 to Orders03 transactions

ALCKZSurcharge or discount indicatorKSCHLCondition type (coded)KOTXTCondition textBETRGFixed surcharge/discount on total grossKPERCCondition percentage rateKRATECondition record per unitUPRBSPrice unitMEAUNUnit of measurementKOBTRIDoc condition end amountMWSKZVAT indicatorMSATZVAT rateKOEINCurrency

E1EDKA1This segment provides information about the customer. It allows for the various partner functions used in the sales order to be defined via the incoming IDoc. For example; this segment defined who the sold to Party of the Order is. For orders with multiple partner functions there will also be multiple KA1 sengments.

PARVWPartner function (e.g. soldto party, shipto party, ...)"AG"Sold-to PartyOften when N101 = BTThis field defined the partner funcion of thie information that is to follow.PARTNPartner numberIn this field the SAP partner number is to be enteredLIFNRVendor number at customer locationN104 where N101 = "VN"This field contains the customers number for the partner function. Ie. If the Partner function was ship-to this fied would contain the custoer's ship-to number. If the Parner function was refering to the Sold-to this field would contain the customer's vendor number for you, the supplier.NAME1Name 1N102If a value is entered for any one of these fields in the Idoc, the information contained in the customer master will not be put into the sales order document. Insead the information entered here will be what shows up on the sales order. It is therefore not always required to enter anything in these fields because the sales order automatically takes the information stored in the customer master.NAME2Name 2N201NAME3Name 3N202NAME4Name 4STRASStreet and house number 1N301STRS2Street and house number 2N302PFACHPO boxORT01CityN401COUNCCounty codeN404PSTLZPostal codeN403PSTL2P.O. Box postal codeLAND1Country keyABLADUnloading pointPERNRContact person's personnel numberPARNRContact person's number (not personnel number)TELF11st telephone number of contact personTELF22nd telephone number of contact personTELBXTelebox numberTELFXFax numberTELTXTeletex numberTELX1Telex numberSPRASLanguage keyANREDFormOfAddrORT02DistrictHAUSNHouse numberSTOCKFloorREGIORegionN402PARGEPartner's genderISOALCountry ISO codeISONUCountry ISO codeFCODECompany key (France)IHREZYour reference (Partner)BNAMEIDoc user namePAORGIDOC organization codeORGTXIDoc organization code textPAGRUIDoc group codeKNREFCustomer description of partner (plant, storage location)ILNNRCharacter field, length 70PFORTPO box citySPRAS_ISOLanguage according to ISO 639

E1EDKA3This segment can be used to define the customer's industry specific identification number. (ie duns number). Not commonly used for inbound 850 to Orders03 transactions.

QUALPIDOC Partner identification (e.g.Dun&Bradstreet number)STDPNCharacter field, length 70

E1EDKA1This segment provides information about the customer. It allows for the various partner functions used in the sales order to be defined via the incoming IDoc. For example; this segment defined who the sold to Party of the Order is. For orders with multiple partner functions there will also be multiple KA1 sengments.

PARVWPartner function (e.g. soldto party, shipto party, ...)"WE"Ship-to PartyOften when N101 = STThis field defined the partner funcion of thie information that is to follow.PARTNPartner numberIn this field the SAP Ship-to number (if known can be entered)LIFNRVendor number at customer locationThis field contains the customer's Ship-to number. If this is the only value known with refrence maintain the ship-to conversion table ( tcode: VOED in 3.x-4.0, VOE3 in 4.5)NAME1Name 1N102If a value is entered for any one of these fields in the Idoc, the information contained in the customer master will not be put into the sales order document. Insead the information entered here will be what shows up on the sales order. It is therefore not always required to enter anything in these fields because the sales order automatically takes the information stored in the customer master.NAME2Name 2N201NAME3Name 3N202NAME4Name 4STRASStreet and house number 1N301STRS2Street and house number 2N302PFACHPO boxORT01CityN401COUNCCounty codeN404PSTLZPostal codeN403PSTL2P.O. Box postal codeLAND1Country keyABLADUnloading pointPERNRContact person's personnel numberPARNRContact person's number (not personnel number)TELF11st telephone number of contact personTELF22nd telephone number of contact personTELBXTelebox numberTELFXFax numberTELTXTeletex numberTELX1Telex numberSPRASLanguage keyANREDFormOfAddrORT02DistrictHAUSNHouse numberSTOCKFloorREGIORegionN402PARGEPartner's genderISOALCountry ISO codeISONUCountry ISO codeFCODECompany key (France)IHREZYour reference (Partner)BNAMEIDoc user namePAORGIDOC organization codeORGTXIDoc organization code textPAGRUIDoc group codeKNREFCustomer description of partner (plant, storage location)ILNNRCharacter field, length 70PFORTPO box citySPRAS_ISOLanguage according to ISO 639

E1EDKA3This segment can be used to define the customer's industry specific identification number. (ie duns number). Not commonly used for inbound 850 to Orders03 transactions.

QUALPIDOC Partner identification (e.g.Dun&Bradstreet number)STDPNCharacter field, length 70

E1EDK02This segment refrences common header information such as the customer's purchas order number.

QUALFIDOC qualifier reference document"001"Purchase Order NumberBELNRIDOC document numberBEG03POSNRItem numberDATUMIDOC: DateBEG05UZEITIDOC: Time

E1EDK17This segment defines the terms of delivery of the sales order. It is not commonly used as this information is defaulted from the customer master if there are no values present in the IDoc

QUALFIDOC qualifier: Terms of deliveryLKONDIDOC delivery condition codeLKTEXTIDOC delivery condition text

E1EDK18This field can be used to define the payment terms of the sales document. It is not commonly used as the information maintained within the customer master is defaulted into the sales document should this segment contain no values.

QUALFIDOC qualifier: Terms of paymentTAGEIDOC Number of daysPRZNTIDOC percentage for terms of paymentZTERM_TXTText line

E1EDKT1This segment is used to define the text ID in which the value enterd in the E1EDKT2 segment will go.

TDIDText ID"001"The Sales order text ID is entered in this field. TSSPRASLanguage keyTSSPRAS_ISOLanguage according to ISO 639

E1EDKT2This segment is used of each line of text coresponding to it's above E1EDKT1 segment. There must be one E1EDKT2 segment for each line of text.

TDLINEMSG01The actual line of text desired is entered in this field. TDFORMAT

E1EDP01This segment is used to provide informaiton pertaining to each line item. Note: For each line item there must be one corresponding E1EDP01 Segment.

POSEXItem numberPO101This field contains the actual customer's Line item number from their sales order.ACTIONAction code for the itemPSTYPItem categoryKZABSFlag: order acknowledgment requiredMENGEQuantityPO102This field defined the desired quantity of the item.MENEEUnit of measurePO103Enter the ISO unit of measure configured in the R/3 System in which the customer is ordering. Note: very often there must be a conversion done within the translator to convet the customer's unit of measure code to a valid SAP unit of measure code.BMNG2Quantity in price unitPMENEPrice unit of measureABFTZAgreed cumulative quantityVPREIPrice (net)PO104The Customer's expected price per unit can be entered in thi field. Note: this value will be entered in the EDI1 pricing condition in the Sales document's pricing procedure. The value is commonly set up as statistical onlyPEINHPrice unitNETWRItem value (net)ANETWAbsolute net value of itemSKFBPAmount qualifying for cash discountNTGEWNet weightGEWEIWeight unitEINKZFlag: More than one schedule line for the itemCURCYCurrencyPREISGross priceMATKLIDOC material classUEPOSHigherlevel item in BOM structuresGRKORDelivery group (items delivered together)EVERSShipping instructionsBPUMNDenominator for conv. of order price unit into order unitBPUMZNumerator for conversion of order price unit into order unitABGRUReason for rejection of quotations and sales ordersABGRTDescriptionANTLFMaximum number of partial deliveries allowed per itemFIXMGDelivery date and quantity fixedKZAZUOrder combination indicatorBRGEWTotal weightPSTYVSales document item categoryEMPSTReceiving point

E1EDP02This segment allows for organizational values to be attatched to the line item. For instance if a customer sends in a refrence to a customer quoation number secific to the line item the value will be enterd in this segment. This segment is not commonly used for the majority of 850 to orders03 sales order mappings

QUALFIDOC qualifier reference documentBELNRIDOC document numberZEILEItem numberDATUMIDOC: DateUZEITIDOC: TimeBSARKIDOC organizationIHREZYour reference (Partner)

E1CUREFNot commonly used for inbound 850 to Orders03 transactions

POSEXCharacter field of length 6CONFIG_IDCharacter field of length 6INST_IDCharacter field, 8 characters long

E1EDP03This segment is used to define specific dates to the line item should they be different than those assigned at the header level (E1EDK03 segment). For example: if a specific line item had a delivery date different from the reast of the line items in the document the delivery date would be enterd in this field.

IDDATqualifier for IDOC Date segmentDATUMDateUZEITTime

E1EDP04Not commonly used for inbound 850 to Orders03 transactions

MWSKZVAT indicatorMSATZVAT rateMWSBTValue added tax amountTXJCDJurisdiction for tax calculation tax Jurisdiction code

E1EDP05Not commonly used for inbound 850 to Orders03 transactions

ALCKZSurcharge or discount indicatorKSCHLCondition type (coded)KOTXTCondition TextBETRGFixed Surcharge/discount on total grossKPERCCondition percentage rateKRATECondition record per unitUPRBSPrice unitMEAUNunit of measurementKOBTRIDOC Condition end amountMENGEPrice scale quantity (SPEC2000)PREISPrice by unit of measure (SPEC2000)MWSKZVAT indicatorMSATZVAT rateKOEINCurrencyCURTPtype of Currency and evaluation

E1EDP20Not commonly used for inbound 850 to Orders03 transactions

WMENGScheduled quantityAMENGPrevious Scheduled quantityEDATUIDOC: DateEZEITIDOC: TimeEDATU_OLDIDOC: DateEZEIT_OLDIDOC: Time

E1EDPA1This segment allows for partner information to be defined at the line item level should it be different from the header information.

PARVWPartner function (e.g. soldto party, shipto party, ...)PARTNPartner numberLIFNRVendor number at customer locationNAME1Name 1NAME2Name 2NAME3Name 3NAME4Name 4STRASStreet and house number 1STRS2Street and house number 2PFACHPO boxORT01CityCOUNCCounty codePSTLZPostal codePSTL2P.O. box Postal codeLAND1Country keyABLADUnloading pointPERNRContact person's personnel numberPARNRContact person's number (not personnel number)TELF11st telephone number of contact personTELF22nd telephone number of contact personTELBXTelebox numberTELFXFax numberTELTXTeletex numberTELX1Telex numberSPRASLanguage keyANREDFormOfAddrORT02DistrictHAUSNhouse numberSTOCKFloorREGIORegionPARGEPartner's genderISOALCountry ISO codeISONUCountry ISO codeFCODECompany key (France)IHREZYour reference (Partner)BNAMEIDOC user NamePAORGIDOC organization codeORGTXIDOC organization code TextPAGRUIDOC group codeKNREFcustomer description of Partner (plant, storage location)ILNNRCharacter field, length 70PFORTPO box CitySPRAS_ISOLanguage according to ISO 639

E1EDPA3This segment can be used to define the customer's industry specific identification number. (ie duns number) at the line item level. It is only used if the calue is different fro that defined at the header (E1EDK03) level. Not commonly used for inbound 850 to Orders03 transactions.

QUALPIDOC Partner identification (e.g.Dun&Bradstreet number)STDPNCharacter field, length 70

E1EDP19This segment is used to define the actual material number in question. One can use many different refrencing options to call upa specific material. The most commonly used ones are the Vendor Material number, Customer material number, and the UPC/EAN code. For each refrence to material number there must be a new occurance of the E1EDP19 segment.

QUALFIDOC object identification such as material no.,customer"001"Buyer's Material NumberEnter the Qualifying value in this field. If the segment contains the Customer Material number enter "001". The customer Material Info-record is referenced when a value is entered within this field.IDTNRIDOC material IDPO107Enter the appropriate material number for the qualifying value in the QUALF field.KTEXTIDOC short TextPID05MFRPNManufacturer part numberMFRNRManufacturer number

E1EDP19This segment is used to define the actual material number in question. One can use many different refrencing options to call upa specific material. The most commonly used ones are the Vendor Material number, Customer material number, and the UPC/EAN code. For each refrence to material number there must be a new occurance of the E1EDP19 segment.

QUALFIDOC object identification such as material no.,customer"002"Vendor's Material NuberEnter the Qualifying value in this field. If the segment contains the Customer Material number enter "001", if the segment contains the vendor material number enter "002" etc.IDTNRIDOC material IDPO111Enter the appropriate material number for the qualifying value in the QUALF field.KTEXTIDOC short TextMFRPNManufacturer part numberMFRNRManufacturer number

E1EDP19This segment is used to define the actual material number in question. One can use many different refrencing options to call upa specific material. The most commonly used ones are the Vendor Material number, Customer material number, and the UPC/EAN code. For each refrence to material number there must be a new occurance of the E1EDP19 segment.

QUALFIDOC object identification such as material no.,customer"003"UPC Code / EAN NumberEnter the Qualifying value in this field. If the segment contains the Customer Material number enter "001", if the segment contains the vendor material number enter "002" etc.IDTNRIDOC material IDPO109Enter the appropriate material number for the qualifying value in the QUALF field.KTEXTIDOC short TextMFRPNManufacturer part numberMFRNRManufacturer number

E1EDP17This segment defines the terms of delivery for the line item should they be different than those defined at the header level (E1EDP17 segment) or in the customer master. This segment is not commonly used.

QUALFIDOC qualifier: Terms of deliveryLKONDIDOC delivery Condition codeLKTEXTIDOC delivery Condition TextLPRIOdelivery priority

E1EDP18This segment is used to define the terms of payment specific to the line item should they be different than those defined at the header level.

QUALFIDOC qualifier: Terms of paymentTAGEIDOC number of daysPRZNTIDOC percentage for Terms of payment

E1EDPT1This segment allows for text the be attatched at the line item level. The test Ids must already be defined within the Sales and Distribution module.

TDIDText IDTSSPRASLanguage keyTSSPRAS_ISOLanguage according to ISO 639

E1EDPT2 IDoc: Doc.item textsThis segment contains the actual text for the text ID denoted in the E1EDPT1 segment before it. There must be one E1EDPT2 segment fot each corresponding line of text.

TDLINETDFORMAT

E1CUCFG

POSEXCharacter field of length 6CONFIG_IDCharacter field of length 6ROOT_IDCharacter field, 8 characters long

E1CUINS

INST_IDCharacter field, 8 characters longOBJ_TYPECharacter field length 10CLASS_TYPE3Byte fieldOBJ_KEYCommentOBJ_TXTCharacter field, length 70QUANTITYChar 15

E1CUPRT

PARENT_IDCharacter field, 8 characters longINST_IDCharacter field, 8 characters longPART_OF_NONothingOBJ_TYPECharacter field length 10CLASS_TYPE3Byte fieldOBJ_KEYComment

E1CUVAL

INST_IDCharacter field, 8 characters longCHARCCharacter field of length 40CHARC_TXTCharacter field, length 70VALUECharacter field of length 40VALUE_TXTCharacter field, length 70

E1EDL37

EXIDVExternal shipping unit IDTARAGTare weight of shipping unitGWEITWeight unit tareBRGEWTotal weight of shipping unitNTGEWLoading weight of shipping unitMAGEWAllowed weight of shipping unitGWEIMUnit of weightBTVOLTotal volume of shipping unitNTVOLLoading volume of shipping unitMAVOLAllowed volume for shipping unitVOLEMVolume unitTAVOLTare volume of shipping unitVOLETVolume unit tareVEGR2Shipping unit group 2 (freely definable)VEGR1Shipping unit group 1 (freely definable)VEGR3Shipping unit group 3 (freely definable)VHILMShipping materialVEGR4Shipping unit group 4 (freely definable)LAENGLengthVEGR5Shipping unit group 5 (freely definable)BREITWidthHOEHEHeightMEABMUnit of dimension for length/width/heightINHALTDescription of shipping unit contentVHARTShipping material typeMAGRVMaterial group: shipping materialsLADLGLgth of loading platform in lgth of LdPlat measurement unitsLADEHUnit of measure to measure the length of loading platformFARZTTravel timeFAREHUnit of driving timeENTFEDistance travelledEHENTUnit of distanceVELTPShipping unit categoryEXIDV2Alternative external identification of shipping unitLANDTCountry providing means of transportLANDFDriver's nationalityNAMEFDriver nameNAMBEPassenger's nameVHILM_KUCustomer shipping materialVEBEZDescription of shipping unitSMGKNSMG identification for material tag

E1EDL39

QUALFqualifier: Control (shipping unit)PARAMIDOC: Control parameters

E1EDL38

VEGR1_BEZDescription of shipping unit 1VEGR2_BEZDescription of shipping unit 2VEGR3_BEZDescription of shipping unit 3VEGR4_BEZDescription of shipping unit 4VEGR5_BEZDescription of shipping unit 5VHART_BEZdescription of shipping material typeMAGRV_BEZdescription of material grouping shipping materialVEBEZdescription of shipping unit

E1EDL44

VELINtype of shipping unit Item contentVBELNSD document numberPOSNRItem number of the SD documentEXIDVExternal shipping unit IDVEMNGdelivery Item quantity in the shipping unit ItemVEMEHunit of measure of delivery Item quantity in ship.elem.item

E1EDS01

SUMIDQualifier for totals segment for shipping notification"001"SUMMETotal value of sum segmentCTT01SUNITTotal value unit for totals segment in the shipping notif.WAERQCurrency

E1EDS01

SUMIDQualifier for totals segment for shipping notification"002"SUMMETotal value of sum segmentAMT02SUNITTotal value unit for totals segment in the shipping notif.WAERQCurrency

Page &P of &N

Sheet1