Frames | No Frames

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

Inspection request message

Version:D
Release:04A
Contr. Agency:UN
Revision:2
Date:2004-05-18
SOURCE:TBG1 Supply Chain

CONTENTS
Inspection request 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 by tag)
    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:
D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

0. INTRODUCTION

This specification provides the definition of the Inspection request message (INSREQ) 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 sent by a supplier to inform a customer that items are ready for inspection prior to despatch.


1.2. Field of application

The Inspection request 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

An Inspection request message is sent by a supplier to a customer's inspection service, or a third party who is acting on his behalf indicating that items are ready for inspection. The inspection process is generally to ensure that the articles are in compliance with a base document such as a purchase order.


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.

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Inspection request message is INSREQ.

Note: Inspection request messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065INSREQ
0052D
005404A
0051UN

0020 BGM, Beginning of message

A segment by which the sender uniquely identifies the Inspection request message by means of its type and number.

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 emission date of the document.

0040 Segment Group 1: RFF-DTM

A segment group for information on previous inspections, reference documents and where necessary, their dates.

0050 RFF, Reference

A segment identifying previous inspection requests, reports, reference document by their number and where appropriate, a line number within the document.

0060 DTM, Date/time/period

A segment specifying the date/time related to the referenced information.

0070 Segment Group 2: NAD-LOC

A group of segments identifying the parties relevant to the whole Inspection request message, with associated information.

0080 NAD, Name and address

A segment identifying names and addresses of parties, in coded or clear form, and their function relevant for the whole Inspection request message. Identification of the Supplier and inspection party is mandatory for the Inspection request message. They are to be given in this segment position.

0090 LOC, Place/location identification

A segment indicating more details regarding specific locations related to the party being described, e.g., internal site/building number where the inspection may be carried out.

0100 Segment Group 3: DOC-SG4-SG5-SG7

A segment group identifying the base document and line items to be inspected.

0110 DOC, Document/message details

A segment identifying the base document (e.g., purchase order) for the items in question by its number.

0120 Segment Group 4: RFF-DTM

A segment group providing complementary information relating to the base document, such as contract number, purchase order version, etc.

0130 RFF, Reference

A segment identifying the complementary information in relation to the base document.

0140 DTM, Date/time/period

A segment specifying the date/time related to the referenced information.

0150 Segment Group 5: NAD-SG6

A group of segments which identifies parties associated with the document.

0160 NAD, Name and address

A segment identifying parties associated with the document such as the issuer of the document.

0170 Segment Group 6: CTA-COM

A group of segments providing contacts and communication numbers associated with the party.

0180 CTA, Contact information

A segment identifying to whom communications should be directed.

0190 COM, Communication contact

A segment identifying communication numbers of the contacts to which communications should be directed.

0200 Segment Group 7: LIN-PIA-IMD-DTM-RFF-FTX-SG8

A group of segments providing the relevant information on the items to be inspected.

0210 LIN, Line item

A segment identifying the line item by its number and additionally, identifying the item involved by an identification number. Other identification numbers may be specified in the following PIA segment, e.g., manufacturer part number, etc.

0220 PIA, Additional product id

A segment providing additional identification information of the item being described, e.g., manufacturer part number.

0230 IMD, Item description

A segment for describing the item.

0240 DTM, Date/time/period

A segment specifying date, time or period details to the line item only.

0250 RFF, Reference

A segment identifying the complementary information in relation to the line item.

0260 FTX, Free text

A segment with free text in coded or clear form, to give further clarification, when required, for the line item. In computer to computer exchanges the use of clear form text will normally require the receiver to handle this message manually.

0270 Segment Group 8: NAD-GEI-LOC-QTY-QVR-RFF-FTX-SG9

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

0280 NAD, Name and address

A segment identifying names and addresses of parties to be delivered, in coded or clear form, and their function relevant for the line item.

0290 GEI, Processing information

A segment indicating general processing information concerning the party.

0300 LOC, Place/location identification

A segment indicating more details regarding specific locations related to the party being described, e.g., internal site or building number.

0310 QTY, Quantity

A segment to specify the quantity to be delivered to the delivery address.

0320 QVR, Quantity variances

A segment identifying a quantity variance with the quantity expected and the reason for it.

0330 RFF, Reference

A segment identifying the complementary information in relation to the party.

0340 FTX, Free text

A segment with free text information to give further clarification. In computer to computer exchanges the use of clear form text will normally require the receiver to handle this message manually.

0350 Segment Group 9: GIN-RFF

A group of segments identifying serial or batch numbers and their related references such as derogation numbers.

0360 GIN, Goods identity number

A segment providing specific serial or batch numbers, relating to the specified product

0370 RFF, Reference

A segment identifying the complementary information in relation to the serial or batch number.

0380 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 by tag)

BGM Beginning of message
COM Communication contact
CTA Contact information
DOC Document/message details
DTM Date/time/period
FTX Free text
GEI Processing information
GIN Goods identity number
IMD Item description
LIN Line item
LOC Place/location identification
NAD Name and address
PIA Additional product id
QTY Quantity
QVR Quantity variances
RFF Reference
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 ×99 (M)
├─Segment Group 1 ×99 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×99 (M)
├─NAD Name and address ×1 (M)
└─LOC Place/location identification ×99 (C)
├─Segment Group 3 ×99 (M)
├─DOC Document/message details ×1 (M)
├─Segment Group 4 ×99 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×99 (C)
├─Segment Group 5 ×99 (C)
├─NAD Name and address ×1 (M)
└─Segment Group 6 ×99 (C)
──├─CTA Contact information ×1 (M)
──└─COM Communication contact ×99 (C)
└─Segment Group 7 ×999 (C)
──├─LIN Line item ×1 (M)
──├─PIA Additional product id ×99 (C)
──├─IMD Item description ×99 (C)
──├─DTM Date/time/period ×99 (C)
──├─RFF Reference ×99 (C)
──├─FTX Free text ×9 (C)
──└─Segment Group 8 ×999 (C)
────├─NAD Name and address ×1 (M)
────├─GEI Processing information ×99 (C)
────├─LOC Place/location identification ×99 (C)
────├─QTY Quantity ×99 (C)
────├─QVR Quantity variances ×99 (C)
────├─RFF Reference ×99 (C)
────├─FTX Free text ×9 (C)
────└─Segment Group 9 ×999 (C)
──────├─GIN Goods identity number ×1 (M)
──────└─RFF Reference ×99 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D04A 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 EDIFACT to XML
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-2016 All Rights Reserved.