D96A
Message D96A/REQDOC
Request for document message
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.
Message description
UNH
M(1) : Message headerA 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 96A 0051 UN
BGM
M(1) : Beginning of messageA segment by which the sender must uniquely identify the request for document by means of its type and number.
DOC
M(1) : Document/message detailsA 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
M(9) : Date/time/periodA segment specifying general dates and, when relevant, times related to the whole message. The request preparation date must be specified using this segment.
SG1 C(9) : RFF-DTM
A group of segments for giving references and where necessary, their dates, relating to the whole message.
RFF
M(1) : ReferenceA segment identifying the reference by its number and where appropriate a line number within the document.
DTM
C(5) : Date/time/periodA segment specifying the date/time related to the reference.
SG2 M(9) : NAD-LOC-SG3
A group of segments identifying the parties with associated information.
NAD
M(1) : Name and addressA 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
C(9) : Place/location identificationA segment to identify a location within the above name and address.
SG3 C(9) : CTA-COM
A group of segments giving contact details of the specific person or department within the party identified in the NAD segment.
CTA
M(1) : Contact informationA segment to identify a person or department, and their function, to whom communications should be directed.
COM
C(9) : Communication contactA segment to identify a communications type and number for the contact specified in the CTA segment.
SG4 M(999) : 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
M(1) : Line itemA 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
C(9) : General indicatorA segment allowing the user to specify any special processing requirements, e.g. that all related documents are also required.
DTM
C(9) : Date/time/periodA segment identifying the date that pertain to the document, e.g. original date, required by date.
PIA
C(9) : Additional product idA segment providing additional identification of the product to which the document pertains.
IMD
C(9) : Item descriptionA 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
C(9) : MeasurementsA segment to describe the physical measurements of the required product, e.g. length, height, weight.
SG5 C(9) : RFF-DTM
A group of segments providing references, and if required applicable dates, pertaining to the above document.
RFF
M(1) : ReferenceA segment to identify applicable references to be included in the document, e.g. order number, certificate number.
DTM
C(9) : Date/time/periodA segment to provide dates/times applicable to the above references.
SG6 C(9) : NAD-LOC-SG7
A group of segments allowing documents to be individually addressed to either particular places, and or particular people within locations.
NAD
M(1) : Name and addressA segment to identify other parties requiring the document.
LOC
C(9) : Place/location identificationA segment to further qualify the above address.
SG7 C(9) : CTA-COM
UNT
M(1) : Message trailerA service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
Message structure
UNH, Message header M 1
BGM, Beginning of message M 1
DOC, Document/message details M 1
DTM, Date/time/period M 9
--- Segment Group 1 ------------------------- C 9 -------+
RFF, Reference M 1 |
DTM, Date/time/period C 5 |
---- -----------------------------------------------------------+
--- Segment Group 2 ------------------------- M 9 -------+
NAD, Name and address M 1 |
LOC, Place/location identification C 9 |
|
--- Segment Group 3 ------------------------- C 9 ------+|
CTA, Contact information M 1 ||
COM, Communication contact C 9 ||
---- ----------------------------------------------------------++
--- Segment Group 4 ------------------------- M 999 -------+
LIN, Line item M 1 |
GIS, General indicator C 9 |
DTM, Date/time/period C 9 |
PIA, Additional product id C 9 |
IMD, Item description C 9 |
MEA, Measurements C 9 |
|
--- Segment Group 5 ------------------------- C 9 ------+|
RFF, Reference M 1 ||
DTM, Date/time/period C 9 ||
---- ----------------------------------------------------------+|
|
--- Segment Group 6 ------------------------- C 9 ------+|
NAD, Name and address M 1 ||
LOC, Place/location identification C 9 ||
||
--- Segment Group 7 ------------------------- C 9 -----+||
CTA, Contact information M 1 |||
COM, Communication contact C 9 |||
---- ---------------------------------------------------------+++
UNT, Message trailer M 1