REQDOC Request for document

TBG1 Supply Chain

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.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. 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 18B 0051 UN

  2. A segment by which the sender must uniquely identify the request for document by means of its type and number.

  3. 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.

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

  5. 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.

  6. Segment group 1
    Repeat 99

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

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

  7. Segment group 2
    Repeat 99

    1. 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.

    2. A segment to identify a location within the above name and address.

    3. Segment group 3
      Repeat 9

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

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

  8. Segment group 4
    Repeat 999

    1. 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.

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

    3. A segment identifying the date that pertain to the document, e.g. original date, required by date.

    4. A segment providing additional identification of the product to which the document pertains.

    5. 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.

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

    7. Segment group 5
      Repeat 99

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

      2. A segment to provide dates/times applicable to the above references.

    8. Segment group 6
      Repeat 99

      1. A segment to identify other parties requiring the document.

      2. A segment to further qualify the above address.

      3. Segment group 7
        Repeat 9

        1. A segment to specify contact person or department.

        2. A segment to specify the communication channel and identifier for the above person / department.

  9. 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.

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.
Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.