25.08.2013 Views

DELFOR Delivery Schedule Message - Eurofer

DELFOR Delivery Schedule Message - Eurofer

DELFOR Delivery Schedule Message - Eurofer

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

4. MESSAGE DEFINITION<br />

4.1 <strong>Message</strong> Structure<br />

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

Section and a Detail Section.<br />

4.1.1. <strong>Message</strong> structure - Heading section<br />

The heading section is used to give the general information relating to the whole message.<br />

Examples of this kind of information are the references to the initial contract, or information<br />

about the customer and the supplier, references and contacts relevant for the whole message.<br />

4.1.2. <strong>Message</strong> structure - Detail section<br />

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

The trigger segment GIS provides the information if the delivery schedule is location or<br />

product driven. Based on the decision taken by <strong>Eurofer</strong>, the GIS segment will indicate that<br />

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

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

references, documents and contacts relevant for the consignee.<br />

The segment group 12 (trigger segment LIN) provides details on each individual item<br />

regarding the product identification, references, the specific location of discharge and<br />

destination, package and labelling information, scheduling information and synchronisation<br />

data to interpret the scheduling information.<br />

Page 18

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

Saved successfully!

Ooh no, something went wrong!