|
This message is available for formal trial in the present version for a period of at least twelve months from the date of approval by the UN/ECE/TRADE/WP.4. Organisations are invited to trial this message and are requested to notify their Rapporteur Team Secretariat of their intention. Comments on the results from the trial should also be forwarded to the Secretariat as soon as they are available. Based on the results of the trials, a UNSM will be issued. It should be noted that this material is contained in a Trial Directory; however, it may differ from that in the UN Directories (UNTDID) having the same identfying tags. Any differences will be reconciled prior to the message becoming a UNSM. |
| Message Type: | DELJIT |
|---|---|
| Version: | D |
| Release: | 93A |
| Contr. Agency: | UN |
| Status: | 2 |
| Date: | 93-07 |
| SOURCE: | Submitted by WEEB-MD1 on behalf of PAEB |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.5, 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 |
This specification provides the definition of Delivery Just In Time Message (DELJIT) to be used in Electronic Data Interchange (EDI) between partners involved in administration, commerce and transport.
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).
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.
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.
See UNTDID, Part 4 Section 2.5 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Section 2.5 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the UN Delivery Just In Time Message is 'DELJIT'. Note: Delivery Just In Time messages conforming to this document must contain the following data in UNH, composite S009: Data element 0065 DELJIT 0052 D 0054 93A 0051 UN
A segment for unique identification of the document name and its number.
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.
A group of segments giving references only relevant to the specified party rather than the whole message, e.g. contract number.
A segment for referencing documents to the whole message, e.g. contract, import/export license.
date/time/period as applied the referred document.
A group of segments identifying names and addresses and their functions relevant for the whole Delivery Just In Time Message.
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.
A segment indicating more details regarding specific place/locations related to the party specified in the NAD segment, e.g. internal site/building number.
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.
A group of segments to identify person, function, department and appropriate numbers to whom communication should be directed.
A segment to identify person, function, department to whom communication should be directed.
Identify communication types and numbers for person, function, department identified in CTA.
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.
A segment providing specific details related to the delivery sequence requested by the buyer or recipient of the product.
A segment specifying the date, and when relevant, the time/period for delivery of that sequence.
A segment identifying a general location to which products, as
A group of segments providing details of the individual line items to be delivered.
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.
A segment providing additional product identification.
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.
A segment indicating that the line item is subject to special conditions owing to origin, customs preference, or commercial factors.
A segment providing sets of related identification numbers for the line item.
A segment specifying the carriage, and the mode and means of transport of the goods to be delivered.
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.
A segment specifying the date, and when relevant, the time/period for delivery of line item.
A group of segments giving references and where necessary, their dates, relating to the line item.
A segment for referencing document and other numbers related to the line item as specified in the LIN segment.
Date/time/period as applied to the referred document.
A group of segments providing delivery location information and where relevant contacts.
A segment indicating more details regarding specific locations related to the line item.
A group of segments to identify person, function, department and appropriate numbers to whom communication should be directed.
A segment to identify person, function, department to whom communication should be directed.
Identify communication types and numbers for person, function, department identified in CTA.
A group of segments specifying quantity related information for actual delivery.
A segment to specify pertinent quantities relating to the line item.
A segment indicating the scheduling conditions.
A segment indicating the date/time/period details relating to the quantity and schedule details in the line item.
A group of segments giving references relating to the quantities.
A segment for referencing the specific product release information e.g. appointment.
Date/time/period as applied to the referred document.
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×10 | (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) |
| │─├─LOC Place/location identification | ×5 | (C) |
| │─└─Segment Group 5 | ×9999 | (M) |
| │───├─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) |
| │───├─DTM Date/time/period | ×5 | (C) |
| │───├─Segment Group 6 | ×5 | (C) |
| │───│─├─RFF Reference | ×1 | (M) |
| │───│─└─DTM Date/time/period | ×1 | (C) |
| │───├─Segment Group 7 | ×5 | (C) |
| │───│─├─LOC Place/location identification | ×1 | (M) |
| │───│─└─Segment Group 8 | ×5 | (C) |
| │───│───├─CTA Contact information | ×1 | (M) |
| │───│───└─COM Communication contact | ×5 | (C) |
| │───└─Segment Group 9 | ×100 | (C) |
| │─────├─QTY Quantity | ×1 | (M) |
| │─────├─SCC Scheduling conditions | ×1 | (C) |
| │─────├─DTM Date/time/period | ×2 | (C) |
| │─────└─Segment Group 10 | ×5 | (C) |
| │───────├─RFF Reference | ×1 | (M) |
| │───────└─DTM Date/time/period | ×1 | (C) |
| └─UNT Message trailer | ×1 | (M) |
| ALI | Additional information | |
| BGM | Beginning of message | |
| COM | Communication contact | |
| CTA | Contact information | |
| DTM | Date/time/period | |
| FTX | Free text | |
| GIR | Related identification numbers | |
| IMD | Item description | |
| LIN | Line item | |
| LOC | Place/location identification | |
| NAD | Name and address | |
| PIA | Additional product id | |
| QTY | Quantity | |
| RFF | Reference | |
| SCC | Scheduling conditions | |
| SEQ | Sequence details | |
| TDT | Details of transport | |
| UNH | Message header | |
| UNT | Message trailer |