RECADV Receiving Advice Message Subset for Application in the European Steel Industry

Transcription

1 RECADV Receiving Advice Message Subset for Application in the European Steel Industry Version September 1999 Corporate Factory Ph. D. Sarraute EDIFER WORKING GROUP - Message development

2 RECEIVING ADVICE MESSAGE (Table of Contents) 0. INTRODUCTION 2 1. BACKGROUND INFORMATION Functional use of the message defined by EDIFACT Functional use of the message recommended by EUROFER 4 2. DATA MODEL Data Model Format Data Model Diagram Data Model Entities Data Model Relationships Data Model Attributes SCOPE Functional Definition Field of Application Principles Message Usage MESSAGE DEFINITION Message Structure Mapping of the Data Model to the Message Branching Diagram of the Segments used by Eurofer General Description of the Message - Subset of Eurofer Detailed Description of the Message - Subset of Eurofer EXAMPLES Example of a receiving advice of Oy Ostomet Ab (Finland) 80 1

3 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. 2

4 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. 3

5 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). 4

6 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. 5

7 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

8 2.2 Data Model Diagram 1 Receiving advice Relates to 0,1 0,1 0,1 Transport information Relates to Relates to 0,N Package 1 Contains Refers to 1,N 1,N Product unit 0,N 0,1 Order Information Reference to Reference to Company Message / Document 7

9 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. 8

10 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 ADVICE TRANSPORT INFORMATION PACKAGE This entity contains the general information about a receiving of steel products at the consignee. The consignee may be an intermediate or final destination. This entity specifies the details of the mode and means of 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. 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... 9

11 ORDER INFORMATION COMPANY MESSAGE & DOCUMENT A product unit can be related to an order, an order item or to 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". An organisation with whom we deal for whatever purpose. This can be the buyer, sales agency, inspection authority, consignor, consignee, manufacturer, freight forwarder, etc.... This entity contains all the references to another message or document. For example order, despatch advice. 10

12 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. 11

13 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. 12

14 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). 13

15 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). 14

16 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. 15

17 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 Field of application This message provides the definition of the Eurofer receiving advice message to be used in Electronic Data Interchange between trading partners 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. 16

18 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. 17

19 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 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 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. 18

20 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 HEADING SECTION COMMENTS BGM DTM ALI To identify the Receiving advice message by its number. To specify general date/time/period related to the whole message. To specify that the message is subject to special conditions due to origin, customs preference or commercial factors. Mandatory. Must be used at least once to identify the date of the receiving advice. Not used. GROUP 1 RFF DTM To specify referencing documents and their date, related to the whole message. To identify the referenced document. To specify the date/time of the referenced document. Only to be used if the information is relevant for all the items. GROUP 2 To identify the discrepancies with the documentary requirements related to the whole message. DOC To identify documents where a discrepancy occurs. Not used. GROUP 3 CDI INP To report the physical or logical state of the document upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. Not used. GROUP 4 NAD LOC To identify the parties (companies) relevant to the whole message. Function, name and address of the company. To indicate locations related to the company. Must be used to specify at least the recipient of the goods. 19

21 SEGMENT GROUP SEGMENT FUNCTION COMMENTS GROUP 5 GROUP 6 RFF DTM CTA COM To specify referencing documents and their date related to the company. To identify the referenced document related to the company. To specify the date/time of the referenced document. To give contact details of the company. To identify to whom communication should be directed. To identify communication type and numbers. Not used GROUP 7 GROUP 8 TOD CDI INP To report on discrepancies on the terms of delivery. To indicate the terms of delivery. To report the physical or logical state of the document upon receipt and to give the appropriate instructions To report a discrepancy on the terms of delivery. To give instructions to correct the discrepancy. Not used. Not used. GROUP 9 LOC CDI To report on discrepancies on locations related to terms of delivery. To indicate locations relevant to the TOD segment. To report discrepancy on locations. Not used. GROUP 10 TDT DTM CDI To specify details of the mode and means of transport and location relevant to the whole receiving advice. To specify the carriage, and the mode and means of transport of the goods being despatched. To give date/time information of the identified means of transport (e.g. date/time of arrival). To report the state of the mode of transport. GROUP 11 GROUP 12 GROUP 13 EQD CDI INP SEL CDI To identify the equipment with which a problem has occurred. To identify the specific equipment. To report the physical or logical state of the equipment upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. To identify the seal number and reporting anomalies. To specify a seal number connected to the equipment named in the EQD segment. To report the anomaly. Not used. Not used. Not used. 20

22 SEGMENT GROUP SEGMENT FUNCTION COMMENTS GROUP 14 GROUP 15 EQA CDI INP To identify the equipment attached with which a problem has occurred. To identify the equipment attached. To report the physical or logical state of the attached equipment upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. Not used. Not used. DETAIL SECTION GROUP 16 CPS To provide details of all package levels and or the individual items received. To identify the sequence in which packing of the consignment is presented. GROUP 17 PAC QVR To identify packaging, marks and numbers, quantities about packing. To specify the number and type of packages of the arrived goods. To identify the quantity variances between the number of units received and expected or planned. The group should only be used if information is required on packaging level. GROUP 18 GROUP 19 PCI RFF CDI INP To specify markings, labels and packing numbers and related anomalies. To specify markings and/or labels used on individual packages as described in the PAC segment. To reference the package identification e.g. master label number. To report the physical or logical state of the package upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. Not used. Not used. GROUP 20 GROUP 21 GIN CDI INP To give package identification number and related anomalies. To provide the identity number of the packages being received or missing. To report the physical or logical state of the identified package upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. 21

23 SEGMENT GROUP SEGMENT FUNCTION COMMENTS GROUP 22 LIN PIA IMD QTY QVR DTM PRI To provide details of the individual received items. To identify the product being received. To provide additional product identification. To describe the product being received. To give quantity information, such as received and despatched quantity, about the product. To identify quantity variances between quantity received and quantity expected or planned. To provide date/time information related to the line item. To provide price information related to the line item. The group is used if information is needed at product level. Not used. Not used. GROUP 23 CDI INP To report the physical or logical state of the product upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. GROUP 24 To identify the discrepancies with the documentary requirements related to the line item. DOC To identify documents where a discrepancy occurs. Not used. GROUP 25 CDI INP To report the physical or logical state of the document upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. Not used. GROUP 26 GROUP 27 GIN CDI INP To give identification number and related anomalies. To provide the identity number of the goods being received or missing. To report the physical or logical state of the identified package upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. GROUP 28 RFF DTM To specify referencing documents and their date, related to the line item. To identify the referenced document. To specify the date/time of the referenced document. 22

24 SEGMENT GROUP SEGMENT FUNCTION COMMENTS GROUP 29 GROUP 30 PCI QTY QVR CDI INP To specify markings, labels and packing numbers and related anomalies. To specify markings and/or labels used on individual packages as described in the PAC segment. To specify the quantity per package. To identify quantity variances quantity per package received and quantity per package expected or planned. To report the physical or logical state of the package upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. Not used. GROUP 31 GROUP 32 GIN CDI INP To give package identification number and related anomalies. To provide the identity number of the packages being received or missing. To report the physical or logical state of the identified package upon receipt and to give the appropriate instructions To report the physical and logical state. To give instructions to correct the discrepancy. SUMMARY SECTION CNT To provide control totals by the sender for checking by the receiver. Not used. 23

25 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 Arrival date/time Group 10 DTM 2380 Transport arrival status Group 10 CDI 7007 Code form or clear form can be used. 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 24

26 ATTRIBUTE SEGMENT GROUP SEGMENT TDID 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 Use the relevant code for Use the relevant code for Gross weight of the package Group 22 QTY 6060 Use the relevant code for 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 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 7140 Use the relevant code for element GIN 7402 Use the relevant code for element Article number Group 22 LIN or 7140 Use the relevant code for PIA element Gross weight of the product unit Group 22 QTY 6060 Use the relevant code for Received quantity Group 22 QTY 6060 Use the relevant code for Product Type Group 22 IMD 7009 or Use of code list Eurofer P01. Use code 8 in element Product unit status Group 23 CDI 7007 Quantity differences of product unit Group 22 QVR C279 25

27 ATTRIBUTE SEGMENT GROUP SEGMENT TDID Data Element REMARKS Entity : ORDER INFORMATION Customer's order number Group 1 or Group 22 or Group 28 Customer's order date Group 1 or Group 28 Customer's order item number Group 1 or Group 22 or Group 28 Supplier's order number Group 1 or Group 28 Supplier's order item number Group 1 or Group 28 RFF LIN Use the relevant code for Use the relevant code for RFF 1154 Use the relevant code for 1153 DTM 2380 DTM segment following the RFF in the segment group. RFF LIN Part number Group 22 LIN or PIA Use the relevant code for Use the relevant code for RFF 1154 Use the relevant code for RFF 1154 Use the relevant code for RFF 1154 Use the relevant code for Use the relevant code for Entity : COMPANY Company code, name and address Group 4 NAD 1154 Use the relevant code for Contact information Group 6 CTA C056 Use the relevant code for Communication contact Group 6 COM C076 Internal place/location related to the consignee Group 4 LOC C517 Use the relevant code for Entity : MESSAGE / DOCUMENT Message / document type Group 1 or Group 28 Message / document number Group 1 or Group 28 Message /document date Group 1 or Group 28 RFF 1153 RFF 1154 DTM 2380 DTM segment following the RFF in the segment group. 26

28 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 8 C 10 X CDI Physical and logical state M 1 X INP Parties to instruct C 5 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 27

29 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 12 C 10 X CDI Physical and logical state M 1 X INP Parties to instruct C 5 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 X SEGMENT GROUP 15 C 10 X CDI Physical and logical state M 1 X INP Parties to instruct C 5 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 X SEGMENT GROUP 19 C 10 X CDI Physical and logical state M 1 X INP Parties to instruct C 5 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 O SEGMENT GROUP 23 C 10 R 66 CDI Physical and logical state M 1 O 67 INP Parties to instruct C 5 28

30 USG.IND. PAGE NUM. TAG NAME STATUS REPEATS GROUP REPEATS X SEGMENT GROUP 24 C 10 X DOC Document / message details M 1 X SEGMENT GROUP 25 C 10 X CDI Physical and logical state M 1 X INP Parties to instruct C 5 O SEGMENT GROUP 26 C 99 R 68 GIN Goods identity number M 1 O SEGMENT GROUP 27 C 10 R 69 CDI Physical and logical state M 1 O 70 INP Parties to instruct C 5 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 SEGMENT GROUP 30 C 10 X CDI Physical and logical state M 1 X INP Parties to instruct C 5 O SEGMENT GROUP 31 C 10 R 76 GIN Goods identity number M 1 O SEGMENT GROUP 32 C 10 R 77 CDI Physical and logical state M 1 O 78 INP Parties to instruct C 5 X CNT Control total C 1 R 79 UNT Message trailer M 1 29

31 EUROFER RECADV RECEIVING ADVICE MESSAGE VERSION - SEPTEMBER 1999 UN/EDIFACT DIRECTORY : D97.A Leve l 00 UNH BG M M 1 M 1 UNT M 1 G01 G04 G10 G16 01 C 10 DTM RFF M 10 M 1 M 10 NAD M 1 C 10 TDT M 1 C 9999 CPS M 1 02 DTM C 1 LOC C 10 G05 C 10 RFF M 1 G06 C 10 CTA M 1 DTM C 10 CDI C 10 G1 7 C 9999 PAC M 1 G22 C 9999 LIN M 1 03 CO M C 5 QV R C 1 See page 2 / part 1 PI A C 10 See page 2 / part 2 Branching Diagram Page 1 EUROFER RECADV RECEIVING ADVICE MESSAGE VERSION - SEPTEMBER 1999 UN/EDIFACT DIRECTORY : D97.A Level See page 1 See page 1 G18 G23 G26 G28 G29 03 C 999 PCI M 1 IMD C 25 QTY C 10 QVR C 10 C 10 CDI M 1 C 99 GIN M 1 C 10 RFF M 1 C 9999 M 1 PCI G20 G27 G31 04 C 999 GIN M 1 INP C 5 C 10 CDI M 1 DTM C 1 QTY C 1 QVR C 1 C 10 GIN M 1 G21 G32 05 C 10 CDI M 1 IN P C 5 C 10 CDI M 1 06 INP INP C 5 C 5 Branching Diagram Page 2 30

32 4.4 General description of the message - subset of Eurofer 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. 31

33 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 ; RECADV D A 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. Segment DTM, Date/time/period 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. 32

34 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. Segment RFF, Reference 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. Segment DTM, Date/time/period 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. 33

35 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 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. 34

36 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. Segment QVR, Quantity variances 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 A segment to give instructions (e.g. replace). Segment group 26 : GIN-SG27 A group of segments giving goods identification numbers and if required the related anomalies. Segment GIN, Goods identity number A segment providing identity numbers of goods being received or missing. 35