ORDERS Purchase Order Message Subject for application in the European Steel Industry

ORDERS Purchase Order Message Subject for application in the European Steel Industry Version January 2000 Corporate Factory Ph. D. Sarraute EDIFER WORKING GROUP - Message development

PURCHASE ORDER MESSAGE (Table of Contents) 0. INTRODUCTION 2 1. DATA MODEL 3 1.1 Data Model Format 3 1.2 Data Model Diagram 4 1.3 Data Model Entities 6 1.4 Data Model Relationships 8 1.5 Data Model Attributes 11 2. SCOPE 19 2.1 Functional Definition 19 2.2 Field of Application 22 2.3 Principles 22 2.4 Message Usage 23 3. MESSAGE DEFINITION 25 3.1 Message Structure 25 3.2 Mapping of the Data Model to the Message 26 3.3 Branching Diagram of the Segments used by Eurofer 34 3.4 General Description of the Message - Subset of Eurofer 42 3.5 Detailed Description of the Message - Subset of Eurofer 55 4. EXAMPLES 137 4.1. Example of an order from Miele to Krupp Hoesch Stahl AG 137 4.2. Example of an order from Watson to British Steel 139 4.3. Example of an order from The Titan industrial corporation 142 to C.S.I. Planos Page 1

PURCHASE ORDER MESSAGE 0. INTRODUCTION This document provides the definition of the EUROFER subset of the ORDERS message based on the UN standard ORDERS message of the UN/EDIFACT directory D97.A. This document replaces previous version dated 01.03.1996, based on the EDIFACT directory D95B. 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 ORDERS, the used segments are indicated. This is followed by a detailed description of the segments used by Eurofer. - Examples of the Eurofer ORDERS message are provided to clarify the nderstanding of the message description. Page 2

1. DATA MODEL 1.1 Data Model Format The data model has been created, to make it possible for potential users to understand the Eurofer subset for the Orders message. The data model provides the following information : - contents of the information (data elements) that can occur in the messages, - 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 order sheet); 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 1.2. Page 3

1.2 Data Model Diagram Has 1 Order 1 Has 0,N Order Allowance & Charge 1 Consists of 0,1 Invoicing Information 1,N Order Item Remark 0,N Has 1 1 Order Item 1 1 1 1 Has Has 0,N 0,N Scheduled by 0,N 1 Has 0,N Has 0,N Document Required Source product Unique Identification Delivery Schedule Detail Labelling Packaging Information Price Information 1 Has Has 0,N 0,N Equipment 0,1 Has 1 Transport Price Allowance & Charge Reference to Reference to Company Rules & Agreements Page 4

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 Order and Order item 1. In the direction from Order to Order item. An Order can have one or many Order items. 2. In the direction from Order item to Order An Order item always belongs to one Order. Page 5

1.3. Data model entities Because the data entities Company, Rules & Agreements 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 ORDER INVOICING INFORMATION ORDER ALLOWANCE & CHARGE ORDER ITEM DELIVERY SCHEDULE DETAIL LABELLING PACKAGING INFORMATION PRICE INFORMATION PRICE ALLOWANCE & CHARGE ORDER ITEM REMARK DOCUMENT REQUIRED SOURCE PRODUCT UNIQUE IDENTIFICATION TRANSPORT EQUIPMENT The related data entities COMPANY RULES & AGREEMENTS ORDER This entity contains general information about the goods and services ordered under the conditions agreed between the buyer and the seller. INVOICING This entity contains the general information concerning INFORMATION invoicing, such as : - the invoicee - the payment terms and conditions - the invoicing currency. ORDER ALLOWANCE & CHARGE This entity specifies an allowance or charge, if necessary the calculation sequence, applicable to the total order and not at the order item level. Page 6

ORDER ITEM This entity contains the following information of an order item : - product specifications of the ordered product - shipping information of the ordered product. DELIVERY SCHEDULE DETAIL This entity specifies the day/period when a requested quantity must be delivered to the consignee. LABELLING This entity contains the following information of an order item : PACKAGING - packaging information INFORMATION - labelling information PRICE INFORMATION PRICE ALLOWANCE & CHARGE ORDER ITEM REMARK DOCUMENT REQUIRED This entity identifies the relevant pricing information for the products ordered, e.g. price type and amount, currency and date/time/period information related to the price, such as period of validity. This entity specifies an allowance or charge, applicable to the price or already included in the net price, and where necessary the calculation sequence. This entity is used to specify all the kinds of order item remarks, such as production, package, labelling and expedition remarks. This entity indicates the type of documents that are required for the delivery of the ordered goods. SOURCE This entity contains the identification of the final-or pre-product PRODUCT list or the identification numbers, such as Serial number, Slab UNIQUE number, of the products chosen by the buyer for the order item. IDENTIFICATION TRANSPORT This entity specifies the mode and means of transport, transport locations and relevant dates for transportation of the goods. EQUIPMENT This entity contains the type and measurements of the requested equipment for the transportation of the products ordered. COMPANY RULES & AGREEMENTS Any organisation with whom we deal for whatever purpose. This can be the buyer, the selling agency, inspection authority consignee and so on. This entity contains all the rules and agreements that are valid and requested by the buyer for the production of steel products and shipping. For example description of the product, despatch limitations. Page 7

1.4. Data model relationships ORDER - INVOICING INFORMATION (relation : has - 1/0,1) - Direction from Order to Invoicing information. An Order may not have or can have one Invoicing information. - Direction from Invoicing information to Order. An Invoicing information relates to only one Order. ORDER - ORDER ALLOWANCE & CHARGE (relation : has - 1/0,N) - Direction from Order to Order Allowance & Charge. A Order may not have Order Allowance & Charge, or can have one or more Order Allowance & Charge. - Direction from Order Allowance & Charge to Order. An Order Allowance & Charge belongs to only one Order. ORDER - ORDER ITEM (relation : consists of - 1/1,N) - Direction from Order to Order item. An Order must consist of one or more Order item. - Direction from Order item to Order. An Order item belongs to one Order. ORDER ITEM - DELIVERY SCHEDULE DETAIL (relation : scheduled by - 1/0,N) - Direction from Order item to Delivery schedule detail. An Order item may not have a Delivery schedule detail, or can have one or more Delivery schedule detail. - Direction from Delivery schedule detail to Order item. A Delivery schedule detail belongs to only one Order item. ORDER ITEM - LABELLING PACKAGING INFORMATION (relation : has - 1/0,N) - Direction from Order item to Labelling packaging information. An Order item may not have Labelling packaging information, or can have one or more Labelling packaging information. - Direction from Labelling packaging information to Order item. A Labelling packaging information belongs to one Order item. Page 8

ORDER ITEM - PRICE INFORMATION (relation : has - 1/0,N) - Direction from Order item to Price information. An Order item may not have Price information, or can have one or more Price information. - Direction from Price information to Order item. A Price information belongs to one Order item. PRICE INFORMATION PRICE ALLOWANCE & CHARGE (relation : has - 1/0,N) - Direction from Price information to Price Allowance & Charge. A Price information may not have Price Allowance & Charge, or can have one or more Price Allowance & Charge. - Direction from Price Allowance & Charge to Price information. An Price Allowance & Charge belongs to only one Price information. ORDER ITEM - ORDER ITEM REMARK (relation : has - 1/0,N) - Direction from Order item to Order item remark. An Order item can have no, one or more Order item remark. - Direction from Order item remark to Order item. An Order item remark belongs to only one Order item. ORDER ITEM - DOCUMENT REQUIRED (relation : has - 1/0,N) - Direction from Order item to Document required. An Order item can have no, one or more Document required. - Direction from Document required to Order item. A Document required belongs to only one Order item. ORDER ITEM - SOURCE PRODUCT UNIQUE IDENTIFICATION (relation : has - 1/0,N) - Direction from Order item to Source product unique identification. An Order item can have no, one or more Source product unique identification. - Direction from Source product unique identification to Order item. A Source product unique identification relates to only one Order item. Page 9

ORDER ITEM - TRANSPORT (relation : has - 1/0,N) - Direction from Order item to Transport. An Order item may not have information about the requested means and mode of Transport, or can have one or more information on the means and mode of Transport. - Direction from Transport to Order item. A means and mode of Transport belongs to only one Order item. TRANSPORT - EQUIPMENT (relation : has - 1/0,1) - Direction from Transport to Equipment. A Transport may not have information about the type of Equipment, or can have information about the type of Equipment. - Direction from Equipment to Transport. A type of Equipment belongs to only one means and mode of Transport. Page 10

1.5. Data model attributes For each entity specified under point 1.3. Data model entities, a list of attributes and a description is given. ENTITY : ORDER order number customer Unique number given by the customer to identify an order. order date customer Date when the order was issued by the customer. contract number Unique number given to the contract (sale) between the customer and the supplier. contract date Date when the contract (sale) was agreed (signed) by the supplier and the customer. order type Code indicating if the order is a spot order, open order or service order. quotation number Reference number assigned by the tenderer to a quotation. quotation date Date when a quotation was issued. agency order reference number Number attributed by the sale agency to a customer's order. agency order reference date Date when the reference to the customer's order was issued by the sales agency. ENTITY : INVOICING INFORMATION invoicing currency The name or symbol of the monetary unit used for the calculation of the invoice. terms of payment Conditions of payment between the parties for the transaction, e.g. payment by the end of the month of delivery. payment conditions Method to be employed in order that a payment may be made, e.g. direct payment, documentary credit. Page 11

duty/tax/fee type Type of duty or tax or fee applicable to the final products. duty/tax/fee rate Rate of duty or tax or fee applicable to the final products. duty/tax/fee currency The name or symbol of the monetary unit used for the calculation of the duty or tax or fee. duty/tax/fee location The location to which the duty/tax/fee or exemption applies, e.g. city or state or country. ENTITY : ORDER ALLOWANCE & CHARGE allowance or charge type Specification of an allowance or charge. allowance or charge number Number assigned by a party referencing an allowance or charge. allowance or charge value, percentage The allowance or charge value, percentage for a given allowance or charge. allowance or charge tax The tax rate for the given allowance or charge. ENTITY : ORDER ITEM order item number Unique number given to an order item for identification. supplier's article number Supplier's reference identifying an article or product. buyer's article number Customer's reference identifying an article or product. source of the product Code identifying if the ordered products are already in stock free for sale, or the preproducts are in an intermediate stock, or if the ordered products must be produced. part number Customer's identification number attributed to the article. drawing number Reference number identifying a drawing list. Page 12

project number Reference number assigned to a project. customer reference number Reference number assigned by the customer to an order. product specifications of the ordered product All the necessary information for the production of the ordered product (such as dimensions, quality, surface treatment, product description, commercial choice). More information about the different elements for the production of the ordered products can be found in the Eurofer code list PDS. Some examples are given below. product type Description of the ordered product shape as specified in the code list of Eurofer or other code lists. steel grade Steel grade or quality of the ordered product. steel grade supplement Steel grade norm or quality norm group. For example AFNOR 4, ASTM, BS4360, DIN17400. length Requested length of the ordered product. length tolerances Tolerances accepted on the requested length of the ordered product. This information can be given as a value in plus, and or minus or can be given as a tolerance table. width Requested width of the ordered product. width tolerances Tolerances accepted on the requested width of the ordered product. This information can be given as a value in plus, and or minus or can be given as a tolerance table. thickness Requested thickness of the ordered product. thickness tolerances Tolerances accepted on the requested thickness of the ordered product. This information can be given as a value in plus, and or minus or can be given as a tolerance table. minimum, maximum outside diameter Minimum and maximum outside diameter of the ordered product (coils) requested. Page 13

inside diameter Inside diameter of the ordered product requested. surface condition Surface condition requested on the ordered product. type of coating upper side and lower side Code identifying the type of coating requested for the ordered product, can be specified for both sides. For example organic coating, inorganic coating, zinc, ferro zinc, etc... thickness of the layer upper side and lower side Requested thickness of the coating layer for one or both sides. Can be different for each side. thickness tolerance of the layer upper side and lower side Tolerances accepted on the requested thickness of the layer. This information can be given as a value in plus and or minus or can be given as a tolerance table. quantity ordered The quantity ordered of the product. quantity tolerance Tolerances accepted on the requested quantity. This information can be given as a value in plus, or minus, or can be given as a tolerance table. delivery period requested The period requested for the delivery of the ordered product. end use of the final product Code identifying the application of the final product by the customer. ENTITY : DELIVERY SCHEDULE DETAILS delivery plan status indicator Code indicating the level of commitment of the schedule detail information. This can be firm, commitment for production and planning/forecast. schedule or period requested The schedule or period requested can be specified as a date, or a period. The period can be presented as a starting- and end date, starting- and end week, a week or a month. quantity requested The quantity requested for delivery on the requested schedule. Page 14

ENTITY : LABELLING PACKAGING INFORMATION information about the contents of the transport label These are all the kinds of information that must be printed on the transport label, such as : unloading point Name and address of exact location of unloading point, such as dock or gate. net weight requested Indication if the net weight and unit is to be printed on the label. gross weight requested Indication if the gross weight and unit is to be printed on the label. numbers requested measured length Which information and unit is to be printed in the field Number of the label, e.g. number of sheets or mesured length and unit of measurement. batch/cast/heat/original coil information requested Indication if the heat number, hot rolled number or cold rolled number must be printed the field Batch/cast/ heat of the label. number of labels and location on the final products This is the number of labels requested inside and outside the package. Also the position of the labels on the product can be specified. type of package Code to specify the ordered package. minimum and maximum weight of the package This is the minimum and maximum weight that must be adhered to in the production of each package. shipping marks and colour Information about the product and label markings. requested final products serial numbers Range of requested serial numbers to be attributed to the final products. ENTITY : PRICE INFORMATION price qualifier Identification of a type of price. E.g. Calculated net price (include allowances & charges, or without allowances & charges). price The monetary value associated with the purchase of a product or service. Page 15

price type Identification of the type of price of an item. E.g. net weight, gross weight, theoretical weight. unit price basis Basis to which the unit price/rate applies, e.g. per tonne, per 100 pieces. price currency The name or symbol of the monetary unit used for pricing purposes. validity date/period Date (from-to)/period referenced price is valid. ENTITY : PRICE ALLOWANCE & CHARGE allowance or charge type Specification of an allowance or charge. allowance or charge number Number assigned by a party referencing an allowance or charge. allowance or charge value, percentage The allowance or charge value, percentage for a given allowance or charge. allowance or charge tax The tax rate for the given allowance or charge. ENTITY : ORDER ITEM REMARK remark subject qualifier Code specifying the subject of the remark, for example production remarks, labelling remarks, shipping remarks or markings. remark A remark can be given as a code or as a clear text. ENTITY : DOCUMENT REQUIRED type of documents Code identifying the requested documents by the customer for the delivery of the ordered products. number of documents The number of originals or copies of the document requested by the customer. Page 16

document communication channel The type of communication channel used for the exchange of the document. ENTITY : SOURCE PRODUCT UNIQUE IDENTIFICATION source product list identification Identification number of the source product list of pre-products, selected for the production of the ordered product. This can also be the identification of a list with final products in stock free for sale. product identification Identification of stock free for sale product selected as ordered product, or a preproduct selected for the production of an ordered product. ENTITY : TRANSPORT mode of transport Method of transport requested for the carriage of the products. means of transport Description of the type of the means of transport requested to be used. terms of delivery Terms and place agreed between the supplier and the customer under which the supplier undertakes to deliver merchandise to the customer. delivery address Name and address of the party to which the goods should be delivered, e.g. consignee. ENTITY : EQUIPMENT equipment qualifier Code identifying type of equipment to be used for the delivery of the product. equipment size and type Code or description of the size and type of equipment. Page 17

THE RELATED DATA ENTITIES ENTITY : COMPANY company code, name and address Code, and if necessary name and address of the partners involved. E.g. sales agency, supplier, customer, manufacturer, consignee, carrier, inspection authority, end-user, invoicee. contact information A person or a department to whom communication should be directed. communication contact A communication number of a department or person to whom communication should be directed. ENTITY : RULES & AGREEMENTS reference number to the rules & agreements Number attributed to the rules & agreements applicable to the order. Page 18

2. SCOPE 2.1. Functional Definition 2.1.1 The EDIFACT order messages To support the ordering process, UN/EDIFACT has developed 3 different messages dealing with the transfer of order information between a customer and a supplier. These messages are : - ORDERS (Purchase order) - ORDRSP (Purchase order response or Purchase order change response) - ORDCHG (Purchase Order change) The ORDERS message is sent from a customer to a supplier, the customer may order one or more goods items or services. By using the ORDERS message all information concerning the product specification, quantity, delivery time and expedition can be given. This message gives the possibility for the placement of a "Spot order", "Open order", "Calloff order" and "service order" (see chapter 2.1.2.). The ORDRSP message is sent from a supplier to a customer, to give order response information (order confirmation) about the reception of a new order or a change to an existing order. The following possibilities are foreseen in the ORDRSP message : - order is accepted as specified in the ORDERS message, - order change is accepted as specified in the ORDCHG message, - order or order change is not accepted, - order or order change is accepted with amendments. The ORDCHG message is sent from a customer to a supplier to modify an existing order. In this message the functionality has been foreseen to change requirements of all the order items, or to transmit only the order items which have been changed. With this message it is also possible to transmit a cancellation of an order item or an entire order, or to add new order items to an existing order. An ORDRSP message and an ORDCHG message cannot refer to more than one ORDERS message. In the ordering process an Order message for a new order may be followed by any number of Order response messages and Order change messages, in a sequence dependent upon the scenarios/business functions being performed. The following example offers various scenarios : - The customer sends an ORDERS message to the supplier to place a new order. - The supplier sends back to the customer an ORDRSP message to confirm the reception of the order. The supplier accept the order with an amendment. Page 19

- After the receipt of the ORDRSP message the customer agrees with the amendment proposed by the supplier, and the customer send an ORDCHG message to agree with the amendment. - The supplier confirms with the ORDRSP message the change requested by the customer in the ORDCHG message. - Due to some production problems the supplier can no longer guarantee the confirmed delivery time, and informs the customer by using the ORDRSP message of a new delivery time. - The customer does not agree with the change of the delivery date and he requests receipt of 50% of the ordered quantity at the initial confirmed delivery time and the other 50% he can agree with the new proposed delivery time. By sending the ORDCHG message to the supplier, the customer requests the above mentioned changes. ORDERS C U S T O M E R ORDRSP ORDCHG ORDRSP ORDRSP ORDCHG ORDRSP S U P P L I E R It must be good business practice to always end these combinations with an ORDRSP message to confirm that the ORDCHG message has been accepted. Eurofer recommends to have an agreement between the parties involved, how to act on an Order change message and the content of the message. Especially when only the changed, cancelled or new order items are transmitted and not the complete new situation of the order. Page 20

2.1.2 Different ways of ordering In the European steel industry a lot of different ways of ordering steel products are in use, such as "Spot order", "Open order", "Call-off order", "service order", etc... To explain the different ways of ordering we make a distinction between two main groups, called "Firm orders" and "Blanket orders" covering the above mentioned ways. Main group "Firm orders" The order contains all the relevant information concerning the production of the ordered products, shipment instructions, quantity and delivery time. The following ways of ordering are present in this main group: - Spot order - Service order - Sales list (stock) order Main group "Blanket orders" The order contains all the relevant information concerning the production of the ordered products and the shipment instructions for a large delivery period and sometimes a total estimated quantity to be delivered. The following ways of ordering are present in this main group : - Open orders - Call-off orders To specify the delivery time and the quantity, two different methods exist : - Delivery instructions by using Delivery schedule - Call-off orders. Various types of orders are described below. 1. Spot order The first way of ordering is known in the steel industry as "Spot order". In this case the order includes all the information concerning product specifications, shipment instructions, quantity and delivery time. 2. Service order The second way of ordering is known in the steel industry as "Service order". In this case the customer orders some services, better known as production steps, to be executed on products provided by the customer to the supplier. This type of ordering can be compared with an order for hire working. 3. Sales list (stock) order When a lot of steel products are in the warehouse of the supplier not allocated to an existing order, the steel company can decide to sell those products to potential customers. In this case the supplier shall produce a sales list containing all the products in the warehouse free for sale and send it to potential customers. Based on this list the customer can decide to buy all the products mentioned on the sale list or he can make a selection from it. Then the customer shall transmit an order which refers to the sales list and gives a selection of the listed products, complete with shipment instruction and delivery time information. This method is used for second choice material, but can also be used for first choice material held in the stock by the supplier. Page 21

Some steel companies distribute product lists of semi-finished material in intermediate production stocks, to allow the customer to purchase semi-finished material for their final products and to reduce the production time. In this case the customer shall transmit in the order message not only the information concerning product specifications, shipment instructions, quantity and delivery time, but also a specification of the selected semi-finished material by referring to the product lists or the semi-finished material units. 4. Open order This method of ordering is known in the steel industry as "Open order". In this case the order refers to a commercially agreed contract. The order message contains the product specifications and the information needed for shipment. After the order and the acceptance of the order, the quantities and the delivery times are in this case given by the subsequent messages, called "Delivery schedule" (DELFOR) and Delivery just in time (DELJIT). 5. Call-off order This method of ordering is known in a great number of industries as a "Call of order". Calloff orders are regular/repeated orders sent against a previous commercially agreed contract and agreed product specifications. Only a few pieces of information, such as part number, quantity and delivery time need to be supplied by the customer. As a principle, commercial agreements such as the product specifications may not be required in the message by using a call-off order. The product specifications can only be changed by using the order change message against the initial order. 2.2. Field of application This message provides the definition of the Eurofer Order message to be used in Electronic Data Interchange between European steel suppliers and their customers. 2.3. Principles With an Order message a customer may order one or more products (goods items) or services. A purchase order may refer to products or services related to one or more delivery schedules or call-offs. A purchase order for cross-border transactions may contain additional information for customs and/or statistical purposes. A purchase order may contain details for transport and destination as well as delivery patterns. By using the Orders message for a service order, the type of products supplied by the customer can be specified at order or at order item level. If there is a choice between the use of code and free text, we recommend to use the code. Therefore free text for name and address information should be avoided. Where possible use existing codes of EDIFACT, Eurofer or other existing code systems. Page 22

2.4. Message usage 2.4.1. The different ways of ordering now in the steel industry The Order message can be used to convey the information for the production and/or the delivery of steel products or to execute some production steps on products (semi-finished products) delivered by the customer to the supplier. Based on the actual existing business relations, the Steel industry is aware of different methods of ordering. All these methods have been catered for in the Orders message as specified in the implementation guide. Based on the inventory of the different ways of ordering given in chapter 2.1.2., the difference between the order types can be given in the segment BGM. The order type will dictate whether more or less information must be provided in the message. Spot order When the ORDERS message is used for a spot order, the ordered quantity and delivery time must be specified at order item level by using the segment QTY and DTM in the segment group 28. The segment group 53 dealing with scheduling conditions must not be used. Service order When the ORDERS message is used for a service order, the ordered quantity and delivery time must be specified at order item level by using the segment QTY and DTM in the segment group 28. The segment group 53 dealing with scheduling conditions must not be used. The starting product provided by the customer can be given in the segment IMD by using the Eurofer code list. The product specification of each basic product provided by the customer must be given by another EDI message, such as the Quality data message. Sales list (stock) order When the ORDERS message is used for a sales list order for the product in the warehouse of the supplier the segment group 53 must not be used. The delivery time and ordered quantity can be given in the segment DTM and QTY of the segment group 28. The sales list can be specified by using the segment group RFF-DTM (group 1 or 33). The selected products must be given in the segment GIN of the segment group 28. Open order The ORDERS message allows the use of the segment group 53 to transmit the first delivery schedule. When the ORDERS message is used for an open order, Eurofer recommends not to use the segment group 53 to specify the scheduling conditions, but to use the DELFOR or the DELJIT message to transmit the first delivery instructions. At the ordering stage, for the total ordered quantity and the delivery period the segments QTY and DTM of segment group 28 must be used. Page 23

Call-off order When the ORDERS message is used for a call-off order only a few pieces of information must be given such as a reference to the Open order, the delivery time and quantity. The quantity and the delivery must be given in segments DTM and QTY of segment group 28. The segment group 53 must not be used. 2.4.2. Different approaches to specify deliveries In line with business practice, three approaches are provided in the Orders message to specify the required deliveries for an order item. 1. Discrete delivery This is the most commonly used approach. For each of the order items the ordered quantity is to be given in the segment QTY (Quantity) under the LIN (Line item) segment (detail section). The delivery location is identified in the detail section, segment group starting with NAD (Name and address) segment (NAD - LOC segment e.g. location for customer, consignee). If the delivery location is the same for all order items this information can be given only once in the header section (order level) by using the segment group 2 starting with NAD segment. The delivery date can be given in the DTM (Date) segment in the detail section under the LIN segment or only in the DTM segment at the header level if the same delivery date is valid for all order items. 2. Split deliveries For the order item identified by the LIN segment, deliveries may be required at different locations with different quantities. The total delivery quantity is specified in the segment QTY under the LIN segment. The location of each delivery point and the relevant quantity requested is given using the segments LOC and QTY in segment group 37. The possibility of using the segment group 37 is not foreseen in the EUROFER subset. Eurofer prefers to use a repetition at the order item level for each location and relevant quantity. 3. Scheduled deliveries at the same location It is foreseen that at the ordering level the first delivery schedule can be given. The following delivery schedules are then transmitted by using the DELFOR message. To transmit the first delivery schedule in the order message is not often used in the steel industry. Mostly the order message is used to transmit the order specifications of an open order and all the delivery schedules (also the first one) are given by using the DELFOR message. For the order item identified by the LIN segment, a specific ordered quantity is to be delivered according to a specific schedule. The total quantity to be delivered should not be specified by using the segment QTY under the LIN segment. The schedule details are to be given in segment group 53 starting with the SCC segment (Scheduling conditions). Page 24

3. MESSAGE DEFINITION 3.1 Message Structure The Order message of UN/EDIFACT is structured in three sections, a Heading Section, a Detail Section and a Summary Section. 3.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 references to the initial contract, contract date, order date or information about the customer. The heading section can also be used to give information which has the same contents for each line in the detail section. Examples of this kind of information are the consignee, the invoicing information, shipping information and so on.. 3.1.2. Message structure - Detail section The detail section is controlled by the segment group 28 with the mandatory segment LIN and the message can have a maximum of 200,000 segments groups. Each line of the detail section provides information about one order item. The detail line is used to specify the requested product detail specifications of the ordered products that must be produced and, or delivered by the supplier. In the detail line the basic product type and the activities requested in the case of a service order. The ordered products, and if necessary the requested services are to be specified in the IMD segment in the segment group LIN by using the Eurofer code lists. The segment PIA can only be used for identifications, such as customer's part number and material code. The segment group 33, with the trigger segment RFF is used to identify references, such as customer s order number, contract number. The requested product detail specifications are specified by the MEA segment and the segment group 29 (CCI - CAV - MEA). If it is possible to specify by the MEA segment a product detail, such as dimensions, the segment MEA must be used. If it is not possible to specify a product detail by the MEA or IMD segment, then the segment group 26 must be used. Examples of the use of the segment group 29 are : surface condition, surface roughness, flatness, edge trimming, rolling temperature, coiling temperature, etc... 3.1.3 Message structure Summary section The summary section can be used to give total amounts for the whole order message. The summary section can also be used to specify allowance and charge totals for the order. Page 25

3.2. Mapping of the Data model to the message To understand the mapping process, completed by the EDIFER working group, it is necessary to have knowledge about the structure of the official UNSM ORDERS 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 use of the official document published by UNITED NATIONS - EDIFACT directory D97.A. Page 26

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 with 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 : ORDER Order number customer BGM 1004 Order date customer DTM 2380 DTM segment in the header, following BGM. Contract number Group 1 or Group 33 RFF 1154 When it is relevant for the complete order. If different per order item. Contract date Group 1 or Group 33 DTM 2380 DTM segment following the RFF segment in the relevant group. Order type BGM 1001 See code list EDIFACT Quotation number Group 1 or Group 33 Quotation date Group 1 or Group 33 Agency order reference number Group 1 or Group 33 Agency order reference date Group 1 or Group 33 RFF RFF 1154 When it is relevant for the complete order. If different per order item. DTM 2380 DTM segment following the RFF segment in the relevant group. RFF 1154 When it is relevant for the complete order. RFF If different per order item. DTM 2380 DTM segment following the RFF segment in the relevant group. Page 27

ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : INVOICING INFORMATION Invoicing currency Group 7 CUX C504 Use of code list EDIFACT. Terms of payment Group 8 PAT C110 Code form or clear form can be used. Eurofer recommends to use the code form. Payment conditions PAI 4439 PAI segment in the header, following the DTM. Duty/tax/fee type Group 6 TAX C241 Code form or clear form can be used. Eurofer recommends to use the code form. Duty/tax/fee rate Group 6 TAX 5278 If necessary the identification of the rate can be given in element 5279. Duty/tax/fee currency Group 7 CUX C504 Use of code list EDIFACT. Duty/tax/fee location Group 6 LOC C517 Use the relevant code for element 3227 Entity : ORDER ALLOWANCE & CHARGE Allowance and charge type Group 19 ALC 5463 Use the code list of EDIFACT. Allowance and charge number Group 19 ALC 1230 Allowance or charge value, percentage Group 22 or Group 21 MOA PCD 5004 5482 Allowance and charge tax Group 24 TAX 5278 Used for an allowance or charge amount. Used for an allowance or charge percentage. Entity : ORDER ITEM Order item number Group 28 LIN 7140 Use the code IN (buyer's item number) in element 7143. Supplier's article number Group 28 PIA 7140 Use the code SA in element 7143. Customer's article number Group 28 LIN 7140 Use the code IN in element 7143. Source of the product Group 28 IMD 7009 or 7008 Use of code list Eurofer. Use code 56 in element 7081. Part number Group 28 PIA 7140 Use the code BP in element 7143. Drawing number Group 33 RFF 1154 Use the code AEQ in element 1153. Project number Group 33 RFF 1154 Use the code AEP in element 1153. Page 28

ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : ORDER ITEM Customer reference number Group 33 RFF 1154 Use the code CO in element 1153. Product specifications of the final product *** Some examples are *** Group 28 or Group 29 IMD or MEA CCI, and CAV or MEA Product type Group 28 IMD 7009 or 7008 Steel grade Group 28 IMD 7009 or 7008 Steel grade supplement Group 28 IMD 7009 or 7008 Length Group 28 MEA 6314 or 6162, 6152 Length tolerances Group 29 CCI and CAV or MEA 7009 6314 or 6162, 6152 Width Group 28 MEA 6314 or 6162, 6152 Width tolerances Group 29 CCI and CAV or MEA 7037 6806 6314 or 6162, 6152 Thickness Group 28 MEA 6314 or 6162, 6152 Thickness tolerances Group 29 CCI and CAV or MEA 7037 6806 6314 or 6162, 6152 Some of the product specifications can be specified in the segment IMD or MEA. Other specifications must be specified in group 25 A. Use of code list Eurofer P01. Use code 8 in element 7081. Use of code list Eurofer. Use code 13 in element 7081. Use of code list Eurofer. Use code 38 in element 7081. Use the relevant code for 6313. To give minimum and maximum length. Use the code list Eurofer PDS to indicate which tolerances. To give the tolerance value. To give a range of the tolerance. Use the relevant code for 6313. To give minimum and maximum width. Use the code list Eurofer PDS to indicate the tolerance. To give the tolerance value. To give a range of the tolerance. Use the relevant code for 6313. To give minimum and maximum thickness. Use the code list Eurofer PDS to indicate the tolerances. To give the tolerance value. To give a range of the tolerance. Minimum, maximum outside diameter Group 28 MEA 6162, 6152 To give a range of the outside diameter. Use the relevant code for 6313. Inside diameter Group 28 MEA 6314 Use the relevant code for 6313. Surface condition Group 29 CCI and CAV Type of coating upper side and lower side Group 28 CCI and CAV 7037 6806 7037 6806 Use code lists of Eurofer (PDS), to specify in 7037 - surface condition and to specify in 6806 - the value of the roughness.. Use code lists of Eurofer (PDS), to specify in 7037 - coating upper - or lower side, and to specify in 6806 - which type of coating. Page 29

ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : ORDER ITEM Thickness of the layer upper side and lower side Thickness tolerances of the upper side and lower side *** End of examples *** Group 29 Group 29 CCI MEA CCI 7037 6314 7037 Use code list of Eurofer (PDS) to specify in 7037 - upper - or lower side. Use the relevant code in 6313. Use code list of Eurofer (PDS) to specify in 7037 - upper - or lower side. Use the relevant code in 6313. MEA 6162, 6152 Quantity ordered Group 28 QTY 6060 Use the relevant code in element 6063. Quantity tolerance Group 29 CCI 7037 Use code list of Eurofer (PDS) to specify in 7037 the quantity MEA 6314 tolerance, and give in 6314 the value. Delivery period requested Group 28 DTM 2380 Use the relevant code in End use of the final product Group 29 CCI CAV 7037 6806 element 2005. Use code list of Eurofer (PDS) to specify in 7037 the end use of the final product, and give in 6806 the value. Entity : DELIVERY SCHEDULE DETAILS Delivery plan status indicator Group 53 SCC 4017 Schedule and period requested Group 54 DTM 2380 Use the relevant code in element 2005. Quantity requested Group 54 QTY 6060 Use the relevant code in element 6063. Entity : LABELLING PACKAGING INFORMATION Information about the content of the transport label Group 29 CCI CAV Unloading point Group 2 or Group 39 LOC Net weight requested Group 29 CCI and CAV Gross weight requested Group 29 CCI and CAV Numbers requested measured length Group 29 CCI and CAV 7037 and 6806 C517 or C519 7037 and 6806 7037 and 6806 7037 and 6806 Use code list of Eurofer (PDS) to specify in 7037 the kind of information, and give in 6806 the corresponding value. Use code 20 in element 3227. Use code list of Eurofer (PDS) to specify in 7037 the kind of information, and give in 6806 the corresponding value. Use code list of Eurofer (PDS) to specify in 7037 the kind of information, and give in 6806 the corresponding value. Use code list of Eurofer (PDS) to specify in 7037 the kind of information, and give in 6806 the corresponding value. Page 30

ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : LABELLING PACKAGING INFORMATION Batch/cast/heat/original coil information Number of labels and location on the final products Group 29 Group 29 CCI and CAV CCI and CAV or MEA 7037 and 6806 7037 6806 6314 Use code list of Eurofer (PDS) to specify in 7037 the kind of information, and give in 6806 the corresponding value. Use code list of Eurofer (PDS) to specify in 7037 and 6806 - the location of the labels and the number of labels is given in 6314. Type of package Group 34 PAC 7065 Use code list of Eurofer to specify in 7065 the type of package. Minimum and maximum weight of the Group 34 MEA 6162, 6152 Use the relevant code in 6313. package Shipping marks and colour Group 36 PCI 7102 Use the relevant code in 4233. Requested final product serial Group 36 GIN 7402 Use code BN on element 7405. numbers Entity : PRICE INFORMATION Price qualifier Group 32 PRI 5125 Use code list of EDIFACT. Price Group 32 PRI 5118 Price type Group 32 PRI 5375 Use code list of EDIFACT. Unit price basis Group 32 PRI 5284 Price currency Group 7 CUX C504 Validity date/period Group 32 DTM 2380 Use the relevant code in element 2005. Entity : PRICE ALLOWANCE & CHARGE Allowance and charge type Group 43 ALC 5463 Use the code list of EDIFACT. Allowance and charge number Group 43 ALC 1230 Allowance or charge value, percentage Group 46 or Group 45 or Group 47 MOA PCD RTE 5004 5482 5420 Allowance and charge tax Group 48 TAX 5278 Used for an allowance or charge amount. Used for an allowance or charge percentage. Used for an allowance or charge rate per unit. Page 31

ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data element REMARKS Entity : ORDER ITEM REMARK Remark subject qualifier Group 28 FTX 4451 Remark Group 28 FTX 4441 or 4440 Code form or clear form can be used. Entity : DOCUMENT REQUIRED Type of document Group 4 or Group 41 Number of documents Group 4 or Group 41 Document communication channel Group 4 or Group 41 DOC C002 Code form or clear form can be used. Eurofer recommends to use the code form. DOC 1220 and/or 1218 DOC 3153 Can be specified as number of copies, or number of originals. Entity : SOURCE PRODUCT UNIQUE IDENTIFICATION Source product list identification Group 33 RFF 1154 Product identification Group 28 GIN 7402 Use code BN in element 7405. Entity : TRANSPORT Mode of transport Group 9 or Group 49 Type of transport Group 9 or Group 49 Terms of delivery Group 11 or Group 51 Delivery address Group 39 or Group 2 TDT 8067 If the mode of transport is the same for all items, group 9 in the header can be used. TDT 8179 If the mode of transport is the same for all items, group 9 in TOD C100 And LOC C517 NAD 3039 or C058 the header can be used. If the terms of delivery is the same for all items, group 11 can be used. Code form or clear form can be used. Eurofer recommends to use the code form. Entity : EQUIPMENT Equipment qualifier Group 15 or Group 52 Equipment size and type Group 15 or Group 52 EQD 8053 If the mode of transport is the same for all items, group 14 in the header can be used. EQD 8155 If the mode of transport is the same for all items, group 14 in the header can be used. Page 32

ATTRIBUTE SEGMENT GROUP SEGMENT TDID - Data Element REMARKS Entity : COMPANY Company code, name and address Group 2 or Group 39 Contact information Group 5 or Group 42 Communication contact Group 5 or Group 42 NAD 3039 or C058, C080, CTA 3412 or 3413 COM 3148 and 3155 Code form, structured or clear form can be used. C059, 3164, 3229, 3521, 3207 Entity : RULES & AGREEMENTS Reference number to the rules & agreements Group 1 or Group 33 RFF 1154 When it is relevant for the complete order. If different per order item. Page 33