Amazon delivery notes
TransdatiX.Convert Amazon delivery notes
Version 2.0.2 of 2008-08-13
Content
General
Converts XML or CSV files to a EDIFACT D.96A DESADV file for Amazon.
How to start the Converter
To 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).
Structure of data - Overview
The 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.Element name | Description |
| Root | Root element |
| Message | Message |
| MessageID | Internal distinct code |
| Envelope | Nachricht |
| MessageID | Reference to MessageID in data group Message |
| SenderId | Sender identification |
| SenderIdType | Sender identification code qualifier |
| RecipientId | Recipient identification |
| RecipientIdType | Recipient identification code qualifier |
| TransmissionId | Interchange control reference |
| TestFlag | Test indicator |
| DeliveryNote | Delivery note head |
| MessageID | Reference to MessageID in data group Message |
| DeliveryNoteID | Internal distinct code |
| Type | Type of message |
| Status | Delivery note type |
| Function | Function |
| Number | Delivery note number |
| Date | Delivery note date |
| ShipmentDate | Despatch date/time |
| ArrivalDate | Estimated arrival date/time |
| BillOfLadingNumber | Bill of Lading number |
| CarrierReferenceNumber | Carrier's reference number |
| ReferenceDate | Date of Bill of Lading / Carrier reference no. |
| BuyerGLN | Buyer's GLN |
| BuyerName1 | Buyer's name (1st line) |
| BuyerName2 | Buyer's name (2nd line) |
| BuyerName3 | Buyer's name (3rd line) |
| BuyerStreet1 | Buyer's street (1st line) |
| BuyerStreet2 | Buyer's street (2nd line) |
| BuyerStreet3 | Buyer's street (3rd line) |
| BuyerCity | Buyer's city |
| BuyerZipCode | Buyer's zip code |
| BuyerCountryCode | Buyer's country |
| SupplierGLN | Supplier's GLN |
| SupplierName1 | Supplier's name (1st line) |
| SupplierName2 | Supplier's name (2nd line) |
| SupplierName3 | Supplier's name (3rd line) |
| SupplierStreet1 | Supplier's street (1st line) |
| SupplierStreet2 | Supplier's street (2nd line) |
| SupplierStreet3 | Supplier's street (3rd line) |
| SupplierCity | Supplier's city |
| SupplierZipCode | Supplier's zip code |
| SupplierCountryCode | Supplier's country |
| DeliveryGLN | Delivery's GLN |
| DeliveryName1 | Delivery's name (1st line) |
| DeliveryName2 | Delivery's name (2nd line) |
| DeliveryName3 | Delivery's name (3rd line) |
| DeliveryStreet1 | Delivery's street (1st line) |
| DeliveryStreet2 | Delivery's street (2nd line) |
| DeliveryStreet3 | Delivery's street (3rd line) |
| DeliveryCity | Delivery's city |
| DeliveryZipCode | Delivery's zip code |
| DeliveryCountryCode | Delivery's country |
| CarrierId | Carrier's identification |
| TransportMode | |
| TransportMedium | Transport mean |
| PalletQuantity | Number of ISO EURO pallets |
| Pack | Shipment's unit of transport (cartons) |
| MessageID | |
| DeliveryNoteID | |
| PackID | |
| BillOfLadingNumber | Bill of Lading number of a package |
| CarrierReferenceNumber | Carrier's reference number of a package |
| ReferenceDate | Date of Bill of Lading / Carrier reference no. of a package |
| GrossWeight | Total gross weight of carton in in kg |
| Length | Length of carton in cm |
| Width | Width of carton in cm |
| Height | Height of carton in cm |
| Handling | Handling instructions |
| SSCC | SSCC of package |
| Pos | Line item |
| MessageID | |
| DeliveryNoteID | |
| PackID | |
| Number | Line item number |
| ItemEAN | EAN item number |
| ItemUPC | UPC item number |
| ItemISBN | ISBN of the book |
| ItemIdSupplier | Supplier's item number |
| Quantity | |
| OrderNumber | Referenced order number |
| Data group | Message | - | Message |
Message
MessageID - Key field
Format: alphanumeric
Hint: Internal distinct code
| Data group | Envelope | - | Nachricht |
Nachricht
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 identification
SenderIdType - Required field: yes
Possible values:
| 14 | = | EAN (European Article Numbering Association) |
RecipientId - Required field: yes
Format: alphanumeric with up to 13 character(s)
Hint: Recipient identification
RecipientIdType - Required field: yes
Possible values:
| 14 | = | EAN (European Article Numbering Association) |
TransmissionId - Required field: no
Format: alphanumeric
Hint: Interchange control reference
Unique reference assigned by the sender to an interchange.
TestFlag - Required field: no
Possible values:
| 0 | = | No Test If not available (=production) |
| 1 | = | Test |
Indication that the interchange is a test.
| Data group | DeliveryNote | - | Delivery note head |
Delivery note head
Contains the data of the delivery note head
MessageID - Key field
Format: alphanumeric
Hint: Reference to MessageID in data group Message
DeliveryNoteID - Key field
Format: alphanumeric
Hint: Internal distinct code
Type - Required field: yes
Possible values:
| DESADV | = | Delivery note |
Status - Required field: yes
Possible values:
| 351 | = | Delivery note |
Function - Required field: yes
Possible values:
| 4 | = | Change |
| 5 | = | Replace |
| 9 | = | Original |
Number - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Delivery note number
Date - Required field: yes
Format: date
Hint: Delivery note date
ShipmentDate - Required field: yes
Format: date
Hint: Despatch date/time
ArrivalDate - Required field: yes
Format: date
Hint: Estimated arrival date/time
BillOfLadingNumber - Required field: no
Format: alphanumeric ***
Hint: Bill of Lading number
The Bill of Lading (BOL) reference number is required for truckload (TL) and less than truckload (LTL) shipments. BOL reference number is the unique number assigned by the shipper in creating the Bill of Lading. This is a number that identifies a unique shipment. Note: The BOL reference number on the paper BOL should match the reference number provided in this data element. Usage: BillOfLadingNumber / CarrierReferenceNumber must be provided at head or package level.
CarrierReferenceNumber - Required field: no
Format: alphanumeric ***
Hint: Carrier's reference number
This field is required in case it can be filled with one of the following values: => carrier PRO number for LTL and TL carriers => carrier tracking number for small parcel carriers => carrier airbill number for air freight The PRO number is required for truckload (TL) and less than truckload (LTL) shipments. The PRO number is a unique number assigned by the carrier. It is used to identify and track the shipment that goes out for delivery. Note regarding small parcel shipments: For small parcel carriers the tracking number per package is required in this field. Note regarding air freight: The airbill number replaces the tracking number or PRO number for air freight shipments. An airbill number is the unique identifier air carriers use to identify a package or pallet. The airbill number is assigned by the carrier to either the package for small parcel shipments or to the pallet for large shipments. The airbill number per package/pallet is required in this field. Usage: BillOfLadingNumber / CarrierReferenceNumber must be provided at head or package level.
ReferenceDate - Required field: no
Format: date
Hint: Date of Bill of Lading / Carrier reference no.
BuyerGLN - Required field: yes
Format: alphanumeric with up to 13 character(s)
Hint: Buyer's GLN
BuyerName1 - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Buyer's name (1st line)
BuyerName2 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Buyer's name (2nd line)
BuyerName3 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Buyer's name (3rd line)
BuyerStreet1 - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Buyer's street (1st line)
BuyerStreet2 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Buyer's street (2nd line)
BuyerStreet3 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Buyer's street (3rd line)
BuyerCity - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Buyer's city
BuyerZipCode - Required field: yes
Format: alphanumeric with up to 9 character(s)
Hint: Buyer's zip code
BuyerCountryCode - Required field: yes
Format: alphanumeric with up to 3 character(s)
Hint: Buyer's country
SupplierGLN - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's GLN
SupplierName1 - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's name (1st line)
SupplierName2 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's name (2nd line)
SupplierName3 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's name (3rd line)
SupplierStreet1 - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's street (1st line)
SupplierStreet2 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's street (2nd line)
SupplierStreet3 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's street (3rd line)
SupplierCity - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's city
SupplierZipCode - Required field: yes
Format: alphanumeric with up to 9 character(s)
Hint: Supplier's zip code
SupplierCountryCode - Required field: yes
Format: alphanumeric with up to 3 character(s)
Hint: Supplier's country
DeliveryGLN - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Delivery's GLN
DeliveryName1 - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Delivery's name (1st line)
DeliveryName2 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Delivery's name (2nd line)
DeliveryName3 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Delivery's name (3rd line)
DeliveryStreet1 - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Delivery's street (1st line)
DeliveryStreet2 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Delivery's street (2nd line)
DeliveryStreet3 - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Delivery's street (3rd line)
DeliveryCity - Required field: yes
Format: alphanumeric with up to 35 character(s)
Hint: Delivery's city
DeliveryZipCode - Required field: yes
Format: alphanumeric with up to 9 character(s)
Hint: Delivery's zip code
DeliveryCountryCode - Required field: yes
Format: alphanumeric with up to 3 character(s)
Hint: Delivery's country
CarrierId - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Carrier's identification
Please liaise with your Amazon Vendor Operations contact to obtain a list of carrier SCAC codes.
TransportMode - Required field: yes
Possible values:
| 10 | = | Carriage by sea |
| 20 | = | Bahntransport |
| 30 | = | Road haulage |
| 40 | = | Carriage by air |
TransportMedium - Required field: yes
Possible values:
| 13 | = | Ocean vessel |
| 25 | = | Rail express |
| 31 | = | Truck |
| 41 | = | Aircraft |
PalletQuantity - Required field: yes
Format: integer
Hint: Number of ISO EURO pallets
| Data group | Pack | - | Shipment's unit of transport (cartons) |
Shipment's unit of transport (cartons)
MessageID - Key field
Format: alphanumeric
DeliveryNoteID - Key field
Format: alphanumeric
PackID - Key field
Format: alphanumeric
BillOfLadingNumber - Required field: no
Format: alphanumeric ***
Hint: Bill of Lading number of a package
See also BillOfLadingNumber - Head
CarrierReferenceNumber - Required field: no
Format: alphanumeric ***
Hint: Carrier's reference number of a package
See also CarrierReferenceNumber - Head
ReferenceDate - Required field: no
Format: date
Hint: Date of Bill of Lading / Carrier reference no. of a package
GrossWeight - Required field: no
Format: decimal
Hint: Total gross weight of carton in in kg
Length - Required field: no
Format: decimal
Hint: Length of carton in cm
Width - Required field: no
Format: decimal
Hint: Width of carton in cm
Height - Required field: no
Format: decimal
Hint: Height of carton in cm
Handling - Required field: no
Possible values:
| BIG | = | Oversized |
| CRU | = | Fragile |
| EAT | = | Food |
| HWC | = | Handle with care |
SSCC - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: SSCC of package
Will contain the License Plate Receive number (SSCC, NVE).
| Data group | Pos | - | Line item |
Line item
MessageID - Key field
Format: alphanumeric
DeliveryNoteID - Key field
Format: alphanumeric
PackID - Key field
Format: alphanumeric
Number - Required field: yes
Format: integer
Hint: Line item number
ItemEAN - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: EAN item number
ItemUPC - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: UPC item number
ItemISBN - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: ISBN of the book
ItemIdSupplier - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Supplier's item number
Quantity - Required field: yes
Format: decimal
Hint:
OrderNumber - Required field: yes
Format: alphanumeric ***
Hint: Referenced order number
Legal notes
All 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
Generated automatically 2008-08-14, 03:50:05