OSTRPT Order Status Report Message - Eurofer

OSTRPT 

Order Status Report Message 

Subject for application in the European Steel Industry 

©Corporate Factory—Ph. D. Sarraute 

Version October 2001 

EDIFER WORKING GROUP - Message development

UN/EDIFACT D97.A OSTRPT - Order status report message 

ORDER STATUS REPORT 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 9 

2. SCOPE 13 

2.1 Functional Definition 13 

2.2 Field of Application 13 

2.3 Principles 13 

2.4 Message Usage 14 

3. MESSAGE DEFINITION 15 

3.1 Message Structure 15 

3.2 Mapping of the Data Model to the Message 15 

3.3 Branching Diagram of the Segments used by Eurofer 19 

3.4 General Description of the Message - Subset of Eurofer 22 

3.5 Detailed Description of the Message - Subset of Eurofer 28 

4. EXAMPLES 69 

4.1 Example of an order status report from ABC Sales department to 

the steel plant XYZ LTD 69 

4.2 Example of an order status report from ZZZ Rod Supplies to the 

customer XYZ LTD 71 

4.3 Example of an order status report from Ensidesa to the customer 

LESAKA 74 

Page 1


ORDER STATUS REPORT MESSAGE 

0. INTRODUCTION 

This document provides the definition of the EUROFER subset of the OSTRPT message 

based on the UN standard OSTRPT message of the UN/EDIFACT directory D97.A. This 

document replaces the previous version dated 01.05.1996, based on the EDIFACT directory 

D95.B. 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 OSTRPT, the used 

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

by Eurofer. 

- Examples of the Eurofer OSTRPT message are provided to clarify the understanding 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 Order status report 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 

Order Status 

Report 

1 

Relates to 

Order 

1,N 

Consists of 

Item 

1 

Order 

1,N 

1 

Scheduled by 

0,N 

Delivery 

Schedule 

Detail 

1 0,1 

Refers to 

1 

1 0,N 

Has 

Reference to 

Company 

Page 4 

Has 

Order Status 

Request 

0,N Item Status 

Information 

Delivery 

Schedule status 

Information


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 entity Company is not really basic information in this message, it has been 

put outside the data model and it is treated as a related data entity. 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 STATUS REPORT 

ORDER STATUS REQUEST 

ORDER 

ORDER ITEM 

ITEM STATUS INFORMATION 

DELIVERY SCHEDULE DETAIL 

DELIVERY SCHEDULE STATUS INFORMATION 

The related data entitiy 

COMPANY 

ORDER STATUS This entity contains general information about the Order status 

REPORT report, such as the Order status report type, number and the report 

date. 

ORDER STATUS This entity contains the information about the Order status 

REQUEST request, such as its number. 

ORDER This entity contains general information about the goods and services 

ordered under the conditions agreed between the buyer and the seller. 

ORDER ITEM This entity contains the following information for an order item : 

- product specifications of the ordered product 

- shipping information of the ordered product. 

ITEM STATUS This entity contains for each required product status of an order item : 

INFORMATION - the status and if necessary the date/time related, 

- the quantity of completion related to the status, 

- identification of the parties related to the status, 

- if relevant, transport information, 

- identification of packages. 

Page 6


DELIVERY This entity specifies the day/period when a requested quantity 

SCHEDULE must be delivered to the consignee. 

DETAIL 

DELIVERY This entity contains for each required product status of a delivery 

SCHEDULE schedule detail : 

STATUS - the status and if necessary the date/time related, 

INFORMATION - the quantity of completion related to the status, 

- identification of the parties related to the status. 

COMPANY Any organisation with whom we deal for whatever purpose. 

This can be the buyer, selling agency, seller, inspection authority, 

consignee and so on. 

Page 7


1.4. Data Model Relationships 

ORDER STATUS REPORT - ORDER STATUS REQUEST 

(relation : refers to - 1/0,1) 

- Direction from Order status report to Order status request. 

An Order status report may or may not refer to one Order status request. 

- Direction from Order status request to Order status report. 

An Order status request given in the Order status report can only appear once. 

ORDER STATUS REPORT - ORDER (relation : relates - 1/1,N) 

- Direction from Order status report to Order. 

An Order status report can relate to one or more Order. 

- Direction from Order to Order status report. 

An Order given in the Order status report can only appear once. 

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 - ITEM STATUS INFORMATION 

(relation : has - 1/0,N) 

- Direction from Order item to Item status information. 

An Order item may or may not have one or more Item status information. 

- Direction from Item status information to Order item. 

Item status information belongs to only one Order item. 

ORDER ITEM - DELIVERY SCHEDULE DETAIL 

(relation : scheduled by - 1/0,N) 

- Direction from Order item to Delivery schedule detail. 

An Order item may or may not have one or more Delivery schedule detail. 

- Direction from Delivery schedule detail to Order item. 

Delivery schedule detail belongs to only one Order item. 

Page 8


DELIVERY SCHEDULE DETAIL - DELIVERY SCHEDULE STATUS 

INFORMATION 

(relation : has - 1/0,N) 

- Direction from Delivery schedule detail to Delivery schedule status information. 

Delivery schedule detail may or may not have one or more Delivery schedule status 

information. 

- Direction from Delivery schedule status information to Delivery schedule detail. 

Delivery schedule status information belongs to only one Delivery schedule detail. 

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 STATUS REPORT 

order status report number 

Unique number normally given by the seller to identify an order status report. 

order status report date 

Date when the order status report was issued by the seller. 

ENTITY : ORDER STATUS REQUEST 

order status request number 

Unique number normally given by the buyer to identify an order status request. 

order status request date 

Date when the order status request was issued by the buyer. 

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. 

ENTITY : ORDER ITEM 

order item number customer 

Unique number given to an order item by the buyer. 

Page 9


supplier's article number 

Supplier's reference identifying an article or product. 

customer's article number 

Customer's reference identifying an article or product. 

part number 

Customer's identification number attributed to the article. 

order number supplier 

Unique number given by the supplier to identify an order. 

order item number supplier 

Unique number given to an order item by the supplier. 

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. 

dimensions 

Requested dimensions of the ordered product. 

ENTITY : ITEM STATUS INFORMATION 

product status 

The different product status against which a steel product can appear. 

date/time status 

Date/time related to the product status. 

quantity 

Quantity of completion related to the product status. 

party involved 

Identification of the party involved in the given product status. 

contact information of the party involved 

A person or a department of the party involved to whom communication should be 

directed. 

communication contact of the party involved 

A communication number of a department or person of the party involved to whom 

communication should be directed. 

Page 10


number of packages 

Number of packages involved in the given product status. 

package identification 

Number assigned to identify a particular package. 

mode of transport 

Method of transport used for the carriage of the products, if the goods are in despatch 

process or have been despatched. 

means of transport 

Description of the means of transport requested to be used at the despatch process, or 

the means used during the despatch. 

ENTITY : DELIVERY SCHEDULE DETAILS 

delivery plan status indicator 

Code indicating the level of commitment of the schedule detail information. This status 

can be firm, commitment for production or 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 start and end date, a start and end week, a week or a month. 

quantity requested 

The quantity requested for delivery against the schedule. 

ENTITY : DELIVERY SCHEDULE STATUS INFORMATION 

product status 

The different product status against which a steel product can appear. 

date/time status 

Date/time related to the product status. 

quantity 

Quantity of completion related to the product status. 

party involved 

Identification of the party involved in the given product status. 

ENTITY : COMPANY 

company code, name and address 

The code and if necessary name and address of the partners involved. E.g. sales agency, 

supplier, customer, manufacturer, consignee, carrier, inspection authority, end-user. 

Page 11


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. 

Page 12


2. SCOPE 

2.1. Functional Definition 

2.1.1 The EDIFACT - OSTRPT message 

To support the follow-up of the ordered goods during the production and, or delivery 

process, UN/EDIFACT has developed 2 different messages. 

These messages are : 

- OSTENQ (Order status enquiry) 

- OSTRPT (Order status report) 

The OSTENQ message is sent normally from a customer or customer's agent to a supplier 

or, supplier's agent asking for information on the current status of previously sent order(s). 

The OSTRPT message is sent normally from a supplier or supplier's agent to a customer or 

customer's agent, reporting information on the current status of previously sent orders. This 

may be a reply to an order status enquiry or a report as agreed between partners. 

2.1.2 Eurofer position 

Eurofer members agreed to send the order status report message (OSTRPT) at regular 

intervals and not necessarily in response to an order status enquiry message (OSTENQ). 

Therefore at this stage Eurofer has decided only to develop a subset for the OSTRPT 

message. 

2.2. Field of application 

This message provides the definition of the Eurofer OSTRPT message to be used in 

Electronic Data Interchange between European steel suppliers and their customers. 

2.3. Principles 

The OSTRPT message has been created as a subset of the OSTRPT message of EDIFACT 

of the directory D97.A. 

Page 13


2.4. Message usage 

The order status report message can be used to convey the information at the following 

levels within an order : 

a) At the order level 

The order status information is globalized at the level of the order. 

b) At the order item level 

The order status information is globalized at the level of the order item. 

c) At the delivery schedule detail level 

The order status information is given at the level of each delivery schedule detail. 

Eurofer has decided that the OSTRPT message can only provide the order status information 

at the level of the order item and, or the delivery schedule detail. 

In the OSTRPT message it is possible to give not only the current situation of the order, but 

also the expected dates in the near future. 

Eurofer recommends to use the code lists PS2, PS1 maintained by Eurofer, to specify the 

different product status or production processes and stages. 

Eurofer has decided to specify the degree of completion related to a particular status by 

using the quantity of completion (segment QTY) and doesn't allow the use of percentage of 

completion (segment PCD). 

Page 14


3. MESSAGE DEFINITION 

3.1 Message Structure 

The Order status report message of UN/EDIFACT is structured in two sections, a Heading 

Section and a Detail 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 order status request, order status 

date, and the identification of the parties involved. 

3.1.2. Message structure - Detail section 

The detail section is controlled by the segment group 3 with the mandatory segment DOC 

and the message can have a maximum of 999 segment groups. 

Each line of the detail section provides the possibility to give order status information at 

three different levels. This can be for an order, for one or several items of an order or for 

one or several delivery schedules, or split deliveries of an order item. 

The segment DOC of the detail section is used to specify the order number and the related 

status information is given in segment group 4, triggered by the status (STS) segment. 

The segment LIN of group 5 is used to specify the order item by its number and the related 

status information is given in the segment group 7, triggered by the STS segment. 

The segment group 15, triggered by the SCC segment, and the segment group 16, triggered 

by the LOC segment allows the specification of a delivery schedule or deliveries split by 

location. The related status information is given in the segment group 17, triggered by the 

STS segment. 

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 EDIFACT OSTRPT 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. 

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 its tag 

- the Edifact data element 

- remarks about the usage. 

Page 15


ATTRIBUTE SEGMENT 

GROUP 

SEGMENT TDID - Data 

element 

Page 16 

REMARKS 

Entity : ORDER STATUS 

REPORT 

Order status report number BGM 1004 

Order status report date DTM 2380 DTM segment in the header, 

following BGM. 

Entity : ORDER STATUS 

REQUEST 

Order status request number RFF 1154 RFF segment in the header, 

following BGM, DTM 

segments. 

Order status request date DTM 2380 DTM segment in the header, 

following BGM. 

Entity : ORDER 

Order number customer Group 03 DOC 1004 

Order date customer Group 03 DTM 2380



GROUP 


element 

Page 17 

REMARKS 

Entity : ORDER ITEM 

Order item number customer Group 05 LIN 7140 Use the code IN (buyer's item 

number) in element 7143. 

Supplier's article number Group 05 PIA 7140 Use the code SA in element 

7143. 

Customer's article number Group 05 LIN 7140 Use the code IN in element 

7143. 

Part number Group 05 PIA 7140 Use the code BP in element 

Order number supplier Group 05 

or 

Group 06 

Order item number supplier Group 05 

or 

Group 06 

PIA 

RFF 

PIA 

or 

RFF 

7140 

1154 

7140 

or 

1154 

or 

1156 

Steel grade Group 05 IMD 7009 

or 

7008 

Steel grade supplement Group 05 IMD 7009 

or 

7008 

Dimensions Group 05 MEA 6314 or 

6162, 6152 

7143. 

Use the code PO in element 

7143 and code 91 in el. 3055. 

Use the code VN in element 

1153. 

Use the code PL or VN in 

element 7143 and code 91 in el. 

3055. 

Use the code LI in element 

1153 

or 

item number together with 

Order number seller. 

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 dimensions. 

Entity : ITEM STATUS 

INFORMATION 

Product status Group 07 STS 9011 Use the code list Eurofer PS1 or 

PS2 to indicate the product 

status. 

Date/time status Group 07 DTM 2380 DTM segment following the 

STS segment in the relevant 

group. 

Quantity Group 07 QTY 6060 Use the relevant code in 

Party involved Group 08 NAD 3039 

or 

Contact information of the party 

involved 

Communication contact of the party 

involved 

C058 

Group 09 CTA 3412 

or 

3413 

Group 09 COM 3148 

and 

3155 

element 6063. 

Code form or clear form can be 

used. Eurofer recommends to 

use the code form.



GROUP 


element 

Page 18 

REMARKS 

Entity : ITEM STATUS 

INFORMATION 

Number of packages Group 13 PAC 7224 

Package identification Group 14 RFF 1154 Use the relevant code for 1153. 

Mode of transport Group 10 TDT 8067 

Type of transport Group 10 TDT 8179 

Entity : DELIVERY SCHEDULE 

DETAILS 

Delivery plan status indicator Group 15 SCC 4017 

Schedule and period requested Group 16 DTM 2380 Use the relevant code in 

element 2005. 

Quantity requested Group 16 QTY 6060 Use the relevant code in 

element 6063. 

Entity : DELIVERY SCHEDULE 

STATUS INFORMATION 

Product status Group 17 STS 9011 Use the code list Eurofer PS1 or 

PS2 to indicate the product 

status. 

Date/time status Group 17 DTM 2380 DTM segment following the 

STS segment in the relevant 

group. 

Quantity Group 17 QTY 6060 Use the relevant code in 

Party involved Group 17 NAD 3039 

or 

C058 

Entity : COMPANY 

Company code, name and address Group 01 NAD 3039 

or 

C058 

Contact information Group 2 CTA 3412 

or 

3413 

Communication contact Group 02 COM 3148 

and 

3155 

element 6063. 


used. Eurofer recommends to 

use the code form. 


used.


3.3 Branching Diagram of the Segments used by Eurofer 

OSTRPT Order status report message version D97A 

Message to enable the transmission of the information concerning the order status 

between parties involved in the steel industry. 

The codes used for the usage indicator (USG. IND.) of 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. 

The codes used for the status of the segments according to EDIFACT: 

M for MANDATORY 

C for CONDITIONAL 

Heading Section 

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

R 29 UNH Message header M 1 

R 30 BGM Beginning of message M 1 

R 31 DTM Date/time/period M 5 

O 32 RFF Reference C 1 

O 33 FTX Free text C 99 

R SEGMENT GROUP 1 M 99 

R 34 NAD Name and address M 1 

O SEGMENT GROUP 2 C 5 

R 36 CTA Contact information M 1 

O 37 COM Communication contact C 5 

Detail Section 


SEGMENT GROUP 3 C 999 

R 38 DOC Document/message details M 1 

O 39 DTM Date/time/period C 5 

X SEGMENT GROUP 4 C 99 

X STS Status M 1 

X DTM Date/time/period C 5 

X PCD Percentage details C 1 

X QTY Quantity C 1 

X NAD Name and address C 1 

R SEGMENT GROUP 5 C 999.999 

R 40 LIN Line item M 1 

O 41 PIA Additional product id C 99 

O 43 IMD Item description C 99 

O 44 MEA Measurements C 5 

X GIN Goods identity number C 99 

X RCS Requirements and conditions C 5 

X FTX Free text C 99 

Page 19


Detail Section 



R 45 RFF Reference M 1 



R 47 STS Status M 1 



O 50 QTY Quantity C 1 


R 51 NAD Name and address M 1 

X RFF Reference C 5 


O CTA Contact information M 1 

O COM Communication contact C 5 

O SEGMENT GROUP 10 C 1 5 

R 53 TDT Details of transport M 1 

O 54 LOC Place/location identification C 1 


X TOD Terms of delivery M 1 

X LOC Place/location identification C 1 


X EQD Equipment details M 1 

X HAN Handling instructions C 5 


R 55 PAC Package M 1 

X QTY Quantity C 1 


M 56 PCI Package information M 1 

O 57 RFF Reference C 99 


R 58 SCC Schedule conditions M 1 

R SEGMENT GROUP 16 C 99 

R 59 LOC Place/location identification M 1 

R 60 DTM Date/time/period C 5 

R 61 QTY Quantity C 1 


R 62 STS Transport status report M 1 



O 65 QTY Quantity M 1 

O 66 NAD Name and address C 1 

R 68 UNT Message trailer M 1 

Page 20


Level 

00 

01 

02 

EUROFER OSTRPT ORDER STATUS REPORT MESSAGE VERSION - OCTOBER 2001 UN/EDIFACT DIRECTORY : D97.A 

UNH 

BGM 

M 1 M 1 

DTM 

M 5 

RFF 

C 1 

FTX 

C 99 

G01 

C 99 

NAD 

M 1 

G02 

C 5 

CTA 

M 1 

G03 

C 999 

DOC 

M 1 

Branching Diagram Page 1 

DTM 

C 5 

Page 21 

G05 

C 999999 

LIN 

M 1 

03 COM 

PIA 

IMD 

C 5 

C 99 C 99 

Level 

03 

04 

05 

06 

MEA 

C 5 

See page 2 

EUROFER OSTRPT ORDER STATUS REPORT MESSAGE VERSION - OCTOBER 2001 UN/EDIFACT DIRECTORY : D97.A 

See page 1 

G06 

C 999 

RFF 

M 1 

DTM DTM QTY NAD TDT PAC 

C 1 

G07 

C 99 

STS 

M 1 

C 1 C 1 

G08 G10 G13 

C 99 

M 1 

G09 

C 5 

CTA 

M 1 

COM 

C 5 

C 5 

M 1 

LOC 

C 1 

C 1 

M 1 

G14 

C 10 

PCI 

M 1 

RFF 

C 99 

Branching Diagram Page 2 

G15 

C 99 

SCC 

M 1 

G16 

C 99 

LOC 

M 1 

DTM QTY 

C 5 C 1 

G17 

C 99 

STS 

M 1 

DTM 

C 5 

QTY 

C 1 

NAD 

C 1 

UNT 

M 1


3.4 General description of the message - subset of Eurofer 

3.4.1 Message definition and segment clarification 

This chapter is provided to give clarification to and further explanation of the usage of the 

segments within the message defined by Eurofer. 

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 date/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) 

Specified dates, times, periods in relation to the status could be actual or planned, depending 

on the date/time/period qualifier. 

Where a choice of code or text is given, only the code element should be used if possible. 

Optional (conditional) data that is not required in the message should be excluded. 

Care must be taken that the segment qualifier in dependent segments does not conflict with 

the segment qualifier of the trigger segment of the group. 

3.4.2 Message description - Heading section 

Information which must be or 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 Order status report message is "OSTRPT". 

Note : Order status report messages conforming to this document must contain the following 

data in the segment UNH composite data element S009 with data elements : 

- 0065 OSTRPT 

- 0052 D 

- 0054 97A 

- 0051 UN 

Segment BGM, Beginning of message 

A segment by which the sender must uniquely identify the order status report by means of 

its type and number and when necessary its function. 

Page 22


Segment DTM, Date/time/period 

A segment specifying general dates and, when relevant, times related to the whole message. 

This segment must be specified at least once to identify the order status report date. The 

Date/time/period segment within other segment groups should be used whenever the 

date/time/period requires to be logically related to another specified data item. 

Segment RFF, Reference 

A segment identifying which Order status request document this message is responding to. 

Segment FTX, Free text 

A segment with free text information, in coded or clear form, used when additional 

information is needed but cannot be accommodated within other segments. In computer to 

computer exchanges such text will normally require the receiver to process this segment 

manually. 

This segment can be used to give production and shipping remarks. 

Segment group 1 : NAD-SG2 

A group of segments identifying the parties with associated information. 

Segment NAD, Name and address 

A segment identifying the name and address of the parties, in coded or clear form, and their 

functions relevant to the order status report. Identification of the sender (normally the seller, 

supplier) is mandatory for a report message. It is recommended that where possible only the 

coded form of the party ID should be specified. 

Segment group 2 : 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 a person or department, and their function, to whom communications 

should be directed. 

Segment COM, Communication contact 

A segment to identify a communication type and number for the contact specified in the 

CTA segment. 

3.4.3 Message description - Detail section 

Information to be provided in the detail section of the message. 

Segment group 3 : DOC-DTM-SG4-SG5 

A group of segments providing details of the individual order(s). 

Segment DOC, Document/message details 

A segment giving references to the order(s) reported. Other references may also be given, 

e.g. sellers reference number. 

Page 23



A segment specifying the date/time related to the reference. 

Segment group 4 : STS-DTM-PCD-QTY-NAD 

A group of segments providing status details related to the individual order. Eurofer has 

decided not to use this segment group, because there is no need in the steel industry to report 

at the order level. 

Segment group 5 : LIN-PIA-IMD-MEA-GIN-RCS-FTX-SG6-SG7-SG15 

A group of segments providing details of the individual order(s) lines being reported. 

Eurofer has decided to use only the segments LIN, PIA, IMD, MEA and the segments 

groups SG6, SG7, and SG15. 

Segment LIN, Line item 

A segment used to identify a line item. 

Segment PIA, Additional product identification 

A segment providing additional identification to the product specified in the LIN segment. 

E.gs. To give seller's item number, technical specification number. 

Segment IMD, Item description 

A segment for describing the product as well as product characteristics. This segment 

should be used for products or services that cannot be fully identified by a product code or 

an article number. 

In the iron and steel industry this segment can be used to give a detailed description of the 

products, the steel grade or the general description of the product group. 

Segment MEA, Measurements 

A segment enabling the physical measurements of the ordered item to be specified where 

this is required for full identification of the product. Any measurements must refer to the 

product in its unpacked form e.g. thickness of steel sheet, length, weight, etc. 

Segment group 6 : RFF-DTM 

A group of segments giving references related to the order line and, when relevant their 

dates. 

Segment RFF, Reference 

A segment giving references to seller’s reference number, contract numbers, etc. 


A segment specifying the date/time related to the reference. 

Segment group 7 : STS-DTM-PCD-QTY-SG8-SG10-SG12-SG13 

A group of segments providing status details and related information for a line item. 

Eurofer has decided to use only the segment STS, DTM, QTY and the segment groups SG8, 

SG10 and SG13. Other segment groups providing associated information should not be 

used. 

Page 24


Segment STS, Transport status report 

A segment giving the status of the referred order line. 


A segment specifying date/time related to the line item status. 

Segment QTY, Quantity 

A segment used to indicate the quantity of completion related to the line item status. 

Segment group 8 : NAD-RFF-SG9 

A group of segments identifying the parties with associated information, relevant to the line 

item status only. 

Eurofer has decided to use only the segment NAD and the segment group 9 of this group. 

The other segment providing associated information should not be used. 


A segment identifying the name and address of the parties, in coded or clear form, and their 

functions relevant to the item being queried. It is recommended that where possible only the 

coded form of the party ID should be specified. 

Segment group 9 : 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 a person or department, and their function to whom communications 

should be directed for the party. 

Segment COM, Communication contact 

A segment to identify a communications type and number for the contact specified in the 

CTA segment. 

Segment group 10 : TDT-LOC 

A group of segments identifying the mode and means of transport and location, related to 

the line item status. 

Segment TDT, Details of transport 

A segment specifying the mode, means and identification of the transport for the line item 

being queried. 

Segment LOC, Place/location identification 

A segment indicating the location relevant to the transport specified in the TDT segment. 

Segment group 13 : PAC-QTY-SG14 

A group of segments identifying the packaging, marks and numbers for goods referenced in 

the line item. 

Eurofer has decided to use only the segment PAC and the segment group 14. Other 

segments providing associated information should not be used. 

Page 25


Segment PAC, Package 

A segment specifying the number of packages and the physical type of packaging for the 

line item, e.g. pallet type. 

Segment group 14 : PCI-RFF 

A group of segments specifying the markings and labels on individual physical units. 

Segment PCI, Package identification 

A segment specifying markings and labels used on individual physical units. 

Segment RFF, RFF 

A segment identifying the master label number, heat number, serial number, etc... 

Segment group 15 : SCC-SG16 

A group of segments specifying the delivery schedules and related locations, quantities and 

date/times of a specific delivery. 

Segment SCC, Schedule conditions 

A segment specifying the type and status of the schedule. 

Segment group 16 : LOC-DTM-QTY-SG17 

A group of segments providing quantity details and related dates/time of a specific delivery. 

Segment LOC, Place/location identification 

A segment indicating the location to which part of the consignment is to be delivered. 


A segment specifying the date/time related to the product quantities. The segment can only 

be used to identify the delivery date. 


A segment identifying the product quantities. 

Segment group 17 : STS-DTM-PCD-QTY-NAD 

A group of segments providing status details on a specific delivery. 

Eurofer has decided to use only the segments STS, DTM, QTY and NAD. The other 

segment PCD providing associated information will not be used. 

Segment STS, Transport status report 

A segment giving the status of the referred delivery. 


A segment specifying the date/time related to the status of the specific delivery. 


A segment used to indicate the quantity of completion related to the status of the specific 

delivery. 

Page 26



A segment identifying the name and address of parties, in coded or clear form, and their 

functions related to the status reported. 

Segment UNT, Message trailer 

A service segment ending the message, giving the total number of segments in the message 

and the control reference number of the message. 

Page 27


3.5 Detailed description of the message - subset of Eurofer 

3.5.1 Detailed segment clarification 

This section is provided to give detailed clarification and a further explanation to the usage 

of the data elements in the segments of the Order status report message defined in the subset 

of Eurofer. The message consists of two sections, a heading section and a detail section. 

The section 3.5.2. describes each segment used in the heading section of the Eurofer Order 

status report message. The section 3.5.3. describes each segment used in the detail section of 

the Eurofer Order status report message. 

The original EDIFACT segment layout is listed. The appropriate comments relevant to the 

Eurofer subset are indicated. 

The segments are presented in the sequence in which they appear in the message. The 

segment and the segment group tag is followed by a Mandatory or Conditional indicator, the 

maximum number of occurrences and the segment description. 

Reading from left to right, in column one the usage indicator is for the use of the EDIFACT 

data elements in the Eurofer subset. 

In the other columns the information is given about the data element tag, data element name, 

followed by the EDIFACT status and the format. 

The codes used for the usage indicator (USG. IND.) for the data elements are, 

R for REQUIRED - Should always be used in the message 

O for OPTIONAL - May be used by trading partners if required. 

X for EXCLUDED - Not used in the message. 

Page 28


3.5.2 Detailed segment description - Heading section 

GROUP : 

SEGMENT : UNH MESSAGE HEADER 

SEGMENT STATUS : Mandatory 1 

FUNCTION : To head, identify and specify a message 

NOTES : This segment would normally be added as part of the translation process. It has been 

included for completeness. 

Data Element Summary 

USG. IND. TAG NAME STATUS FORMAT 

R 0062 MESSAGE REFERENCE NUMBER M an..14 

Unique message number assigned by the sender 

R S009 MESSAGE IDENTIFIER M 

R 0065 Message type identifier M an..6 

OSTRPT Order status report message 

R 0052 Message type version number M an..3 

D 

R 0054 Message type release number M an..3 

97A 

R 0051 Controlling agency M an..2 

UN United Nations 

X 0057 Association assigned code C an..6 

X 0068 COMMON ACCESS REFERENCE C an..35 

X S010 STATUS OF THE TRANSFER C 

X 0070 Sequence message transfer number M n..2 

X 0073 First/last sequence message transfer C a1 

Page 29


GROUP : 

SEGMENT : BGM BEGINNING OF MESSAGE 

SEGMENT STATUS : Mandatory segment repeat : 1 

FUNCTION : To indicate the type and function of a message and to transmit the identifying 

number. 

NOTES : 



R C002 DOCUMENT/MESSAGE NAME C 

R 1001 Document/message name, coded C an..3 

23 Status information 

O 1131 Code list qualifier C an..3 

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

X 1000 Document/message name C an..35 

R C106 DOCUMENT/MESSAGE IDENTIFICATION C 

R 1004 Document/message number C an..35 

Contains the Order status report number 

X 1056 Version C an..9 

X 1060 Revision number C an..6 

R 1225 MESSAGE FUNCTION, CODED C an..3 

1 Cancellation 

7 Duplicate (re-transmission) 

9 Original 

O 4343 RESPONSE TYPE, CODED C an..3 

AB Message acknowledgement 

NA No acknowledgement needed 

Page 30


GROUP : 

SEGMENT : DTM DATE / TIME / PERIOD 


FUNCTION : To specify date, and/or time, period. 

NOTES : All specified dates/times should be in the format 'CCYYMMDD'/'hhmm' unless all 

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

alternative format. 



R C507 DATE/TIME/PERIOD M 

R 2005 Date/time/period qualifier M an..3 

137 Document/message date/time 

318 Request date 

See code list EDIFACT for other values 

R 2380 Date/time/period C an..35 

R 2379 Date/time/period format qualifier C an..3 

102 CCYYMMDD 

203 CCYYMMDDhhmm 

204 CCYYMMDDhhmmss 


Page 31


GROUP : 

SEGMENT : RFF REFERENCE 

SEGMENT STATUS : Conditional segment repeat : 1 

FUNCTION : To specify a reference. 

NOTES : This segment is used only for identifying which Order status request message this 

message is responding to. 



R C506 REFERENCE M 

R 1153 Reference qualifier M an..3 

AAV Enquiry number 

R 1154 Reference number C an..35 

O 1156 Line number C an..6 

X 4000 Reference version number C an..35 

Page 32


GROUP : 

SEGMENT : FTX FREE TEXT 


FUNCTION : To provide free form or coded text information. 

NOTES : 



R 4451 TEXT SUBJECT QUALIFIER M an..3 

AAI General information 

See code list EDIFACT for other codes 

X 4453 TEXT FUNCTION, CODED C an..3 

O C107 TEXT REFERENCE M 

R 4441 Free text, coded C an..17 



O C108 TEXT LITERAL C 

R 4440 Free text C an..70 

O 4440 Free text C an..70 




O 3453 LANGUAGE, CODED C an..3 

Page 33


GROUP : Group 01 : NAD - SG02 

Mandatory group repeat : 99 

SEGMENT : NAD NAME AND ADDRESS 


FUNCTION : To specify the name/address and their related function, either by C082 only and/or 

unstructured by C058 or structured by C080 thru 3207. 

NOTES : This segment is used for identifying the parties relevant to the whole message. 

Party details can be given in coded form or clear text. We recommend the use of 

coded form,using C082. The basis of this codification could be one of the national or 

international code lists. Examples of such code lists are VAT-registration number, 

Chamber of commerce, Wirtschaftsvereinigung, Odette, EAN, etc. 



R 3035 PARTY QUALIFIER M an..3 

AG Agent/representative (in case an agent is involved) 

BY Buyer 

CN Consignee 

SE Seller 

SU Supplier 


O C082 PARTY IDENTIFICATION DETAILS C 

R 3039 Party id identification M an..35 


R 3055 Code list responsible agency, coded C an..3 

58 EUROFER 

91 Assigned by seller or seller's agent 

92 Assigned by buyer or buyer's agent 

See code list EDIFACT for VAT numbers 

O C058 NAME AND ADDRESS C 

R 3124 Name and address line M an..35 

O 3124 Name and address line C an..35 




O C080 PARTY NAME C 

R 3036 Party name M an..35 

O 3036 Party name C an..35 




O 3045 Party name format, coded C an..3 

Page 34




O C059 STREET C 

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

O 3042 Street and number/P.O. Box C an..35 



O 3164 CITY NAME C an..35 

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

O 3251 POSTCODE IDENTIFICATION C an..9 

O 3207 COUNTRY, CODED C an..3 

Use ISO 3166 two alpha country code. 

Page 35


GROUP : Group 02 : CTA - COM 

Conditional group repeat : 5 

SEGMENT : CTA CONTACT INFORMATION 


FUNCTION : To identify a person or a department to whom communication should be directed.. 

NOTES : 



O 3139 CONTACT FUNCTION, CODED C an..3 

CC Responsible person for information production 

IC Information contact 

OC Order contact 

See code list EDIFACT for other codes. 

R C056 DEPARTMENT OR EMPLOYEE, CODED C 

R 3413 Department or employee identification C an..17 

R 3412 Department or employee C an..35 

Page 36


GROUP : Group 02 : CTA - COM 


SEGMENT : COM COMMUNICATION CONTACT 


FUNCTION : To identify a communication number of a department or a person to whom 

communication should be directed. 

NOTES : 



R C076 COMMUNICATION CONTACT M 

R 3148 Communication number M an..512 

R 3155 Communication channel qualifier M an..3 

EM Electronic mail 

FX Telefax 

TE Telephone 

TL Telex 


Page 37


3.5.3 Detailed segment description - Detail section 

GROUP : Group 3 : DOC - DTM - SG4 - SG5 


SEGMENT : DOC DOCUMENT/MESSAGE DETAILS 


FUNCTION : To identify documents, either printed, electronically transferred, or referenced. 

NOTES : 



R C002 DOCUMENT/MESSAGE NAME M 

R 1001 Document/message name, coded C an..3 

105 Purchase order (spot order) 

221 Blanket order (open order) 

226 Call off order 

232 Hire order (service order) 




O 1000 Document/message name C an..35 

R C503 DOCUMENT/MESSAGE DETAILS C 

R 1004 Document/message number C an..35 

X 1373 Document/message status, coded C an..3 

X 1366 Document/message source C an..35 

X 3453 Language, coded C an..3 

X 3153 COMMUNICATION CHANNEL IDENTIFIER, CODED C an..3 

X 1220 NUMBER OF COPIES OF DOCUMENT REQUIRED C n..2 

X 1218 NUMBER OF ORIGINALS OF DOCUMENT REQUIRED C n..2 

Page 38


GROUP : Group 3 : DOC - DTM - SG4 - SG5 












4 Order date/time 

137 Document/message date/time 




102 CCYYMMDD 




Page 39


GROUP : Group 5 : LIN - PIA - IMD - MEA - GIN - RCS - FTX - SG6 - SG7 - SG15 

Conditional group repeat : 999.999 

SEGMENT : LIN LINE ITEM 


FUNCTION : To identify a line item by the line number and configuration level. 

NOTES : 



R 1082 LINE ITEM NUMBER C n..6 

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

R C212 ITEM NUMBER IDENTIFICATION C 

R 7140 Item number C an..35 

R 7143 Item number type, coded C an..3 

IN Buyer's item number 

PL Purchaser's order line number 

SA Supplier's article number 

VN Vendor item number 




91 Assigned by seller 

92 Assigned by buyer 

not used for values of the code list EDIFACT. 

X C829 SUB-LINE INFORMATION C 

X 5495 Sub-line indicator, coded C an..3 

X 1082 Line item number C an..6 

X 1222 CONFIGURATION LEVEL C n..2 

X 7083 CONFIGURATION, CODED C an..3 

Page 40




SEGMENT : PIA ADDITIONAL PRODUCT ID 


FUNCTION : To specify additional or substitutional item identification codes. 

NOTES : 



R 4347 PRODUCT ID FUNCTION QUALIFIER M an..3 

1 Additional identification 

5 Product identification 

R C212 ITEM NUMBER IDENTIFICATION M 



BP Buyer's part number 

EF Material code 

GS General specification number 

ON Customer order number 

PL Purchaser's order line number 

PO Purchase order number 

SA Supplier's article number 

VN Vendor item number 




91 Assigned by seller 

92 Assigned by buyer 

not used for values of the code list EDIFACT. 

O C212 ITEM NUMBER IDENTIFICATION C 















Page 41









Page 42




SEGMENT : IMD ITEM DESCRIPTION 


FUNCTION : To describe an item in either an industry or free format. 

NOTES : 



O 7077 ITEM DESCRIPTION TYPE, CODED C an..3 

C Code (from industry code list) 

F Free-form 

S Structured (from industry code list) 

X Semi-structured (code+text) 

R 7081 ITEM CHARACTERISTIC , CODED C an..3 

8 Product 

13 Quality 

38 Grade 

R C273 ITEM DESCRIPTION C 

O 7009 Item description identification C an..17 

See Eurofer code lists or industry code lists for values 


Identification of the code list 


58 EUROFER 



O 7008 Item description C an..35 

Plain language description 

O 7008 Item description C an..35 

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

Page 43




SEGMENT : MEA MEASUREMENTS 


FUNCTION : To specify physical measurements, including dimension tolerances, weights and 

counts. 

NOTES : 



R 6311 MEASUREMENT APPLICATION QUALIFIER M an..3 

AAE Measurement 

PD Physical dimensions (product ordered) 

WT Weight 

R C502 MEASUREMENTS DETAILS C 

R 6313 Property measured, coded C an..3 

AAL Net weight 

DP Depth 

DI Diameter 

ID Inside diameter 

G Gross weight 

LN Length dimension 

OD Outside diameter 

TH Thickness 

WD Width dimension 

WU Weight per unit length 

R 6321 Measurement significance, coded C an..3 

3 Approximately 

4 Equal to 


O 6155 Measurement attribute identification C an..17 

X 6155 Measurement attribute C an..70 

R C174 VALUE / RANGE C 

R 6411 Measure unit qualifier M an..3 

KGM Kilogram 

KL Kilogram/Metre 

MMT Millimetre 

MTR Metre 

TNE Tonne 


O 6314 Measurement value C an..18 

O 6162 Range minimum C n..18 

O 6152 Range maximum C n..18 

X 6432 Significant digits C n..2 

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

Page 44


GROUP : Group 6 : RFF - DTM 





NOTES : This segment is used for referencing documents, relating to the order item specified 

in the LIN segment. 





AEG Customer's specification number 

AEP Project number 

AEQ Drawing list number 

CO Buyer's order number 

CT Contract number 

LI Line item reference number 

MH Manufacturing order number 

ON Order number 

SS Seller's reference number 

VN Order number (vendor) 



O 1156 Line number C an..6 


Page 45


GROUP : Group 6 : RFF - DTM 




FUNCTION : To specify date, and/or time, period of the referenced document. 








137 Document / message date/time 

171 Reference date/time 




102 CCYYMMDD 


Page 46


GROUP : Group 7 : STS - DTM - PCD - QTY – SG8 - SG10 - SG11 - SG12 - SG13 


SEGMENT : STS TRANSPORT STATUS REPORT 


FUNCTION : To specify the type of industry sector/application to which this segment refers, giving 

the status and the status reason relevant to conducting business and/or services. 

NOTES : 



X C601 STATUS TYPE C 

X 9015 Status type, coded M an..3 

X 1131 Code list qualifier C an..3 

X 3055 Code list responsible agency, coded C an..3 

R C555 STATUS EVENT C 

R 9011 Status event, coded M an..3 

See Eurofer code list PS1 or PS2 for the codes used for each production status 


PS1 Production processes and stages 

PS2 Product status 


58 Eurofer 

X 9010 Status event C an..35 

X C556 STATUS REASON C 

X 9013 Status reason, coded M an..3 



X 9012 Status reason C an..35 
















Page 47









Page 48














7 Effective date/time 

291 Start date/time, planned 

292 Works completion date/time, planned 

324 Processing date/period 

334 Status change, date 




102 CCYYMMDD 



610 CCYYWW 


Page 49




SEGMENT : QTY QUANTITY 


FUNCTION : To specify a pertinent quantity. 

NOTES : 



R C186 QUANTITY DETAILS M 

R 6063 Quantity qualifier M an..3 

25 As is quantity 

99 Estimated quantity 


R 6060 Quantity M n..15 

R 6411 Measure unit qualifier C an..3 

KGM Kilogram 

MTR Metre 

PCE Pieces 

TNE Tonnes 


Page 50


GROUP : Group 08 : NAD - RFF - SG9 






NOTES : This segment is used for identifying the parties relevant to the status of the line item. 








CA Carrier 

CE Consignee 

CZ Consignor 

DP Delivery party 

MF Manufacturer 

OI Outside inspection party 

SU Supplier 






58 EUROFER 

















Page 51














Page 52


GROUP : Group 10 : TDT- LOC 


SEGMENT : TDT DETAILS OF TRANSPORT 


FUNCTION : To specify the transport details such as mode of transport, means of transport, its 

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

NOTES : 



R 8051 TRANSPORT STAGE QUALIFIER M an..3 

10 Pre-carriage transport 

20 Main-carriage transport 

30 On-carriage transport 

X 8028 CONVEYANCE REFERENCE NUMBER C an..17 

R C220 MODE OF TRANSPORT C 

R 8067 Mode of transport, coded C an..3 

10 Maritime 

20 Rail 

30 Road 

80 Inland waterway 

X 8066 Mode of transport C an..17 

X C228 TRANSPORT MEANS C 

X 8179 Type of means of transport identification C an..8 

X 8178 Type of means of transport C an..17 

O C040 CARRIER C 

O 3127 Carrier identification C an..17 



O 3128 Carrier name C an..35 

X 8101 TRANSIT DIRECTION, CODED C an..3 

X C401 EXCESS TRANSPORTATION INFORMATION C 

X 8457 Excess transportation reason, coded M an..3 

X 8459 Excess transportation responsibility, coded M an..3 

X 7130 Customer authorization number C an..17 

O C222 TRANSPORT IDENTIFICATION C 

O 8213 Id of means of transport identification C an..9 



O 8212 Id of means of transport C an..35 

O 8453 Nationality of means of transport, coded C an..3 

X 8281 TRANSPORT OWNERSHIP, CODED C an..3 

Page 53


GROUP : Group 10 : TDT- LOC 


SEGMENT : LOC PLACE/LOCATION IDENTIFICATION 


FUNCTION : To identify a country/place/location/related location one/related location two. 

NOTES : 



R 3227 PLACE/LOCATION IDENTIFICATION M an..3 

7 Place of delivery 

8 Place of destination 

O C517 LOCATION IDENTIFICATION C 

O 3225 Place/location identification C an..25 



O 3224 Place/location C an..70 

O C519 RELATED LOCATION ONE IDENTIFICATION C 

O 3223 Related place/location one identification C an..25 



O 3222 Related place/location one C an..70 

O C553 RELATED LOCATION TWO IDENTIFICATION C 

O 3233 Related place/location two identification C an..25 



O 3232 Related place/location two C an..70 

X 5479 RELATION, CODED C an..3 

Page 54


GROUP : Group 13 : PAC - QTY - SG14 


SEGMENT : PAC PACKAGE 


FUNCTION : To describe the number and type of packages/physical units. 

NOTES : 



O 7224 NUMBER OF PACKAGES C n..8 

X C531 PACKAGES DETAILS C 

X 7075 Packaging level, coded C an..3 

X 7233 Packaging related information, coded C an..3 

X 7073 Packaging terms and conditions, coded C an..3 

O C202 PACKAGE TYPE C 

O 7065 Type of packages identification C an..17 



58 EUROFER 



O 7064 Type of packages C an..35 

X C402 PACKAGE TYPE IDENTIFICATION C 

X 7077 Item description type, coded M an..3 

X 7064 Type of packages M an..35 

X 7143 Item number type, coded C an..3 

X 7064 Type of packages C an..35 

X 7143 Item number type, coded C an..3 

X C532 RETURNABLE PACKAGE DETAILS C 

X 8395 Returnable package freight payment responsibility, coded C an..3 

X 8393 Returnable package load contents, coded C an..3 

Page 55


GROUP : Group 14 : PCI - RFF 


SEGMENT : PCI PACKAGE IDENTIFICATION 


FUNCTION : To specify markings and labels on individual packages or physical units. 

NOTES : 



R 4233 MARKING INSTRUCTIONS, CODED C an..3 

1 Do not mark suppliers company name 

2 Mark customer's company name 

3 Mark customer's references 


O C210 MARKS & LABELS C 

R 7102 Shipping marks M an..35 

O 7102 Shipping marks C an..35 









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

X C827 TYPE OF MARKING 

X 7511 Type of marking, coded M an..3 



Page 56


GROUP : Group 14 : PCI - RFF 





NOTES : This segment is used for identification of the master label number, serial number, heat 

number , etc ... 





AAT Master label number 

ACO Iron charge number 

SE Serial number 


X 1156 Line number C an..6 


Page 57


GROUP : Group 15 : SCC - SG16 


SEGMENT : SCC SCHEDULING CONDITIONS 


FUNCTION : To specify scheduling conditions. 

NOTES : 



R 4017 DELIVERY PLAN STATUS INDICATOR, CODED M an..3 

1 Firm 

2 Commitment for manufacturing and material 

4 Planning/forecast 

X 4493 DELIVERY REQUIREMENTS, CODED C an..3 

X C329 PATTERN DESCRIPTION C 

X 2013 Frequency, coded C an..3 

X 2015 Despatch pattern, coded C an..3 

X 2017 Despatch pattern timing, coded C an..3 

Page 58


GROUP : Group 16 : LOC - DTM - QTY - SG17 


SEGMENT : LOC PLACE/LOCATION IDENTIFICATION 


FUNCTION : To identify the location to which part of the consignment is to be delivered. 

NOTES : 



R 3227 PLACE/LOCATION IDENTIFICATION M an..3 

7 Place of delivery 


O C517 LOCATION IDENTIFICATION C 

O 3225 Place/location identification C an..25 



O 3224 Place/location C an..70 

O C519 RELATED LOCATION ONE IDENTIFICATION C 

O 3223 Related place/location one identification C an..25 



O 3222 Related place/location one C an..70 

O C553 RELATED LOCATION TWO IDENTIFICATION C 

O 3233 Related place/location two identification C an..25 



O 3232 Related place/location two C an..70 

X 5479 RELATION, CODED C an..3 

Page 59







NOTES : 





2 Delivery date/time, requested 

63 Delivery date/time, latest 

64 Delivery date/time, earliest 




102 CCYYMMDD 

610 CCYYMM 

616 CCYYWW 

710 CCYYMM-CCYYMM 

716 CCYYWW-CCYYWW 

718 CCYYMMDD-CCYYMMDD 


Page 60







NOTES : 





21 Ordered quantity 

32 Minimum delivery batch 

33 Maximum delivery batch 




KGM Kilogram 

MTR Metre 

PCE Piece 

TNE Tonne 


Page 61


GROUP : Group 17 : STS - DTM - PCD - QTY - NAD 


SEGMENT : STS TRANSPORT STATUS REPORT 


FUNCTION : To specify the type of industry sector/application to which this segment refers, giving 

the status and the status reason relevant to conducting business and/or services. 

NOTES : 



X C601 STATUS TYPE C 

X 9015 Status type, coded M an..3 



R C555 STATUS EVENT C 

R 9011 Status event, coded M an..3 

See Eurofer code list PS1 or PS2 for the codes used for each production status 


PS1 Production processes and stages 

PS2 Product status 


58 Eurofer 

X 9010 Status event C an..35 





















Page 62









Page 63














7 Effective date/time 

291 Start date/time, planned 

292 Works completion date/time, planned 

324 Processing date/period 




102 CCYYMMDD 



610 CCYYWW 


Page 64







NOTES : 





25 As is quantity 

99 Estimated quantity 




KGM Kilogram 

MTR Metre 

PCE Pieces 

TNE Tonnes 


Page 65








NOTES : This segment is used for identifying the parties relevant to the status of the specified 

delivery schedule of the line item. 








CA Carrier 

CN Consignee 

CZ Consignor 

DP Delivery party 

MF Manufacturer 

OI Outside inspection party 

SU Supplier 






58 EUROFER 

















Page 66














Page 67


GROUP : 

SEGMENT : UNT MESSAGE TRAILER 

SEGMENT STATUS : Mandatory 1 

FUNCTION : Service segment ending a message, giving the total number of segments. 

NOTES : This segment would normally be added as part of the translation process. It has been 

included for completeness. 



R 0074 NUMBER OF SEGMENTS IN A MESSAGE M n..6 

R 0062 MESSAGE REFERENCE NUMBER M an..14 

Unique message number assigned by the sender 

Page 68


4. EXAMPLES 

4.1. Example of an order status report from ABC Sales department to the steel 

plant XYZ LTD 

On the next pages an example is presented of the translation of an order status report from 

ABC to the steel company XYZ LTD. The example has been limited to the customer order 

1302A. This order consists of 6 order items; four of them were produced in week 95-08, 

and the production of the two other items was planned in week 95-09. 

EDI message Information in the document and remarks 

HEADER - SERVICE SEGMENT 

UNH+ME000001+OSTRPT:D:95B:UN' First message in the interchange is an order status report message. 

HEADER SECTION 

BGM+23+ST95055+9' Order status report message with as example ST95055 as message 

reference number. 

DTM+137:199502241406:203' Date of the order status report message. (24-FEB-95 14:06) 

NAD+BY+1R0744' BY is used for buyer. The code 1R0744 is attributed to XYZ. 

NAD+SE+ABC' SE is used for seller. (ABC SALES DEPARTMENT) 

DETAIL SECTION (First order) 

DOC+105+1302A' Customer order number. (Cust.Order) 

(First order item) 

LIN+1++155613:VN' Vendor item number. (Regstr) 

PIA+1+AB123:GS' General specification number. (Specification Name) 

IMD+C+13+6032::91' The quality is 6032 assigned by the seller. (Quality) 

IMD+C+8+ROD::91' The order product is rod, coded as ROD by the seller. (Prof) 

MEA+PD+DI:4+MMT:12.5' Value of the diameter of the rod. (Size) 

STS++3:PS2:58' The status of the order item is in production in week 95-08. The 

status is given by using the Eurofer code list PS2. The code 3 in 

this code list is attributed to "In production". (Prog. Wt) 

DTM+7:199508:610' The production is planned in week 95-08. (Wk) 

QTY+25:23:TNE' Quantity in production is 23 Tonnes. (Prog Wt) 

(Second order item) 


PIA+1+CM345:GS' General specification number. (Specification Name) 









Page 69



(Third order item) 


PIA+1+CM345:GS' General specification number. (Specification Name) 









(Fourth order item) 


PIA+1+PR321:GS' General specification number. (Specification Name) 









(Fifth order item) 


PIA+1+PR322:GS' General specification number. (Specification Name) 




STS++2:PS2:58' The status of the order item is production planned in week 95-09. 

The status is given by using the Eurofer code list PS2. The code 2 

in this code list is attributed to "Production planned". (Prog. Wt) 



(Sixth order item) 

LIN+6++158001:VN' Supplier article number. (Regstr) 

PIA+1+LX246:GS' General specification number. (Specification Name) 




STS++2:PS2:58' The status of the order item is production planned in week 95-09. 


in this code list is attributed to "Production planned". (Prog. Wt) 



TRAILER - SERVICE SEGMENT 

UNT+055+ME000001' First message in the interchange is an order message. 

Page 70


4.2. Example of an order status report ZZZ ROD SUPPLIES to the customer 

XYZ LTD 


ZZZ to the customer XYZ LTD. The example has been limited to the first 7 lines of the 

customer progress print. 







DTM+137:19950124:102' Date of the order status report message. (24-01-95) 

NAD+BY+0347043' BY is used for buyer. The code 0347043 is attributed to XYZ. 

NAD+SE+ZZZ' SE is used for seller. (ZZZ ROD SUPPLIES) 


DOC+105+0412A' Customer order number. (CUSTOMER ORDER) 


LIN+1++782482:VN' Vendor item number. (ORDER) 

PIA+1+AB123:GS' General specification number. (SPECIFICATION) 

IMD+C+8+RD::91' The order product is rod, coded as RD by the seller. (FIN SHP) 

MEA+PD+DI:4+MMT:14.5' Value of the diameter of the rod. (FIN SIZE) 

MEA+PD+WT:4+KGM:10000' Order weight. (ORD.WT) 

STS++16:PS2:58' The status of the order item is delivered to the consignee. 


in this code list is attributed to "Delivered to consignee". (D/D WT) 

DTM+69:199451:610' Delivery week foreseen was week 51 of 1994. 

QTY+25:5442:KGM' Quantity delivered. (D/D WT) 

STS++5:PS2:58' The status of the order item is in stock. 


in this code list is attributed to "In stock". 

QTY+25:5732:KGM' Quantity in stock. (WT STOCK) 



PIA+1+PR322:GS' General specification number. (SPECIFICATION) 









Page 71














DETAIL SECTION (Second order) 

DOC+105+1401A' Customer order number. (CUSTOMER ORDER) 





















DTM+69:199503:610' Delivery week foreseen wass week 51 of 1994. 

















Page 72





PIA+1+AB123:GS' General specification number. (SPECIFICATION) 











Page 73


4.3. Example of an order status report of Ensidesa to the customer LESAKA 


Ensidesa to the customer Lesaka. The example has been limited to the orders with a 

confirmed delivery week 18 in 1996. 







DTM+137:19960409:102' Date of the order status report message. (09-04-96) 

NAD+BY+155' BY is used for buyer. The code 155 is attributed to Lesaka. 

NAD+SE+ENSIDESA' SE is used for seller. (Ensidesa) 


DOC+105+LL00300' Customer order number. (ORDER REFERENCIA) 


LIN+1++01:IN' Buyer's item number. (-POS REFERENCIA) 

PIA+1+390481-01:VN' Vendor item number. (ORDEN -POS) 

IMD+C+8+608::91' The ordered product is hot rolled coils, coded as 608 by the seller. 

(PRD) 

IMD+C+13+E91::91' The ordered quality is coded as E91 by the seller. (CLD) 

MEA+PD+TH:4+MMT:1.50' Value of the thickness. (ESPESR) 

MEA+PD+WD:4+MMT:800' Value of the width. (ANCHO) 

MEA+PD+WT:4+TNE:2000' Ordered weight. (ORD.WT) 




DTM+2:199618:610' Delivery week requested is week 18 of 1996. 

DTM+69:199618:610' Delivery week confirmed is week 18 of 1996. 

QTY+25:0:TNE' Quantity delivered is zero. (PESO PEDIDO) 

STS++5:PS2:58' The status is that a part of the material is already in stock 

(warehouse). 

The status is given by using the Eurofer code list PS2. 

The code 5 is attributed to warehouse. ( ALMACN APA) 

QTY+25:135:TNE' 135 Tonnes are in the warehouse. 

STS++25:PS1:58' The status is that a part of the material is at the casting. 


The code 25 is attributed to casting. (PDT ACERO) 

QTY+25:71:TNE' 71 Tonnes are at casting. 

STS++29:PS1:58' The status is that a part of the material is at the slabbing. 


The code 29 is attributed to slabbing. (DESBT) 

QTY+25:1996:TNE' 1996 Tonnes are at slabbing. 

STS++59:PS1:58' The status is that a part of the material is at the coiling line. 


The code 59 is attributed to coiling line. (PARRS) 

QTY+25:13:TNE' 13 Tonnes are at the coiling line. 

Page 74



DETAIL SECTION (Second order) 






(PRD) 

IMD+C+13+IF1::91' The ordered quality is coded as IF1 by the seller. (CLD) 














DETAIL SECTION (Third order) 






(PRD) 

IMD+C+13+EF9::91' The ordered quality is coded as EF9 by the seller. (CLD) 














Page 75







(PRD) 















STS++6:PS2:58' The status is that a part of the material is in quality control. 


The code 6 is attributed to quality control. (PARQUE 15) 

QTY+25:53:TNE' 53 Tonnes are in quality control. 





(PRD) 



















Page 76







(PRD) 



















(Fifth order item) 




(PRD) 



















Page 77



DETAIL SECTION (Fourth order) 






(PRD) 

IMD+C+13+D25::91' The ordered quality is coded as EF9 by the seller. (CLD) 


















(PRD) 

IMD+C+13+D25::91' The ordered quality is coded as EF9 by the seller. (CLD) 
















Page 78


All information provided in this documentation is provided “as is” without any warranties of any 

kind including warranties of accuracy, fitness for a particular purpose, or non-infringement or 

intellectual property. 

EUROFER shall not be held responsible for any errors or any loss resulting from any use of this 

document or the specification herein. 

The materials contained in this document may be copied provided that ALL copies retain the 

copyright and any other proprietary notices contained on the materials. No material may be 

modified, edited or taken out of context such as its use creates a false or misleading statement or 

impression as to the positions, statements or actions of the publisher. 

©2001 EUROFER. All rights reserved. All countries. 

Page 79

OSTRPT Order Status Report Message - Eurofer

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?