recadv receiving advice message - · pdf filerecadv receiving advice message subset for...

RECADV Receiving Advice Message

Subset for Application in the European Steel Industry

Version September 1999

EDIFER WORKING GROUP - Message development

©Co

rpor

ate

Fact

ory—

Ph. D

. Sar

raut

e

UN/EDIFACT D97.A RECADV - Receiving Advice message

1

RECEIVING ADVICE MESSAGE (Table of Contents) 0. INTRODUCTION 2 1. BACKGROUND INFORMATION 3 1.1 Functional use of the message defined by EDIFACT 3 1.2 Functional use of the message recommended by EUROFER 4 2. DATA MODEL 6 2.1 Data Model Format 6 2.2 Data Model Diagram 7 2.3 Data Model Entities 9 2.4 Data Model Relationships 11 2.5 Data Model Attributes 13 3. SCOPE 16 3.1 Functional Definition 16 3.2 Field of Application 16 3.3 Principles 16 3.4 Message Usage 17 4. MESSAGE DEFINITION 18 4.1 Message Structure 18 4.2 Mapping of the Data Model to the Message 19 4.3 Branching Diagram of the Segments used by Eurofer 27 4.4 General Description of the Message - Subset of Eurofer 31 4.5 Detailed Description of the Message - Subset of Eurofer 38 5. EXAMPLES 80 5.1 Example of a receiving advice of Oy Ostomet Ab (Finland) 80


2

RECEIVING ADVICE MESSAGE 0. INTRODUCTION

This document provides the definition of the EUROFER subset of the RECEIVING ADVICE message based on the UN standard RECADV message of the UN/EDIFACT directory D97A. This message has been created by the EDIFER "Message development" working group. The message is to be used in Electronic Data Interchange (EDI) between partners involved in the steel industry. The manual has been structured in the following format:

- A Data Model definition describes the data entities, attributes and their relationships.

- The scope describes the field of application, principles and message usage.

- The message definition covers the structure, the entity/attribute mapping and how the

data described in the data model relates to the message.

- The message definition outlines the general structure of the message and specifies the use of each segment group and, or segment.

- Based on the branching diagram of the original EDIFACT message RECADV, the

segments used are indicated. This is followed by a detailed description of the segments used by Eurofer.

- Examples of some Receiving advice’s are provided to clarify the understanding of the

message description.


3

1. BACKGROUND INFORMATION 1.1 Functional use of the message defined by EDIFACT

The Receiving advice message is to address the business needs related to the goods receipt. The message is used to report on the physical receipt of goods. The message also allows reporting of discrepancies in goods, quantities, terms, packages, etc…

The message may also contain only the information that the received consignment is completely in line with the consignment information given in the Despatch advice message. In this case there is no detail to be provided on the consignment.

The message may report the discrepancies and give the appropriate instructions: 1. between the received consignment and the consignment provided in the Despatch

advice message. 2. between the received goods and the ordered goods in the Order (ORDERS) message,

the Delivery schedule (DELFOR) message or the Delivery just in time (DELJIT) message.

In the EDIFACT message it is capable of reporting on the following discrepancies: - at the Receiving advice level:

- arrival date and time, - missing and incorrect documents related to the whole consignment, - incorrect terms of delivery, - mode and means of transport other than those announced, - the physical state of the equipment (e.g. damaged, missing, not announced), - anomalies about the seal number of the equipment,

- at the Consignment detail level: - quantity variances between the number of packages received and the number of

packages expected or planned, - the physical state of the package (e.g. damaged, missing, not expected), - quantity variances between the goods received and the number of goods expected

or planned, - the physical state of the goods (e.g. damaged, missing, not expected, wrong),

missing and incorrect documents related to the goods, - quantity variances between the quantity per package received and quantity per

package expected or planned.


4

1.2 Functional use of the message recommended by EUROFER

Related to the functional use of the Receiving advice message defined by EDIFACT, the following business functions can be clearly defined. 1. To report on the arrival of a consignment The Receiving advice message contains only the information that the consignment is arrived. In this case there is no detail section provided. Only general information, such as arrival date/time, despatch advice number, packing list or waybill number are provided. 2. To confirm the received consignment matched the Despatch advice message The Receiving advice message contains only the information that the received consignment is completely in line with the consignment information provided in the Despatch advice message. In this case there is no detail section provided, only general information such as arrival date/time, despatch advice number are provided. This case will normally only be implemented if the Despatch advice (DESADV) message is implemented. 3. To report only on the physical receipt of goods In this case the Receiving advice message reports on the physical receipt of goods without comparing with the consignment information provided in the Despatch advice message. This functionality of the message can be used when; - the Despatch advice message is not implemented between the sender and the receiver of

the goods, - the Receiving advice message is used to report on several consignments received during

a certain period (e.g. goods received during a day, week) - there are discrepancies between the received consignment and the consignment

information provided in the Despatch advice message. This requires an agreement between the parties that if there are discrepancies, to report in detail on the physical receipt of the goods.

4. To report on the discrepancies between receipt and preceding messages The Receiving advice will not only report on the physical receipt of the goods but will also highlight the discrepancies detected with the consignment information provided in the Despatch advice message or requested in the Orders, Delivery schedule or Delivery just in time message. That means that the message will also report on missing items and received items not announced or requested. The functionality of this message can only be used if the Despatch advice message, Orders, Delivery schedule or Delivery just in time message has been implemented between both parties.

5. To give instruction on actions to be taken For every non acceptable status condition, the sender of the message can indicate preferred actions against the package or product unit level (e.g. replace damaged product unit, issue of a credit note).


5

EUROFER recommendation The Eurofer user implementation guide of the Receiving advice message allows the implementation of the different business functions. EUROFER recommends priority be given to the implementation of the first three possibilities and to limit the use of the Receiving advice message for the reporting of discrepancies. The implementation of the RECADV message reporting on discrepancies is, for both partners, more complex than the other functions. This is due to the amount of items on which discrepancies and quantity variances can be reported and the comparison at each level between received and announced. Therefore Eurofer has decided to limit the reporting of the level of discrepancies to the following possibilities without disturbing the usage of the message; - at the Receiving advice level:

- on the physical state of the mode and means of transport. - at the Consignment level:

- on the physical state of the package (e.g. missing, damaged, not expected) - on quantity variances between the goods received and the number of goods

expected - on the physical state of the goods (e.g. missing, damaged, not expected) - on quantity variances between the quantity per pack received and expected.

Remark : Trading partners should not forget that the implementation of the Receiving

Advice message, as any EDI message, is intended to be automatically processed by computer applications. Therefore it is strongly recommended that both parties should analyse very carefully the implementation of an automatic processing of discrepancies between goods despatched and goods received or ordered. The analysis of the discrepancies has to be done by both partners, firstly to be able to generate the information and secondly to be able to process and action the variances identified.


6

2. DATA MODEL 2.1 Data Model Format

The data model of the Receiving advice message has been created taking in account the data model of the EDIFER despatch advice message. The data model has been created, to make it possible for potential users to understand the Eurofer subset of the Receiving advice message. This data model gives the following information : - contents of the information (data elements) that can occur in the message, - relationships between the different data elements, - grouping of the data elements within the data entities, - and the relationship between data entities.

To simplify the understanding of the data model, the model is defined at a summary level, specifying when necessary a group of data elements instead of each data element. The data model consists of data entities, the relationships between those data entities and the attributes (data elements) in each data entity. An entity specifies an object against which information is held; it has a name, a description and attributes. An attribute describes a unique characteristic (information which can appear on the receiving advice); it has a name, a description and a value. The relationships of the data entities within the data model are reflected in the structure of the diagram in chapter 2.2.


7

2.2 Data Model Diagram

Receiving advice

Relates to

Transport information

Order Information

Package

Relates to

Refers to

Contains

Product unit

Reference to

Message / Document

1

0,N

0,1

1

0,1

1,N

0,1

Company

Reference to

1,N

0,1

Relates to

0,N


8

In this diagram, the rectangles represent data entities and the ovals show us the relationship between two data entities. How often a relationship can exist between two data entities is given in both directions and is specified as 0, 1, N.

- 0 means that there is no relationship between the entities. - 1 means that there is one and only one relationship between the entities. - N means that there are many relationships between the entities. - 0,1 means that there can be no or one relationship between the entities. - 1,N means that there can be one or many relationships between the entities. - 0,N means that there can be no or many (one or more) relationships between the

entities.

Example relationship between Package and Product unit 1. In the direction from Package to Product unit. A Package can contain one or more Product units. 2. In the direction from Product unit to Package. A Product unit can only be in one Package.


9

2.3. Data model entities

Because the data entities Company and Message/document are not really basic information in this message, they have been put outside the data model and they are treated as related data entities. This has been done to simplify and not to overload the data model, so that the data model is easier to understand. The entities are regrouped in two groups. The first group includes all the basic data entities and the second the related data entities. The following entities are contained within the data model. The basic data entities RECEIVING ADVICE TRANSPORT INFORMATION PACKAGE PRODUCT UNIT ORDER INFORMATION The related data entities COMPANY MESSAGE/DOCUMENT RECEIVING This entity contains the general information about a receiving ADVICE of steel products at the consignee. The consignee may be an intermediate or final destination. TRANSPORT This entity specifies the details of the mode and means of INFORMATION transport of the goods being received. The mode of transport, such as road, rail or sea. The means of transport, such as a truck, train or vessel. PACKAGE This entity gives the package identification and hierarchy, type of package and the weight of the package containing one or more product units. In the transport process the outer package is better known as a transport unit or handling unit. PRODUCT This entity contains the information about a product, such as UNIT material number, serial number or unique identifier (ISO 9002), production date, quantities, size, weights, etc ...


10

ORDER A product unit can be related to an order, an order item or to INFORMATION an order item-delivery schedule detail. The entity contains the information about the goods ordered under the conditions agreed between the buyer and the seller. Further information about the entity can be found in the document " User implementation guide of the ORDERS message". COMPANY An organisation with whom we deal for whatever purpose. This can be the buyer, sales agency, inspection authority, consignor , consignee, manufacturer, freight forwarder, etc ... . MESSAGE & This entity contains all the references to another message or DOCUMENT document. For example order, despatch advice.


11

2.4. Data model relationships

RECEIVING ADVICE - TRANSPORT INFORMATION (relation : relates to - 1/0,1)

- Direction from Receiving advice to Transport information. A Receiving advice may not relate to a Transport information , or can relate to one Transport information (e.g. transport at arrival).

- Direction from Transport information to Receiving advice. A Transport information belongs to only one Receiving advice.

RECEIVING ADVICE - PACKAGE (relation : carries - 0,1/0,N)

- Direction from Receiving advice to Package. A Receiving advice may contain no information on Package, or can relate to one or more Packages.

- Direction from Package to Receiving advice if package information is provided. A Package is received by only one Receiving advice.

PACKAGE - PRODUCT UNIT (relation : contains - 1/1,N)

- Direction from Package to Package. A outer Package may contain one or more inner Packages.

- Direction from Package to Product unit. A Package may contain one or more Product units.

- Direction from Product unit to Package. A Product unit may be related to only one Package.

RECEIVING ADVICE - PRODUCT UNIT (relation : contains - 0,1/0,N)

- Direction from Receiving advice to Product unit if no package information is provided. A Receiving advice may contain no information on Product unit or can relate directly to one or more Product units.

- Direction from Product unit to Receiving advice if no package information is provided. A Product unit may be related to only one Receiving advice.


12

PRODUCT UNIT - ORDER INFORMATION (relation : refers to - 1,N/0,1)

- Direction from Product unit to Order information.

A Product unit can refer to non or one Order information. - Direction from Order information to Product unit.

An Order information refers to one or more Product units.


13

2.5. Data model attributes

For each entity specified under point 2.3. Data model entities, a list of attributes and a description is given. ENTITY : RECEIVING ADVICE receiving advice number

Unique number given by the consignee to identify a receipt of goods.

receiving advice date/time Date/time of the issue of the receiving advice.

reception date/time

Date/time of recording of the receipt of the consignment of goods at the consignee.

carrier's consignment number Unique number of the consignment given by the carrier.

despatch advice number

Unique number given by the consignor to identify a despatch advice.

despatch date/time Date/time of the issue of the despatch advice.

ENTITY : TRANSPORT INFORMATION

mode of transport

Method of transport used for the carriage of the goods.

type of means of transport Description of the type of the means of transport being utilised.

id of the means of transport

Identification of the means of transport by name or number.

carrier identification or name Identification or name of the party undertaking or arranging transport.

arrival date/time

Date/time of arrival of the means of transport at the consignee.

transport arrival status Physical or logical status of the arrival of the means of transport (e.g. too late).


14

ENTITY : PACKAGE

serial number of the package

Serial number or unique number (ISO 9002) identifying a package containing one or more product units.

gross weight of the package

Gross weight of the package.

type of package Type of package. (e.g. Bundles, coils).

package status

Physical or logical status of the package (e.g. not received, damaged).

quantity difference per package type The quantity difference between the number per package type received and the number per package announced or requested.

quantity per package

The quantity of product units per package. Action requested

Instruction to another party to take the appropriate measure related to the identified package status (e.g. pick-up, replacement).

ENTITY : PRODUCT UNIT

identity number of the product unit

Unique number given by the producer to identify a product unit.

article number Number assigned by the producer to a product.

gross weight of the product unit

Gross weight of the product unit.

received quantity Quantity received (accepted) by the consignee.

product type

Description of the ordered product shape as specified in the code list of Eurofer or other code lists.

product unit status

Physical or logical status of the product unit (e.g. not received, damaged).


15

quantity difference of the product unit

The quantity difference between the received quantity and the quantity announced or requested of the product unit

ENTITY : PRODUCT UNIT Action requested

Instruction to another party to take the appropriate measure related to the identified product unit status (e.g. replacement, credit note).

ENTITY: ORDER INFORMATION

customer's order number

Unique number given by the customer to identify an order.

customer's order date Date when the order was issued by the customer.

customer's order item number

Unique number given by the customer to identify an order item.

supplier's order number Unique number given by the supplier to identify an order.

supplier's order item number

Unique number given by the supplier to identify an order item.

part number Customer's identification number attributed to the article.

THE RELATED DATA ENTITIES ENTITY : COMPANY company code, name and address

Code and if necessary the name and address, contact persons and communication channels of the partners involved by the buyer or seller. Examples are : buyer, seller, consignor, consignee, sales office.

ENTITY : MESSAGE / DOCUMENT

message / document type

Code identifying a referenced message or document (e.g. delivery schedule message, order, delivery just in time message).

message / document number

Identification number of a referenced message or document.

message /document date The date/time of the referenced message or document.


16

3. SCOPE 3.1. Functional Definition

This message is used in the steel industry to address the business needs related to the goods receipt. This message is used to report the physical receipt of goods. The message also allows the reporting of discrepancies in products, quantities, packages. The message may contain only the information that the received consignment is completely in line with the consignment information given in the Despatch advice message. The message may inform about the discrepancies: - between the received consignment and consignment given in the Despatch advice

message, - between the received goods and the ordered goods in the ORDERS, DELFOR or

DELJIT message.

3.2. Field of application

This message provides the definition of the Eurofer receiving advice message to be used in Electronic Data Interchange between trading partners.

3.3. Principles

This Eurofer Receiving advice message has been created as a subset of the UNSM RECADV message of EDIFACT. The message is initiated by the party who receives the goods. The message relates to a single or multiple receiving points. It may cover a number of different items or packages. This message allows the recipient to: - know when the goods were received, - give the precise details of the consignment received, - reconcile between the despatched goods and the received goods, - receive instructions in case of anomalies.


17

3.4. Message usage

The Receiving advice message can be used in different ways based on the agreement between the partners involved. The different functions of the message are explained in chapter 1.2. In the case the RECADV message is used in conjunction with the Despatch advice (DESADV) and is reporting on discrepancies, Eurofer recommends to reflect in the RECADV message the same structure as in the DESADV message for package and product units. If the received consignment is completely in line with the DESADV message, Eurofer recommends to limit the RECADV message to the following information in the header section): -the receiving advice number in the segment BGM, - the date of receipt in the segment DTM, - the despatch order number in the segment group 01 (RFF-DTM), - and the parties involved in the segment (NAD-LOC-….). In the case the RECADV message is used without the DESADV, the message can only report on received packages or product units. If the reporting is limited to packages, Eurofer recommends to use only the segment groups 16 and 17 in the detail section. If the reporting is limited to product unit, Eurofer recommends only to use the segment groups 16,22 and 26 in the detail section.


18

4. MESSAGE DEFINITION 4.1 Message Structure

The RECADV message of UN/EDIFACT is structured in two sections, a Heading Section and a Detail Section.

4.1.1. Message structure - Heading section

The heading section is used to give the general information relating to the whole message. Examples of this kind of information are receiving advice number, date of reception, date of arrival, parties involved, details of the mode of transport and information about the equipment used. The heading section can also be used to give information which has the same content for each line in the detail section. Examples of this kind of information are references valid for all detail items specified in the detail section.

. 4.1.2. Message structure - Detail section

The detail section can be used to provide details of all packages and the individual despatch items contained in the consignment. The segment group CPS provides the capability to give the hierarchical packing relationships. The group defines a logical top-down structure. The lowest level package information of the hierarchy, can be followed by the segment group 22, triggered by the segment LIN, to provide detailed product information. The segment group 16 provides information on the packages and on the products of a consignment : - case 1 : by using only the segment group 17 with the mandatory segment PAC, the

information is limited to the package level and no information is given at the product unit level

- case 2 : by using only the segment group 22 with the mandatory segment LIN, the information is limited to the item level and all information is given with relation to products unit(s).

- case 3 : by using both segment groups (group 17 and 22) together, the information is given at the level of the packages (group 17), and the product units (group 22). In this case it is possible to define the content for each the lowest package level, by using the relationship between the segment groups 17 and 22.

More details on the package levels, can be found in the Eurofer user implementation guide of the Despatch advice message.


19

4.2. Mapping of the Data model to the message

For the understanding of the mapping process, done by the EDIFER working group, it is necessary to have the knowledge about the structure of the official UNSM RECADV message and the functionality of the segment groups and segments as defined by the EDIFACT message development group MD1 - Trade. To have the complete information about the official version we recommend the usage of the official document published by UNITED NATIONS - EDIFACT directory D97.A. In the following table a short overview is given about the meaning and the functionality of the segment groups and segments in the message. The information given covers : - the segment group - the segment - the description of the meaning and the functionality - the comments of the EDIFER working group

SEGMENT GROUP

SEGMENT FUNCTION COMMENTS

HEADING SECTION BGM To identify the Receiving advice message by its

number. Mandatory.

DTM To specify general date/time/period related to the whole message.

Must be used at least once to identify the date of the receiving advice.

ALI To specify that the message is subject to special conditions due to origin, customs preference or commercial factors.

Not used.

GROUP 1 To specify referencing documents and their date,

related to the whole message. Only to be used if the information is relevant for all the items.

RFF To identify the referenced document. DTM To specify the date/time of the referenced

document.

GROUP 2 To identify the discrepancies with the

documentary requirements related to the whole message.

Not used.

DOC To identify documents where a discrepancy occurs.

GROUP 3 To report the physical or logical state of the

document upon receipt and to give the appropriate instructions

Not used.

CDI To report the physical and logical state. INP To give instructions to correct the discrepancy.

GROUP 4 To identify the parties (companies) relevant to the whole message.

Must be used to specify at least the recipient of the goods.

NAD Function, name and address of the company. LOC To indicate locations related to the company.


20

SEGMENT GROUP


GROUP 5 To specify referencing documents and their date

related to the company.

RFF To identify the referenced document related to the company.

DTM To specify the date/time of the referenced document.

Not used

GROUP 6 To give contact details of the company. CTA To identify to whom communication should be

directed.

COM To identify communication type and numbers.

GROUP 7 To report on discrepancies on the terms of delivery.

Not used.

TOD To indicate the terms of delivery. GROUP 8 To report the physical or logical state of the


Not used.

CDI To report a discrepancy on the terms of delivery. INP To give instructions to correct the discrepancy.

GROUP 9 To report on discrepancies on locations related to terms of delivery.

Not used.

LOC To indicate locations relevant to the TOD segment.

CDI To report discrepancy on locations.

GROUP 10 To specify details of the mode and means of transport and location relevant to the whole receiving advice.

TDT To specify the carriage, and the mode and means of transport of the goods being despatched.

DTM To give date/time information of the identified means of transport (e.g. date/time of arrival).

CDI To report the state of the mode of transport.

GROUP 11 To identify the equipment with which a problem has occurred.

Not used.

EQD To identify the specific equipment. GROUP 12 To report the physical or logical state of the

equipment upon receipt and to give the appropriate instructions

Not used.


GROUP 13 To identify the seal number and reporting anomalies.

Not used.

SEL To specify a seal number connected to the equipment named in the EQD segment.

CDI To report the anomaly.


21

SEGMENT GROUP


GROUP 14 To identify the equipment attached with which a

problem has occurred. Not used.

EQA To identify the equipment attached. GROUP 15 To report the physical or logical state of the

attached equipment upon receipt and to give the appropriate instructions

Not used.


DETAIL SECTION

GROUP 16 To provide details of all package levels and or the individual items received.

CPS To identify the sequence in which packing of the consignment is presented.

GROUP 17 To identify packaging, marks and numbers,

quantities about packing. The group should only be used if information is required on packaging level.

PAC To specify the number and type of packages of the arrived goods.

QVR To identify the quantity variances between the number of units received and expected or planned.

GROUP 18 To specify markings, labels and packing

numbers and related anomalies.

PCI To specify markings and/or labels used on individual packages as described in the PAC segment.

RFF To reference the package identification e.g. master label number.

Not used.

GROUP 19 To report the physical or logical state of the package upon receipt and to give the appropriate instructions

Not used.


GROUP 20 To give package identification number and

related anomalies.

GIN To provide the identity number of the packages being received or missing.

GROUP 21 To report the physical or logical state of the identified package upon receipt and to give the appropriate instructions



22

SEGMENT GROUP


GROUP 22 To provide details of the individual received

items. The group is used if information is needed at product level.

LIN To identify the product being received. PIA To provide additional product identification.

IMD To describe the product being received. QTY To give quantity information, such as received

and despatched quantity, about the product.

QVR To identify quantity variances between quantity received and quantity expected or planned.

DTM To provide date/time information related to the line item.

Not used.

PRI To provide price information related to the line item.

Not used.


product upon receipt and to give the appropriate instructions


GROUP 24 To identify the discrepancies with the

documentary requirements related to the line item.

Not used.

DOC To identify documents where a discrepancy occurs.



Not used.


GROUP 26 To give identification number and related anomalies.

GIN To provide the identity number of the goods being received or missing.



GROUP 28 To specify referencing documents and their date, related to the line item.

RFF To identify the referenced document. DTM To specify the date/time of the referenced

document.


23

SEGMENT GROUP


GROUP 29 To specify markings, labels and packing

numbers and related anomalies.

PCI To specify markings and/or labels used on individual packages as described in the PAC segment.

QTY To specify the quantity per package. QVR To identify quantity variances quantity per

package received and quantity per package expected or planned.

GROUP 30 To report the physical or logical state of the package upon receipt and to give the appropriate instructions

Not used.


GROUP 31 To give package identification number and

related anomalies.

GIN To provide the identity number of the packages being received or missing.



SUMMARY SECTION

CNT To provide control totals by the sender for

checking by the receiver. Not used.


24

The mapping is done starting from the entities, relationships and attributes of the data model to the EDIFACT message. This mapping is presented as a table containing the entities of the following information ; - the attributes - the segment group number - the segment by his tag - the Edifact data element - remarks about the usage.

ATTRIBUTE SEGMENT

GROUP SEGMENT TDID –

Data Element

REMARKS

Entity : RECEIVING ADVICE Receiving advice number BGM 1004 Receiving advice date/time DTM 2380 DTM segment in the header,

following BGM. Reception date/time DTM 2380 DTM segment in the header,

following BGM. Carrier's consignment number Group 1 RFF 1154 Use the relevant code for 1153

to indicate Carrier's consignment number.

Despatch advice number Group 1

RFF 1154 Use the relevant code for 1153 to indicate despatch advice number.

Despatch advice date/time Group 1

DTM 2380 DTM segment following the RFF segment.

Entity : TRANSPORT INFORMATION

Mode of transport Group 10 TDT 8067 Type of means of transport Group 10 TDT 8179 Id of the means of transport Group 10 TDT 8213 Carrier identification or name Group 4 NAD 3039 or

C058 Code form or clear form can be used.

Arrival date/time Group 10 DTM 2380 Transport arrival status Group 10 CDI 7007 Entity : PACKAGE Package hierarchy level Group 16 CPS 7164, 7166

and 7075

Type of package Group 17 PAC 7065 Package information at package level using segment group 17

Serial number of the package Group 20 GIN C208 (7402)

Gross weight of the package Not foreseen in the EDIFACT message, at this level, see segment group 22 and 29.

Package status Group 21 CDI 7007 Quantity differences of package type Group 17 QVR C279 Action request Group 21 INP C522


25

ATTRIBUTE SEGMENT


Data Element

REMARKS

Entity : PACKAGE Package information at product level using segment group 22

Serial number of the package Group 22 or

Group 28

LIN

RFF

7140

1154

Use the relevant code for 7143. Use the relevant code for 1153.

Gross weight of the package Group 22 QTY 6060 Use the relevant code for 6063.

Package status Group 23 CDI 7007 Quantity differences of package type Group 22 QVR C279 Action request Group 23 INP C522 Package information at product level and package level using segment group 29

Serial number of the package Group 31 GIN C208 (7402)

Gross weight of the package Group 29 QTY 6060 Use the relevant code for 6063.

Package status Group 32 CDI 7007 Quantity differences of package type Group 29 QVR C279 Action request Group 32 INP C522 Entity : PRODUCT UNIT Identity number of the product unit Group 22

Or

Group 26

LIN or PIA

GIN

7140

7402

Use the relevant code for element 7143. Use the relevant code for element 7405.

Article number Group 22 LIN or PIA

7140 Use the relevant code for element 7143.

Gross weight of the product unit Group 22

QTY 6060 Use the relevant code for 6063.

Received quantity Group 22 QTY 6060 Use the relevant code for 6063. Product Type Group 22 IMD 7009

or 7008

Use of code list Eurofer P01. Use code 8 in element 7081.

Product unit status Group 23 CDI 7007 Quantity differences of product unit Group 22 QVR C279


26

ATTRIBUTE SEGMENT


Data Element

REMARKS

Entity : ORDER INFORMATION Customer's order number Group 1

or Group 22

or Group 28

RFF

LIN

RFF

1154

7140

1154

Use the relevant code for 1153. Use the relevant code for 7143. Use the relevant code for 1153

Customer's order date Group 1 or

Group 28

DTM 2380 DTM segment following the RFF in the segment group.

Customer's order item number Group 1 or

Group 22 or

Group 28

RFF

LIN

RFF

1154

7140

1154

Use the relevant code for 1153. Use the relevant code for 7143. Use the relevant code for 1153.

Supplier's order number Group 1 or

Group 28

RFF 1154 Use the relevant code for 1153.

Supplier's order item number Group 1 or

Group 28

RFF 1154 Use the relevant code for 1153.

Part number Group 22 LIN or PIA

7140 Use the relevant code for 7143.

Entity : COMPANY Company code, name and address Group 4 NAD 1154 Use the relevant code for 1153. Contact information Group 6 CTA C056 Use the relevant code for 3139. Communication contact Group 6 COM C076 Internal place/location related to the consignee

Group 4 LOC C517 Use the relevant code for 3227.

Entity : MESSAGE / DOCUMENT Message / document type Group 1

or Group 28

RFF 1153

Message / document number Group 1 or

Group 28

RFF 1154

Message /document date Group 1 or

Group 28

DTM 2380 DTM segment following the RFF in the segment group.


27

4.3 Branching Diagram of the Segments used by Eurofer

RECADV Receiving advice message, version D97A Message to enable the transmission of the information concerning the receipt of goods. The codes used for the usage indicator (USG. IND.) for the segments. R for REQUIRED - Should always be used in the message O for OPTIONAL - May be used by trading partners if required. X for EXCLUDED - Not used in the message.

Heading Section USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS

R 39 UNH Message header M 1 R 40 BGM Beginning of message M 1 R 41 DTM Date/time/period M 10 X ALI Additional information C 5

O SEGMENT GROUP 1 C 10 R 42 RFF Reference M 1 O 43 DTM Date/time/period C 1

X SEGMENT GROUP 2 C 10 X DOC Document / message details M 1

X SEGMENT GROUP 3 C 10 X CDI Physical and logical state M 1 X INP Parties to instruct C 5

R SEGMENT GROUP 4 M 10 R 44 NAD Name and address M 1 O 46 LOC Place/location identification C 10

O SEGMENT GROUP 5 C 10 R 47 RFF Reference M 1 X DTM Date/time/period C 1

O SEGMENT GROUP 6 C 10 R 48 CTA Contact information M 1 O 49 COM Communication contact C 5

X SEGMENT GROUP 7 C 10 X TOD Terms of delivery or transport M 1


X SEGMENT GROUP 9 C 10 X LOC Place/location identification M 1 X CDI Physical and logical state C 10

O SEGMENT GROUP 10 C 10 R 50 TDT Details of transport M 1 O 51 DTM Date/time/period C 10 O 52 CDI Physical and logical status C 10


28

Heading Section USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS

X SEGMENT GROUP 11 C 9999 X EQD Equipment details M 1


X SEGMENT GROUP 13 C 25 X SEL Seal number M 1 X CDI Physical and logical state M 10

X SEGMENT GROUP 14 C 10 X EQA Attached equipment M 1


Detail Section USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS

O SEGMENT GROUP 16 C 9999 R 53 CPS Consignment packing sequence M 1

O SEGMENT GROUP 17 C 9999 R 54 PAC Package M 1 O 55 QVR Quantity variances C 1

O SEGMENT GROUP 18 C 999 R 56 PCI Package identification M 1 X RFF Reference C 1


O SEGMENT GROUP 20 C 999 R 57 GIN Goods identity number M 1

O SEGMENT GROUP 21 C 10 R 58 CDI Physical and logical state M 1 O 59 INP Parties to instruct C 5

O SEGMENT GROUP 22 C 9999 R 60 LIN Line item M 1 O 61 PIA Additional product id C 10 O 63 IMD Item description C 25 O 64 QTY Quantity C 10 O 65 QVR Quantity variances C 10 X DTM Date/time/period C 5 X PRI Price details C 1



29

USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS

X SEGMENT GROUP 24 C 10 X DOC Document / message details M 1




O SEGMENT GROUP 28 C 10 R 71 RFF Reference M 1 O 72 DTM Date/time/period C 1

O SEGMENT GROUP 29 C 9999 R 73 PCI Package identification M 1 O 74 QTY Quantity C 1 O 75 QVR Quantity variances C 1




X CNT Control total C 1 R 79 UNT Message trailer M 1


30

EUROFER RECADV RECEIVING ADVICE MESSAGE VERSION - SEPTEMBER 1999 UN/EDIFACT DIRECTORY : D97.A

Branching Diagram

Page 1

UNH

M 1 M 1

BGM

DTM

G01

C 10

G04

M 10

RFF

M 10 M 1

DTM C 1

NAD

M 1

LOC

C 10

G05

C 10

RFF

M 1

G06

C 10

CTA

M 1

COM C 5

G16

C 9999

CPS

M 1

DTM

C 10

G10

C 10

TDT

M 1

PAC

M 1

CDI

C 10

G22

C 9999

LIN

M 1

G17

C 9999

QVR

C 1

See page 2 / part 1

Level

00

01

02

03

UNT

M 1

PIA

C 10

See page 2 / part 2

EUROFER RECADV RECEIVING ADVICE MESSAGE VERSION - SEPTEMBER 1999 UN/EDIFACT DIRECTORY : D97.A

Page 2Branching Diagram

See page 1

G18

C 999

PCI M 1

G20

C 999

CDI

M 1

G21

C 10

INP

C 5

Level

03

04

05

06

IMD

C 25

QTY

C 10

QVR

C 10

CDI

G23

C 10

INP

C 5

GIN

C 99

M 1

CDI

C 5

G27

INP

RFF

GIN

M 1

See page 1

M 1

G26

C 10

M 1

G28

C 10

M 1

DTM

C 1

G29

C 9999

PCI

QTY QVR

G31

C 1 C 1

C 10

GIN

M 1

CDI

M 1

G32

C 10

INP

C 5

M 1


31

4.4 General description of the message - subset of Eurofer 4.4.1 Message definition and segment clarification

This section is provided to give clarification and further explanation to the usage of the segments within the message defined by Eurofer. The message consists of two sections, a heading section and a detail section. The heading section is representing the transportation details, the corresponding references and the parties involved. Some detail information which applies or relates to all the line items of the detail section can also be given in the heading section. This section should be read in conjunction with the segment usage and the branching diagram (chapter 3.3.) which indicates the required (R) and optional (O) segments and segment groups. The following guidelines and principles apply to the whole message of Eurofer and are intended to facilitate the understanding and the implementation of the message. All the specified data/times (segment DTM) should be in the format 'CCYYMMDD'/'hhmm' unless all parties involved in the transaction agree that there is a functional requirement for an alternative format. Periods should be specified as whole numbers representing the required period as indicated in the format qualifier (weeks, month, etc) Where a choice of code or text is given, only the code element should be used if possible. Optional (conditional) data that are not required in the message should not be included. Care must be taken that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of the group.


32

4.4.2 Message description - Heading section

Information to be or which can be provided in the heading section of the message. Segment UNH, Message Header

A service segment starting and uniquely identifying a message. The message type code for the EUROFER receiving advice message is "RECADV". Note : Receiving advice messages complying with this document must contain the following data in the segment UNH composite data element S009 with data elements ; - 0065 RECADV - 0052 D - 0054 97A - 0051 UN

Segment BGM, Beginning of message

A segment for unique identification of the receiving advice document, name and its number.

Segment DTM, Date/time/period

Date/time/period related to the whole message. The DTM segment must be specified at least once to identify the date of the receiving advice.

Segment ALI, Additional information

A segment indicating that the message is subject to special conditions owing to origin or commercial factors. Eurofer has decided not to use this segment.

Segment group 1 : RFF-DTM

A group of segments giving references and where necessary, their dates relating to the whole message, e.g. despatch advice, purchase order, delivery instructions.

Segment RFF, Reference

A segment for referencing documents relating to the whole receiving advice message, e.g. despatch advice, purchase orders, delivery instructions. If the RECADV message refers to a prior message, this message has to be referenced.


Date/time/period as applied to the referred document.

Segment group 2 : DOC-SG3 A group of segments identifying the discrepancies with the documentary requirements relating to the whole consignment. Eurofer has decided not to use the segment group.

Segment group 4 : NAD-LOC-SG5-SG6

A group of segments identifying names, addresses and locations, relevant to the whole Receiving advice.


33

Segment NAD, Name and address

A segment for identifying names and addresses and their functions relevant for the whole Receiving advice. Identification of at least the recipient of the goods is mandatory. It is recommended that where possible only coded form of the party ID should be specified.

Segment LOC, Place/location identification

A segment indicating more details regarding specific places or locations related to the party specified in the NAD segment, e.g. internal site and, or building number.

Segment group 5 : RFF-DTM

A group of segments giving references only relevant to the specified party rather than the whole message. Eurofer has decided to use only the segment RFF of this group.


A segment for referencing documents relating to the party specified in the NAD segment.

Segment group 6 : CTA-COM

A group of segments giving contact details of the specific person or department within the party identified in the NAD segment.

Segment CTA, Contact information

A segment to identify person, function, department to whom communication should be directed

Segment COM, Communication contact

A segment to identify communication type and numbers for person function, department identified in CTA segment.

Segment group 7 : TOD-SG8-SG9

A group of segments to report on discrepancies on terms of deliveries. Eurofer has decided not to use the segment group.

Segment group 10 : TDT-DTM-CDI

A group of segments specifying details of the mode and means of transport, the date or date time of arrival, if a discrepancy has occurred or if required by the recipient of the message for further identification.

Segment TDT, Details of transport

A segment specifying the carriage, and the mode and means of transport of the goods arrived.


A segment giving the date or date and time information of the identified means of transport.

Segment CDI, Physical and logical state

A segment to report the state of the mode and means of transport.


34

Segment Group 11 : EQD-SG12-SG13-SG14

A group of segments identifying equipment with which a problem has occurred or if required by the recipient of the message for further identification. Eurofer has decided not to use the segment group.

4.4.3 Message description – Detail section

Information to be or which can be provided in the detail section of the message.

Segment group 16 : CPS-SG17-SG22 A group of segments providing details of all packages and/or individual items received. This segment group provides the capability to give the top-down hierarchical relationship of the package levels.

Segment CPS, Consignment packing sequence

A segment identifying the sequence in which packing of the consignment is presented, e.g. a pallet loaded with boxes.

Segment group 17 : PAC-QVR-SG18

A group of segments identifying packaging, quantities and marks and numbers.

Segment PAC, Package A segment specifying the number and type of packages or physical units and the physical type of packaging of the arrived goods.

Segment QVR, Quantity variances

A segment identifying quantity variances between the number of units received (as specified in the PAC segment) and the number of units expected or planned.

Segment group 18 : PCI-RFF-SG19-SG20

A group of segments specifying markings and labels and, if required, related anomalies. Eurofer has decided to use only the segment PCI and the segment group 20 of this segment group.

Segment PCI, Package identification

A segment specifying markings and labels used on individual physical units (packages) described in the PAC segment.

Segment group 20 : GIN-SG21

A group of segments giving package identification numbers and if required the related anomalies.

Segment GIN, Goods identity number

A segment providing identity numbers applied to packages being received or missing.

Segment group 21 : CDI-INP A group of segments to report the physical or logical state of the identified package upon receipt and to give the appropriate instructions if needed.


35

Segment CDI, Physical and logical state

A segment to report the physical state of the identified package upon receipt, e.g. damaged, missing.

Segment INP, Parties to instruction

A segment to give instructions (e.g. replace).

Segment group 22 : LIN-PIA-IMD-QTY-QVR-DTM-PRI-SG23-SG24-SG26-SG28- SG29

A group of segments providing details of the product or service received. Eurofer has decided to use only the segments LIN, PIA, IMD, QTY, QVR, and the segment groups SG23, SG26, SG28 and SG29 of this segment group.

Segment LIN, Line item

A segment identifying the product or service received.

Segment PIA, Additional product id A segment providing additional product or service identification.

Segment IMD, Item description

A segment describing the product or service received. This segment should be used for a product or service that cannot be identified by a product code or article number.

Segment QTY, Quantity

A segment to give quantity information about the product specified in the LIN, PIA or IMD segment.


A segment identifying quantity variances between quantity per item received and quantity per item expected or planned.

Segment group 23 : CDI-INP

A group of segments to report the physical state of the product given in the LIN or IMD segment upon receipt and to give the appropriate instructions, if needed.

Segment CDI, Physical or logical state

A segment to report the physical state of the product upon receipt e.g. wrong colour. Segment INP, Parties to instruct


Segment group 26 : GIN-SG27 A group of segments giving goods identification numbers and if required the related anomalies.


A segment providing identity numbers of goods being received or missing.


36

Segment group 27 : CDI-INP

A group of segments to report the physical state of the identified goods at receipt and to give the appropriate instructions, if needed.


A segment to report the receipt conditions for the identified goods, e.g. missing, damaged.

Segment INP, Parties to instruct


Segment group 28 : RFF-DTM A group of segments giving references relevant to the line item.


A segment for referencing documents relating to the line item specified by the LIN or IMD segment.


A segment for date or date and time as related to the referred document.

Segment group 29 : PCI-QTY-QVR-SG30-SG31 A group of segments identifying one specific package or a number of packages, the marks and numbers, quantities and receiving conditions. Eurofer has decided to use only the segment PCI, QTY, QVR and the segment group 31.

Segment PCI, Package identification

A segment specifying marking and labels used in identified package(s).

Segment QTY, Quantity A segment to specify the quantity per package.


A segment identifying quantity variances between quantity per package received and quantity per package expected or planned.

Segment group 31 : GIN-SG32

A group of segments giving package identification numbers and if required the related anomalies.


A segment providing identity numbers of packages received or missing.

Segment group 32 : CDI-INP A group of segments to report the physical state of the identified packages upon receipt and to give the appropriate instructions, if needed.


37


A segment to report the receipt conditions for the identified packages, e.g. missing, damaged.

Segment INP, Parties to instruct


Segment CNT, Control total A segment by which control total may be provided by sender for checking by the receiver. Eurofer has decided not to use this segment.

Segment UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.


38

4.5 Detailed description of the message - subset of Eurofer 4.5.1 Detailed segment clarification

This section is provided to give detailed clarification and a further explanation to the usage of the data elements in the segments of the Receiving advice message defined in the subset of Eurofer. The message consists of two sections, a heading section and a detail section. The section 4.5.2. describes each segment used in the heading section of the Eurofer Receiving advice message. The section 4.5.3. describes each segment used in the detail section of the Eurofer Receiving advice message. The original EDIFACT segment layout is listed. The appropriate comments relevant to the Eurofer subset are indicated. The segments are presented in the sequence in which they appear in the message. The segment and the segment group tag is followed by Mandatory or Conditional indicator, the maximum number of occurrences and the segment description. Reading from left to right, in column one the usage indicator is for the use of the EDIFACT data elements in the Eurofer subset. In the other columns the information is given about the data element tag, data element name, followed by the EDIFACT status and the format. The codes used for the usage indicator (USG. IND.) for the data elements are, R for REQUIRED - Should always be used in the message O for OPTIONAL - May be used by trading partners if required. X for EXCLUDED - Not used in the message.


39

4.5.2 Detailed segment description - Heading section GROUP : SEGMENT : UNH MESSAGE HEADER SEGMENT STATUS : Mandatory 1 FUNCTION : To head, identify and specify a message NOTES : This segment would normally be added as part of the translation process. It has been

included for completeness.

Data Element Summary USG. IND. TAG NAME STATUS FORMAT

R 0062 MESSAGE REFERENCE NUMBER M an..14 Unique message number assigned by the sender

R S009 MESSAGE IDENTIFIER M R 0065 Message type identifier M an..6 RECADV Receiving advice message

R 0052 Message type version number M an..3 D

R 0054 Message type release number M an..3 97A

R 0051 Controlling agency M an..2 UN United nations

X 0057 Association assigned code C an..6

X 0068 COMMON ACCESS REFERENCE C an..35

X S010 STATUS OF THE TRANSFER C X 0070 Sequence message transfer number M n..2 X 0073 First/last sequence message transfer C a1


40

GROUP : SEGMENT : BGM BEGINNING OF MESSAGE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To indicate the type and function of a message and to transmit the identifying number. NOTES :


R C002 DOCUMENT/MESSAGE NAME C R 1001 Document/message name, coded C an..3 98 Arrival information

632 Goods receipt

O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 X 1000 Document/message name C an..35

R 1004 DOCUMENT/MESSAGE NUMBER C an..35 Contains the Receiving advice number

R 1225 MESSAGE FUNCTION, CODED C an..3 5 Replace

7 Duplicate (re-transmission) 9 Original

O 4343 RESPONSE TYPE, CODED C an..3 AB Message acknowledgement

NA No acknowledgement needed


41

GROUP : SEGMENT : DTM DATE / TIME / PERIOD SEGMENT STATUS : Mandatory segment repeat : 10 FUNCTION : To specify date, and/or time, period. NOTES : All specified dates/times should be in the format 'CCYYMMDD'/'hhmm' unless all

parties involved in the transaction agree that there is a functional requirement for an alternative format.


R C507 DATE/TIME/PERIOD M R 2005 Date/time/period qualifier M an..3 35 Delivery date/time, actual

50 Goods receipt date/time 137 Document/message date/time 310 Received date/time See code list EDIFACT for other values

R 2380 Date/time/period C an..35 R 2379 Date/time/period format qualifier C an..3 102 CCYYMMDD

203 CCYYMMDDhhmm See code list EDIFACT for other values


42

GROUP : Group 01 : RFF - DTM

Conditional group repeat : 10 SEGMENT : RFF REFERENCE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To specify a reference. NOTES : This segment is used for referencing documents, relating to the whole message or to

all the received items specified in the detail section.


R C506 REFERENCE M R 1153 Reference qualifier M an..3 AAK Dispatch advice number

AAM Waybill number AAN Delivery schedule (instruction) number AAS Transport document number ABT Goods declaration number AEV Shipping note number CO Buyer's order number ON Order number PK Packing list number POR Purchase order response number VN Order number (Vendor) See code list EDIFACT for other codes

R 1154 Reference number C an..35 X 1156 Line number C an..6 X 4000 Reference version number C an..35


43


Conditional group repeat : 10 SEGMENT : DTM DATE / TIME / PERIOD SEGMENT STATUS : Conditional segment repeat : 1 FUNCTION : To specify date, and/or time, period of the referenced document. NOTES : All specified dates/times should be in the format 'CCYYMMDD'/'hhmm' unless all



R C507 DATE/TIME/PERIOD M R 2005 Date/time/period qualifier M an..3 171 Reference date/time

See code list EDIFACT for other values




44

GROUP : Group 04 : NAD - LOC- SG5 – SG-

Conditional group repeat : 10 SEGMENT : NAD NAME AND ADDRESS SEGMENT STATUS : Mandatory segment repeat : 1 To specify the name/address and their related function, either by C082 only and/or

unstructured by C058 or structured by C080 thru 3207. NOTES : This segment is used for identifying the parties relevant for the whole message.

Party details can be given in coded form or clear text. We recommend the use of coded form,using C082. The basis of this codification could be one of the national or international code lists. Examples of such code lists are VAT-registration number, Chamber of commerce, Wirtschaftsvereinigung, Odette, EAN, etc.


R 3035 PARTY QUALIFIER M an..3 BY Buyer (service requester)

CA Carrier CN Consignee CZ Consignor SE Seller See code list EDIFACT for other codes

O C082 PARTY IDENTIFICATION DETAILS C R 3039 Party id identification M an..35 O 1131 Code list qualifier C an..3 R 3055 Code list responsible agency, coded C an..3 58 EUROFER

91 Assigned by seller or seller's agent 92 Assigned by byer or buyer's agent

O C058 NAME AND ADDRESS C R 3124 Name and address line M an..35 O 3124 Name and address line C an..35 O 3124 Name and address line C an..35 O 3124 Name and address line C an..35 O 3124 Name and address line C an..35

O C080 PARTY NAME C R 3036 Party name M an..35 O 3036 Party name C an..35 O 3036 Party name C an..35 O 3036 Party name C an..35 O 3036 Party name C an..35 O 3045 Party name format, coded C an..3


45

Data Element Summary

USG. IND. TAG NAME STATUS FORMAT

O C059 STREET C R 3042 Street and number/P.O. Box M an..35 O 3042 Street and number/P.O. Box C an..35 O 3042 Street and number/P.O. Box C an..35 O 3042 Street and number/P.O. Box C an..35

O 3164 CITY NAME C an..35

O 3229 COUNTRY SUB-ENTITY IDENTIFICATION C an..9

O 3251 POSTCODE IDENTIFICATION C an..9

O 3207 COUNTRY, CODED C an..3 Use ISO 3166 two alpha country code.


46

GROUP : Group 04 : NAD - LOC- SG5 – SG6

Conditional group repeat : 10 SEGMENT : LOC PLACE/LOCATION IDENTIFICATION SEGMENT STATUS : Conditional segment repeat : 10 FUNCTION : To identify a country/place/location/related location one/related location two. NOTES :


R 3227 PLACE/LOCATION IDENTIFICATION M an..3 4 Goods receipt place

8 Place of destination 11 Place/port of discharge 20 Place of ultimate destination of goods See code list EDIFACT for other codes

O C517 LOCATION IDENTIFICATION C O 3225 Place/location identification C an..25 O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O 3224 Place/location C an..70

O C519 RELATED LOCATION ONE IDENTIFICATION C O 3223 Related place/location one identification C an..25 O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O 3222 Related place/location one C an..70

O C553 RELATED LOCATION TWO IDENTIFICATION C O 3233 Related place/location two identification C an..25 O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O 3232 Related place/location two C an..70

X 5479 RELATION, CODED C an..3


47


Conditional group repeat : 10 SEGMENT : RFF REFERENCE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To specify a reference. NOTES : This segment is used for referencing documents, relating to the party specified in the

NAD segment.


R C506 REFERENCE M R 1153 Reference qualifier M an..3 GN Government reference number

VA VAT registration number See code list EDIFACT for other codes

R 1154 Reference number C an..35 X 1156 Line number C an..6 X 4000 Reference version number C an..35


48

GROUP : Group 06: CTA - COM

Conditional group repeat : 10 SEGMENT : CTA CONTACT INFORMATION SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To identify a person or a department to whom communication should be directed.. NOTES :



R 3139 CONTACT FUNCTION, CODED C an..3 IC Information contact

LB Place of delivery contact See code list EDIFACT for other codes.

R C056 DEPARTMENT OR EMPLOYEE, CODED C R 3413 Department or employee identification C an..17 R 3412 Department or employee C an..35


49

GROUP : Group 06: CTA - COM

Conditional group repeat : 10 SEGMENT : COM COMMUNICATION CONTACT SEGMENT STATUS : Conditional segment repeat : 5 FUNCTION : To identify a communication number of a department or a person to whom

communication should be directed. NOTES :



R C076 COMMUNICATION CONTACT M R 3148 Communication number M an..512 R 3155 Communication channel qualifier M an..3

EM Electronic mail FX Telefax TE Telephone TL Telex See code list EDIFACT for other codes


50

GROUP : Group 10 : TDT- DTM – CDI

Conditional group repeat : 10 SEGMENT : TDT DETAILS OF TRANSPORT SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To specify the transport details such as mode of transport, means of transport, its

conveyance reference number and the identification of the means of transport. NOTES :


R 8051 TRANSPORT STAGE QUALIFIER M an..3 20 Main-carriage transport

30 On-carriage transport See code list EDIFACT for other codes.

X 8028 CONVEYANCE REFERENCE NUMBER C an..17

R C220 MODE OF TRANSPORT C R 8067 Mode of transport, coded C an..3 10 Maritime

20 Rail 30 Road 80 Inland waterway See code list EDIFACT for other codes.

O 8066 Mode of transport C an..17

O C228 TRANSPORT MEANS C O 8179 Type of means of transport identification C an..8 O 8178 Type of means of transport C an..17

X C040 CARRIER C X 3127 Carrier identification C an..17 X 1131 Code list qualifier C an..3 X 3055 Code list responsible agency, coded C an..3 X 3128 Carrier name C an..35

X 8101 TRANSIT DIRECTION, CODED C an..3

X C401 EXCESS TRANSPORTATION INFORMATION C X 8457 Excess transportation reason, coded M an..3 X 8459 Excess transportation responsibility, coded M an..3 X 7130 Customer authorization number C an..17

O C222 TRANSPORT IDENTIFICATION C O 8213 Id of means of transport identification C an..9 O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O 8212 Id of means of transport C an..35 O 8453 Nationality of means of transport, coded C an..3

X 8281 TRANSPORT OWNERSHIP, CODED C an..3


51


Conditional group repeat : 10 SEGMENT : DTM DATE / TIME / PERIOD SEGMENT STATUS : Conditional segment repeat : 1 FUNCTION : To specify date, and/or time information of the identified means of transport. NOTES : All specified dates/times should be in the format 'CCYYMMDD'/'hhmm' unless all



R C507 DATE/TIME/PERIOD M R 2005 Date/time/period qualifier M an..3 178 Arrival date/time, actual



203 CCYYMMDDhhmm 204 CCYYMMDDhhmmss See code list EDIFACT for other values


52


Conditional group repeat : 10 SEGMENT : CDI PHYSICAL OR LOGICAL STATE SEGMENT STATUS : Conditional segment repeat : 10 FUNCTION : To report the state of the mode and means of transport. NOTES : Use the code list of the EDIFACT transport group


R 7001 PHYSICAL OR LOGICAL STATE QUALIFIER M an..3 3 Upon arrival condition

R C564 PHYSICAL OR LOGICAL STATE INFORMATION M O 7007 Physical or logical state, coded C an..3 1 Arrived

116 Missing 251 Date not respected 266 Standing over: delay See recommendation 24 of UN/ECE Trade Facilitation

O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 6 UN/ECE

O 7008 Physical or logical state C an..70


53

4.5.3 Detailed segment description - Detail section GROUP : Group 16 : CPS - SG17 – SG22

Conditional group repeat : 9999 SEGMENT : CPS CONSIGNMENT PACKING SEQUENCE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To identify the sequence in which physical packing is presented in the consignment,

and optionally to identify the hierarchical relationship between packing layers. NOTES :


R 7164 HIERARCHICAL ID NUMBER M an..12

O 7166 HIERARCHICAL PARENT ID C an..12

O 7075 PACKAGING LEVEL, CODED C an..3 1 Inner

2 Intermediate 3 Outer


54

GROUP : Group 17 : PAC - QVR - SG18

Conditional group repeat : 9999 SEGMENT : PAC PACKAGE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To describe the number and type of packages/physical units. NOTES :


O 7224 NUMBER OF PACKAGES C n..8

X C531 PACKAGES DETAILS C X 7075 Packaging level, coded C an..3 X 7233 Packaging related information, coded C an..3 X 7073 Packaging terms and conditions, coded C an..3

O C202 PACKAGE TYPE C O 7065 Type of packages identification C an..17 BG Bag

BB Bobbin BE Bundle BX Box CL Coil CS Case NE Unpacked PA Packet PAL Pallet PK Package RO Roll SM Sheet See code list EDIFACT for other codes

O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 58 EUROFER

91 Assigned by seller or seller's agent 92 Assigned by buyer or buyer's agent

O 7064 Type of packages C an..35

X C402 PACKAGE TYPE IDENTIFICATION C O 7077 Item description type, coded M an..3 O 7064 Type of packages M an..35 O 7143 Item number type, coded C an..3 X 7064 Type of packages C an..35 X 7143 Item number type, coded C an..3

X C532 RETURNABLE PACKAGE DETAILS C O 8395 Returnable package freight payment responsibility, coded C an..3 X 8393 Returnable package load contents, coded C an..3


55

GROUP : Group 17 : PAC - QVR - SG18

Conditional group repeat : 9999 SEGMENT : QVR QUANTITY VARIANCES SEGMENT STATUS : Conditional segment repeat : 1 FUNCTION : To identify quantity variances between the number of units received and the number

of units expected or planned. NOTES : In element 6064 the difference between the received number of units and the relevant

units defined in the quantity qualifier. In element 6063 the code indicates to which number of packages the difference is calculated. E.g. despatched number of packages is 5, received number of packages is 7: in element 6064, 2 packages are mentioned and in element 6063, code 12 is used to indicate that the difference is calculated based on the despatch quantity specified in the DESADV message.


R C279 QUANTITY DIFFERENCE INFORMATION C R 6064 Quantity difference M n..15 R 6063 Quantity qualifier C an..3 12 Despatch quantity

21 Ordered quantity 190 Despatch note quantity See code list EDIFACT for other codes

O 4221 DISCREPANCY, CODED C an..3

O C960 REASON FOR CHANGE C O 4295 Change reason, coded C an..3 O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 58 EUROFER


O 4294 Change reason C an..35


56

GROUP : Group 18 : PCI - RFF – SG19 – SG20

Conditional group repeat : 999 SEGMENT : PCI PACKAGE IDENTIFICATION SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To specify markings and labels on individual packages or physical units. NOTES :


R 4233 MARKING INSTRUCTIONS, CODED C an..3 16 Buyer's instruction

17 Seller's instruction 18 Carrier's instruction 19 Legal requirements 20 Industry instruction See code list EDIFACT for other codes

O C210 MARKS & LABELS C R 7102 Shipping marks M an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35

X 8275 CONTAINER/PACKAGE STATUS, CODED C an..3

O C827 TYPE OF MARKINGS C O 7511 Type of marking, coded C an..3 O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3


57

GROUP : Group 20 : GIN – SG21

Conditional group repeat : 999 SEGMENT : GIN GOODS IDENTITY NUMBER SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To give specific identification numbers, either as single numbers or ranges, for the

packages or physical units being received or missing. NOTES : Only package identification can be used in this segment of the segment group.


R 7405 IDENTITY NUMBER QUALIFIER M an..3 BN Serial number

ML Marking label number PN Part number See code list EDIFACT for other codes

R C208 IDENTITY NUMBER RANGE M R 7402 Identity number M an..35 O 7402 Identity number C an..35

O C208 IDENTITY NUMBER RANGE C O 7402 Identity number M an..35 O 7402 Identity number C an..35





58

GROUP : Group 21 : CDI- INP

Conditional group repeat : 10 SEGMENT : CDI PHYSICAL OR LOGICAL STATE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To report the state of the identified package upon receipt. NOTES :



R C564 PHYSICAL OR LOGICAL STATE INFORMATION M O 7007 Physical or logical state, coded C an..3 2 Missing

3 Wrong identification 4 Damaged See code list EDIFACT for other values

O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O 7008 Physical or logical state C an..70


59


Conditional group repeat : 10 SEGMENT : INP PARTY TO INSTRUCTION SEGMENT STATUS : Conditional segment repeat : 5 FUNCTION : To specify parties to an instruction and where relevant, the instruction. NOTES : The instructions are always directed to the receiver of the RECADV message.


X C849 PARTIES TO INSTRUCTION C X 3301 Party enacting instruction identification C an..17 X 3285 Recipient of the instruction identification C an..17

O C522 INSTRUCTION C R 4403 Instruction qualifier M an..3 1 Action required

2 Party instructions See code list EDIFACT for other values

O 4401 Instruction, coded C an..3 AA Send credit note

AG Send replacement AH Pick-up See code list EDIFACT for other values

O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O 4400 Instruction C an..35

X C850 STATUS OF INSTRUCTION C X 4405 Status, coded C an..3 X 3036 Party name C an..35

X 1229 ACTION REQUEST/NOTIFICATION, CODED C an..3


60

GROUP : Group 22 : LIN - PIA - IMD – QTY - QVR - DTM - PRI – SG23 - SG24 -

SG26 – SG28 – SG29 Conditional group repeat : 9999

SEGMENT : LIN LINE ITEM SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To identify a line item by the line number and an item number. NOTES :


R 1082 LINE ITEM NUMBER C n..6

O 1229 ACTION REQUEST/NOTIFICATION, CODED C an..3

R C212 ITEM NUMBER IDENTIFICATION C R 7140 Item number C an..35 R 7143 Item number type, coded C an..3 BP Buyer's part number

IN Buyer's item number PO Purchase order number SA Supplier's article number SN Serial number See code list EDIFACT for other codes

O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3

X C829 SUB-LINE INFORMATION C X 5495 Sub-line indicator, coded C an..3 X 1082 Line item number C n..6

X 1222 CONFIGURATION LEVEL C n..2

X 7083 CONFIGURATION, CODED C an..3


61



SEGMENT : PIA ADDITIONAL PRODUCT ID SEGMENT STATUS : Conditional segment repeat : 10 FUNCTION : To specify additional or substitutional item identification codes. NOTES :


R 4347 PRODUCT ID FUNCTION QUALIFIER M an..3 1 Additional information

5 Product identification

R C212 ITEM NUMBER IDENTIFICATION M R 7140 Item number C an..35 R 7143 Item number type, coded C an..3 BP Buyer's part number

CV Customs article number (tariff code number) EF Material code GS General specification number MF Manufacturer's article number NB Batch number PL Purchaser's order line number PO Purchase order number SA Supplier's article number UA Ultimate customer's article number See code list EDIFACT for other codes

O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3

O C212 ITEM NUMBER IDENTIFICATION C R 7140 Item number C an..35 R 7143 Item number type, coded C an..3 O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3




62





63



SEGMENT : IMD ITEM DESCRIPTION SEGMENT STATUS : Conditional segment repeat : 25 FUNCTION : To describe an item in either an industry or free format. NOTES :


O 7077 ITEM DESCRIPTION TYPE, CODED C an..3 C Code (from industry code list)

F Free-form S Structured (from industry code list) X Semi-structured (code+text)

R 7081 ITEM CHARACTERISTIC , CODED C an..3 8 Product (for final product)

13 Quality 38 Grade See code list EDIFACT for other codes

R C273 ITEM DESCRIPTION C R 7009 Item description identification C an..17 See Eurofer code lists or industry code lists for values

O 1131 Code list qualifier C an..3 Identification of the code list

O 3055 Code list responsible agency, coded C an..3 58 EUROFER

91 Assigned by seller or seller's agent 92 Assigned by byer or buyer's agent

O 7008 Item description C an..35 Plain language description

O 7008 Item description C an..35 O 3453 Language, coded C an..3

X 7383 SURFACE/LAYER INDICATOR, CODED C an..3


64



SEGMENT : QTY QUANTITY SEGMENT STATUS : Conditional segment repeat : 10 FUNCTION : To specify quantity information concerning the product. NOTES :


R C186 QUANTITY DETAILS M R 6063 Quantity qualifier M an..3 12 Despatch quantity

47 Invoiced quantity 48 Received quantity

123 Surplus goods 124 Damaged goods 126 Lost goods 194 Received and accepted See code list EDIFACT for other values

R 6060 Quantity M n..15 R 6411 Measure unit qualifier C an..3 KGM Kilogram

MTK Square metre MTR Metre NAR Number of articles NMP Number of packages PCE Piece TNE Tonne See code list EDIFACT for other values


65



SEGMENT : QVR QUANTITY VARIANCES SEGMENT STATUS : Conditional segment repeat : 10 FUNCTION : To identify quantity variances between quantity per item received and the quantity per

item expected or planned. NOTES : In element 6064 the difference between the received quantity and the relevant

quantity defined in the quantity qualifier. In element 6063 the code indicates to which quantity the difference is calculated.


R C279 QUANTITY DIFFERENCE INFORMATION C R 6064 Quantity difference M n..15 R 6063 Quantity qualifier C an..3 12 Despatch quantity

21 Ordered quantity 190 Despatch note quantity See code list EDIFACT for other codes






66


Conditional group repeat : 10 SEGMENT : CDI PHYSICAL OR LOGICAL STATE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To report the state of the identified product upon receipt. NOTES :







67













68



goods being received or missing. NOTES : Identification of product units.



ML Marking label number See code list EDIFACT for other codes







69


Conditional group repeat : 10 SEGMENT : CDI PHYSICAL OR LOGICAL STATE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To report the state of the identified goods upon receipt. NOTES :







70













71


Conditional group repeat : 10 SEGMENT : RFF REFERENCE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To specify a reference. NOTES : This segment is used for referencing documents, relating to all the specified items in

the detail section.


R C506 REFERENCE M R 1153 Reference qualifier M an..3 AAN Delivery schedule (instruction) number

ADA Buyer's item number CO Buyer’s order number CR Customer reference number CT Contract number LC Letter of credit LI Line's item number UC Ultimate customer's reference number UO Ultimate customer's order number VN Order number (Vendor) See code list EDIFACT for other codes

R 1154 Reference number C an..35 O 1156 Line number C an..6 X 4000 Reference version number C an..35


72


Conditional group repeat : 10 SEGMENT : DTM DATE / TIME / PERIOD SEGMENT STATUS : Conditional segment repeat : 1 FUNCTION : To specify date, and/or time, period of the referenced document. NOTES : All specified dates/times should be in the format 'CCYYMMDD'/'hhmm' unless all



R C507 DATE/TIME/PERIOD M R 2005 Date/time/period qualifier M an..3 171 Reference date/time





73

GROUP : Group 29 : PCI - QTY - QVR - SG30 – SG31

Conditional group repeat : 9999 SEGMENT : PCI PACKAGE IDENTIFICATION SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To specify markings and labels on individual packages or physical units. NOTES :


R 4233 MARKING INSTRUCTIONS, CODED C an..3 16 Buyer's instruction

17 Seller's instruction 18 Carrier's instruction 19 Legal requirements 20 Industry instruction See code list EDIFACT for other codes

O C210 MARKS & LABELS C R 7102 Shipping marks M an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35 O 7102 Shipping marks C an..35

X 8275 CONTAINER/PACKAGE STATUS, CODED C an..3

O C827 TYPE OF MARKINGS C O 7511 Type of marking, coded C an..3 O 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3


74


Conditional group repeat : 9999 SEGMENT : QTY QUANTITY SEGMENT STATUS : Conditional segment repeat : 1 FUNCTION : To specify a pertinent quantity. NOTES :


R C186 QUANTITY DETAILS M R 6063 Quantity qualifier M an..3 52 Quantity per pack


R 6060 Quantity M n..15 R 6411 Measure unit qualifier C an..3

NAR Number of articles NBB Number of bobbins NMP Number of packs NRL Number of rolls SH Sheet PCE Piece See code list EDIFACT for other values


75


Conditional group repeat : 9999 SEGMENT : QVR QUANTITY VARIANCES SEGMENT STATUS : Conditional segment repeat : 1 FUNCTION : To identify quantity variances between the number of units received and the number

of units expected or planned. NOTES : In element 6064 the difference between the received number of units and the relevant

units defined in the quantity qualifier. In the element 6063 the codes indicates to which number of packages the difference is calculated.


R C279 QUANTITY DIFFERENCE INFORMATION C R 6064 Quantity difference M n..15 R 6063 Quantity qualifier C an..3 52 Quantity per pack






76



packages being received or missing. NOTES : Used for the package identification numbers.



ML Marking label number See code list EDIFACT for other codes







77


Conditional group repeat : 10 SEGMENT : CDI PHYSICAL OR LOGICAL STATE SEGMENT STATUS : Mandatory segment repeat : 1 FUNCTION : To report the state of the identified packages upon receipt. NOTES :







78













79

GROUP : SEGMENT : UNT MESSAGE HEADER SEGMENT STATUS : Mandatory 1 FUNCTION : Service segment ending a message, giving the totals number of segments. NOTES : This segment would normally be added as part of the translation process. It has been

included for completeness.


R 0074 NUMBER OF SEGMENTS IN A MESSAGE M n..6 R 0062 MESSAGE REFERENCE NUMBER M an..14 Unique message number assigned by the sender


80

5. EXAMPLES 5.1. Example of a receiving advice of Oy Ostomet Ab (Finland)

The head quarters of Oy Ostomet Ab has ordered two articles to its plant situated in Turku from the Tekoteräs Oy. These articles were delivered with the despatch advice 9910786/13-1, and the waybill 000072385. The article numbers of the order items are A4863 and E3277. The articles were packed in the boxes identified as P1153, P1154 and P1155. The delivery was received and inspected on the 23rd of June 1999. With the receiving advice 4853/99 Oy Ostomet A informs Tekoteräs Oy about the arrival of the delivery , the damages and the discrepancies. The box P1153 has not arrived and there is one piece of the article E3277 damaged in box P1154. On the next pages an example is presented of the translation of a receiving advice of Oy Ostomet Ab.


81

Oy Ostomet Ab VASTAANOTTOILMOITUS

Nro 4853/99 Pvm 23.6.1999

Vastaanottaja Oy Ostomet Ab Turun tehdas Terästie 18 20810 TURKU

Lähettäjä Tekoteräs Oy Alasintie 6 3382 TAMPERE

Tilaaja Oy Ostomet Ab Pääkonttori Tehtaankatu 31 02170 ESPOO

Lähetysluettelon nro 9910786/13-1

Rahtikirjan nro 000072385

Määräpaikka Turku

Purkupaikka Turku/Raide 4

Kuljetusliike VR

Rekisterinumero ym.

Huomautuksia Laatikko P1153 ei ole saapunut muun toimituksen mukana. Laatikossa P1154 yksi kappale artikkelia E3277 vaurioitunut. Ilmoituksen antoi: M.Lehtinen


82

EDI message Information in the document and remarks

HEADER - SERVICE SEGMENT UNH+ME000001+RECADV:D:97A:UN' First message in an interchange is a receiving advice message.

HEADER SECTION BGM+632+4853/99+9' Receiving advice message with number 4953/99. (Nro) DTM+137:19990623:102' Date of the receiving advice message. (Pvm) RFF+AAK:9910786/13-1' Despatch advice number (Lähetysluettelon nro) RFF+AAM:000072385' Way bill number. (Rahtikirjan nro) NAD+BY+692350::91++OY OSTOMET AB:PÄÄKONTTORI+ TEHAANKATU 31+ESPOO++02170+FI’'

BY is used for the buyer. (Tilaaja)

NAD+CZ+007721::92++TEKOTERÄS OY+ALASINTIE 6+ TAMPERE++33820+FI’

CZ is used for consignor. (Lähettäjä)

NAD+CN+692352::91++OY OSTOMET AB:TURUN TEHDAS+TERÄSTIE 18+TURKU++20810+FI’

CN is used for the consignee. (Vastaanottaja)

LOC+8+:::TURKU’ Place of destination. (Määräpaikka) LOC+4+:::TURKU+:::RAIDE 4’ Goods receipt place. (Purkupaikka) CTA+LB+/M.LEHTINEN’ Contact address (Ilmoituksen antoi) NAD+CA+++VR’ CA is used for the carrier. (Kuljetusliike) TDT+20++20' Transport is done by rail.

DETAIL SECTION (Packaging information) CPS+1++3' Hierarchical level 1, outer packaging level.

Packaging information - first package PAC+1’' PCI+17' Dummy segment, package idenification. GIN+BN+P1153' Serial number of the package. (Huomautuksia) CDI+3+2::LAATIKKO P1153 EI OLE SAAPUNUT MUUN TOIMITUKSEN MUKANA’

Status – missing package.

Packaging information – second package

PAC+1' PCI+17' Dummy segment, package idenification. GIN+BN+P1154' Serial numberof the package. (Huomautuksia) LIN+1++E3277:SA’ Article number (Huomautuksia) QTY+124:1:PCE' One article damaged. (Huomautuksia) CDI+3+4:::VAURIOTUNUT’ Status - damaged article.

TRAILER - SERVICE SEGMENT UNT+025+ME000001' First message in an interchange is a receiving advice message.


83

All information provided in this documentation is provided “as is” without any warranties of any kind including warranties of accuracy, fitness for a particular purpose, or non-infringement or intellectual property. EUROFER shall not be held responsible for any errors or any loss resulting from any use of this document or the specification herein. The materials contained in this document may be copied provided that ALL copies retain the copyright and any other proprietary notices contained on the materials. No material may be modified, edited or taken out of context such as its use creates a false or misleading statement or impression as to the positions, statements or actions of the publisher. ©2001 EUROFER. All rights reserved. All countries.

recadv receiving advice message - · pdf filerecadv receiving advice message subset for...

Documents