Metro Bulgaria Delivery Notes
TransdatiX.Convert Metro Bulgaria Delivery Notes
Version 2.0.6 from 2008-12-09
Content
General
This Converter translates your delivery note data into a EDIFACT DESADV D.01B message for Metro Bulgaria.
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).
Hints
Apart from the basic distinction between hierarchical delivery note (all articles are allocated distinct to a package - usually in association with SSCC labeling) and sequential delivery note (without allocation to packages) this converter offers several additional functionality to define the packing hierarchy.
For a detailed description including examples see the document Possibilities for hierarchical packing sequences within electronic delivery notes.
A bill of material is an article that contains other articles (e.g. a display). The assortment components have to be indicated as sub-items.
The main article - the article, that contains the other articles - is like any other normal article. For the included sub-positions SubPosition must be set to 1 and SubPositionReferenceNumber must refer to the position number Number of the superordinate article.
That implies that the automatic generation of position numbers must not be used, so that a unique reference is possible. That means that every position must have a filled in unique Number to enable a correct declaration of sub-positions.
There are several possibilities to define the date of delivery:
- Fixed - use DeliveryDate to define a fixed date.
- Earliest - use DeliveryEarliestDate to define an earliest delivery date.
- Latest - use DeliveryLastDate to define a latest delivery date.
- Timeframe - use a combination of DeliveryEarliestDate and DeliveryLastDate to define a timeframe.
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 unique identification |
| Envelope | Transmission Section |
| MessageID | Reference to MessageID in data group Message |
| SenderId | Sender |
| RecipientId | Recipient |
| MessageType | EDIFACT Message Type Identifier |
| TransmissionId | Message Reference Number |
| TestFlag | Test Indicator |
| DeliveryNote | Delivery Note Heading Section |
| MessageID | Reference to MessageID in data group Message |
| DeliveryNoteID | Internal unique identification |
| Number | Delivery Note Number |
| Date | Delivery note date |
| DeliveryDate | Delivery date |
| DeliveryEarliestDate | Delivery date earliest |
| DeliveryLastDate | Delivery date latest |
| OrderNumber | Order number |
| OrderDate | Order date |
| DeliveryNoteNumber | Number of the paper base delivery note |
| BuyerGLN | The Buyer's GLN |
| SupplierGLN | The Supplier's GLN |
| SupplierId | The Supplier's internal id |
| DeliveryGLN | GLN of party where goods are deliverd |
| UltimateCustomerGLN | GLN of the Ultimate Customer |
| OrderedByGLN | GLN of the party who issued an order |
| TransportMode | Mode of transport |
| TransportMedium | Type of means of transport |
| Pack | Package Unit Section |
| MessageID | Reference to MessageID in data group Message |
| DeliveryNoteID | Reference to DeliveryNoteID in data group DeliveryNote |
| PackID | Internal unique identification |
| Quantity | Number of packages |
| Type | Type of packages |
| BoxQuantity | Number of contained packages |
| Volume | Volume of the package in cubic meter |
| GrossWeight | Total gross weight of the package in kg |
| Length | Length of the package in mm |
| Width | Width of the package in mm |
| Height | Height of the package in mm |
| Handling | Handling instructions |
| SSCC | SSCC of the package |
| Group | Package Group |
| Pos | Delivery Note Detail Section |
| MessageID | Reference to MessageID in data group Message |
| DeliveryNoteID | Reference to DeliveryNoteID in data group DeliveryNote |
| PackID | Reference to PackID in data group Pack |
| Number | Position number |
| SubPosition | Sub-position information |
| SubPositionReferenceNumber | Reference position |
| EAN | EAN of article |
| ItemIdBuyer | Buyer's Internal item number |
| Quantity | Delivered quantity in order units |
| DeliveryUnit | Invoicing unit |
| BestBeforeDate | Best before date |
| ExpiryDate | Expiry date |
| BatchNumber | Batch number |
| Data group | Message | - | Message |
Message
MessageID - Key field
Format: alphanumeric
Hint: Internal unique identification
| Data group | Envelope | - | Transmission Section |
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.
The default is DESADV
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. If not existing a reference composed of actual system date and time is generated.
TestFlag - Required field: no
Possible values:
| 1 | = | Interchange is a test |
Only used during testing period
| Data group | DeliveryNote | - | Delivery Note Heading Section |
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
Must be identical to the paper based delivery note. If not, the number printed on the paper based delivery note must be 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 earliest
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
DeliveryNoteNumber - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Number of the paper base delivery note
Required, if different from Number
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
SupplierId - Required field: no
Format: alphanumeric
Hint: The Supplier's internal id
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
Required in case of Cross Docking
TransportMode - Required field: no
Possible values:
| 20 | = | Rail transport |
| 30 | = | Road transport |
| 50 | = | Mail |
TransportMedium - Required field: no
Possible values:
| 25 | = | Rail express |
| X05 | = | Road parcel express |
| X09 | = | Parcel post |
| X11 | = | Surface mail |
| X13 | = | Air mail |
| Data group | Pack | - | Package Unit Section |
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:
| 201 | = | EURO pallet |
| 200 | = | 1/2 EURO pallet |
| PK | = | Package |
BoxQuantity - Required field: no
Format: integer
Hint: Number of contained packages
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:
| CRU | = | Crushable |
| FTD | = | Frost danger |
| EAT | = | Foodstaff |
| HWC | = | Handle with care |
| PER | = | Perishable cargo |
| RFG | = | Flammable compressed gas |
| RFL | = | Flammable liquid |
| RFS | = | Flammable solid |
| STR | = | Limited stackable |
| STK | = | Stackable |
| UST | = | Unstackable |
use only in case of warehouse delivery
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
| Data group | Pos | - | Delivery Note Detail Section |
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:
| 1 | = | This article is a sub-item. Omit this data element if the article is not a sub-item. |
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
ItemIdBuyer - Required field: no
Format: alphanumeric
Hint: Buyer's Internal item number
Quantity - Required field: yes
Format: decimal
Hint: Delivered quantity in order units
DeliveryUnit - Required field: no
Possible values:
| KGM | = | Kilogram |
| PCE | = | Piece |
Required for weight variable goods (see description DeliveryQuantity)
BestBeforeDate - Required field: no
Format: date
Hint: Best before date
Required for perishable products
ExpiryDate - Required field: no
Format: date
Hint: Expiry date
For easily perishable products the date can be specified, after which the product must not be sold any more.
BatchNumber - Required field: no
Format: alphanumeric with up to 35 character(s)
Hint: Batch number
Required for always batched articles
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 - 2008 TransdatiX Software
Generated automatically 2008-12-10, 00:06:44