0.    INTRODUCTION

       This specification provides the definition of the Request for
       document message (REQDOC) 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 to enable a party request the sending, or re-sending,
       of data, either as a document or message, or in some other
       agreed form.

1.2   Field of Application

       The Request for Document Message may be applied for both
       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 message is used to request a document to be sent, either
       electronically or otherwise. Its use should be limited to
       requesting documents, for which there is no other more specific
       message already provided (e.g. Request for Quotation).
       
       Parties can request documents on their own behalf, or on behalf
       of third parties.
       
       The message can be used to request individual documents by
       identity, or by specifying product and/or other related data to
       retrieve all relevant documents.
       
       Typical uses of the Request for Document Message are to request
       information from a data base (e.g. requesting a copy of a test
       certificate), requesting catalogue data, and requesting
       statements of account.

2.    REFERENCES

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

3.    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 Branching
       Diagram and the Segment Table which indicate mandatory,
       conditional and repeating requirements.

 | UNH, Message header
       A service segment starting and uniquely identifying a message.
       The message type code for the Request for document message is
       REQDOC.
       
       Note: Request for document messages conforming to this document
       must contain the following data in segment UNH, composite S009:

       Data element  0065 REQDOC
                     0052 D
                     0054 95A
                     0051 UN

   BGM, Beginning of message
       A segment by which the sender must uniquely identify the
       request for document by means of its type and number.

   DOC, Document/message details
       A segment indicating the type of document that is required, how
       many copies, and in what form it is required, e.g. EDI, mail,
       etc.

   DTM, Date/time/period
       A segment specifying general dates and, when relevant, times
       related to the whole message. The request preparation date must
       be specified using this segment.


   Segment group 1: RFF-DTM
       A group of segments for giving references and where necessary,
       their dates, relating to the whole message.

      RFF, Reference
          A segment identifying the reference by its number and where
          appropriate a line number within the document.

      DTM, Date/time/period
          A segment specifying the date/time related to the reference.


   Segment group 2: NAD-LOC-SG3
       A group of segments identifying the parties with associated
       information.

      NAD, Name and address
          A segment identifying names and addresses of the parties, in
          coded or clear form, and their functions relevant to the
          request for document message. Identification of the sender
          of the request and the recipient is mandatory for the
          request for document message. It is recommended that where
          possible only the coded form of the party ID should be
          specified e.g. the sender and receiver of the report are
          known to each other, thus only the coded ID is required, but
          when a new address might have to be clearly specified, e.g.
          where the document is to be sent to a third party, this
          should be done preferably in structured format.

      LOC, Place/location identification
          A segment to identify a location within the above name and
          address.


      Segment group 3: CTA-COM
          A group of segments giving contact details of the specific
          person or department within the party identified in the NAD
          segment.

         CTA, Contact information
             A segment to identify a person or department, and their
             function, to whom communications should be directed.

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


   Segment group 4: LIN-GIS-DTM-PIA-IMD-MEA-SG5-SG6
       A group of segments providing details of what information is
       required to be included in the document.
       There must be at least one occurrence of Segment group 4 within
       a request for document message.

      LIN, Line item
          A segment identifying the line item of the message by the
          line number and optionally identifying the product or
          service to be included in the document/message.

      GIS, General indicator
          A segment allowing the user to specify any special
          processing requirements, e.g. that all related documents are
          also required.

      DTM, Date/time/period
          A segment identifying the date that pertain to the document,
          e.g. original date, required by date.

      PIA, Additional product id
          A segment providing additional identification of the product
          to which the document pertains.

      IMD, Item description
          A segment used to identify the product by free format or
          semi- structured description. Used when no appropriate code
          is available in the PIA segment to fully describe the
          product.

      MEA, Measurements
          A segment to describe the physical measurements of the
          required product, e.g. length, height, weight.


      Segment group 5: RFF-DTM
          A group of segments providing references, and if required
          applicable dates, pertaining to the above document.

         RFF, Reference
             A segment to identify applicable references to be
             included in the document, e.g. order number, certificate
             number.

         DTM, Date/time/period
             A segment to provide dates/times applicable to the above
             references.


      Segment group 6: NAD-LOC-SG7
          A group of segments allowing documents to be individually
          addressed to either particular places, and or particular
          people within locations.

         NAD, Name and address
             A segment to identify other parties requiring the
             document.

         LOC, Place/location identification
             A segment to further qualify the above address.


         Segment group 7: CTA-COM
             A group of segments to identify individual contacts
             relevant to the above party.

            CTA, Contact information
                A segment to specify contact person or department.

            COM, Communication contact
                A segment to specify the communication channel and
                identifier for the above person / department.

   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
          GIS General indicator
          IMD Item description
          LIN Line item
          LOC Place/location identification
          MEA Measurements
          NAD Name and address
          PIA Additional product id
          RFF Reference
          UNH Message header
          UNT Message trailer

Contents of REQDOC