EANCOM message set Receiving advice 1. Introduction Language select:

Preface

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

The basis of this elaboration is the international standard EANCOM^® 2002. The message type RECADV 005 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 message sender and receiver, delivery party, receiving date and document number.

Detail section
The detail section mirrors the detail section of the DESADV message and is used to specify differences between quantities advised and received, if applicable.

Summary section
The summary section contains no data and has syntactical reasons.

Project description

The receiving advice message is sent from the retailer to the supplier after the physical receiving of goods. It specifies details of goods received on agreed conditions.

The message relates to a single despatch point and a single receiving point. It may cover a number of different items or packages. It gives information to the consignor about received and accepted/not accepted goods.

New with recommendation 2008:

The transmission of a DESADV by the sender of goods is a pre-condition for that process. The following RECADV indicates again all information of the heading and detail section inclusive SSCC. It is also recommended to send back the batch number. This is to be agreed bilaterally by the partners. Like SSCC the indication is not mandatory, but helps in the process of tracking and tracing. Both, correct deliveries and discrepancies are communicated. The data from the RECADV can directly be used to create an INVOIC without differences.

This procedure is recommended to minimise differences in invoices at later time.

The segments QTY and QVR in SG 22

Used qualifiers:

Examples:

1. Acceptance of the entire delivery

The RECADV message mirrors the heading- and detail section of the received DESADV message. Its heading section also provides a reference to the DESADV document number.

In all following cases the RECADV message mirrors the heading- and detail section of the received DESADV message. Its heading section also provides a reference to the DESADV document number. Additionally the detail section contains information about differences between the quantity ordered and received / accepted.

2. Information about damaged goods

3. Partial delivery with damaged goods to be destroyed

4. Back order quantity to be delivered later

5. Over shipped quantity back

6. Godds not ordered, back

7. Product durability date unacceptable

8. Delivered too late, back