25.08.2013 Views

DELFOR Delivery Schedule Message - Eurofer

DELFOR Delivery Schedule Message - Eurofer

DELFOR Delivery Schedule Message - Eurofer

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

UN/EDIFACT D97.A <strong>DELFOR</strong> - <strong>Delivery</strong> schedule message<br />

DELIVERY SCHEDULE MESSAGE<br />

0. INTRODUCTION<br />

This document provides the definition of the EUROFER subset of the <strong>Delivery</strong> schedule message<br />

based on the UN standard <strong>DELFOR</strong> message of the UN/EDIFACT directory D97A.<br />

This message has been created by the EDIFER "<strong>Message</strong> development" working group. The<br />

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

industry.<br />

The manual has been structured in the following format:<br />

- Background information describing the use of the <strong>Delivery</strong> schedule message.<br />

- A Data Model definition describes the data entities, attributes and their<br />

relationships.<br />

- The scope describes the field of application, principles and message usage.<br />

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

the data described in the data model relates to the message.<br />

- The message definition outlines the general structure of the message and specifies<br />

the use of each segment group and, or segment.<br />

- Based on the branching diagram of the original EDIFACT message <strong>DELFOR</strong>, the<br />

segments used are indicated. This is followed by a detailed description of the<br />

segments used by <strong>Eurofer</strong>.<br />

- Examples of some <strong>Delivery</strong> schedules are provided to clarify the understanding of<br />

the message description<br />

Page 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!