delfor delivery forecast delivery schedule …...last saved : 12 july 2016...

DELFOR Delivery Forecast Delivery Schedule

Message

Document Name : EDI-Guideline_DELFOR_V2.2.docx

Date : 12 July 2016 Version : 2.3

Author : Rainer Jungton

Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx of 35

Table of Contents.

1 INTRODUCTION ...................................................................................................................................................... 3

2 SEGMENT/SEGMENT-GROUP OVERVIEW ...................................................................................................... 4

2.1 GENERATED BY “LN PLANTS” – DELFOR D.97A................................................................................................. 4 2.2 GENERATED BY “JDE PLANTS” – DELFOR D.97A ............................................................................................... 5 2.3 GENERATED BY “XPERT PLANTS” – DELFOR D.96A ........................................................................................... 6

2.3.1 Message structure ......................................................................................................................................... 7

3 SEGMENT DETAILS ................................................................................................................................................ 8

3.1 SEGMENT: UNH MESSAGE HEADER ...................................................................................................................... 8 3.2 SEGMENT: BGM BEGINNING OF MESSAGE ............................................................................................................ 9 3.3 SEGMENT: DTM DATE/TIME/PERIOD .................................................................................................................. 10 3.4 GROUP: NAD SEGMENT GROUP 2: NAME AND ADDRESS .................................................................................... 11

3.4.1 Segment: NAD Name and Address .............................................................................................................. 12 3.5 GROUP: GIS SEGMENT GROUP 6: GENERAL INDICATOR ...................................................................................... 14

3.5.1 Segment: GIS General Indicator ................................................................................................................. 14 3.6 GROUP: NAD SEGMENT GROUP 7: NAME AND ADDRESS .................................................................................... 15

3.6.1 Segment: NAD Name and Address .............................................................................................................. 16 3.7 GROUP: LIN SEGMENT GROUP 12: LINE ITEM ..................................................................................................... 17

3.7.1 Segment: LIN Line Item .............................................................................................................................. 18 3.7.2 Segment: IMD Item Description ................................................................................................................. 19 3.7.3 Segment: LOC Place/Location Identification ............................................................................................. 20

3.8 GROUP: RFF SEGMENT GROUP 13: REFERENCE .................................................................................................. 21 3.8.1 Segment: RFF Reference ............................................................................................................................ 21 3.8.2 Segment: DTM Date/Time/Period............................................................................................................... 22

3.9 GROUP: QTY SEGMENT GROUP 15: QUANTITY ................................................................................................... 23 3.9.1 Segment: QTY Quantity .............................................................................................................................. 24 3.9.2 Segment: DTM Date/Time/Period............................................................................................................... 25

3.10 GROUP: SCC SEGMENT GROUP 17: SCHEDULING CONDITIONS ........................................................................... 26 3.10.1 Segment: SCC Scheduling Conditions ........................................................................................................ 27

3.11 GROUP: QTY SEGMENT GROUP 18: QUANTITY ................................................................................................... 28 3.11.1 Segment: QTY Quantity .............................................................................................................................. 28 3.11.2 Segment: DTM Date/Time/Period............................................................................................................... 29

3.12 SEGMENT: UNS SECTION CONTROL .................................................................................................................... 30 3.13 SEGMENT: UNT MESSAGE TRAILER .................................................................................................................... 31

4 EXAMPLE MESSAGE (LN PLANT) .................................................................................................................... 32

5 EXAMPLE MESSAGE (JDE PLANT) .................................................................................................................. 33

6 EXAMPLE MESSAGE (XPERT PLANT) ............................................................................................................ 34

7 CHANGE LOG ......................................................................................................................................................... 35


1 Introduction This version of the DELFOR is not upward compatible with versions prior to D96B.

DELFOR is a message which is sent from a party who is planning the use or consumption of products to a party who has

to plan for the supply of the products.

The message gives the requirements regarding details for short term delivery and/or medium to long scheduling for

products.

The scheduling can be used to authorize manufacturing and or the provision of materials.

This is based on the terms and conditions defined in a purchase order or contract.

Because of Bosal is using different IT systems, there are different DELFOR standards used:

There are:

LN plants

JDE plants

Xpert plants

Please check below the variances.


2 Segment/Segment-Group Overview

2.1 Generated by “LN plants” – DELFOR D.97A

Pos. No.

Seg. ID

Name Req. Des.

Max. Use

Group Repeat

Note and comments

0010 UNH Message Header M 1

0020 BGM Beginning of Message M 1

0030 DTM Date/Time/Period M 10

0080 Segment Group 2: NAD C 99

0090 NAD Name and Address M 1

0190 Segment Group 6: GIS-SG7-SG12 C 9999

0200 GIS General Indicator M 1

0210 Segment Group 7: NAD 1


0370 Segment Group 12: LIN-IMD-LOC-SG13-SG15-SG17

C 9999

0380 LIN Line Item M 1

0400 IMD Item Description C 10

0450 LOC Place/Location Identification C 999

0480 Segment Group 13: RFF-DTM C 10

0490 RFF Reference M 1

0500 DTM Date/Time/Period C 1

0540 Segment Group 15: QTY-DTM C 10

0550 QTY Quantity M 1


0600 Segment Group 17: SCC-SG18 C 999

0610 SCC Scheduling Conditions M 1




1030 UNT Final segment of message M 1

M = Mandatory

C = Conditional

N = Not used


2.2 Generated by “JDE plants” – DELFOR D.97A

Pos. No.

Seg. ID

Name Req. Des.

Max. Use

Group Repeat

Note and comments



0030 DTM Date/Time/Period M 10

0080 Segment Group 2: NAD C 99


0190 Segment Group 6: GIS-SG7-SG12 C 9999

0200 GIS General Indicator M 1

0210 Segment Group 7: NAD M 1


0370 Segment Group 12: LIN-IMD-LOC-SG13-SG15-SG17

C 9999


0400 IMD Item Description C 10

0450 LOC Place/Location Identification C 999

0480 Segment Group 13: RFF-DTM C 10

0490 RFF Reference M 1





0600 Segment Group 17: SCC-SG18 C 999

0610 SCC Scheduling Conditions M 1




1030 UNT Final segment of message M 1

M = Mandatory

C = Conditional

N = Not used


2.3 Generated by “Xpert plants” – DELFOR D.96A

Pos. No.

Seg. ID

Name Req. Des.

Max. Use

Group Repeat

Note and comments

0000 UNB Interchange Header M 1



0030 DTM Date/Time/Period M

0070 Segment Group 2: NAD-LOC-SG3 C


0100 Segment Group 3: CTA-COM C

0110 CTA Contact information C

0130 UNS Section control M

0140 Segment Group 4: NAD-LOC-FTX-SG5-SG6-SG7-SG8


0270 Segment group 8: LIN-PIA-IMD-MEA-ALI-GIN-GIR-LOC-DTM-FTX-SG9-SG10-SG11-SG12-SG14

C

0280 LIN Line Item M

0290 PIA Additional product id

0300 IMD Item Description C

0350 LOC Place/Location Identification C

0410 Segment Group 10: RFF-DTM

C

0420 RFF Reference M

0430 DTM Date/Time/Period C

0470 Segment group 12: QTY-SCC-DTM-SG13

C

0480 QTY Quantity M

0490 SCC Scheduling conditions M

0500 DTM Date/Time/Period M

1220 UNS Section Control C

1250 UNT Message Trailer M 1

M = Mandatory

C = Conditional

N = Not used

Remark:

The content for D96A is used in the same way as for D97A.


2.3.1 Message structure

http://www.unece.org/trade/untdid/d96a/trmd/delfor_s.htm

─UNH Message header ×1 (M)

├─BGM Beginning of message ×1 (M)

├─DTM Date/time/period ×10 (M) ├─Segment Group 1 ×10 (C)

│─├─RFF Reference ×1 (M)

│─└─DTM Date/time/period ×1 (C) ├─Segment Group 2 ×20 (C)

│─├─NAD Name and address ×1 (M)

│─├─LOC Place/location identification ×10 (C) │─└─Segment Group 3 ×5 (C)

│───├─CTA Contact information ×1 (M)

│───└─COM Communication contact ×5 (C) ├─UNS Section control ×1 (M)

├─Segment Group 4 ×500 (C)

│─├─NAD Name and address ×1 (M) │─├─LOC Place/location identification ×10 (C)

│─├─FTX Free text ×5 (C)

│─├─Segment Group 5 ×10 (C) │─│─├─DOC Document/message details ×1 (M)

│─│─└─DTM Date/time/period ×10 (C) │─├─Segment Group 6 ×5 (C)

│─│─├─CTA Contact information ×1 (M)

│─│─└─COM Communication contact ×5 (C) │─├─Segment Group 7 ×10 (C)

│─│─├─TDT Details of transport ×1 (M)

│─│─└─DTM Date/time/period ×5 (C) │─└─Segment Group 8 ×9999 (C)

│───├─LIN Line item ×1 (M)

│───├─PIA Additional product id ×10 (C) │───├─IMD Item description ×10 (C)

│───├─MEA Measurements ×5 (C)

│───├─ALI Additional information ×5 (C) │───├─GIN Goods identity number ×100 (C)

│───├─GIR Related identification numbers ×100 (C)

│───├─LOC Place/location identification ×100 (C) │───├─DTM Date/time/period ×5 (C)

│───├─FTX Free text ×5 (C)

│───├─Segment Group 9 ×5 (C) │───│─├─CTA Contact information ×1 (M)

│───│─└─COM Communication contact ×5 (C)

│───├─Segment Group 10 ×10 (C) │───│─├─RFF Reference ×1 (M)

│───│─└─DTM Date/time/period ×1 (C)

│───├─Segment Group 11 ×10 (C) │───│─├─TDT Details of transport ×1 (M)

│───│─└─DTM Date/time/period ×5 (C)

│───├─Segment Group 12 ×200 (C) │───│─├─QTY Quantity ×1 (M)

│───│─├─SCC Scheduling conditions ×1 (C)

│───│─├─DTM Date/time/period ×2 (C) │───│─└─Segment Group 13 ×10 (C)

│───│───├─RFF Reference ×1 (M)

│───│───└─DTM Date/time/period ×1 (C) │───└─Segment Group 14 ×50 (C)

│─────├─PAC Package ×1 (M)

│─────├─MEA Measurements ×10 (C) │─────├─QTY Quantity ×5 (C)

│─────├─DTM Date/time/period ×5 (C)

│─────├─Segment Group 15 ×10 (C) │─────│─├─PCI Package identification ×1 (M)

│─────│─└─GIN Goods identity number ×10 (C)

│─────└─Segment Group 16 ×10 (C) │───────├─QVR Quantity variances ×1 (M)

│───────├─DTM Date/time/period ×5 (C)

│───────└─Segment Group 17 ×10 (C) │─────────├─RFF Reference ×1 (M)

│─────────└─DTM Date/time/period ×1 (C)

The segment details (below/next page) is referring to D97A !!!

http://www.unece.org/trade/untdid/d96a/trmd/delfor_s.htm


3 Segment details

3.1 Segment: UNH Message Header Position 0010

Group

Level 0

Usage Mandatory

Max Use 1

Purpose 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 S009: Data element

0065 DELFOR 0052 D 0054 97A 0051 UN

Dependency

Notes:

Semantic

Notes:

Comments

Data Element Summary

Data

Element

Component

Element

Name Attributes

M 0062 MESSAGE REFERENCE NUMBER

Unique message reference assigned by the sender.

M an..14

M S009 MESSAGE IDENTIFIER

Identification of the type, version etc. of the message

being interchanged.

M

M 0065 Message type identifier

Code identifying a type of message and assigned by its

controlling agency.

DELFOR Delivery schedule message

A code to identify the delivery

schedule message.

M an..6

M 0052 Message type version number

Version number of a message type.

D Draft version/UN/EDIFACT Directory

Message approved and issued as a draft

message (Valid for directories published after

March 1993 and prior to March 1997).

Message approved as a standard message

(Valid for directories published after March

1997).

M an..3

M 0054 Message type release number

Release number within the current message type version

number (0052).

97A Release 1997 – A

Message approved and issued in the first 1997

release of the UNTDID (United Nations Trade

Data Interchange Directory).

96A Release 1996 – A

M an..3

M 0051 Controlling agency

Code identifying the agency controlling the

specification, maintenance and

publication of the message type.

UN UN/ECE/TRADE/WP.4

United Nations Economic UN Economic

Commission for Europe (UN/ECE),

Committee on the development of trade

(TRADE), Working Party on facilitation of

international trade procedures (WP.4).

M an..2


3.2 Segment: BGM Beginning of Message Position 0020

Group

Level 0

Usage Mandatory

Max Use 1

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

name and its number and its function (original, replacement, change).

Comments


Data element Component

Element

Name Attributes

C002 DOCUMENT/MESSAGE NAME

Identification of a type of document/message by code or

name. Code preferred

C

1001 Document/message name, coded

Document/message identifier expressed in code.

241 = Delivery schedule

Usage of DELFOR-message.

C an..3

C106 DOCUMENT/MESSAGE IDENTIFICATION

Identification of a document/message by its number and

eventually its version

or revision.

C

1004 Document/message number

Reference number assigned to the document/message by

the issuer.

C an..35

MESSAGE FUNCTION, CODED

Code indicating the function of the message

5 = Replace

Message replacing a previous message.

C an..3


3.3 Segment: DTM Date/Time/Period

Position 0030

Group

Level 1

Usage Mandatory

Max Use 10

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

Dependency

Notes:

Semantic

Notes:

Comments



Element

Name Attributes

M C507 DATE/TIME/PERIOD

Date and/or time, or period relevant to the specified

date/time/period type.

M

M 2005 Date/time/period qualifier

Code giving specific meaning to a date, time or

period.

137 Document/message date/time

(2006) Date/time when a document/message is

issued.This may include authentication

M an..3

2380 Date/time/period

The value of a date, a date and time, a time or of a

period in a specified representation.

C an..35

2379 Date/time/period format qualifier

Specification of the representation of a date, a date

and time or of a period.

203 CCYYMMDDHHMM Calendar date including

time with minutes: C=Century; Y=Year; M=Month;

D=Day; H=Hour; M=Minutes.

C an..3


3.4 Group: NAD Segment Group 2: Name and Address

Position 0080

Group

Level 1

Usage Conditional (Optional)

Max Use 99

Purpose A group of segments identifying parties by their names, addresses, locations, references

and contacts relevant to the whole delivery schedule.

Comments


Pos. Segment ID Name Req.

Desired

Max use Group

(repeat):

0090 NAD Name and

Address

M 1


3.4.1 Segment: NAD Name and Address

Position 0090 (Trigger Segment)

Group Segment Group 2 (Name and Address) Conditional (Optional)

Level 1

Usage Mandatory

Max Use 1

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

Comments



Element

Name Attributes

3035 PARTY QUALIFIER.

Code giving specific meaning to a party.

BY Buyer

(3002) Party to which merchandise is sold.

SE Seller

(3346) Party selling merchandise to a buyer.

SU Supplier

(3280) Party which manufactures or otherwise

has possession of goods, and consigns or

makes them available in trade.

M an..3

C082 PARTY IDENTIFICATION DETAILS

Identification of a transaction party by code.

C

3039 Party id. Identification

Code identifying a party involved in a transaction.

M an…35

1131 Code list qualifier

Identification of a code list.

Refer to D.97A Data Element Dictionary for acceptable

code values.

Not used

3055 Code list responsible agency, coded

Code identifying the agency responsible for a code list.


code values

92 Assigned by buyer or buyer's agent

C an..3

C080 PARTY NAME

Identification of a transaction party by name, one to five

lines. Party name may be formatted

C

3036 Party name

Name of a party involved in a transaction.

M an..35

C059 STREET

Street address and/or PO Box number in a structured

address: one to three lines.

C

3042 Street and number/p.o. box

Street and number in plain language, or Post Office Box

No.

M an..35

3164 CITY NAME

Name of a city for addressing purposes.

C an..35

3229 COUNTRY SUB-ENTITY IDENTIFICATION

Identification of the name of sub-entities (state,

province) defined by appropriate governmental

agencies.

C an..9



Element

Name Attributes

3251 POSTCODE IDENTIFICATION

Code defining postal zones or addresses.

C an..9

3207 COUNTRY, CODED

Identification of the name of a country or other

geographical entity as specified in ISO 3166.

C an..3


3.5 Group: GIS Segment Group 6: General Indicator

Position 0190

Group Segment Group 6 (General Indicator) Conditional (Optional)

Level 1


Max Use 9999

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

information using one of both scheduling methods (as described in 1.3 Principles).

Comments


Position No. Segment ID Name Req.

Desired

Max use Group (repeat):

0200 GIS General

Indicator

M 1

0210 Segment

Group 7: Name

and Address

C 1

0370 Segment

Group 12: Line

Item

C 9999

3.5.1 Segment: GIS General Indicator



Level 1


Max Use 1

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

Comments



Element

Name Attributes

C529 PROCESSING INDICATOR

Type of process indication.

M

7365 Processing indicator, coded

Identifies the value to be attributed to indicators

required by the processing

system.

M an..3

37 Complete information

Processing of information to note that

complete data details (not just changes) are

transmitted.


3.6 Group: NAD Segment Group 7: Name and Address

Position 0210


Level 2


Max Use 1

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

when the delivery point method is used.

Comments



Desired

Max use Group

(repeat):

0220 NAD Name and

Address

M 1


3.6.1 Segment: NAD Name and Address


Group Segment Group 7 (Name and Address) Conditional (Optional)

Level 2

Usage Mandatory

Max Use 1

Purpose A segment for identifying the consignee.

Comments


Group Data/ Component

Element

Name Attributes Example

010 3035 PARTY QUALIFIER

Code giving specific meaning to a party.

ST Ship to

Identification of the party to where goods will

be or have been shipped.

M an..3 ST

020 C082 PARTY IDENTIFICATION DETAILS

Identification of a transaction party by code.

C

3039 Party id. Identification

Code identifying a party involved in a transaction.

M an..35 022001

1131

Code list qualifier

Identification of a code list.


code values.

N an..3

3055

Code list responsible agency, coded

Code identifying the agency responsible for a code list.


code values.

C an..3 92

030 C058 NAME AND ADDRESS

Unstructured name and address: one to five lines.

C

3124

Name and address line

Free form name and address description.

M an..35 BOSAL:BELGIUM

040 C080 PARTY NAME

Identification of a transaction party by name, one to five

lines. Party name may

be formatted.

C

3036 Party name

Name of a party involved in a transaction.

M an..35 Czech Warehouse

050 C059 STREET

Street address and/or PO Box number in a structured

address: one to three

lines.

C

3042 Street and number/p.o. box

Street and number in plain language, or Post Office Box

No.

M an..35 Dellestraat 20

060 3164 CITY NAME

Name of a city (a town, a village) for addressing

purposes.

C an..35

070 3229 COUNTRY SUB-ENTITY IDENTIFICATION

Identification of the name of sub-entities (state, province)

defined by appropriate governmental agencies.

C an..9 48

080 3251 POSTCODE IDENTIFICATION

Code defining postal zones or addresses.

C an..9 603004

090 3207 COUNTRY, CODED

Identification of the name of a country or other

geographical entity as specified in ISO 3166.

C an..3 RU

Example:

NAD+ST+022001::92+BOSAL Addr#1:BOSAL Addr#2+Name+Street+48+603004+RU


3.7 Group: LIN Segment Group 12: Line Item Position 0370


Level 2


Max Use 9999

Purpose A group of segments providing details of the individual line items for both methods.

Comments



Desired

Max use Group

(repeat):


0400 IMD Item

Discription

C 10

0450 LOC Place/Location

Identification

C 999

0480 Segment

Group 13:

Reference

C 10

0540 Segment

Group 15:

Quantity

C 10

0600 Segment

Group 17:

Scheduling

Conditions

C 999


3.7.1 Segment: LIN Line Item


Group Segment Group 12 (Line Item) Conditional (Optional)

Level 2

Usage Mandatory

Max Use 1

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

Comments



Element

Name Attributes

1082 LINE ITEM NUMBER

Serial number designating each separate item within a

series of articles.

C an..6

C212 ITEM NUMBER IDENTIFICATION

Goods identification for a specified source.

C

7140 Item number

A number allocated to a group or item.

C an..35

7143 Item number type, coded

Identification of the type of item number.

IN Buyer's item number

C an..3


3.7.2 Segment: IMD Item Description

Position 0400


Level 3


Max Use 10

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

Dependency

Notes

Semantic

Notes

Comments


Data element Component Element Name Attributes

C273 ITEM DESCRIPTION

Description of an item.

C

X 7009 Item description identification C an..17

7008 Item description

Plain language description of articles or products.

C an..35

7008 Item description

Plain language description of articles or products.

C an..35


3.7.3 Segment: LOC Place/Location Identification

Position 0450


Level 3


Max Use 9999

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

Comments



Element

Name Attributes

3227 PLACE/LOCATION QUALIFIER

Code identifying the function of a location.

11 Place/port of discharge

(3392 + 3414) Seaport, airport, freight terminal, rail

station or other place at which the goods (cargo) are

unloaded from the means of transport having been used

for their carriage.

C an..3

C517 LOCATION IDENTIFICATION

Identification of a location by code or name.

C

3225 Place/location identification

Identification of the name of place/location, other than

3164 City name.

C an..25


3.8 Group: RFF Segment Group 13: Reference

Position 0480


Level 3


Max Use 10

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

dates.

Comments



Desired

Max use Group

(repeat):

M 0490 RFF Reference M 1


3.8.1 Segment: RFF Reference


Group Segment Group 13 (Reference) Conditional (Optional)

Level 3


Max Use 1

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

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

Comments For JDE plants the dispatch advice number is not used!



Element

Name Attributes

C506 REFERENCE

Identification of a reference.

M

1153 REFERENCE QUALIFIER

Code giving specific meaning to a reference segment or

a reference number.

AAK Dispatch advice number

Reference number assigned by issuing party to

a dispatch advice.

ON Order number (purchase)

[1022] Reference number assigned by the

buyer to an order.

M an..3

1154 Reference number

Identification number the nature and function of which

can be qualified by an entry in data element 1153

Reference qualifier.

C an..35


3.8.2 Segment: DTM Date/Time/Period

Position 0500

Group Segment Group 13 (Reference) Conditional (Optional)

Level 4


Max Use 1

Purpose Date/time/period of the reference.

Dependency

Notes:

Semantic

Notes:

Comments



Element

Name Attributes




M


Code giving specific meaning to a date, time or period.

171 Reference date/time

Date/time on which the reference was issued.

M an..3


The value of a date, a date and time, a time or of a period

in a specified representation.

C an..35


Specification of the representation of a date, a date and

time or of a period.

102 CCYYMMDD

Calendar date:

C = Century

Y = Year

M = Month

D = Day

C an..3


3.9 Group: QTY Segment Group 15: Quantity Position 0540


Level 3


Max Use 10

Purpose A group of segments specifying product quantities and associated dates not related to

schedules and where relevant, references.

Comments



Desired

Max use Group (repeat):




3.9.1 Segment: QTY Quantity


Group Segment Group 15 (Quantity) Conditional (Optional)

Level 3

Usage Mandatory

Max Use 1

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

quantity, last quantity considered.

Dependency

Notes:

Semantic

Notes:

Comments


Data element Component Element Name Attributes

M C186 QUANTITY DETAILS

Quantity information in a transaction, qualified when

relevant.

M

M 6063 Quantity qualifier

Code giving specific meaning to a quantity.

70 Cumulative quantity received

Cumulative quantity of all deliveries of this

article received by the buyer.

79 Previous cumulative quantity

Cumulative quantity prior the actual order.

83 Backorder quantity

194 Received and accepted

Quantity which has been received and

accepted at a given location

M an..3

M 6060 Quantity

Numeric value of a quantity.

M n..15

6411 Measure unit qualifier

Indication of the unit of measurement in which

weight (mass), capacity, length, area, volume or other

quantity is expressed.

C an..3



Position 0560

Group Segment Group 17 (Scheduling Conditions) Conditional (Optional)

Level 3

Usage Mandatory

Max Use 1

Purpose A segment specifying the status of the schedule.

Optionally a delivery pattern can be established, e.g. firm or proposed delivery pattern.

Comments


Position 0560


Level 4


Max Use 2

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

Dependency

Notes:

Semantic

Notes:

Comments



Element

Name Attributes




M



51 Cumulative quantity start date

First Date for accumulation of delivery

quantities.

M an..3


The value of a date, a date and time, a time or of a period

in a specified representation.

C an..35




102 CCYYMMDD

Calendar date:

C = Century

Y = Year

M= Month

D = Day

C an..3


3.10 Group: SCC Segment Group 17: Scheduling Conditions

Position 0600


Level 3


Max Use 999

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

With the product driven method this segment group can be used to summarize all schedules

provided with the subsequent delivery point information given in segment group 22.

Comments



Desired

Max use Group

(repeat):

0610 SCC Scheduling

Conditions

M 1

0620 Segment

Group 18:

Quantity

C 999


3.10.1 Segment: SCC Scheduling Conditions



Level 3

Usage Mandatory

Max Use 1

Purpose A segment specifying the status of the schedule.

Optionally a delivery pattern can be established, e.g. firm or proposed delivery pattern.

Comments



Element

Name Attributes

4017 DELIVERY PLAN STATUS INDICATOR, CODED

Code indicating the level of commitment of schedule

information.

1 Firm

Indicates that the scheduling information is a

firm commitment.

10 Immediate

Indicates that the scheduling information is for

immediate execution (backlog)

4 Planning/forecast

Self-explanatory

M an..3

C329 PATTERN DESCRIPTION

Shipment, delivery or production interval pattern and

timing.

C

2013 Frequency, coded

Code specifying interval grouping of the delivery,

production, etc. of the

schedule.

W Weekly

Code defining a forecast for weekly intervals.

Y Daily

Code defining a forecast for yearly intervals.

D Discrete

Flexible frequency according to planning

process.

C an..3

Example:

…

QTY+113:1000:PCE'

…


3.11 Group: QTY Segment Group 18: Quantity

Position 0620


Level 4


Max Use 999

Purpose A group of segments specifying product quantities and associated dates.

Comments



Desired

Max use Group

(repeat):



3.11.1 Segment: QTY Quantity



Level 4

Usage Mandatory

Max Use 1

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

Comments



Element

Name Attributes

C186 QUANTITY DETAILS

Quantity information in a transaction, qualified when

relevant.

M

6063 Quantity qualifier

Code giving specific meaning to a quantity.

113 Quantity to be delivered

The quantity to be delivered.

M an…3

6060 Quantity

Numeric value of a quantity.

M n…15

6411 Measure unit qualifier

Indication of the unit of measurement in which weight

(mass), capacity, length, area, volume or other quantity

is expressed.

PCE Piece

C an…3

Example:

…

QTY+113:1000:PCE'

…



Position 0640


Level 5


Max Use 2

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

Comments


Data

Element

Component

Element

Name Attributes




M



2 Delivery date/time, requested Date on which buyer requests goods to be

delivered.

M an..3


The value of a date, a date and time, a time or of a

period in a specified

C an..35




102 CCYYMMDD

Calendar date: C = Century ; Y = Year ;

M = Month ; D = Day.

C an..3

Example:

…

DTM+2:20160401:102'

…


3.12 Segment: UNS Section Control

Position

Group

Level 0

Usage Conditional

Max Use

Purpose A character identifying the next section in a message.

Comments


Data

Element

Component

Element

Name Attributes

M 0081 D Header/detail section separation

To qualify the segment UNS, when separating

the header from the detail section of a

message.

S Detail/summary section separation

To qualify the segment UNS, when separating

the detail from the summary section of a

message.

M an…1

Example:

UNS+D'

…

UNS+S'


3.13 Segment: UNT Message Trailer

Position 1030

Group

Level 0

Usage Mandatory

Max Use 1

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

and the control reference number of the message

Comments


Data

Element

Component

Element

Name Attributes

M 0074 NUMBER OF SEGMENTS IN A MESSAGE

Control count of number of segments in a message.

M n..6

M 0062 MESSAGE REFERENCE NUMBER

Unique message reference assigned by the sender. M n..14


4 Example message (LN Plant)

UNB+UNOC:1+O0013BOSALSFID+O0013TESTSUPPLIER+140113:1435+4’

UNH+1+DELFOR:D:97A:UN’

BGM+241+020000004+5’

DTM+137:201401131634:203’

NAD+SU+000000005::92++Test Supplier GmbH’

NAD+BY+BOSAL::92’

GIS+37’

NAD+ST+022001::92+:+Raw Material++Nizhny Novgorod+48++RU’

LIN+1++1150022821:IN’

IMD+++:::Tube B’

LOC+11+027101’

RFF+ON:020000001’

QTY+70:0:PCE’

DTM+51:20130903:102’

SCC+1++D’

QTY+113:1002:PCE’

DTM+2:20131106:102’

SCC+1++D’

QTY+113:25:PCE’

DTM+2:20131109:102’

SCC+1++D’

QTY+113:25:PCE’

DTM+2:20131121:102’

UNT+23+1’

UNZ+1+4’


5 Example message (JDE Plant)

UNB+UNOC:1+OSENDER:OD+ORECEIVER:OD+160519:1722+13'

UNH+1+DELFOR:D:97A:UN'

BGM+241+201605121208050944+5'

DTM+137:201605121408:203'

NAD+SU+50944::92'

NAD+BY+00045::92++BOSAL CZ, spol. s r.o.'

GIS+37'

NAD+ST+BCZB::92++BOSAL CZ, spol. s r.o.++Brandys nad Labem Brandys nad Labem+++CZ '

LIN+3++2550020320:IN'

IMD+++:::KLAPPEELEKTRISCH-4H0253691H'

LOC+11+BCZB'

RFF+ON:460'

SCC+1++D'

QTY+113:120:PCE'

DTM+2:20160520:102'

SCC+10++D'

QTY+113:27:PCE'

DTM+2:20160401:102'

SCC+4++D'

QTY+113:0:PCE'

DTM+2:20160613:102'

SCC+4++D'

QTY+113:0:PCE'

DTM+2:20160620:102'

UNT+24+1'

UNZ+1+13'


6 Example message (Xpert Plant)

UNB+UNOA:2+O01770000000000A04Cxxxx+ORECEIVERID+160628:0451+00000000000001'

UNH+1+DELFOR:D:96A:UN:A09041'

BGM+241+2+5'

DTM+137:201606280000:203'

DTM+158:20160422:102'

DTM+159:20161219:102'

NAD+SE+20088::92+++++++HU'

NAD+BY+::92'

CTA+PD+:Mr. Contact'

UNS+D'

NAD+CN+O0013001133ORIS::92'

LIN+1++0123456789:IN'

IMD+++:::Test item'

LOC+159+RE'

RFF+ON:0010126'

RFF+AIF:10'

DTM+171:20160422:102'

RFF+AAN:11'

DTM+171:20160628:102'

QTY+70:400:PCE'

QTY+78:400:PCE'

QTY+12:100:PCE'

RFF+AAK:00074595'

DTM+171:20160602:102'

QTY+48:100:PCE'

DTM+171:20160602:102'

QTY+113:0:PCE'

SCC+1++D'

DTM+2:20160627:102'

QTY+113:26:PCE'

SCC+1++D'

DTM+2:20160802:102'

QTY+113:55:PCE'

SCC+1++D'

DTM+2:20160809:102'

QTY+113:55:PCE'

SCC+1++D'

DTM+2:20160816:102'

QTY+113:0:PCE'

SCC+1++D'

DTM+2:20160822:102'

QTY+113:55:PCE'

SCC+1++D'

DTM+2:20160823:102'

QTY+113:0:PCE'

SCC+1++D'

DTM+2:20160829:102'

UNS+S'

UNT+48+1'

UNZ+1+00000000000001'


7 Change log

Version Reason Release date Change Page

1.0 Layout Some reformatting of text Several

1.1 Layout

1.2 Change

chapter

Additional chapter: “change log” 21

1.3 Add table Difference between DELFOR messages sent

from BOSAL plants (LN or JDE) 5

1.4 Layout

Change

chapter

Some reformatting of text/tables

Delete not used information for JDE plants several

5

1.5 Add table 31/3/2014 New BOSAL plants (Xpert) added

Layout changes 5

1.6 Layout

Change

Some reformatting of text/tables 11

1.7 Change

table

NAD+ST table – examples added 14

Page margin changed from “Standard” to

“Medium” All

1.8 Add table UNS (only for Xpert plants) 24

Change

table

Xpert plant – segment overview 6

1.9 Content 10/11/2015 Changed cover page:

“DELFOR Delivery Forecast Delivery Schedule

Message”

removed: “DELFOR D.97A DELFOR D.96A).

Added “Generated by”

Added format: “DELFOR D.97A” for JDE

plants

1

4/5/6

5

2.0 Layout 19/05/2016 Different tables standardized

Changed index Several

Add QTY

variance

QTY+83 = Backlog Quantity 22

Add SCC SCC+10 = immediate demand 25

2.1 Layout 02/06/2016 Some layout changes on the NAD segment 11

02/06/2016 QTY+194 added (last received DN – quantity) 23

2.2 Content 12/07/2016 Added Example message for Xpert

Deleted “GIS segment” for “Xpert plants” 33

6

2.3 Content 12/07/2016 Changed Example message for “Xpert plants”

Changed message structure for “Xpert plants” –

because of different message version/release

number (D96A instead of D97A).

34

6/7

delfor delivery forecast delivery schedule …...last saved : 12 july 2016...

Documents