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)

Order status report message

Version:D
Release:97A
Contr. Agency:UN
Revision:1
Date:96-12-13
SOURCE:Western European EDIFACT Board - MD1

CONTENTS
Order status report 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
    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:
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 Order status report message (OSTRPT) 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 between a buyer or buyer's agent and a seller or seller's agent reporting status information on the current status of a previously sent order(s). This may be a reply to an order status enquiry or a report as agreed between the partners.


1.2. Field of Application

The Order status report 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

This message covers one seller and one buyer and may relate to:

  • one enquiry
  • one or more purchase orders
  • specific lines within purchase orders

The status can not trigger any action by the receiver of the message. For example, if the status is 'ready for shipment', it can not be used as a despatch advice information. A DESADV message, or an equivalent document, has to be sent as well.

This message can only be used to provide status information.


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 required in the message should be omitted.
  • Care must be taken that the segment qualifier in dependent segments does 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 Order status report message is OSTRPT.

Note: Order status report messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065OSTRPT
0052D
005497A
0051UN

0020 BGM, Beginning of message

A segment by which the sender must uniquely identify the order status report by means of its type and number and when necessary it's function.

0030 DTM, Date/time/period

A segment specifying general dates and, when relevant, times related to the whole message. The segment must be specified at least once to identify the request date.

0040 RFF, Reference

A segment identifying which enquiry document this message is responding to.

0050 FTX, Free text

A segment for free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.

0060 Segment Group 1: NAD-SG2

A group of segments identifying the parties with associated information.

0070 NAD, Name and address

A segment identifying names and addresses of the parties, in coded or clear form, and their functions. Identification of the seller is mandatory for an report. It is recommended that where possible only the coded form of the party ID should be specified.

0080 Segment Group 2: CTA-COM

A group of segments giving contact details of the specific person or department within the party identified in the NAD segment.

0090 CTA, Contact information

A segment to identify a person or department, and their function, to whom communication should be directed.

0100 COM, Communication contact

A segment to identify a communications type and number for the contact specified in the CTA segment.

0110 Segment Group 3: DOC-DTM-SG4-SG5

A group of segments providing details of the individual order(s).

0120 DOC, Document/message details

A segment giving references to the order(s) reported. Other references may also be given, e.g. seller's reference number.

0130 DTM, Date/time/period

A segment specifying the date/time related to the reference.

0140 Segment Group 4: STS-DTM-PCD-QTY-NAD

A group of segments providing status details related to the individual order.

0150 STS, Status

A segment giving the status of the referred order.

0160 DTM, Date/time/period

A segment specifying the date/time related to the order status.

0170 PCD, Percentage details

A segment used to indicate the percentage of completion related to the order status.

0180 QTY, Quantity

A segment used to indicate the quantity of completion related to the order status.

0190 NAD, Name and address

A segment identifying names and addresses of parties, in coded or clear form, and their functions relevant to the status reported.

0200 Segment Group 5: LIN-PIA-IMD-MEA-GIN-RCS-FTX-SG6-SG7-SG15

A group of segments providing details of the individual order(s) lines being reported.

0210 LIN, Line item

A segment used to identify a line item.

0220 PIA, Additional product id

A segment providing additional identification on the product specified in the LIN segment. E.g. To give seller's item number, EAN number, technical specification number.

0230 IMD, Item description

A segment for describing the product as well as product characteristic. This segment should be used for products or services that cannot be fully identified by a product code or article number.

0240 MEA, Measurements

A segment enabling the physical measurements of the ordered item to be specified where this is required for full identification of the product. Any measurements must refer to the product in its unpacked form e.g. thickness of plastic film, length, weight, etc.

0250 GIN, Goods identity number

A segment providing identity numbers to be applied to the items being queried e.g. serial numbers for assembled equipment.

0260 RCS, Requirements and conditions

A segment to enable industry or national requirements to be specified.

0270 FTX, Free text

A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually.

0280 Segment Group 6: RFF-DTM

A group of segments giving references related to the order line(s) and, where relevant, their dates.

0290 RFF, Reference

A segment giving references to seller's reference number, contract numbers, etc.

0300 DTM, Date/time/period

A segment specifying the date/time related to the reference.

0310 Segment Group 7: STS-DTM-PCD-QTY-SG8-SG10-SG11-SG12-

SG13 A group of segments providing status details and related information for the line or sub-line.

0320 STS, Status

A segment giving the status of the referred order line(s).

0330 DTM, Date/time/period

A segment specifying the date/time related to the order status.

0340 PCD, Percentage details

A segment used to indicate the percentage of completion related to the order status.

0350 QTY, Quantity

A segment used to indicate the quantity of completion related to the order status.

0360 Segment Group 8: NAD-RFF-SG9

A group of segments identifying the parties with associated information, relevant to the line item only.

0370 NAD, Name and address

A segment identifying names and addresses of parties, in coded or clear form, and their functions relevant to the item being queried. 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.

0380 RFF, Reference

A segment identifying the reference relevant to a party by its number and where appropriate a line number within a document.

0390 Segment Group 9: CTA-COM

A group of segments giving contact details of the specific person or department within the party identified in the NAD segment.

0400 CTA, Contact information

A segment to identify a person or department, and their function, to whom communication should be directed for the party.

0410 COM, Communication contact

A segment to identify a communication type and number for the contact specified in the CTA segment.

0420 Segment Group 10: TDT-LOC

A group of segments identifying the mode and means of transport, location and relevant dates and times for transportation, relating to the line item.

0430 TDT, Details of transport

A segment specifying the mode, means and identification of the transport for the line item being queried.

0440 LOC, Place/location identification

A segment identifying the locations relevant to the transport specified in the TDT segment.

0450 Segment Group 11: TOD-LOC

A group of segments indicating the terms of delivery which are relevant to the line item.

0460 TOD, Terms of delivery or transport

A segment identifying the delivery terms to be used.

0470 LOC, Place/location identification

A segment indicating the location relevant to the delivery terms specified in the TOD segment.

0480 Segment Group 12: EQD-HAN

A group of segments providing information relating to equipment identification and ownership, handling and notification of hazardous materials, relating to the line item.

0490 EQD, Equipment details

A segment to define fixed information regarding equipment to be used in conjunction with the line item being queried, and if required, to indicate responsibility for supply of the equipment e.g. a container identification.

0500 HAN, Handling instructions

A segment providing information on required handling of materials and additionally, if required, identifying hazardous materials in the item being queried.

0510 Segment Group 13: PAC-QTY-SG14

A group of segments identifying the packaging, physical dimensions, and marks and numbers for goods referenced in the line or sub-line item.

0520 PAC, Package

A segment specifying the number of packages and the physical type of packaging for the line item e.g. pallet type.

0530 QTY, Quantity

A segment specifying the maximum quantity number of packages which can be stacked safely on another and/or the number of items normally contained within the package.

0540 Segment Group 14: PCI-RFF

A group of segments specifying the markings and labels on individual physical units.

0550 PCI, Package identification

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

0560 RFF, Reference

A segment identifying the master label number.

0570 Segment Group 15: SCC-SG16

A group of segments specifying the delivery schedules and related locations, quantities and dates/times of a specific delivery.

0580 SCC, Scheduling conditions

A segment specifying the type and status of the schedule.

0590 Segment Group 16: LOC-DTM-QTY-SG17

A group of segments providing quantity details and related dates/times of a specific delivery.

0600 LOC, Place/location identification

A segment indicating the location to which part of the consignment is to be delivered.

0610 DTM, Date/time/period

A segment specifying the date/time related to the product quantities. The segment can only be used to identify the delivery date.

0620 QTY, Quantity

A segment identifying the product quantities.

0630 Segment Group 17: STS-DTM-PCD-QTY-NAD

A group of segments providing status details and related dates/time.

0640 STS, Status

A segment giving the status of the referred delivery.

0650 DTM, Date/time/period

A segment specifying the date/time related to the order status.

0660 PCD, Percentage details

A segment used to indicate the percentage of completion related to the order status.

0670 QTY, Quantity

A segment used to indicate the quantity of completion related to the order status.

0680 NAD, Name and address

A segment identifying names and addresses of parties, in coded or clear form, and their functions related to the status reported.

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

BGM Beginning of message
COM Communication contact
CTA Contact information
DOC Document/message details
DTM Date/time/period
EQD Equipment details
FTX Free text
GIN Goods identity number
HAN Handling instructions
IMD Item description
LIN Line item
LOC Place/location identification
MEA Measurements
NAD Name and address
PAC Package
PCD Percentage details
PCI Package identification
PIA Additional product id
QTY Quantity
RCS Requirements and conditions
RFF Reference
SCC Scheduling conditions
STS Status
TDT Details of transport
TOD Terms of delivery or 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 ×5 (M)
├─RFF Reference ×1 (C)
├─FTX Free text ×99 (C)
├─Segment Group 1 ×99 (M)
├─NAD Name and address ×1 (M)
└─Segment Group 2 ×5 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×5 (C)
├─Segment Group 3 ×999 (M)
├─DOC Document/message details ×1 (M)
├─DTM Date/time/period ×5 (C)
├─Segment Group 4 ×99 (C)
├─STS Status ×1 (M)
├─DTM Date/time/period ×5 (C)
├─PCD Percentage details ×1 (C)
├─QTY Quantity ×1 (C)
└─NAD Name and address ×1 (C)
└─Segment Group 5 ×99999 (C)
──├─LIN Line item ×1 (M)
──├─PIA Additional product id ×99 (C)
──├─IMD Item description ×99 (C)
──├─MEA Measurements ×5 (C)
──├─GIN Goods identity number ×99 (C)
──├─RCS Requirements and conditions ×5 (C)
──├─FTX Free text ×99 (C)
──├─Segment Group 6 ×999 (C)
──├─RFF Reference ×1 (M)
──└─DTM Date/time/period ×1 (C)
──├─Segment Group 7 ×99 (C)
──├─STS Status ×1 (M)
──├─DTM Date/time/period ×5 (C)
──├─PCD Percentage details ×1 (C)
──├─QTY Quantity ×1 (C)
──├─Segment Group 8 ×99 (C)
──├─NAD Name and address ×1 (M)
──├─RFF Reference ×5 (C)
──└─Segment Group 9 ×5 (C)
────├─CTA Contact information ×1 (M)
────└─COM Communication contact ×5 (C)
──├─Segment Group 10 ×5 (C)
──├─TDT Details of transport ×1 (M)
──└─LOC Place/location identification ×1 (C)
──├─Segment Group 11 ×5 (C)
──├─TOD Terms of delivery or transport ×1 (M)
──└─LOC Place/location identification ×1 (C)
──├─Segment Group 12 ×5 (C)
──├─EQD Equipment details ×1 (M)
──└─HAN Handling instructions ×5 (C)
──└─Segment Group 13 ×1 (C)
────├─PAC Package ×1 (M)
────├─QTY Quantity ×1 (C)
────└─Segment Group 14 ×10 (C)
──────├─PCI Package identification ×1 (M)
──────└─RFF Reference ×99 (C)
──└─Segment Group 15 ×99 (C)
────├─SCC Scheduling conditions ×1 (M)
────└─Segment Group 16 ×99 (C)
──────├─LOC Place/location identification ×1 (M)
──────├─DTM Date/time/period ×5 (C)
──────├─QTY Quantity ×1 (C)
──────└─Segment Group 17 ×99 (C)
────────├─STS Status ×1 (M)
────────├─DTM Date/time/period ×5 (C)
────────├─PCD Percentage details ×1 (C)
────────├─QTY Quantity ×1 (C)
────────└─NAD Name and address ×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.