Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D00A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Delivery schedule message

Version:D
Release:00A
Contr. Agency:UN
Revision:6
Date:2000-01-27
SOURCE:Joint Rapporteurs Message Design Group JM1

CONTENTS
Delivery schedule message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Segment clarification
    2. Segment index (alphabetical sequence)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction


This message also occurs in the following versions of this standard:
D93A, D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

0. INTRODUCTION

This specification provides the definition of the Delivery schedule message (DELFOR) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional definition

WARNING! 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.

The message may also be sent in response by a party which has received a DELFOR message to indicate to the party which has issued the message, the acceptance of, rejection of, or to propose amendments to the previous message.


1.2. Field of application

The Delivery schedule message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.


1.3. Principles

1.3.1. DELFOR used for scheduling and forecasting.

The Delivery schedule message shall be used to:

  • specify firm delivery dates and the quantities scheduled (using segment SCC, data element Delivery plan status indicator, coded (4017)= "Firm".
  • specify forecasted production requirements (using SCC, data element Delivery plan status indicator, coded (4017)=either "commitment for manufacturing and material (2)" or "commitment for material (3)" or "planning/forecast (4)".
  • define the aspects that guarantee the synchronization between the supplying and receiving parties, thus allowing the supplier to plan for the resources necessary to fulfill customer requirements.

The Delivery schedule message provides the option to use one of 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 address information triggers product information. Usage of segment group 7 is consequently required for the specification of delivery points.

Method 2: product driven This is when a given product is to be delivered to a number of different delivery points. This means that product information triggers address information. Consequently, segment group 7 is not to be used. Delivery point information shall be specified in segment group 22.

An initiating Delivery schedule message is identified in the BGM with the "document name code (1001)" equal to "delivery schedule (241)" and "message function code (1225)" equal to "original (9)".

A subsequent message may be used to replace the schedule completely (quantities and dates). This is identified in the BGM with the "message function code (1225)" equal to "replace (5)". The replacement of a schedule requires the new schedule to totally override the previous one.

Alternatively the message may be used to partially alter the schedule. This is identified in the BGM with the "message function code (1225)" equal to "change (4)". Such alteration to the schedule shall adhere to the following recommendations:

1. All the date information in the QTY-DTM segment group shall be systematically used to identify the group to be changed.

2. How the information is to be changed:

2.a. To change a quantity - where the date information matches the current quantity is replaced with the new quantity.

2.b. To change a date - the current quantity has to be changed to zero and the new date information has to be given with the quantity from the former schedule.

2.c. To change a date and quantity - the current quantity has to be changed to zero and the new date information has to be given with appropriate new quantity.

2.d. To delete quantities and dates - the current quantity has to be changed to zero.

2.e. To add quantities and dates - the new date information has to be given with the appropriate new quantity.

3. Unchanged dates and quantities - unchanged dates and quantities from the former schedule need to be resent.

4. Delivered quantities - delivered quantities are automatically eliminated from the schedule.

The association to the previous Delivery schedule message is given by referencing the appropriate document/message number.

1.3.2. DELFOR used for response purposes.

The indication of a DELFOR message for response purposes is achieved through the use of 'Delivery Schedule Response' code value in data element 1001 of the BGM segment.

When used as a response to a previous DELFOR message the message may be used to indicate one of the following conditions using code values in data element 1225 of the BGM segment:

  • Total acceptance;
  • Total rejection;
  • Not processed;
  • Proposal for change.

Total acceptance of a previous DELFOR message may be indicated using code value '29, Accepted without amendment', in data element 1225 of the BGM segment. Where a previous DELFOR message is being totally accepted then only the EDIFACT mandatory segments, and those agreed by the parties exchanging the message which enable the identification of the previous message, need be re-sent.

Total rejection of a previous DELFOR message may be indicated using code value '27, Not accepted', in data element 1225 of the BGM segment. Where a previous DELFOR message is being totally rejected then only the EDIFACT mandatory segments, and those agreed by the parties exchanging the message which enable the identification of the previous message, need be re-sent. If required the reason for rejection may be indicated in the FTX segment at header level using either a bi-laterally agreed reason code, or a free text reason.

Should a DELFOR message have been received but not yet processed through the relevant internal application(s), a response may be issued indicating this fact using code value '12, Not processed', in data element 1225 of the BGM segment. Where this code value is being used then only the EDIFACT mandatory segments, and those agreed by the parties exchanging the message which enable the identification of the previous message, need be re-sent.

When the party responding to a previous DELFOR message wishes to propose changes to some of the information contained in the previous message, then the code value '4, Change' should be used in data element 1225 of the BGM segment.

If no information at the detail level of the message (i.e. from the GIS segment onwards) changes then only the EDIFACT mandatory segments, those agreed by the parties exchanging the message which enable the identification of the previous message, and the segments containing the data proposed for change need be re-sent.

When changes are proposed to data contained at the detail level of the message then the following recommendations should be applied:

1. All the date information in the QTY-DTM segment group shall be systematically used to identify the group to be changed.

2. How the information is to be changed:

2.a. To change a quantity - where the date information matches the current quantity is replaced with the new quantity.

2.b. To change a date - the current quantity has to be changed to zero and the new date information has to be given with the quantity from the former schedule.

2.c. To change a date and quantity - the current quantity has to be changed to zero and the new date information has to be given with appropriate new quantity.

2.d. To delete quantities and dates - the current quantity has to be changed to zero.

2.e. To add quantities and dates - the new date information has to be given with the appropriate new quantity.

3. Unchanged dates and quantities - unchanged dates and quantities from the former schedule need to be resent.

4. Delivered quantities - delivered quantities are automatically eliminated from the schedule.


2. REFERENCES

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.


4. MESSAGE DEFINITION


4.1. Segment clarification

This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.

The following guidelines and principles apply to the whole message and are intended to facilitate the understanding and implementation of the message:

All specified dates/times should be in the format 'yymmdd'/'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, months, etc.)

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

Conditional data that is 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 a group.

Free text information within the message should be avoided as this inhibits automatic processing.

0010 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 S009:

Data element0065DELFOR
0052D
005400A
0051UN

0020 BGM, Beginning of message

A segment for unique identification of the Delivery schedule message by means of its name and its number and its function (original, replacement, change).

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

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

0050 Segment Group 1: RFF-DTM

A group of segments giving references relevant to the whole message, e.g. contract number.

0060 RFF, Reference

A segment for giving references to the whole Delivery schedule message, e.g. contract, original message number (AGO), previous message number (ACW), import or export licence.

0070 DTM, Date/time/period

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

0080 Segment Group 2: NAD-SG3-SG4

A group of segments identifying parties by their names, addresses, locations, references and contacts relevant to the whole delivery schedule.

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

0100 Segment Group 3: RFF-DTM

A group of segments giving references relevant to the party.

0110 RFF, Reference

A segment giving references related to the party.

0120 DTM, Date/time/period

Date/time/period of the reference.

0130 Segment Group 4: CTA-COM

A group of segments to identify person, function, or department and appropriate numbers to whom communication should be directed.

0140 CTA, Contact information

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

0150 COM, Communication contact

A segment identifying communication types and numbers for the person, function, or department identified in the CTA segment.

0160 Segment Group 5: TDT-DTM

A group of segments specifying details of the mode and means of transport, and date/time/period relating to the whole message. This group of segments is used only when the requested mode and means of transport deviates from the norm.

0170 TDT, Details of transport

A segment specifying the carriage, and the mode and means of transport.

0180 DTM, Date/time/period

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

0190 Segment Group 6: GIS-SG7-SG12

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

0200 X GIS, General indicator

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

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

0220 NAD, Name and address

A segment for identifying the consignee.

0230 LOC, Place/location identification

A segment identifying a specific location at the consignee address (e.g. dock, gate,..) to which product, as specified in the LIN-Segment groups, should be delivered.

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

0250 Segment Group 8: RFF-DTM

A group of segments giving references relevant to the consignee.

0260 RFF, Reference

A segment giving references related to the consignee.

0270 DTM, Date/time/period

Date/time/period of the reference.

0280 Segment Group 9: DOC-DTM

A group of segments providing information relating to documents required for the consignee.

0290 DOC, Document/message details

A segment describing the documents required for the specified consignee.

0300 DTM, Date/time/period

Date/time/period of documents required.

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

0320 CTA, Contact information

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

0330 COM, Communication contact

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

0340 Segment Group 11: TDT-DTM

A group of segments specifying details of the mode and means of transport, and date and/or time of departure and destination relating to specified delivery point. This group of segments is used only when the requested mode and means of transport deviates from the norm.

0350 TDT, Details of transport

A segment specifying the carriage, and the mode and means of transport.

0360 DTM, Date/time/period

A segment indicating the date/time/period details of departure or arrival relating to the TDT segment.

0370 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 for both methods.

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

0390 PIA, Additional product id

A segment providing additional product identification.

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

0410 MEA, Measurements

A segment specifying physical measurements of the item to be delivered in original or unpacked form.

0420 ALI, Additional information

A segment indicating that the line item is subject to special conditions due to origin, customs preference, or commercial factors.

0430 GIN, Goods identity number

A segment providing identity numbers to be applied to the goods to be delivered, e.g. serial numbers.

0440 GIR, Related identification numbers

A segment providing sets of related identification numbers for a line item, e.g. engine number, chassis number and transmission number for a vehicle.

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

0460 DTM, Date/time/period

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

0470 FTX, Free text

A segment with free text in coded or clear form to give further clarification, when required, to the line item to be delivered. In computer to computer exchanges such text will normally require the receiver to process this segment manually.

0480 Segment Group 13: RFF-DTM

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

0490 RFF, Reference

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.

0500 DTM, Date/time/period

Date/time/period of the reference.

0510 Segment Group 14: TDT-TMD-DTM

A group of segments specifying details of the mode, movement and means of transport, and date/time/period related to the specified transport details. When using the delivery point method this segment group overrides for the product identified in the LIN segment the information specified in segment group 11.

0520 TDT, Details of transport

A segment specifying the carriage, and the mode and means of transport of the goods for the specified location.

0530 TMD, Transport movement details

A segment to specify transport movement details for an item.

0540 DTM, Date/time/period

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

0550 Segment Group 15: QTY-DTM-SG16

A group of segments specifying product quantities and associated dates not related to schedules and where relevant, references.

0560 QTY, Quantity

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

0570 DTM, Date/time/period

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

0580 Segment Group 16: RFF-DTM

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

0590 RFF, Reference

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

0600 DTM, Date/time/period

Date/time/period of the reference.

0610 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. With the product driven method this segment group can be used to summarise all schedules provided with the subsequent delivery point information given in segment group 22.

0620 SCC, Scheduling conditions

A segment specifying the status of the schedule. Optionally a delivery pattern can be established, e.g. firm or proposed delivery pattern.

0630 Segment Group 18: QTY-DTM-SG19

A group of segments specifying product quantities and associated dates.

0640 QTY, Quantity

A segment to specify pertinent quantities which may relate to schedule(s) and, or pattern established in the SCC segment, e.g. delivery quantity for a specified date.

0650 DTM, Date/time/period

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

0660 Segment Group 19: RFF-DTM

A group of segments for specifying references associated with the given schedule's quantity and date and where necessary the reference dates.

0670 RFF, Reference

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

0680 DTM, Date/time/period

Date/time/period of the reference.

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

0700 PAC, Package

A segment specifying the number of package units and the type of packaging for the line item, e.g. pallet.

0710 MEA, Measurements

A segment specifying physical measurements of packages described in the PAC segment, e.g. pallet dimensions.

0720 QTY, Quantity

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

0730 DTM, Date/time/period

A segment specifying date/time/period details relating to the physical units (packages) described in the PAC segment, e.g. packaging specification date.

0740 Segment Group 21: PCI-GIN

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

0750 PCI, Package identification

A segment specifying markings and labels used on individual physical units (packages) described in the PAC segment.

0760 GIN, Goods identity number

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

0770 Segment Group 22: NAD-LOC-FTX-SG23-SG24-SG25-SG27-SG30

A group of segments providing details of the individual delivery points for the given product.

0780 NAD, Name and address

A segment for identifying names and addresses relevant to the delivery point.

0790 LOC, Place/location identification

A segment identifying a specific location at the address (e.g. dock, gate,..).

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

0810 Segment Group 23: DOC-DTM

A group of segments providing information relating to documents required for the delivery point.

0820 DOC, Document/message details

A segment providing information relating to the documents required for specified delivery points.

0830 DTM, Date/time/period

Date/time/period of documents required.

0840 Segment Group 24: CTA-COM

A group of segments to identify a person, function or department and appropriate numbers to whom communication should be directed. The information specified in this group is related to the delivery point.

0850 CTA, Contact information

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

0860 COM, Communication contact

A segment to identify communication types and numbers for the person, function, or department identified in CTA segment.

0870 Segment Group 25: QTY-DTM-SG26

A group of segments specifying product quantities and associated dates and where relevant, references relating to the delivery point.

0880 QTY, Quantity

A segment to specify pertinent quantities for the delivery point not related to schedule(s), e.g. cumulative quantities, last quantity considered.

0890 DTM, Date/time/period

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

0900 Segment Group 26: RFF-DTM

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

0910 RFF, Reference

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

0920 DTM, Date/time/period

Date/time/period of the reference.

0930 Segment Group 27: SCC-SG28

A group of segments specifying scheduling information detailing quantities and date for the given delivery point. This segment group also specifies references and their associated dates related to the schedule as required for the delivery point.

0940 SCC, Scheduling conditions

A segment specifying the status of the schedule. Optionally a delivery pattern can be established, e.g. firm or proposed delivery schedule for a weekly pattern.

0950 Segment Group 28: QTY-DTM-SG29

A group of segments specifying product quantities and associated dates.

0960 QTY, Quantity

A segment to specify pertinent quantities which may relate to schedule(s) and/or pattern established in the SCC segment, e.g. delivery quantity for a specified date.

0970 DTM, Date/time/period

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

0980 Segment Group 29: RFF-DTM

A group of segments for specifying references associated with the given schedule and delivery point and where necessary their dates.

0990 RFF, Reference

A segment to provide references for the given schedules.

1000 DTM, Date/time/period

Date/time/period of the reference.

1010 Segment Group 30: TDT-DTM

A group of segments specifying details of the mode and means of transport, and date/time/period relating to the delivery point. This segment's information overrides transport detail information for the identified delivery point given in segment group 5 or segment group 14.

1020 TDT, Details of transport

A segment specifying the carriage, and the mode and means of transport of the goods for the delivery point.

1030 DTM, Date/time/period

A segment indicating the date/time/period relating to the TDT segment.

1040 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.


4.2. Segment index (alphabetical sequence)

ALI Additional information
BGM Beginning of message
COM Communication contact
CTA Contact information
DOC Document/message details
DTM Date/time/period
FTX Free text
GIN Goods identity number
GIR Related identification numbers
GIS General indicator
IMD Item description
LIN Line item
LOC Place/location identification
MEA Measurements
NAD Name and address
PAC Package
PCI Package identification
PIA Additional product id
QTY Quantity
RFF Reference
SCC Scheduling conditions
TDT Details of transport
TMD Transport movement details
UNH Message header
UNT Message trailer

4.3. Message structure


4.3.1. Segment table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─DTM Date/time/period ×10 (M)
├─FTX Free text ×5 (C)
├─Segment Group 1 ×10 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×1 (C)
├─Segment Group 2 ×99 (C)
├─NAD Name and address ×1 (M)
├─Segment Group 3 ×10 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×1 (C)
└─Segment Group 4 ×5 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×5 (C)
├─Segment Group 5 ×10 (C)
├─TDT Details of transport ×1 (M)
└─DTM Date/time/period ×5 (C)
├─Segment Group 6 ×9999 (C)
├─GIS General indicator ×1 (M)
├─Segment Group 7 ×1 (C)
├─NAD Name and address ×1 (M)
├─LOC Place/location identification ×10 (C)
├─FTX Free text ×5 (C)
├─Segment Group 8 ×10 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×1 (C)
├─Segment Group 9 ×10 (C)
├─DOC Document/message details ×1 (M)
└─DTM Date/time/period ×10 (C)
├─Segment Group 10 ×5 (C)
├─CTA Contact information ×1 (M)
└─COM Communication contact ×5 (C)
└─Segment Group 11 ×10 (C)
──├─TDT Details of transport ×1 (M)
──└─DTM Date/time/period ×5 (C)
└─Segment Group 12 ×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 ×999 (C)
──├─GIR Related identification numbers ×999 (C)
──├─LOC Place/location identification ×999 (C)
──├─DTM Date/time/period ×5 (C)
──├─FTX Free text ×5 (C)
──├─Segment Group 13 ×10 (C)
──├─RFF Reference ×1 (M)
──└─DTM Date/time/period ×1 (C)
──├─Segment Group 14 ×10 (C)
──├─TDT Details of transport ×1 (M)
──├─TMD Transport movement details ×1 (C)
──└─DTM Date/time/period ×5 (C)
──├─Segment Group 15 ×99 (C)
──├─QTY Quantity ×1 (M)
──├─DTM Date/time/period ×2 (C)
──└─Segment Group 16 ×10 (C)
────├─RFF Reference ×1 (M)
────└─DTM Date/time/period ×1 (C)
──├─Segment Group 17 ×999 (C)
──├─SCC Scheduling conditions ×1 (M)
──└─Segment Group 18 ×999 (C)
────├─QTY Quantity ×1 (M)
────├─DTM Date/time/period ×2 (C)
────└─Segment Group 19 ×10 (C)
──────├─RFF Reference ×1 (M)
──────└─DTM Date/time/period ×1 (C)
──├─Segment Group 20 ×99 (C)
──├─PAC Package ×1 (M)
──├─MEA Measurements ×10 (C)
──├─QTY Quantity ×5 (C)
──├─DTM Date/time/period ×5 (C)
──└─Segment Group 21 ×10 (C)
────├─PCI Package identification ×1 (M)
────└─GIN Goods identity number ×10 (C)
──└─Segment Group 22 ×999 (C)
────├─NAD Name and address ×1 (M)
────├─LOC Place/location identification ×10 (C)
────├─FTX Free text ×5 (C)
────├─Segment Group 23 ×10 (C)
────├─DOC Document/message details ×1 (M)
────└─DTM Date/time/period ×1 (C)
────├─Segment Group 24 ×5 (C)
────├─CTA Contact information ×1 (M)
────└─COM Communication contact ×5 (C)
────├─Segment Group 25 ×10 (C)
────├─QTY Quantity ×1 (M)
────├─DTM Date/time/period ×2 (C)
────└─Segment Group 26 ×10 (C)
──────├─RFF Reference ×1 (M)
──────└─DTM Date/time/period ×1 (C)
────├─Segment Group 27 ×999 (M)
────├─SCC Scheduling conditions ×1 (M)
────└─Segment Group 28 ×999 (M)
──────├─QTY Quantity ×1 (M)
──────├─DTM Date/time/period ×2 (C)
──────└─Segment Group 29 ×10 (C)
────────├─RFF Reference ×1 (M)
────────└─DTM Date/time/period ×1 (C)
────└─Segment Group 30 ×10 (C)
──────├─TDT Details of transport ×1 (M)
──────└─DTM Date/time/period ×5 (C)
└─UNT Message trailer ×1 (M)

Change indicators
plus sign An addition.
asterisk Addition/substraction/change to a code entry for a particular data element.
hash or pound sign Changes to names.
vertical bar Changes to text for descriptions, notes and functions.
minus sign A deletion.
letter X Marked for deletion.

Return to Stylus Studio EDIFACT D00A Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify Legacy Data Integration with Stylus Studio XML Enterprise Edition - Free Download!
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.