Frames | No Frames

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

Delivery just in time message

Version:D
Release:97A
Contr. Agency:UN
Revision:3
Date:96-12-13
SOURCE:Submitted by WEEB-MD1 on behalf of PAEB

CONTENTS
Delivery just in time 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. Data segment clarification
      1. Header section
      2. Detail section
    2. Data 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.6, 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 just in time message (DELJIT) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

A message provides the ability for a customer to convey precise delivery sequence and Just In Time schedule requirements to a supplier, and is intended to supplement the Delivery Schedule Message (DELFOR).


1.2. Field of Application

The UN Standard Delivery Just In Time Message may be applied to national and international trade. It is based on universal commercial practice and is not dependent on the type of business or industry.


1.3. Principles

The use of this message will facilitate the practice of Just In Time (JIT) delivery by providing the customer with a mechanism to issue precise shipping schedule requirements in terms of a 24 hour clock and on a more frequent basis than with the instance of a delivery schedule message, e.g. daily shipping schedules versus weekly planning schedules.


2. REFERENCES

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


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

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


4. MESSAGE DEFINITION


4.1. Data Segment Clarification

This section should be read in conjunction with the Segment Table which indicate 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.


4.1.1. Header section

Information to be provided in the Header section:

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Delivery just in time message is DELJIT.

Note: Delivery just in time messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065DELJIT
0052D
005497A
0051UN

0020 BGM, Beginning of message

A segment for unique identification of the document name and its number.

0030 DTM, Date/time/period

A segment specifying the date and, when relevant, the time/period for delivery of that sequence, relating to the whole message. The DTM segment must be specified at least once to identify the Delivery Just In Time document date.

The date/time/period segment within other Segment group should be used whenever the date/time/period requires to be logically related to another specified data item.

0040 + FTX, Free text

Segment giving additional information relevant to the entire message.

0050 Segment Group 1: RFF-DTM

A group of segments giving references only relevant to the specified party rather than the whole message, e.g. contract number.

0060 RFF, Reference

A segment for referencing documents to the whole message, e.g. contract, import/export license.

0070 DTM, Date/time/period

date/time/period as applied the referred document.

0080 Segment Group 2: NAD-LOC-FTX-SG3

A group of segments identifying names and addresses and their functions relevant for the whole Delivery Just In Time Message.

0090 NAD, Name and address

A segment for identifying names and addresses and their functions relevant for the whole Delivery Just In Time Message. Identification of the seller and buyer parties is recommended for the Delivery Just In Time. They are to be given in the NAD segment.

It is recommended that where possible only the coded form of the party ID should be specified. e.g. The Buyer and Seller are known to each other, thus only the coded ID is required, but the Consignee or Delivery address may vary and would have to be clearly specified, preferably in structured format.

0100 LOC, Place/location identification

A segment indicating more details regarding specific place/locations related to the party specified in the NAD segment, e.g. internal site/building number.

0110 FTX, Free text

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

0120 Segment Group 3: CTA-COM

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

0130 CTA, Contact information

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

0140 COM, Communication contact

Identify communication types and numbers for person, function, department identified in CTA.


4.1.2. Detail section

Information to be provided in the Detail section:

0150 Segment group 4: SEQ-DTM-GIR-LOC-SG5-SG7 A group of segments providing details related to the delivery sequence. All other segments in this Segment Group 4 following the SEQ segment refer to that sequence.

0160 SEQ, Sequence details

A segment providing specific details related to the delivery sequence requested by the buyer or recipient of the product.

0170 DTM, Date/time/period

A segment specifying the date, and when relevant, the time/period for delivery of that sequence.

0180 GIR, Related identification numbers

A segment to be able to give related identification numbers.

0190 LOC, Place/location identification

A segment identifying a general location to which products, as specified in the Segment Group 7, should be delivered.

0200 Segment Group 5: PAC-SG6

Segment group to support KANBAN operation where customers must notify a supplier packaging labels and conditions.

0210 PAC, Package

To describe the number and type of packages/physical units.

0220 Segment Group 6: PCI-GIN

A segment group giving packaging identification and good identity number related to the segment PAC.

0230 PCI, Package identification

To specify markings and labels on individual packages or physical units.

0240 GIN, Goods identity number

To give specific identification numbers, either as single numbers or ranges.

0250 Segment Group 7: LIN-PIA-IMD-ALI-GIR-TDT-FTX-PAC-DTM-SG8-

SG9-SG11 A group of segments providing details of the individual line items to be delivered.

0260 LIN, Line item

A segment identifying the details of the product/service being delivered e.g. product identification. All other segments in the detail section following the LIN segment refer to the line item.

0270 PIA, Additional product id

A segment providing additional product identification.

0280 IMD, Item description

A segment for describing the product to be delivered. This segment should be used for products that cannot be identified by a product code or article number.

0290 ALI, Additional information

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

0300 GIR, Related identification numbers

A segment providing sets of related identification numbers for the line item.

0310 TDT, Details of transport

A segment specifying the carriage, and the mode and means of transport of the goods to be delivered.

0320 FTX, Free text

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

0330 PAC, Package

Segment giving information related to the instruction for package type which is valid for the specified deliveries of the line item.

0340 DTM, Date/time/period

A segment specifying the date, and when relevant, the time/period for delivery of line item.

0350 Segment Group 8: RFF-DTM

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

0360 RFF, Reference

A segment for referencing document and other numbers related to the line item as specified in the LIN segment.

0370 DTM, Date/time/period

Date/time/period as applied to the referred document.

0380 Segment Group 9: LOC-SG10

A group of segments providing delivery location information and where relevant contacts.

0390 LOC, Place/location identification

A segment indicating more details regarding specific locations related to the line item.

0400 Segment Group 10: CTA-COM

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

0410 CTA, Contact information

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

0420 COM, Communication contact

Identify communication types and numbers for person, function, department identified in CTA.

0430 Segment Group 11: QTY-SCC-DTM-SG12

A group of segments specifying quantity related information for actual delivery.

0440 QTY, Quantity

A segment to specify pertinent quantities relating to the line item.

0450 SCC, Scheduling conditions

A segment indicating the scheduling conditions.

0460 DTM, Date/time/period

A segment indicating the date/time/period details relating to the quantity and schedule details in the line item.

0470 Segment Group 12: RFF-DTM

A group of segments giving references relating to the quantities.

0480 RFF, Reference

A segment for referencing the specific product release information e.g. appointment.

0490 DTM, Date/time/period

Date/time/period as applied to the referred document.

0500 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.


4.2. Data segment index (Alphabetical sequence by tag)

ALI Additional information
BGM Beginning of message
COM Communication contact
CTA Contact information
DTM Date/time/period
FTX Free text
GIN Goods identity number
GIR Related identification numbers
IMD Item description
LIN Line item
LOC Place/location identification
NAD Name and address
PAC Package
PCI Package identification
PIA Additional product id
QTY Quantity
RFF Reference
SCC Scheduling conditions
SEQ Sequence details
TDT Details of transport
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 ×20 (C)
├─NAD Name and address ×1 (M)
├─LOC Place/location identification ×10 (C)
├─FTX Free text ×5 (C)
└─Segment Group 3 ×5 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×5 (C)
├─Segment Group 4 ×9999 (M)
├─SEQ Sequence details ×1 (M)
├─DTM Date/time/period ×5 (C)
├─GIR Related identification numbers ×99 (C)
├─LOC Place/location identification ×5 (C)
├─Segment Group 5 ×5 (C)
├─PAC Package ×1 (M)
└─Segment Group 6 ×999 (C)
──├─PCI Package identification ×1 (M)
──└─GIN Goods identity number ×10 (C)
└─Segment Group 7 ×9999 (C)
──├─LIN Line item ×1 (M)
──├─PIA Additional product id ×10 (C)
──├─IMD Item description ×10 (C)
──├─ALI Additional information ×5 (C)
──├─GIR Related identification numbers ×5 (C)
──├─TDT Details of transport ×5 (C)
──├─FTX Free text ×5 (C)
──├─PAC Package ×5 (C)
──├─DTM Date/time/period ×5 (C)
──├─Segment Group 8 ×5 (C)
──├─RFF Reference ×1 (M)
──└─DTM Date/time/period ×1 (C)
──├─Segment Group 9 ×5 (C)
──├─LOC Place/location identification ×1 (M)
──└─Segment Group 10 ×5 (C)
────├─CTA Contact information ×1 (M)
────└─COM Communication contact ×5 (C)
──└─Segment Group 11 ×100 (C)
────├─QTY Quantity ×1 (M)
────├─SCC Scheduling conditions ×1 (C)
────├─DTM Date/time/period ×2 (C)
────└─Segment Group 12 ×5 (C)
──────├─RFF Reference ×1 (M)
──────└─DTM Date/time/period ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D97A 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.