Language select:

Preface

The aim of the brochure on hand is to offer documentation describing the exchange of delivery data between business partners.

The basis of this elaboration is the international standard EANCOM^® 2002. The message type DESADV 007 is used to transmit relevant data. GEFEG.FX (Gefeg mbH, Berlin) was used as the documentation tool.

Please be aware to know that this booklet does not replace the complete specifications in the original chapters or other relevant instructions within the EANCOM^® 2002 documentation. Instead, it deals with the description of segments, data elements and codes to be used for a specific task.

The current documentation has been produced by the GS1 Germany GmbH in Cologne. GS1 Germany assumes no liability for any damages incurring from the use of this documentation. This brochure or extracts thereof may only be published or forwarded to third parties with the express written consent of GS1 Germany, which holds copyright on this work.

GS1 Germany thanks all experts who contributed significantly to these guidelines with knowledge from their daily business.

Important note:

To fulfill the requirements of directive 2003/58/EG, article 4, C058 has been opened in NAD segments identifying a message sender. If the place in the 5 DE 3124 is not sufficient, the following RFF segments can be used, qualified with DE 1153 = GN. DE 1154 has got a capacity of 70 digits. Only in those cases, when no RFF segment follows NAD, a RFF+GN can be used in the heading section of the message. Within the EDI recommendations of GS! Germany this is only applicable for the messages REMADV and SLSFCT..

Conventions

This brochure offers different ways to start:

Section 2, "Business Terms", is a table which links directly to the sequence numbers of the segments.

Section 3, "Message Structure Chart", is a list of all used segments in the same sequence as they are defined in the EANCOM^® message. In general, for each piece of information one single segment is provided. Exeptions may arrise when the the occurence of a segment is limited and can contain alternative information (e.g., segment BGM).

Section 4, "Branching Diagram", is a hierarchical graphic depiction of all used segments in the same sequence as they are defined in the EANCOM^® message. However, every segment is shown only once, and it is therefore possible that the sequence numbering is interrupted.

Section 5, "Segments Description", is a brief summary of the use of each segment.

In Section 6, "Segments Layout", an illustration that has been chosen to match the business terms (data from the inhouse application) with the elements from the EANCOM^® syntax.

In Section 7, "EANCOM^® Segments Layout", the message is presented in a similar layout as in the EANCOM^® manual.

Note on sections 6 and 7:

An additional column (GER) to provide a German status has been added to the layouts. An entry indicates that the recommended status differs from the EANCOM^® status. If the recommended status is weaker than the EANCOM^® status, the data element (or, if only one term exists the entire segment) can be omitted.

In general, code names are presented in red; these must to be understood as restricted and should not be changed/modified without bilateral agreement with the partner. If codes are given as examples, they are represented in blue (e.g., measurements). In this case, all codes of the relevant code list can be used.

Section 8, "Example(s)", provides at least one message example with comments.

Please note that, for technical reasons, the examples can contain component data element separators, which would otherwise be represented as data element separators in the original messages.

The following conventions apply to this brochure:

Message structure

Heading section
Specification of buyer and supplier message date and message number.

Detail section
Specification of GTIN to identify goods and services and their quantity.

Summary section
The summary section is for syntactical reasons only.

Notes to the detail section:

Within the detail section it is possible to transmit SSCC to identify the consignment and/or consignment lines.

Additionally it is possible to describe the hierarchy of the consignment. Therefore the detail section is presented in three paragraphs:

1. Detail section - Presentation of the entire consignment
   This detail section is mandatory in the message, (e.g., description of a pallet).
    
2. Detail section - Presentation of despatch unit(s)
   This detail section can be used in the message, (e.g., description of cartons placed on the pallet).
    
3. Detail section - Presentation of despatch unit(s)/article(s)
   This detail section can be used in the message, (e.g., description of consumer units within the cartons).

Application scenarios of the DESADV message

Below different possibilities are illustrated on the use of the despatch advice message (DESADV). Please note especially the allocation of delivery - despatch advice and the allocation of delivery - transport means/units.

The despatch advice (DESADV) can have references to one or more purchase orders (ORDERS). If a consignment is split into multiple transport means/units more than one DESADV can have references to one ORDERS.

Basic principle

In general at least one DESADV should be sent per transport means/units, e.g., truck, container or swap trailer even if a consignment is allocated to multiple transport means/units.

Scenario 1: One despatch advice (DESADV) per order

One truck transports consignments of different suppliers. Each consignment of a supplier relates to one purchase order (ORDERS) and is adviced by one DESADV and will be followed by one commercial invoice (INVOIC).

Scenario 2: One despatch advice (DESADV) per supplier

One truck transports consignments of different suppliers. Only one DESADV is sent per supplier. Each of them has references to different purchase orders (ORDERS). Every DESADV will be followed by one commercial invoice (INVOIC) containing a reference to this DESADV.

Scenario 3: One despatch advice (DESADV) per truck

Initiated by one purchase order (ORDERS) different trucks transport one consignment of one supplier. For each truck a DESADV is sent, all referencing to one ORDERS. In the following procedure one commercial invoice (INVOIC) is generated per DESADV.

Sequence of the segment groups SG11 (PAC) and SG17 (LIN)

As the PAC and LIN group are on the same hierarchy level of the detail section different ways of interpretation are possible about the sequence of information relating the packages (PAC) and goods (LIN) in the DESADV.

If the detail section provides information about packages and the contained goods the related LIN group should follow immediately the PAC group. The PAC group should NOT be used to describe all packages first and than be followed by the LIN group describing all goods.

Example:

Indication of SSCC

In general the SSCC of the package is to be indicated within the PAC group. The PCI group below LIN primary provides information about the article. An example of the use is 17 = supplier's instructions followed by GIN containing a serial number, batch number, etc.

Description of the consignment hierarchy (CPS)

The following example describes a consignment containing of three pallets. The first pallet contains 5 cartons marked with SSCC. The second pallet describes a "sandwich pallet" separating single layers with a pallet. Each pallet of each layer is marked with SSCC. The creation of a hierarchy shows one pallet with multiple layers (pallets). The third pallet contains only one type of article.

The CPS segment should describe all despatch units within the hierarchy that are marked with package identification (SSCC).

Example:
One pallet contains 10cartons marked with SSCC

For more examples see paragraph 8 of the current chapter.