© 2018 ProgM

Nachricht REQDOC: D

NameREQDOC
VersionD
Release18B
BeschreibungRequest for document message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A 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 D B UNMandatory
BGM0A segment by which the sender must uniquely identify the request for document by means of its type and number.Mandatory
DOC0A segment indicating the type of document that is required, how many copies, and in what form it is required, e.g. EDI, mail, etc.Mandatory
DTM0A segment specifying general dates and, when relevant, times related to the whole message. The request preparation date must be specified using this segment.Mandatory
FTX0A 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.Optional
SG10SG1Optional
RFF1A segment identifying the reference by its number and where appropriate a line number within the document.Mandatory
DTM1A segment specifying the date/time related to the reference.Optional
SG20SG2Optional
NAD1A 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.Mandatory
LOC1A segment to identify a location within the above name and address.Optional
SG31SG3Optional
CTA2A segment to identify a person or department, and their function, to whom communications should be directed.Mandatory
COM2A segment to identify a communications type and number for the contact specified in the CTA segment.Optional
SG40SG4Optional
LIN1A 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.Mandatory
GEI1A segment allowing the user to specify any special processing requirements, e.g. that all related documents are also required.Optional
DTM1A segment identifying the date that pertain to the document, e.g. original date, required by date.Optional
PIA1A segment providing additional identification of the product to which the document pertains.Optional
IMD1A 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.Optional
MEA1A segment to describe the physical measurements of the required product, e.g. length, height, weight.Optional
SG51SG5Optional
RFF2A segment to identify applicable references to be included in the document, e.g. order number, certificate number.Mandatory
DTM2A segment to provide dates/times applicable to the above references.Optional
SG61SG6Optional
NAD2A segment to identify other parties requiring the document.Mandatory
LOC2A segment to further qualify the above address.Optional
SG72SG7Optional
CTA3A segment to specify contact person or department.Mandatory
COM3A segment to specify the communication channel and identifier for the above person / department.Optional
UNT0A 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.Mandatory