ECR Austria EANCOM 2002 Delivery Notes
TransdatiX.Convert ECR Austria EANCOM 2002 Delivery NotesVersion 2.0.0 from 2007-01-26
ContentGeneralWith this converter delivery note data in EANCOM 2002 format according to ECR Austria specification can be converted to XML or CSV. How to start the ConverterTo use this TransdatiX.Convert you first have to export your outbound data to CSV- or XML-file(s). All you need to prepare your data for this converter can be found here (this document is currently only available in german).Then you have various possibilities to start the TransdatiX.Convert, e.g. by defining a process, in which you also include a TransdatiX.Comm to automate conversion and transmission. More information on the TransdatiX.Configurator as well as further automation technologies can be found here (this document is currently only available in german). HintsThis converter handles bot hierarchical delivery notes (all articles are allocated distinct to a package) and sequential delivery notes (without allocation to packages). For a detailed description including examples see the document Possibilities for hierarchical packing sequences within electronic delivery notes. The output created by the converter either conforms to example a for sequential delivery notes or example f for hierarchical delivery notes. A bill of material is an article that contains other articles (e.g. a display). The assortment components are indicated as sub-items. The main article differs not from any other normal article. For the included sub-positions SubPosition is set to 1 and SubPositionReferenceNumber refers to the position number Number of the superordinate article. Structure of data - OverviewThe following listing shows the formal data structure accepted by the converter. Bold descripitions means, that an element is required, excepting a term is quoted explicit within the description of the element.
Message MessageID - Key field Format: alphanumeric Hint: Internal unique identification
Transmission Section MessageID - Key field Format: alphanumeric Hint: Reference to MessageID in data group Message SenderId - Required field: yes Format: alphanumeric with up to 13 character(s) Hint: Sender Mailbox-ID of Message Sender RecipientId - Required field: yes Format: alphanumeric with up to 13 character(s) Hint: Recipient Mailbox-ID of Message Recipient MessageType - Required field: no Format: alphanumeric with up to 6 character(s) Hint: EDIFACT Message Type Identifier If a transmission includes only Messages of the same type the message type can be specified within the envelope as an information for the recipient. TransmissionId - Required field: no Format: alphanumeric with up to 14 character(s) Hint: Message Reference Number Unique Reference for the transmission generated by the sender. TestFlag - Required field: no Possible values:
Only used during testing period
Delivery Note Heading Section Includes the Heading Data MessageID - Key field Format: alphanumeric Hint: Reference to MessageID in data group Message DeliveryNoteID - Key field Format: alphanumeric Hint: Internal unique identification Number - Required field: yes Format: alphanumeric with up to 35 character(s) Hint: Delivery Note Number Delivery note number assigned by the document sender If not identical with the paper based delivery note, the number printed on the paper based delivery note is specified in DeliveryNoteNumber. Date - Required field: yes Format: date Hint: Delivery note date DeliveryDate - Required field: no Format: date Hint: Delivery date DeliveryEarliestDate - Required field: no Format: date Hint: Delivery date eraliest DeliveryLastDate - Required field: no Format: date Hint: Delivery date latest OrderNumber - Required field: yes Format: alphanumeric with up to 16 character(s) Hint: Order number OrderDate - Required field: no Format: date Hint: Order date OrderNumberSupplier - Required field: no Format: alphanumeric with up to 16 character(s) Hint: Supplier's order number DeliveryNoteNumber - Required field: no Format: alphanumeric with up to 35 character(s) Hint: Number of the paper base delivery note BuyerGLN - Required field: yes Format: alphanumeric with up to 13 character(s) Hint: The Buyer's GLN SupplierGLN - Required field: yes Format: alphanumeric with up to 13 character(s) Hint: The Supplier's GLN DeliveryGLN - Required field: no Format: alphanumeric with up to 13 character(s) Hint: GLN of party where goods are deliverd UltimateCustomerGLN - Required field: no Format: alphanumeric with up to 13 character(s) Hint: GLN of the Ultimate Customer OrderedByGLN - Required field: no Format: alphanumeric with up to 13 character(s) Hint: GLN of the party who issued an order InvoiceeGLN - Required field: no Format: alphanumeric with up to 13 character(s) Hint: GLN of the party who issued an order TransportMode - Required field: no Possible values:
TransportMedium - Required field: no Possible values:
Package Unit Section MessageID - Key field Format: alphanumeric Hint: Reference to MessageID in data group Message DeliveryNoteID - Key field Format: alphanumeric Hint: Reference to DeliveryNoteID in data group DeliveryNote PackID - Key field Format: alphanumeric Hint: Internal unique identification Quantity - Required field: no Format: integer Hint: Number of packages Type - Required field: no Possible values:
Volume - Required field: no Format: decimal Hint: Volume of the package in cubic meter GrossWeight - Required field: no Format: decimal Hint: Total gross weight of the package in kg Length - Required field: no Format: decimal Hint: Length of the package in mm Width - Required field: no Format: decimal Hint: Width of the package in mm Height - Required field: no Format: decimal Hint: Height of the package in mm Handling - Required field: no Possible values:
SSCC - Required field: no Format: alphanumeric with up to 35 character(s) Hint: SSCC of the package Group - Required field: no Format: alphanumeric Hint: Package Group
Delivery Note Detail Section MessageID - Key field Format: alphanumeric Hint: Reference to MessageID in data group Message DeliveryNoteID - Key field Format: alphanumeric Hint: Reference to DeliveryNoteID in data group DeliveryNote PackID - Key field Format: alphanumeric Hint: Reference to PackID in data group Pack Number - Required field: no Format: integer Hint: Position number SubPosition - Required field: no Possible values:
Indicates, that this position is a sub-item. See bills of materials for more informations. SubPositionReferenceNumber - Required field: no Format: integer Hint: Reference position Reference to Number of the superordinate position this sub-position relates to. See bills of materials for more informations. EAN - Required field: yes Format: alphanumeric with up to 14 character(s) Hint: EAN of article Quantity - Required field: yes Format: decimal Hint: Delivered quantity in order units DeliveryQuantity - Required field: no Format: decimal Hint: Delivered quantity in invoicing units DeliveryUnit - Required field: no Possible values:
InvoiceQuantity - Required field: no Format: decimal Hint: Invoiced quantity in invoicing units For weight variable goods beyond the delivered quantity in invoicing units also the quantity relevant for the invoice can be specified. The unit is equal to DeliveryUnit ConsumerUnitsQuantity - Required field: no Format: decimal Hint: Number of consumer units in one unit GrossAmount - Required field: no Format: decimal Hint: Total position gross amount BestBeforeDate - Required field: no Format: date Hint: Best before date ExpiryDate - Required field: no Format: date Hint: Expiry date BatchNumber - Required field: no Format: alphanumeric with up to 35 character(s) Hint: Batch number Legal notesAll information contained in this document is provided without any whatsoever guarantees. TransdatiX expressly refuses all liability claims, explicit or implicit, including claims regarding suitability for selling or specific purpose. In no case TransdatiX or one of its suppliers can be held responsible for any damages, occuring direct or indirect, quite accidentally or as a consequential damage. Especially business losses, data losses or special damages are excluded explicitly from liability, even if TransdatiX or its suppliers pointed to the possibility of such damages. In any case liability claims are rejected to the legal highest possible dimension. © 2002 - 2007 TransdatiX Software
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||