DELFOR Delivery Schedule Message - Eurofer

DELFOR 

Delivery Schedule Message 

Subset for Application in the European Steel 

Industry 

©Corporate Factory—Ph. D. Sarraute 

Version December 1998 

EDIFER WORKING GROUP - Message development

UN/EDIFACT D97.A DELFOR - Delivery schedule message 

DELIVERY SCHEDULE MESSAGE (Table of Contents) 

0. INTRODUCTION 2 

1. BACKGROUND INFORMATION 3 

1.1 General information 3 

1.2 The different types of the message 4 

1.3 The level of commitment 5 

1.4 Synchronisation of the information received 6 

2. DATA MODEL 7 

2.1 Data Model Format 7 

2.2 Data Model Diagram 8 

2.3 Data Model Entities 9 

2.4 Data Model Relationships 10 

2.5 Data Model Attributes 12 

3. SCOPE 17 

3.1 Functional Definition 17 

3.2 Field of Application 17 

3.3 Principles 17 

3.4 Message Usage 17 

4. MESSAGE DEFINITION 18 

4.1 Message Structure 18 

4.2 Mapping of the Data Model to the Message 19 

4.3 Branching Diagram of the Segments used by Eurofer 27 

4.4 General Description of the Message - Subset of Eurofer 31 

4.5 Detailed Description of the Message - Subset of Eurofer 37 

5. EXAMPLES 79 

5.1 Example of a delivery schedule (forecast only) of Scania 80 

5.2 Example of a delivery schedule (firm delivery only) of Scania 83 

Page 1


DELIVERY SCHEDULE MESSAGE 

0. INTRODUCTION 

This document provides the definition of the EUROFER subset of the Delivery schedule message 

based on the UN standard DELFOR message of the UN/EDIFACT directory D97A. 

This message has been created by the EDIFER "Message development" working group. The 

message is to be used in Electronic Data Interchange (EDI) between partners involved in the steel 

industry. 

The manual has been structured in the following format: 

- Background information describing the use of the Delivery schedule message. 

- 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 DELFOR, the 

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

segments used by Eurofer. 

- Examples of some Delivery schedules are provided to clarify the understanding of 

the message description 

Page 2


1. BACKGROUND INFORMATION 

1.1. General information 

In the steel industry the Delivery schedule message is sent by the customer to a supplier to 

give details on short, medium and long term material requirements in line with the 

conditions set out in the purchase contract or order. 

Delivery schedule messages are used to synchronise a continuous material flow (e.g. repeat 

business) between supplier and customer, when the delivery specifications are not 

completely defined in the contract or order. 

The delivery schedule message is intended to : 

- specify requirements based on the delivery conditions, 

- define the aspects that guarantee synchronisation between the customer and the 

supplier, 

- provide information allowing the supplier to plan future requirements, to purchase 

raw material, to fabricate and to plan the delivery of goods in line with the 

delivery instructions , specified in the delivery schedule. 

The customer and the seller must agree on the commercial conditions prior to starting up 

the use of the delivery schedule. A contract or an order must be issued by the customer 

defining the product specifications, and the commercial conditions, such as delivery 

conditions, payment conditions, price agreement, etc … 

A Delivery schedule message can be issued in any frequency (e.g. once per month, week), 

and may cover fixed or variable time periods (e.g. week, month, quarter, six months, a year). 

Medium and long term delivery schedules issued each month, can be altered by short-term 

delivery schedules issued each week. 

Guidelines for the understanding of the Delivery schedule are to be provided by the 

customer to the supplier with the aim of clarifying the use of the message in practice. 

Without guidance there is a risk of misinterpretation due to the degree of complexity of the 

message. However, it is the responsibility of the trading partners to determine the 

conditions for use of the message. 

All products (articles) specified in the Delivery schedule should be uniquely identified by an 

order item number, an article number or a part number. The identification number can be 

defined by either the customer or the supplier. The conditions for use of the unique 

identification number must be agreed between the partners. 

The deliveries requested in the Delivery schedule can be directed to a precise location 

within the customer’s premises or to an external warehouse or consignment warehouse. 

Direct deliveries to a precise location within the customer’s premises is an important 

requirement, having impact on the delivery process and the labelling of the goods to be 

delivered. This can be done using the consignee’s information as follows : 

Page 3


- The consignee’s identification number or the Consignee’s name and address 

identify the company or the business unit to which the despatch is consigned. If 

the address clearly identifies the delivery point for the specified delivery, no 

further information is required. 

- The place of discharge is required wherever there is more than one place of 

discharge at the consignee’s premises. 

- The place of destination can be used to provide details of the ultimate destination 

at the request of the consignee. This can either be a place of destination at the 

assembly line or a place of destination at the warehouse. 

- If a scheduled article in a delivery schedule should be delivered to several places 

of discharge and, or places of destination , the same scheduled article has to be 

repeated for each combination of place of discharge and, or destination to provide 

the scheduling information. 

1.2. The different types of the message 

The DELFOR message can be used in three different ways based on the agreement between 

the partners involved. The circumstances in which the types of message are used need to be 

clearly defined between the customer and the supplier (seller). 

The difference is made based on the level of commitment, specified in point 1.3. in the 

following way : 

- A firm delivery covers only the commitment for firm order, allowing the supplier 

to deliver goods according to the delivery plan given in the message. 

- A forecast delivery covers not only the planning/forecast, but also the 

commitment to manufacture the goods or to buy the raw material needed for the 

manufacturing of the goods. 

The different functions are : 

• Forecast Delivery schedule 

When the message covers only the forecast information, the message covers a longer period 

of time (e.g. from one month to one year) and is used to give the supplier a basis for 

planning his own production. Forecast information can be updated by sending a new 

forecast information, but it can never be used to order the delivery of the goods. The 

delivery of the goods can be requested by a DELFOR message having the function ‘firm 

delivery’ or by a DELJIT message requesting a delivery just-in-time. 

• Firm Delivery schedule 

When the DELFOR is used only to transmit the firm delivery information, the message 

covers a short period of time (e.g. one day to one month) and is the instruction to move the 

goods. Being used for a firm order, delivery quantities and dates given in the message 

should not be changed by another Delivery schedule message. 

Page 4


• Firm and Forecast delivery schedule 

In this case the Delivery schedule message covers the forecast information, with the 

different levels of commitment (planning/forecast, material, manufacturing), and the firm 

delivery information. 

Depending on the specified delivery period in the message, the information provided can 

replace partly or completely the information provided in the previous DELFOR message . 

To clarify the difference between a partial or a complete replacement of the delivery 

information given in a DELFOR message, the following two examples have been added. 

If the DELFOR message is only replacing partial the previously sent information the period 

for which the replacement is valid shall be given in the message. 

1. Complete replacement 

At the beginning of each week the customer sends a firm delivery DELFOR message to 

specify the delivery instructions from the second and subsequent four weeks. 

E.g. the previously sent DELFOR message has specified the deliveries for the first week of 

1998 up to the fourth week of 1998. The next DELFOR message specifies the deliveries 

from the second week of 1998 up to the fifth week of 1998. In this case the information 

provided for the second week up to the fourth week in the previous message is overruled 

with the specification given in the second DELFOR message. 

2. Partial replacement 

As an example the previously sent DELFOR message specifies the delivery period from 

01.01.1998 up to 31.01.98, the second message specifies deliveries only valid from 

15.01.1998 up to 22.01.1998). In this case the delivery information provided in the first 

message is updated with the information provided in the second message for the period 

15.01 up to 22.01.1998. The rest of the deliveries specified in the previously message is still 

valid. 

1.3. The level of commitment 

The responsibility between the customer and the supplier concerning the information 

provided and the delivery of the goods is indicated by means of the level of commitment. 

The following levels of commitment can be specified : 

♦ Firm : The supplier may deliver the goods according to the schedule. No further 

confirmation or notification is needed and there are no changes to the quantity or 

delivery time. 

♦ Forecast : 

Commitment for manufacturing : The supplier may start producing according the 

schedule. 

Commitment for material : The supplier may buy raw material according to the 

schedule. 

Planning/Forecast : The supplier can use the information according the schedule 

as a forecast information for his own planning system. 

Page 5


1.4. Synchronisation of the information received 

The DELFOR message allows the customer to define the aspects that guarantee the 

synchronisation between the supplying and receiving parties. This information allows the 

supplier to plan the resources necessary to fulfil the customers’ requirements, taking into 

account the despatches received and used to calculate the revised needs of the customer. 

The trading partners may agree to use one of the two following possibilities : 

• No synchronisation data is provided. 

In this case it is very difficult to align the new requests for delivery and forecast with the 

goods delivered, underway and received. Firm agreements between the parties are required 

about the previous despatched goods taken into account for the calculation of the new 

delivery schedule , otherwise this can lead to short or over deliveries. 

• Synchronisation data is provided. 

The message allows the synchronisation of data in different ways : 

The following data must always provided : 

- Delivery calculation date/time (date/time on which the requested delivery 

quantities are calculated), 

- Actual cumulative quantity received. 

To simplify the synchronisation at the supplier side, the customer can provide some 

supplementary information, such as 

- the start date when the cumulative quantity was set to zero, 

- the cumulative quantity given in the previous delivery schedule 

- the cumulative quantity scheduled. 

To inform the supplier of the latest received goods, the customer can specify up to a certain 

number the last received goods by providing the following information : 

- Quantities received or despatched 

- Despatch advice number or goods receipt reference number. 

Page 6


2. DATA MODEL 

2.1 Data Model Format 

The data model has been created to make it possible for potential users to understand the 

Eurofer subset of the Delivery schedule message. This data model gives the following 

information : 

- contents of the information (data elements) that can occur in the message, 

- relationships between the different data elements, 

- grouping of the data elements within the data entities, 

- and the relationship between data entities. 

To simplify the understanding of the data model, the model is defined at a summary level, 

description 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 delivery 

schedule); it has a name, a description and a value. 

The relationships of the data entities within the data model are reflected in the structure of 

the diagram in chapter 2.2. 

Page 7


2.2 Data Model Diagram 

Synchronisation 

infomation 

Has 

0,N 

Received - 

despatched 

quantities 

0,N 

Reference to 

Company 

Has 

0,N 

1 

1 

Delivery schedule 

Relates to 

Consignee 

Relates to 

Order item 

Has 

Delivery 

schedule details 

Page 8 

1 

1 

1,N 

1,N 

1 

1,N 

1 

1 

Reference to 

Message / 

Document 

Has 

0,1 

Delivery variance 

restrictions 

Has 

0,1 

Labelling - 

Package 

information


In these diagrams, 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 Consignee and Order item 

1. In the direction from Consignee to Order item. 

A Consignee can have one or more Order items. 

2. In the direction from Order item to Consignee. 

An Order item can only belong to one Consignee. 

2.3. Data model entities 

Because the data entities Company and Message / Document are not really basic information 

in this message and can be referenced at different levels, they have been put outside the data 

model and 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 The related data entities 

DELIVERY SCHEDULE COMPANY 

CONSIGNEE MESSAGE/DOCUMENT 

ORDER ITEM 

DELIVERY SCHEDULE DETAILS 

SYNCHRONISATION INFORMATION 

RECEIVED - DESPATCHED QUANTITIES 

DELIVERY VARIANCE RESTRICTIONS 

LABELLING AND PACKAGING INFORMATION 

DELIVERY This entity contains the general information about a delivery 

SCHEDULE schedule such as the type of schedule, its number and date, the 

period/date covered in the delivery schedule. 

CONSIGNEE This entity contains information about the party to which goods 

are to be consigned. 

Page 9


ORDER The entity contains the information about the goods ordered to allow 

ITEM reference to the correct order item specified in the order message as 

agreed between the customer and the supplier (seller). 

DELIVERY This entity provides the information about a requested delivery, such 

SCHEDULE as the quantity, the date/time/period, and the level of commitment. 

DETAILS 

SYNCHRONISATION This entity provides the cumulative quantities taken into 

INFORMATION account for the calculation of the revised delivery schedule 

details. 

RECEIVED - This entity gives information about the previous received and/or 

DESPATCHED despatched quantities taken into account for the calculation of the 

QUANTITIES delivery schedule details of the order item. 

DELIVERY This entity contains a set of data defining the maximum and minimum 

VARIANCE quantities for delivery during a specific period or per type of sub- 

RESTRICTIONS period. For example the minimum and maximum quantity to be 

delivered during any week of a specific period. 

LABELLING This entity is used to describe either the handling unit or a 

PACKAGING package type and can be used to specify the labelling information. 

INFORMATION 

COMPANY This entity identifies the parties with associated information, such as 

name and address, contact details and communication types and 

numbers. This can be the customer, supplier, consignor, consignee, 

manufacturer, etc ... . 

MESSAGE & This entity contains all the references to another message or 

DOCUMENT document. For example contract, order, previous delivery schedule. 

2.4. Data model relationships 

DELIVERY SCHEDULE - CONSIGNEE 

- Direction from Delivery schedule to Consignee. 

A Delivery schedule can relate to one or more Consignees. 

Page 10 

(relation : relates to - 1/1,N) 

- Direction from Consignee to Delivery schedule. 

The information concerning the delivery request of a Consignee belongs to one Delivery 

schedule.


CONSIGNEE - ORDER ITEM 

- Direction from Consignee to Order item. 

A Consignee relates to one or more Order items. 

- Direction from Order item to Consignee. 

An Order item belongs to one Consignee. 

ORDER ITEM - DELIVERY SCHEDULE DETAILS 

- Direction from Order item to Delivery schedule details. 

An Order item can have one or more Delivery schedule details . 

- Direction from Delivery schedule details to Order item. 

A Delivery schedule details belongs to one Order item. 

Page 11 

(relation : relates to - 1/1,N) 

(relation : has - 1/1,N) 

ORDER ITEM - SYNCHRONISATION INFORMATION 


- Direction from Order item to Synchronisation information. 

An Order item can have no, one or more Synchronisation information. 

- Direction from Synchronisation information to Order item. 

A Synchronisation information belongs to one Order item. 

ORDER ITEM - RECEIVED-DESPATCHED QUANTITIES 


- Direction from Order item to Received-despatched quantities. 

An Order item can have no, one or more Received-despatched quantities. 

- Direction from Received-despatched quantities to Order item. 

A Received-despatched quantities belongs to one Order item.


ORDER ITEM - DELIVERY VARIANCE RESTRICTIONS 

(relation : has - 1/0,1) 

- Direction from Order item to Delivery variance restrictions. 

An Order item can have no or one Delivery variance restrictions. 

- Direction from Delivery variance restrictions to Order item. 

A Delivery variance restrictions belongs to one Order item. 

ORDER ITEM - LABELLING-PACKAGE INFORMATION 

(relation : has - 1/0,1) 

- Direction from Order item to Labelling-package information. 

A Order item can give details on no or one Labelling-package information. 

- Direction from Labelling-package information to Order item. 

A Labelling-package information belongs to one Order item. 

2.5. Data model attributes 

For each entity specified under point 2.3. Data model entities, a list of attributes and a 

description is given. 

ENTITY : DELIVERY SCHEDULE 

document/message type 

Document/message type expressed in code specifying the message function 

(e.g. Delivery schedule, forecast, firm delivery). 

document/message number 

Reference number assigned to the document/message by the issuer (e.g. delivery 

schedule number). 

document/message date/time 

Date and if necessary the time when the document/message was issued. 

validity period 

Start date/time and end date/time of the validity period of the delivery schedule. 

release type code 

Clarification about the meaning of the date/time/period given in the delivery 

schedule details (e.g. its the delivery date/time requested, shipment date/time 

request, availability date/time or the production/manufacture date). 

Page 12


schedule release frequency 

ENTITY : CONSIGNEE 

The frequency of transmission of the delivery schedule (e.g. daily, weekly or 

monthly). 

company code, name and address 

Code and if necessary the name and address, contact persons and 

communication channels of the consignee. 

ENTITY : ORDER ITEM 

order number buyer 

Unique number given by the buyer to identify an order. 

order date buyer 

Date when the order was issued by the buyer. 

order item number 

Unique number given to an order item for identification. 

seller’s article number 

Seller’s reference identifying an article or product. 

buyer’s article number 

Buyer’s reference identifying an article or product. 

part number 

Buyer’s identification number attributed to the article. 

drawing/revision number (Design revision number) 

Reference number identifying a revision of a drawing of the article. 

drawing/revision date (Design revision date) 

Date assigned to the drawing revision. 

engineering change number 

Reference number assigned an engineering change. 

engineering change date 

Date assigned to the engineering change. 

place of discharge 

The place within the consignee premises where goods are (to be) unloaded 

(e.g. Dock and gate). 

Page 13


additional internal address (place of destination) 

An internal location within the consignee premises, where goods are moved to after 

they have been unloaded (e.g. an assembly line, a warehouse). 

order item remarks 

A remark related to the order item. 

ENTITY : DELIVERY SCHEDULE DETAILS 

level of commitment 

Code indicating the level of commitment of a delivery instruction. 

delivery date/time or period 

Date and time or period of the requested delivery. 

delivery date/time first 

Earliest date/time of the requested delivery. 

delivery date/time last 

Latest date/time of the requested delivery. 

quantity to be delivered 

The quantity scheduled for the requested delivery. 

reference of the delivery 

Reference number given to a specific requested consignment. 

ENTITY : SYNCHRONISATION INFORMATION 

level of commitment 

Code indicating the level of commitment of the synchronisation information. 

delivery calculation date/time 

Date and time on which the requested delivery quantities are calculated. 

quantities accumulation start date 

Date and time on which the accumulation of quantities started. 

actual cumulative quantity received 

Actual quantity received by the consignee, starting from the accumulation start 

date. 

cumulative quantity since accumulative start date 

The quantity scheduled for delivery of a specific order item since the quantities 

accumulation start date. 

cumulative quantity previously scheduled 

The quantity scheduled for delivery of a specific order item by the previous 

delivery schedule. 

Page 14


actual cumulative quantity scheduled 

The actual cumulative quantity scheduled in the delivery schedule message by the 

buyer. 

delivery quantity balance 

The difference between the cumulative quantity scheduled in the previous delivery 

schedule and the cumulative quantity received from the accumulation start date. 

For positive values, the quantity scheduled is greater than the quantity received. 

ENTITY : RECEIVED - DESPATCHED QUANTITIES 

quantity received 

The quantity received by the consignee. 

goods receipt reference 

Unique identification given to the receipt of goods. 

reception date 

The date/time when the goods were received by the consignee. 

quantity despatched 

The quantity despatched by the seller to the consignee. 

despatch advice number 

Unique identification number of a despatch. 

despatch advice date 

The date/time of the despatch advice message/document 

ENTITY : DELIVERY VARIANCE RESTRICTIONS 

date/time/period of the delivery variance restrictions 

The start date and the end date of the period, or the period valid for the delivery 

variance restrictions. 

number of working days within the referenced period 

Number of working days included in the referenced period ‘date/time/period’ of the 

delivery variance restrictions. 

daily average quantity within the referenced period 

Average quantity scheduled for each working day of the referenced period. 

period maximum quantity 

Maximum quantity which may be called-off during the referenced period. 

period minimum quantity 

Minimum quantity which may be called-off during the referenced period. 

Page 15


ENTITY : LABELLING - PACKAGING INFORMATION 

type of package 

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

dimensions of the package 

Length, width, height, inside diameter and outside diameter of the package. 

number of pieces per package 

Number of pieces requested per package unit 

marks and numbers 

These are all the kinds of information that must be printed on the transport 

label of the package units. 

marking label number 

Number(s) requested to be put on the label of the package unit(s). 

THE RELATED DATA ENTITY 

ENTITY : COMPANY 

company code, name and address 

Code and if necessary the name and address, contact persons and 

communication channels of the partners involved. 

Examples are : buyer, supplier, manufacturer, delivery party, invoicee. 

ENTITY : MESSAGE / DOCUMENT 

message / document type 

Code identifying a referenced message or document (e.g. previous delivery schedule 

message, order, contract document). 

message / document number 

Identification number of a referenced message or document. 

message /document date 

The date/time of the referenced message or document. 

Page 16


3. SCOPE 

3.1. Functional definition 

This message is used in the steel industry to provide information from a party who is 

planning the use or consumption of products (customer) to a party who has to plan for the 

supply of the products (supplier). The message gives the requirements regarding details for 

short term delivery and/or medium to long term scheduling for products. The scheduling 

can be used to authorise manufacturing and/or the provision of basic materials for the 

production. 

3.2. Field of application 

This message provides the definition of the Eurofer delivery schedule message to be used in 

Electronic Data Interchange between trading partners. 

3.3. Principles 

The Delivery schedule message shall be used to : 

- specify forecast production requirements, either for planning/forecast, commitment for 

material and commitment for manufacturing and material. 

- specify firm delivery dates and the quantities scheduled, 

- define the aspects that guarantee the synchronisation between the supplying and 

receiving parties, thus allowing the supplier to plan for the resources necessary to fulfill 

customer requirements. 

The EDIFACT - Delivery schedule message provides the option to use one of the two 

scheduling methods. 

Method 1 : Delivery point driven 

This is when for a given delivery point a number of different products are to be delivered. 

This means that the address of the consignee triggers the product information. 

Method 2 : Product driven 

This is when a given product is to be delivered to a number of different delivery points. 

This means that the product information triggers the delivery address information. 

Eurofer has decided to use only the Delivery point driven method. 

3.4. Message usage 

The Delivery schedule message can be used in three different ways based on the agreement 

between the partners involved. The different functions of the message are explained in 

chapter 1.2. 

Page 17


4. MESSAGE DEFINITION 

4.1 Message Structure 

The Delivery schedule message of UN/EDIFACT is structured in two sections, a Heading 

Section and a Detail Section. 

4.1.1. Message structure - Heading section 

The heading section is used to give the general information relating to the whole message. 

Examples of this kind of information are the references to the initial contract, or information 

about the customer and the supplier, references and contacts relevant for the whole message. 

4.1.2. Message structure - Detail section 

The detail section is controlled by the segment group 6 (with trigger segment GIS). 

The trigger segment GIS provides the information if the delivery schedule is location or 

product driven. Based on the decision taken by Eurofer, the GIS segment will indicate that 

the location driven approach is used. This means that the segment group 7 (triggered by the 

segment NAD) is used to give details about the consignee, such as the delivery address and 

references, documents and contacts relevant for the consignee. 

The segment group 12 (trigger segment LIN) provides details on each individual item 

regarding the product identification, references, the specific location of discharge and 

destination, package and labelling information, scheduling information and synchronisation 

data to interpret the scheduling information. 

Page 18


4.2. Mapping of the Data model to the message 

SEGMENT 

GROUP 

To understand the mapping process, completed by the EDIFER working group, it is 

necessary to have knowledge about the structure of the official UNSM DELFOR message 

and the functionality of the segment groups and segments as defined by the EDIFACT 

message development group EEG1 - 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. 

In the following table a short overview is given about the meaning and the functionality of 

the segment groups and segments in the message. The information given covers : 

- the segment group 

- the segment 

- the description of the meaning and the functionality 

- the comments of the EDIFER working group. 

SEGMENT FUNCTION COMMENTS 

HEADING SECTION 

BGM To identify the type of Delivery schedule Mandatory. 

message and its number. 

DTM To specify general date/time/period related to Must be used at least once to identify 

the whole message. 

the date of the Delivery schedule. 

FTX Free text information. Not recommended by Eurofer. 

GROUP 1 To specify referencing documents and their date, 

related to the whole message. 

RFF For referencing documents related to the whole 

DELFOR message. 

DTM To specify the date/time of the reference. 

GROUP 2 To identify the parties (companies) relevant to Must be used to specify at least the 

the whole message. 

supplier and the customer. 

NAD Function, name and address of the party. 

GROUP 3 To specify referencing documents and their date Not used 

related to the party. 

RFF To identify the reference related to the party. 

DTM To specify the date/time of the reference. 

GROUP 4 To give contact details of the party. 

CTA To identify to whom communication should be 

directed. 

COM To identify communication type and numbers. 

GROUP 5 To specify details of the mode and means of Not used 

transport relating to the whole message 

TDT To specify the carriage, mode and means of 

transport. 

DTM Date/time/period relating to the TDT segment. 

Page 19


SEGMENT 

GROUP 

GROUP 6 (GIS, SG.7 

SG.12) 


DETAIL SECTION 

To provide details on delivery points and 

products and related information using the one 

of both scheduling methods. 

GROUP 7 To identify the delivery point and its attached 

information when the delivery point driven 

approach is used. 

NAD To identify the consignee. 

LOC To identify specific location at the consignee 

address to which the product should be 

delivered. 

FTX Free text information. Not used. 

GROUP 8 To give references relevant to the consignee. Not used. 

RFF To give references related to the consignee. 

DTM Date/time/period of the reference. 

GROUP 9 To provide information relating to documents 

required for the consignee. 

DOC To describe the documents required for the 

specified consignee. 

DTM Date/time/period of the document required. 

GROUP 10 To give contact details of the consignee. 

CTA To identify to whom communication should be 

directed. 

COM To identify communication type and numbers. 

Page 20 

GIS segment indicates that the 

delivery point driven approach is 

used. 

Not used, (see group 12). 

Not used. 

GROUP 11 To specify details of the mode and means of Not used. 

transport relating to the specified delivery point. 

TDT To specify carriage, and the mode and means of 

transport. 

DTM Date/time/period of departure or arrival relating 

to the TDT segment. 

GROUP 12 To provide detailed information, on each line of 

the delivery schedule. 

LIN To identify the line item by the line number and 

additionally, identifying the product. 

PIA To provide additional identification to the 

product specified in the LIN segment. 

IMD To describe the product. 

MEA To specify physical measurements of the item to 

be delivered. 

ALI To indicate that the line item is subject to special 

conditions due to origin, customs reference, 

embargo regulations or commercial factors. 

GIN To provide identity number to be applied to the 

goods to be delivered. 

GIR To provide related identification numbers for the 

line item specified in the LIN segment. 

Not used. 

Not used.


SEGMENT 

GROUP 


LOC To identify specific location to which products, 

as specified in the LIN segment, should be 

placed after delivery (e.g. dock, gate, point of 

destination). 

DTM To specify date/time/period details relating to 

the line item only. 

FTX Free text information. Not recommended by Eurofer. 

GROUP 13 To give references and where necessary, their 

dates, relating to the line item. 

RFF To identify the referenced document. 

DTM To specify the date/time of the referenced 

document. 

GROUP 14 To specify details of the mode and means of 

transport and date/time/period related to the 

specified transport details. 

TDT To specify carriage, and the mode and means of 

transport. 

DTM To indicate the date/time/period details relating 

to the TDT segment. 

GROUP 15 To specify quantities and associated date not 

related to schedules and when relevant the 

references. 

QTY To specify quantities for synchronisation, 

received - despatched quantities not related to 

schedules. 

DTM Date/time/period relating to the quantity. 

GROUP 16 To give references related to the quantities and 

when necessary their date. 

RFF To identify references related to the quantity. 


GROUP 17 To specify the schedule information. 

SCC To specify the level of commitment. 

GROUP 18 To specify product quantities and associated 

dates. 

QTY To specify scheduled quantities. 

DTM Date/time/period relating to the given quantity. 

GROUP 19 To specify references associated with the given 

scheduled quantity. 

RFF To identify references related to the quantity 

(e.g. Kanban card number). 


GROUP 20 To identify the packaging, physical dimensions 

and marks and numbers for the goods specified 

in the line item. 

PAC To specify the number and type of packages. 

Page 21 

Not used.


SEGMENT 

GROUP 


MEA To specify physical measurement of the 

packages described in the PAC segment. 

QTY To specify the quantity per package described in 

the PAC segment. 

DTM To specify date/time/period details relating to 

the physical units (packages) described in the 

PAC 

GROUP 21 To specify markings, labels and packing. 

PCI To specify markings and, or labels used on 

individual physical units (packages) described in 

the PAC segment. 

GIN To provide identity numbers to be applied to the 

packages. 

GROUP 22 NAD-LOC- 

FTX-SG23- 

SG24- 

SG25- 

SG27-SG30 

To provide details of the individual delivery 

points for the given product, when the product 

driven approach is used. 

Page 22 

Not used. 

Not used.


The mapping is done starting from the entities, relationships and attributes of the data model to the 

EDIFACT message. 

This mapping is presented as a table containing the entities of the following information ; 

- the attributes 

- the segment group number 

- the segment by its tag 

- the Edifact data element 

- remarks about the usage. 

ATTRIBUTE SEGMENT 

GROUP 

SEGMENT TDID - Data 

element 

Page 23 

REMARKS 

Entity : DELIVERY SCHEDULE 

Document/message type BGM 1001 

Document/message number BGM 1004 

Document/message date/time DTM 2380 DTM segment in the header, 

following BGM. Use code 137 

in element 2005. 

Validity period DTM 2380 DTM segment in the header, 

following BGM. Use code 273 

or 157 in element 2005. 

Release type code DTM 2005 DTM segment in the header, 

following BGM. Use code 2, 

10, 44 or 94 in element 2005. 

Schedule release frequency DTM 2379 DTM segment in the header, 

following BGM, with code 264 

in element 2005. 

Entity : CONSIGNEE 

Company code, name and address of 

the consignee 

Group 7 NAD 3039 

or 

C058, C080, 

Contact information Group 10 CTA 3412 

or 

3413 

Communication contact Group 10 COM 3148 

or 

3155 

Code form, structured or clear 

form can be used. 

C059, 3164, 3229, 3521, 3207 

Entity : ORDER ITEM 

Order number buyer Group 13 RFF 1154 Use the code ON in element 

1153. 

Order date buyer Group 13 DTM 2380 Use the code 137 or 171 in 

Order item number Group 13 

or 

Group 12 

RFF 

LIN 

Seller’s article number Group 12 LIN or 

PIA 

Buyer’s article number Group 12 LIN or 

PIA 

1154 

element 2005. 

Use the relevant code for 1153. 

7140 Use the code IN in element 

7143. 

7140 Use the code SA in element 

7143. 


7143.



GROUP 

Entity : ORDER ITEM 

Part number Group 12 LIN or 


element 

PIA 

Page 24 

REMARKS 


7143. 

Drawing/revision number Group 12 PIA 7140 Use the code DR in element 

7143. 

Drawing/revision date Group 12 DTM 2380 Use the code 380 in element 

2005. 

Engineering change number Group 12 PIA 7140 Use the code EC in element 

7143. 

Engineering change date Group 12 DTM 2380 Use the code 60 in element 

Place of discharge Group 12 LOC 

Additional internal address 

(Place of destination) 

Group 12 LOC 

3225 

or 

3224 

3225 

or 

3224 

Order item remarks Group 12 FTX 4440 

2005. 

Use the code 11 for element 

3227. 

Use the code 159 for element 

3227. 

Entity : DELIVERY SCHEDULE 

DETAILS 

Level of commitment Group 17 SCC 4017 Use the relevant code. 

Delivery date/time or period Group 18 DTM 2380 Use code 2 in element 2005 

Delivery date/time first Group 18 DTM 2380 Use code 64 in element 2005. 

Delivery date/time last Group 18 DTM 2380 Use code 63 in element 2005. 

Quantity to be delivered Group 18 QTY 6060 Use the relevant code in 6063. 

Reference of the delivery Group 19 RFF 1153 Use the relevant code in 1154. 

Entity : SYNCHRONISATION 

INFORMATION 

Level of commitment Group 17 SCC 4017 Use the relevant code. 

Delivery calculation date/time Group 12 DTM 2380 Use code 257 in element 2005. 

Quantities accumulation start date Group 12 DTM 2380 Use code 51 in element 2005. 

Actual cumulative quantity received Group 15 

or 18 

QTY 6060 Use code 70 in element 6063. 

Cumulative quantity since Group 15 QTY 6060 Use code 186 in element 6063. 

accumulative start date 

or 18 

Cumulative quantity previously Group 15 QTY 6060 Use code 79 in element 6063. 

scheduled 

or 18 

Actual cumulative quantity scheduled Group 15 QTY 6060 Use code 78 in element 6063. 

or 18 

Delivery quantity balance Group 15 

or 18 

QTY 6060 Use code 73 in element 6063. 

Entity : RECEIVED- 

DESPATCHED QUANTITIES 

Quantity received Group 15 QTY 6060 Use code 48 in element 6063. 

Goods receipt reference number Group 16 RFF 1154 Use code SI in element 1153. 

Reception date Group 15 DTM 2380 Use code 310 in element 2005. 

Quantity despatched Group 15 QTY 6060 Use code 12 in element 6063. 

Despatch advice number Group 16 RFF 1154 Use code AAK in element 

1153. 

Despatch advice date Group 16 DTM 2380 Use code 171 in element 2005.



GROUP 

Entity : DELIVERY VARIANCE 

RESTRICTIONS 

Date/time/period of the delivery 

variance restrictions 

Number of working days within the 

referenced period 

Daily average quantity within the 

referenced period 


element 

Page 25 

REMARKS 

Group 15 DTM 2380 Use code 206 in element 2005. 

Group 15 QTY 6060 Use code 77 in element 6063. 

Group 15 QTY 6060 Use code 1 in element 6063. 

Period maximum quantity Group 15 QTY 6060 Use code 54 in element 6063. 

Period minimum quantity Group 15 QTY 6060 Use code 53 in element 6063. 

Entity : LABELLING- 

PACKAGING INFORMATION 

Type of package Group 20 PAC 7065 

Dimensions of the package Group 20 MEA 6314 Use the relevant code for 

element 6314. 

Number of pieces Group 20 QTY 6060 Use the code 52 in element 

6063. 

Marks and numbers Group 21 PCI 7102 

Marking label number Group 21 GIN 7402 Use the code ML in element 

7405. 

Entity : COMPANY 

Company code, name and address Group 2 NAD 3039 

or 

C058, C080, 

Contact information Group 4 CTA 3412 

or 

3413 

Communication contact Group 4 COM 3148 

or 

3155 

Entity : MESSAGE / DOCUMENT 

Message / document type Group 1 

or 

Group 13 

Message / document number Group 1 

or 

Group 13 

Message / document date Group 1 

or 

Group 13 

RFF 

1153 

Code form, structured or clear 

form can be used. 

C059, 3164, 3229, 3521, 3207 

RFF 1153 

RFF 1154 

and 

RFF 1156 

DTM 2380 Use the code 171 in element 

2005


The use of the segments groups 15 and 17 

The difficulty when implementing the DELFOR message is the use of the segment group 15 

(triggered by quantity) and segment group 17 (triggered by SCC) at the line item. This is 

due to the fact that the two segment groups were designed to transmit any kind of quantity 

related to the line item. These quantities are specified in the following entities : 

- Delivery schedule details 

- Synchronisation information 

- Received -despatched quantities 

- Delivery variance restrictions. 

In the data model and the DELFOR message, there are four main types of quantities to be 

transmitted in one of the two groups : 

1. Delivery schedule details 

This quantity information is transmitted by using the segment group 17. 

- In the segment SCC the level of commitment is given and if necessary a delivery 

pattern. 

- The segment QTY is used to specify the requested delivery quantity. 

- The segment DTM specifies the requested delivery date/time/period. 

- The segment RFF can be used to refer to a part consignment number. 

2. Synchronisation data 

Only when the synchronisation data is provided at the global level, then the segment group 

15 shall be used. 

- The segment QTY is used to specify the type of cumulative quantity and the value. 

- The segment DTM is used to specify the related date and time. 

When the synchronisation data is provided at the level of commitment, then the segment 

group 17 shall be used. 

- The segment SCC is used to give the level of commitment applicable to the 

synchronisation data. 

- The segment QTY is used to specify the type of cumulative quantity and the value. 

- The segment DTM is used to specify the related date and time. 

3. Received-despatched quantities 

This information is transmitted by using the segment group 15. 

- The segment QTY is used to specify the received or the despatched quantity. 

- The segment DTM is used to give goods receipt date/time. 

- The segment group 16, triggered by the segment RFF is used to give reference to the 

Despatch advice number or Shipper’s ID number for shipment and the despatch 

date/time. 

4. Delivery variance restrictions 

This information is transmitted by using the segment group 15. 

- The segment QTY is used to specify the delivery variance restrictions, such as number 

of working days, daily average quantity, minimum and maximum quantity. 

- The segment DTM is used to specify the related date/time/period. 

Page 26


4.3 Branching Diagram of the Segments used by Eurofer 

DELFOR Delivery schedule message version D97A 

Message to enable the transmission of the requirements regarding details 

for short term delivery and/or medium to long scheduling for products. 

The codes used for the usage indicator (USG. IND.) for the segments. 

R for REQUIRED - Should always be used in the message 

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

X for EXCLUDED - Not used in the message. 

Heading Section 

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

R 38 UNH Message header M 1 

R 39 BGM Beginning of message M 1 

R 40 DTM Date/time/period M 10 

O 41 FTX Free text C 5 

O SEGMENT GROUP 1 C 10 

R 42 RFF Reference M 1 

O 43 DTM Date/time/period C 1 

R SEGMENT GROUP 2 C 99 

R 44 NAD Name and address M 1 

X SEGMENT GROUP 3 C 10 

X RFF Reference M 1 

X DTM Date/time/period C 1 


R 46 CTA Contact information M 1 

O 47 COM Communication contact C 5 


X TDT Details of transport M 1 


Page 27


Detail Section 

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


R 48 GIS General indicator M 1 


R 49 NAD Name and address M 1 

X LOC Place/location identification C 10 

X FTX Free text C 5 





X DOC Document/message details M 1 



R 51 CTA Contact information M 1 

O 52 COM Communication contact C 5 





R 53 LIN Line item M 1 

O 54 PIA Additional product id C 10 

O 56 IMD Item description C 10 

O 57 MEA Measurements C 5 

O 58 ALI Additional information C 5 

X GIN Goods identity numbers C 999 

X GIR Related identification numbers C 999 

O 59 LOC Place/location identification C 999 


O 61 FTX Free text C 5 








R 64 QTY Quantity M 1 





Page 28



R 68 SCC Scheduling conditions M 1 


R 69 QTY Quantity M 1 






R 73 PAC Package M 1 

O 74 MEA Measurements C 10 

O 75 QTY Quantity C 5 



R 76 PCI Package identification M 1 

O 77 GIN Goods identity numbers C 10 


X NAD Name and address M 1 

X LOC Place/location identification C 10 

X FTX Free text C 5 


X DOC Document/message details M 1 



X CTA Contact information M 1 

X COM Communication contact C 5 


X QTY Quantity M 1 






X SCC Scheduling conditions M 1 


X QTY Quantity M 1 








R 78 UNT Message trailer M 1 

Page 29


Level 

00 

01 

02 

03 

04 

Level 

03 

04 

04 

05 

06 

EUROFER DELFOR DELIVERY SCHEDULE MESSAGE VERSION - DECEMBER 1998 UN/EDIFACT DIRECTORY : D97.A 

UNH 

M 1 

BGM 

M 1 

DTM 

M 10 

FTX 

C 5 

G01 

C 10 

RFF 

M 1 

DTM 

C 1 

G02 

C 99 

NAD 

M 1 

G04 

C 5 

CTA 

M 1 

COM 

C 5 

G06 

C 9999 

GIS 

M 1 

G07 

C 1 

NAD 

M 1 

G10 

C 5 

CTA 

M 1 

COM 

C 5 

G12 

C 9999 

LIN 

M 1 

Branching Diagram Page 1 

PIA 

C 10 

Page 30 

IMD MEA ALI 

C 10 C 5 C 5 

LOC 

C 999 

DTM FTX 

C 5 

C 5 

See page 2 

EUROFER DELFOR DELIVERY SCHEDULE MESSAGE VERSION - DECEMBER 1998 UN/EDIFACT DIRECTORY : D97.A 

See page 1 

G13 

C 10 

RFF 

M 1 

DTM 

C 1 

G15 

C 10 

QTY 

M 1 

DTM 

C 1 

G16 

C 10 

RFF 

M 1 

DTM 

C 1 

G17 

C 999 

SCC 

M 1 

G18 

C 999 

QTY 

M 1 

DTM 

C 2 

G19 

C 10 

RFF 

M 1 

DTM 

C 1 

G20 

C 99 

PAC 

M 1 

MEA 

C 10 

Branching Diagram Page 2 

QTY 

C 5 

G21 

C 10 

PCI 

M 1 

GIN 

C 10 

UNT 

M 1


4.4 General description of the message - subset of Eurofer 

4.4.1 Message definition and segment clarification 

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

segments within the message defined by Eurofer. The message consists of two sections, a 

heading section and a detail section. 

The heading section is representing the corresponding references and the parties involved. 

Some detail information which applies or relates to all the line items of the detail section can 

also be given in the heading section. 

This section should be read in conjunction with the segment usage and the branching 

diagram (chapter 4.3.) which indicates the required (R) and optional (O) segments and 

segment groups. 

The following guidelines and principles apply to the whole message of Eurofer and are 

intended to facilitate the understanding and the implementation of the message. 

All the specified data/times (segment DTM) should be in the format 'CCYYMMDD'/'hhmm' 

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

an alternative format. 

Periods should be specified as whole numbers representing the required period as indicated 

in the format qualifier (weeks, month, etc) 

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

Optional (conditional) data that are not required in the message should not be included. 

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

segment qualifier of the trigger segment of the group. 

4.4.2 Message description - Heading section 

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

Segment UNH, Message Header 

A service segment starting and uniquely identifying a message. The message type code for 

the Delivery schedule message is DELFOR. 

Note: Delivery schedule messages conforming to this document must contain the following 

data in segment UNH, composite data element S009 : 

Data elements ; - 0065 DELFOR 

- 0052 D 

- 0054 97A 

- 0051 UN 

Page 31


Segment BGM, Beginning of message 

A segment for unique identification of the Delivery schedule message by means of its type 

(e.g. firm, forecast, delivery schedule), its number and its function (original, replacement). 

Segment DTM, Date/time/period 

The DTM segment shall be specified at least once to identify the Delivery schedule message 

date. This segment can be included to indicate the beginning and the end date of the 

schedule. 

Segment FTX, Free text 

A segment with free text in coded or clear form to give further clarification when required. 

In computer to computer exchanges such text will normally require the receiver to process 

this segment manually. 

Eurofer recommends not to use this segment. 

Segment group 1: RFF-DTM 

A group of segments giving references and where necessary, their dates relating to the 

whole message, e.g. contract number. 

Segment RFF, Reference 

A segment for giving references to the whole Delivery schedule message, e.g. 

contract, original message number, previous message number. 


Date or time, or date and time of the reference. 

Segment group 2: NAD-SG3-SG4 

A group of segments identifying parties by their names, addresses, references and contacts 

relevant to the whole Delivery schedule message. 

Eurofer has decided not to use the segment group 3 for giving references related to the party 

specified in the NAD segment. 

Page 32


Segment NAD, Name and address 

A segment for identifying names and addresses and their functions relevant for the whole 

Delivery schedule. The principal parties for the Delivery schedule message shall be 

identified. The identification of the recipient of the goods must be given in the NAD 

segment in the detail section. It is recommended that where possible only the coded form 

of the party ID should be specified. 

Segment group 4: CTA-COM 

A group of segments to identify person, function, or department and appropriate numbers to 

whom communication should be directed. 

Segment CTA, Contact information 

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

directed. 

Segment COM, Communication contact 

A segment identifying communication types and numbers for the person, function or 

department identified in the CTA segment. 

Page 33


4.4.3 Message description - Detail section 

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

Eurofer has decided to use only the delivery point driven method to specify the delivery schedule, 

therefore the segment group 22 will not be used. 

Segment group 6 : GIS-SG7-SG12 

A group of segments providing details on delivery points and products and related 

information. 

Segment GIS, General indicator 

A segment to indicate which method is used by the relevant processing indicator code. 

Segment group 7 : NAD-LOC-FTX-SG8-SG9-SG10-SG11 

A group of segments needed to identify a delivery point and its attached information 

when the delivery point method is used. 

Eurofer has decided not to use the segments LOC, FTX and the segment groups 8, 9 and 

11. 

Segment NAD, Name and address 

A segment for identifying the consignee. 

Segment group 10 : CTA-COM 

A group of segments to identify a person, function or department at the consignee and 

appropriate numbers to whom communication should be directed. 

Segment CTA, Contact information 

A segment to identify the person, function or department to whom communication should 

be directed. 

Segment COM, Communication contact 

Communication types and numbers for the person, function or department identified in 

CTA segment. 

Segment group 12 : LIN-PIA-IMD-MEA-ALI-GIN-GIR-LOC-DTM-FTX-SG13-SG14- 

SG15-SG17-SG20-SG22 

A group of segments providing details of the individual line items. 

Eurofer has decided not to use the segments GIN, GIR and the segment groups 14 and 22. 

Segment LIN, Line item 

A segment identifying the details of the product or service to be delivered, e.g. product 

identification. All other segments in the detail section following the LIN segment refer to 

the line item. 

Segment PIA, Additional product id 

A segment providing additional product identification. 

Page 34


Segment IMD, Item description 

A segment for describing the product or the service to be delivered. This segment should 

be used for products that cannot be identified by a product code or article number. 

Segment MEA, Measurements 

A segment specifying physical measurements of the item to be delivered in original and 

unpacked form. 

Segment ALI, Additional information 

A segment indicating that the line item is subject to special conditions due to origin, 

customs preference or commercial factors. 

Segment LOC, Place/location identification 

A segment identifying a specific location to which products, as specified in the LIN 

segment group, should be placed after delivery. This function should only be used with 

the delivery point driven method. 


Date/time/period associated with the line item, such as the date of the engineering 

change. 

Segment FTX, Free text 

A segment with free text in coded or clear form to give further clarification when 

required. In computer to computer exchanges such text will normally require the 

receiver to process this segment manually. 

Eurofer recommends not to use this segment. 

Segment group 13 : RFF-DTM 

A group of segments giving references related to the line item and when necessary, their 

dates. 

Segment RFF, References 

A segment for identifying references to the line item, e.g. contract and its appropriate line 

item, original message number, previous message number if different per line item. 


Date/time/period of the reference. 

Segment group 15 : QTY-DTM-SG16 

A group of segments specifying product quantities for synchronisation , received - 

despatched quantities, and associated dates not related to schedules and where relevant, 

their dates. 

Segment QTY, Quantity 

A segment to specify pertinent quantities not related to schedule(s), e.g. cumulative 

quantity, last quantity considered. 


A segment indicating the date/time/period details relating to the quantity. 

Page 35



A group of segments giving references related to the quantity and where necessary, their 

date. 


A segment for identifying reference to the quantity, e.g. despatch advice number. 



Segment group 17 : SCC-SG18 

A group of segments specifying the schedule information for the product identified in the 

LIN segment. With the delivery point driven method this segment group provides the 

schedule for the identified delivery point and product. 

Segment SCC, Scheduling conditions 

A segment specifying the level of commitment. Optionally a delivery pattern can be 

established. 

Segment group 18 : QTY-DTM-SG19 

A group of segments specifying product quantities and associated dates. 


A segment to specify scheduled quantities which may be related to schedule(s) and, or 

pattern established in the following DTM segment, e.g. delivery quantity for a specified 

date. 


A segment indicating date/time/period details relating to the given quantity. 


A group of segments for specifying references associated with the given schedule’s quantity 

and date and where necessary the reference dates. 


A segment to provide reference for the given schedule’s quantity and date. 



Segment group 20 : PAC-MEA-QTY-DTM-SG21 

A group of segments identifying the packaging, physical dimensions, and marks and 

numbers for goods referenced in the line item to be delivered. 

Segment PAC, Package 

A segment specifying the number of package units and the type of packaging for the line 

item, e.g. pallet. 

Page 36


Segment MEA, Measurements 

A segment specifying physical measurements of packages described in the PAC segment, 

e.g. pallet dimensions. 


A segment to specify pertinent quantities relating to the physical units (packages) described 

in the PAC segment. 

Segment group 21 : PCI-GIN 

A group of segments identifying markings and labels and if relevant package numbers. 

Segment PCI, Package identification 

A segment specifying markings and labels used on individual physical units (packages) 

described in the PAC segment. 

Segment GIN, Goods identity numbers 

A segment providing identity numbers to be applied to the packages to be delivered. 

Segment UNT 

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

and the control reference number of the message. 

4.5 Detailed description of the message - subset of Eurofer 

4.5.1 Detailed segment clarification 

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

of the data elements in the segments of the Delivery schedule message defined in the subset 

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

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

Delivery schedule message. The section 4.5.3. describes each segment used in the detail 

section of the Eurofer Delivery schedule message. 

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

Eurofer subset are indicated. 

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

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

maximum number of occurrences and the segment description. 

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

data elements in the Eurofer subset. 

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

followed by the EDIFACT status and the format. 

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

R for REQUIRED - Should always be used in the message 

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

X for EXCLUDED - Not used in the message. 

Page 37


4.5.2 Detailed segment description - Heading section 

GROUP : 

SEGMENT : 

UNH MESSAGE HEADER 

SEGMENT STATUS : Mandatory 1 

FUNCTION : To head, identify and specify a message 

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

included for completeness. 

Data Element Summary 

USG. IND. TAG NAME STATUS FORMAT 

R 0062 MESSAGE REFERENCE NUMBER M an..14 

Unique message number assigned by the sender 

R S009 MESSAGE IDENTIFIER M 

R 0065 Message type identifier M an..6 

DELFOR Delivery schedule 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 38


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 

241 Delivery schedule 

1 Delivery schedule forecast (*) 

2 Delivery schedule firm (*) 

(*) code must be used with code 58 in data element 3055 

X 1131 Code list qualifier C an..3 

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

58 Eurofer 

X 1000 Document/message name C an..35 

R C106 DOCUMENT/MESSAGE IDENTIFICATION C 

R 1004 Document/message number C an..35 

Contains the deliver schedule number 

X 1056 Version C an..9 

X 1060 Revision number C an..6 

R 1225 MESSAGE FUNCTION, CODED C an..3 

5 Replace 

7 Duplicate (re-transmission) 

9 Original 

O 4343 RESPONSE TYPE, CODED C an..3 

AB Message acknowledgement 

NA No acknowledgement needed 

Page 39


GROUP : 

SEGMENT : 

DTM DATE / TIME / PERIOD 

SEGMENT STATUS : Conditional segment repeat : 10 

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

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

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

alternative format. 



R C507 DATE/TIME/PERIOD M 

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

2 Delivery date/time requested (as release type code) 

10 Shipment date/time, requested (as release type code) 

36 Expiry date 

44 Availability (as release type code) 

94 Production/manufacture date (as release type code) 

137 Document/Message date/time 

157 Validity start date 

264 Release frequency 

273 Validity period 

See code list EDIFACT for other values 

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

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

102 CCYYMMDD 

203 CCYYMMDDhhmm 

802 Month (used in combination with Release frequency in 2005) 

803 Week (used in combination with Release frequency in 2005) 

804 Day (used in combination with Release frequency in 2005) 


Page 40


GROUP : 

SEGMENT : 

FTX FREE TEXT 


FUNCTION : To provide free from or coded text information. 

NOTES : Not recommended by Eurofer 



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 C 

R 4441 Free text identification M an..17 

O 1131 Code list qualifier C an..3 


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 41


GROUP : Group 01 : RFF - DTM 

Conditional group repeat : 10 

SEGMENT : 

RFF REFERENCE 


FUNCTION : To specify a reference. 

NOTES : This segment is used for referencing documents, relating to the whole message or to 

all the items specified in the detail section. 



R C506 REFERENCE M 

R 1153 Reference qualifier M an..3 

ACW Previous message number 

AGO Original message number 

CT Contract number 

CO Buyers’ order number 


R 1154 Reference number C an..35 

O 1156 Line number C an..6 

X 4000 Reference version number C an..35 

Page 42




SEGMENT : 



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

NOTES : All specified dates should be in the format 'CCYYMMDD' unless all parties involved 

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

format. 





171 Reference date/time 


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

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

102 CCYYMMDD 


Page 43


GROUP : Group 02 : NAD - SG3 - SG4 


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 through 3207. 

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

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

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

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

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



R 3035 PARTY QUALIFIER M an..3 

AG Agent/representative 

BY Buyer 

CZ Consignor 

IV Invoicee 

MF Manufacturer 

MI Planning schedule/material release issuer 

DP Delivery party 

SE Seller 


O C082 PARTY IDENTIFICATION DETAILS C 

R 3039 Party id identification M an..35 



58 EUROFER 

91 Assigned by seller or seller's agent 

92 Assigned by byer or buyer's agent 


O C058 NAME AND ADDRESS C 

R 3124 Name and address line M an..35 

O 3124 Name and address line C an..35 




O 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 44




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 45


GROUP : Group 04: CTA - COM 


SEGMENT : 

CTA CONTACT INFORMATION 


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

NOTES : 



R 3139 CONTACT FUNCTION, CODED C an..3 

AD Accounting contact 

DL Delivery contact 

IC Information contact 

PD Purchase contact 

See code list EDIFACT for other codes. 

R C056 DEPARTMENT OR EMPLOYEE, CODED C 

O 3413 Department or employee identification C an..17 

O 3412 Department or employee C an..35 

Page 46




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 47


4.5.3 Detailed segment description - Detail section 

GROUP : Group 6 : GIS - SG7 - SG12 


SEGMENT : 

GIS GENERAL INDICATOR 


FUNCTION : To transmit a processing indicator. 

NOTES : 



R C529 PROCESSING INDICATOR M 

R 7365 Processing indicator, coded M an..3 

100 Delivery place driven (*) 

(*) code must be used with code 58 in data element 3055 


X 1131 Code list qualifier C an..3 


58 Eurofer 

X 7187 Process type identification C an..17 

Page 48


GROUP : Group 07 : NAD - LOC - FTX - SG8 - SG9 - SG10 - SG11 


SEGMENT : 

NAD NAME AND ADDRESS 


FUNCTION : To specify the name/address of the consignee, either by C082 only and/or 

unstructured by C058 or structured by C080 through 3207. 

NOTES : 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 

CN Consignee 

ST Ship to 

O C082 PARTY IDENTIFICATION DETAILS C 

R 3039 Party id identification M an..35 



58 EUROFER 




O C058 NAME AND ADDRESS C 

R 3124 Name and address line M an..35 





O C080 PARTY NAME C 

R 3036 Party name M an..35 





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

Page 49




O C059 STREET C 

R 3042 Street and number/P.O. Box M 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 50




SEGMENT : 

CTA CONTACT INFORMATION 


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

NOTES : 



R 3139 CONTACT FUNCTION, CODED C an..3 

IC Information contact 

MC Material control contact 

See code list EDIFACT for other codes. 

R C056 DEPARTMENT OR EMPLOYEE, CODED C 

O 3413 Department or employee identification C an..17 

O 3412 Department or employee C an..35 

Page 51




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 52


GROUP : Group 12 : LIN - PIA - IMD - MEA - ALI - GIN - GIR - LOC - DTM - FTX - 

SG13 - SG14 - SG15 - SG17 - SG20 - SG22 


SEGMENT : 

LIN LINE ITEM 


FUNCTION : To identify a delivery schedule 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 

SA Supplier's article number 




X C829 SUB-LINE INFORMATION C 

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

X 1082 Line item number C n..6 

X 1222 CONFIGURATION LEVEL C n..2 

X 7083 CONFIGURATION, CODED C an..3 

Page 53



SG13 - SG14 - SG15 - SG17 - SG20 - SG22 


SEGMENT : 

PIA ADDITIONAL PRODUCT ID 


FUNCTION : To specify additional or substitute 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 



BL Control number 

DR Drawing revision number 

EC Engineering change number 

IN Buyer’s item number 

MF Manufacturer’s article number 

MP Product/service identification number 

SA Supplier’s article number 




91 Assigned by seller 

92 Assigned by buyer 

O C212 ITEM NUMBER IDENTIFICATION C 















Page 54









Page 55



SG13 - SG14 - SG15 - SG17 - SG20 - SG22 


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 

B Code and text 

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 


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 

O 3453 Language, coded C an..3 

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

See Edifact code list for values 

Page 56



SG13 - SG14 - SG15 - SG17 - SG20 - SG22 


SEGMENT : 

MEA MEASUREMENTS 


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

counts. 

NOTES : 



R 6311 MEASUREMENT PURPOSE QUALIFIER M an..3 

AAE Measurement 

PD Physical dimensions (product ordered) 

SE Property specification 

WT Weight 

R C502 MEASUREMENTS DETAILS C 

R 6313 Property measured, coded C an..3 

AAL Net weight 

AR Area 

DI Diameter 

DP Depth 

ID Inside diameter 

G Gross weight 

HT Height 

LN Length dimension 

OD Outside diameter 

TH Thickness 

U Weight per unit 

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 6154 Measurement attribute C an..70 

R C174 VALUE / RANGE C 

R 6411 Measure unit qualifier M an..3 

KGM Kilogram 

KL Kilogram/M 

MMT Millimetre 

MTK Square metre 

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 

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

See Edifact code list for values 

Page 57



SG13 - SG14 - SG15 - SG17 - SG20 - SG22 


SEGMENT : 

² 

ALI ADDITIONAL INFORMATION 


FUNCTION : To indicate that special conditions due to the origin preference are applicable. 

NOTES : 



R 3239 COUNTRY OF ORIGIN, CODED C an..3 

O 9213 TYPE OF DUTY REGIME, CODED C an..3 

O 4183 SPECIAL CONDITIONS, CODED C an..3 

X 4183 SPECIAL CONDITIONS, CODED C an..3 




Page 58



SG13 - SG14 - SG15 - SG17 - SG20 - SG22 


SEGMENT : 

LOC PLACE/LOCATION IDENTIFICATION 


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

NOTES : 



R 3227 PLACE/LOCATION QUALIFIER M an..3 

9 Place/port of loading 

11 Place/port of discharge 

159 Additional internal address 


R 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



SG13 - SG14 - SG15 - SG17 - SG20 - SG22 


SEGMENT : 



FUNCTION : To specify date, and/or time, period related to the line item. 



format. 





51 Cumulative quantity start date 

60 Engineering change level date 

128 Delivery date/time last 

257 Calculation date 

380 Drawing revision date 




102 CCYYMMDD 


Page 60



SG13 - SG14 - SG15 - SG17 - SG20 - SG22 


SEGMENT : 

FTX FREE TEXT 


FUNCTION : To provide free from or coded text information. 

NOTES : Not recommended by Eurofer 



R 4451 TEXT SUBJECT QUALIFIER M an..3 

AAI General information 

LIN Line item 


X 4453 TEXT FUNCTION, CODED C an..3 

O C107 TEXT REFERENCE C 

R 4441 Free text identification M an..17 



O C108 TEXT LITERAL C 

R 4440 Free text C an..70 





O 3453 LANGUAGE, CODED C an..3 

Page 61




SEGMENT : 

RFF REFERENCE 



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

the detail section. 





AAN Delivery schedule number 

AAL Drawing number 

AER Project number 

AIF Previous delivery instruction number 

ON Order number 





Page 62




SEGMENT : 






format. 









102 CCYYMMDD 


Page 63


GROUP : Group 15 : QTY - DTM - SG16 


SEGMENT : 

QTY QUANTITY 


FUNCTION : To specify a pertinent quantity for synchronisation and received - despatched not 

related to schedule(s). 

NOTES : 



R C186 QUANTITY DETAILS M 

R 6063 Quantity qualifier M an..3 

12 Despatch quantity 

48 Received quantity 

54 Minimum order quantity (for Period minimum quantity) 

55 Maximum order quantity (for Period maximum quantity) 

70 Cumulative quantity received 

73 Outstanding quantity 

74 Latest cumulative quantity scheduled 

77 Number of working days 

78 Cumulative quantity scheduled 

79 Previous cumulative quantity 

145 Actual stock (quantity instock) 

186 Cumulative quantity scheduled up to accumulation date 


R 6060 Quantity M n..15 

R 6411 Measure unit qualifier C an..3 

KGM Kilogram 


MTR Metres 

NMB Number 

PCE Pieces 

TNE Tonnes 


Page 64




SEGMENT : 



FUNCTION : To specify date, and/or time, period relating to the quantity. 



format. 





50 Goods receipt date/time 

160 Authorisation date 

194 Start date time 

206 End date/time 




102 CCYYMMDD 


Page 65




SEGMENT : 

RFF REFERENCE 



NOTES : This segment is used for referencing documents, relating to the quantity. 





AAK Despatch advice number 

SI Shipper’s ID number for shipment 





Page 66




SEGMENT : 






format. 









102 CCYYMMDD 


Page 67


GROUP : Group 17 : SCC - SG18 


SEGMENT : 

SCC SCHEDULING CONDITIONS 


FUNCTION : To specify the level of commitment 

NOTES : 



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

1 Firm 

2 Commitment for manufacturing and material 

3 Commitment for material 

4 Planning/forecast 

X 4493 DELIVERY REQUIREMENTS, CODED C an..3 

O C329 PATTERN DESCRIPTION C 

O 2013 Frequency, coded C an..3 

M Monthly 

W Weekly 

Y Daily 


O 2015 Despatch pattern, coded C an..3 

1 1 st week of the month 

10 Monday through Friday 

16 Thursday 

24 First decade of the month 

See code list EDIFACT for the values 

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

Page 68




SEGMENT : 

QTY QUANTITY 


FUNCTION : To specify scheduled quantities related to schedule(s). 

NOTES : 





1 Discrete quantity 

74 Latest cumulative quantity scheduled 

77 Number of working days 

81 Extra unplanned delivery 

84 Urgent delivery quantity 

113 Quantity to be delivered 




KGM Kilogram 


MTR Metres 

NMB Number 

PCE Pieces 

TNE Tonnes 


Page 69




SEGMENT : 



FUNCTION : To specify date, and/or time, period relating to the quantity. 



format. 





2 Delivery date/time, requested 

63 Delivery date/time latest 

64 Delivery date/time earliest 

160 Authorisation date 

273 Validity period 




102 CCYYMMDD 

610 CCYYMM 

616 CCYYWW 

716 CCYYWW-CCYYWW 

711 CCYYMMDD-CCYYMMDD 


Page 70




SEGMENT : 

RFF REFERENCE 


FUNCTION : To specify a reference associated with the given quantity. 

NOTES : 





AAP Part consignment number 





Page 71




SEGMENT : 






format. 









102 CCYYMMDD 


Page 72


GROUP : Group 20 : PAC - MEA - QTY - SG21 


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 

BE Bundle 

BX Box 

CL Coil 

CS Case 

NE Unpacked 

PA Packet 

PAL Pallet 

PK Package 

RO Roll 

SM Sheet 




58 EUROFER 


92 Assigned by buyer or buyer's agent 

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 73




SEGMENT : 

MEA MEASUREMENTS 


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

counts of the packages described in the segment PAC. 

NOTES : 



R 6311 MEASUREMENT PURPOSE QUALIFIER M an..3 

AAY Package measurement 

R C502 MEASUREMENTS DETAILS C 

R 6313 Property measured, coded C an..3 

AAL Net weight 

G Gross weight 

HT Height dimension 

LN Length dimension 

OD Outside diameter 

T Tare weight 

U Weight per unit 

WD Width dimension 


R 6321 Measurement significance, coded C an..3 

3 Approximately 

4 Equal to 


X 6155 Measurement attribute identification C an..17 

X 6154 Measurement attribute C an..70 

R C174 VALUE / RANGE C 

R 6411 Measure unit qualifier M an..3 

KGM Kilogram 

MMT Millimetre 

MTR Metre 

TNE Tonne 

See code lisr EDIFACT for other codes 

O 6314 Measurement value C an..18 

O 6162 Range minimum C n..18 

O 6152 Range maximum C n..18 

O 6432 Significant digits C n..2 

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

Page 74




SEGMENT : 

QTY QUANTITY 


FUNCTION : To specify a pertinent quantity. 

NOTES : 





52 Quantity per pack 




NAR Number of articles 

NMP Number of packs 

NRL Number of rolls 

SH Sheet 

PCE Piece 


Page 75


GROUP : Group 21 : PCI - GIN 


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 

16 Buyer's instruction 


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 

O C827 TYPE OF MARKINGS C 

O 7511 Type of marking, coded C an..3 



Page 76


GROUP : Group 21 : PCI - GIN 


SEGMENT : 

GIN GOODS IDENTITY NUMBER 


FUNCTION : To give specific identification numbers, either as single numbers or ranges, for the 

packages or physical units. 

NOTES : 



R 7405 IDENTITY NUMBER QUALIFIER M an..3 

ML Marking label number 


R C208 IDENTITY NUMBER RANGE M 

R 7402 Identity number M an..35 

O 7402 Identity number C an..35 

O C208 IDENTITY NUMBER RANGE C 

O 7402 Identity number M an..35 











Page 77


GROUP : 

SEGMENT : 

UNT MESSAGE TRAILER 

SEGMENT STATUS : Mandatory 1 

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

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

included for completeness. 



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

R 0062 MESSAGE REFERENCE NUMBER M an..14 

Unique message number assigned by the sender 

Page 78


5. EXAMPLES 

******* ABRUFE SACHTEILNUMMER ******* 

SACHTEILNUMMER KUNDE : 356162 

BESCHREIBUNG : SHEET 

LIEFERANTEN NUMMER : 7261 

LIEFERABRUF NUMMER : 10086 

LIEFERABRUF DATUM : 19980828 

Change (2) or Replace (1) : 1 

EDI-CENTRE NUMMER LIEFERORT : 600011 

LIEFERORT : SCA 

ABLADESTELLE : 

AUFTRAGNUMMER KUNDE : 01385 

LIEFERADDRESSE : SCANIA EUROPE 

LIEFERADDRESSE : 

LIEFERABRUF SACHTEILNUMMER 

MENGE ***** ***** ** STA ANFANGPERIODE ENDPERIODE SP 

75000 0 0 4 19981130 

50000 0 0 4 19981207 

25000 0 0 4 19981214 

25000 0 0 4 19981221 

50000 0 0 4 19981228 

25000 0 0 4 19990104 

50000 0 0 4 19990111 

75000 0 0 4 19990118 

75000 0 0 4 19990125 

75000 0 0 4 19990208 

25000 0 0 4 19990215 

100000 0 0 4 19990222 

175000 0 0 4 19990308 19990404 

100000 0 0 4 19990405 19990502 

Page 79


5.1. Example of a delivery schedule (forecast only) of Scania 

On the next pages an example is presented of the translation of a delivery schedule message, 

covering forecast information from Scania to a steel company. 

EDI message Information in the document and remarks 

HEADER - SERVICE SEGMENT 

UNH+ME000001+DELFOR:D:97A:UN' First message in an interchange of a delivery schedule message. 

HEADER SECTION 

BGM+241+10086+9' Delivery schedule message with reference number 10086. 

(LIEFERABRUF NUMMER) 

DTM+137:19980828:102' Date of the delivery schedule message. (LIEFERABRUF DATUM) 

NAD+BY+++SCANIA EUROPE' BY is used for the buyer. (LIEFERADRESSE) 

NAD+SE+7261::92' SE is used for the seller, code 7261 is given by SCANIA to the Steel 

company. (LIEFERANTEN NUMMER) 

DETAIL SECTION (Delivery location driven) 

GIS+100::58' The delivery instructions are given per delivery place. 

NAD+CN+++SCANIA EUROPE' CN is used for the consignee. (LIEFERADRESSE) 

LIN+1++356162:IN' Article number of the buyer. (SACHTEILNUMMER KUNDE) 

IMD+F+8+:::SHEET' Article description. (BESCHREIBUNG) 

LOC+11+SCA' Place of discharge. (LIEFERORT) 

RFF+ON:01385' Order number buyer. (AUFTRAGNUMMER KUNDE) 

SCC+4++W’ Forecast information on a weekly basis. (STA) 

QTY+113:75000:KGM’ Quantity to be delivered. (MENGE) 

DTM+2:19981130:102' Delivery date requested. (ANFANGPERIODE) 























Page 80



SCC+4’ Forecast information on a period basis. (STA) 


DTM+2:1999030819990404:718' Delivery date requested. (ANFANGPERIODE – ENDPERIODE) 


DTM+2:1999040519990502:718' Delivery date requested. (ANFANGPERIODE – ENDPERIODE) 

SUMMARY SECTION 

UNT+42+ME000001' First message in an interchange of a delivery schedule message. 

Page 81


******* ABRUFE SACHTEILNUMMER ******* 

SACHTEILNUMMER KUNDE : 356162 

BESCHREIBUNG : SHEET 

LIEFERANTEN NUMMER : 7261 

LIEFERABRUF NUMMER : 13791 

LIEFERABRUF DATUM : 19980917 

Change (2) or Replace (1) : 1 

EDI-CENTRE NUMMER LIEFERORT : 835176 

LIEFERORT : BLO 

ABLADESTELLE : 653 /635 

AUFTRAGNUMMER KUNDE : 0138505 

LIEFERADDRESSE : SCANIA-CAB 

LIEFERADDRESSE : OSKARSHAMN SWEDEN 

INFORMATION LETZTER LIEFERUNGEN 

DOKUMENTE NR. DATUM LIEFERMENGE ******** ***** ***** ***** 

5570502 19980909 18780 0 

5364301 19980905 28865 0 

5337701 19980905 9675 0 

LIEFERABRUF SACHTEILNUMMER 

MENGE ***** ***** ** STA ANFANGPERIODE ENDPERIODE SP 

50000 0 0 1 19981005 

50000 0 0 1 19981012 

25000 0 0 1 19981019 

50000 0 0 1 19981023 

75000 0 0 1 19981030 

75000 0 0 1 19981102 

75000 0 0 1 19981113 

25000 0 0 1 19981116 

50000 0 0 1 19981120 

75000 0 0 1 19981123 

75000 0 0 1 19981130 

75000 0 0 1 19981210 

75000 0 0 1 19981218 

Page 82


5.2. Example of a delivery schedule (firm delivery only) of Scania 

On the next pages an example is presented of the translation of an delivery schedule 

message, covering only firm delivery information from Scania to a steel company. 


HEADER - SERVICE SEGMENT 

UNH+ME000002+DELFOR:D:97A:UN' Second message in an interchange of a delivery schedule message. 

HEADER SECTION 

BGM+241+13791+9' Delivery schedule message with reference number 13791. 

(LIEFERABRUF NUMMER) 

DTM+137:19980917:102' Date of the delivery schedule message. (LIEFERABRUF DATUM) 

NAD+BY+++SCANIA EUROPE' BY is used for the buyer. (LIEFERADRESSE) 

NAD+SE+7261::92' SE is used for the seller, code 7261 is given by SCANIA to the Steel 

company. (LIEFERANTEN NUMMER) 

DETAIL SECTION (Delivery location driven) 

GIS+100::58’ The delivery instructions are given per delivery place. 

NAD+CN+++SCANIA CAB’ CN is used for the consignee. (LIEFERADRESSE) 

LIN+1++356162:IN’ Article number of the buyer. (SACHTEILNUMMER KUNDE) 

IMD+F+8+:::SHEET’ Article description. (BESCHREIBUNG) 

LOC+11+BLO’ Place of discharge. (LIEFERORT) 

LOC+159+653 /635’ Place of destination. (ABLADESTELLE) 

RFF+ON:0138505’ Order number buyer. (AUFTRAGNUMMER KUNDE) 

SYNCHRONISATION DATA – last 3 deliveries 

QTY+12:18780:KGM’ Quantity delivered. (LIEFERMENGE) 

RFF+AAK:5570502’ Despatch advice number (DOCUMENT NR.) 

DTM+171:19980909:102’ Date on the despatch advice. (DATUM) 







SCHEDULE DATA 

SCC+1++D’ Firm delivery information on a daily basis. (STA) 


DTM+2:19981005:102’ Delivery date requested. (ANFANGPERIODE) 















Page 83









SUMMARY SECTION 

UNT+45+ME000002' First message in an interchange of a delivery schedule message. 

Page 84


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 85

DELFOR Delivery Schedule Message - Eurofer

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

Delete template?

Save as template?