© 2018 ProgM

Nachricht IMPDEF: D

NameIMPDEF
VersionD
Release18B
BeschreibungEDI implementation guide definition message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A service segment starting and uniquely identifying a message. The message type code for the EDI implementation guide definition message is IMPDEF. Note: EDI implementation guide definition messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 IMPDEF D B UNMandatory
BGM0A segment to indicate the beginning of the message and to transmit function, type and number of the message.Mandatory
MSG0A segment identifying a message type to which the implementation details apply.Mandatory
RCS0A segment specifying the distribution conditions for the implementation.Optional
DII0A segment specifying the identity of the source directory set and giving its language and maintenance operation. This identifies the underlying standard from which the standard message is drawn.Mandatory
RFF0A segment carrying reference information for the implementation as a whole. This may specify the unique registration identifier of this implementation guide; it may carry references to graphical information to be used or displayed whenever the implementation is physically displayed.Optional
DTM0A segment specifying dates related to the implementation guide, such as date of issue or date of approval.Optional
FTX0A segment providing implementation guide notes which relate to the implementation as a whole. It may also carry various legal or contractual phrases which may apply to the ownership or copyright of the implementation guide, or contractual terms which will be incorporated by reference into any contract of which a data transmission using this implementation is a part.Optional
SG10SG1Optional
PNA1A segment identifying the names of the parties involved in the transaction, e.g., originator, requester, author or secretariat.Mandatory
ADR1A segment identifying the address of the party.Optional
SG21SG2Optional
CTA2A segment identifying a person or a department for the party to whom the communication should be directed.Mandatory
COM2A segment identifying communication type and number of the person.Optional
SG30SG3Optional
DFN1A segment identifying the object of the definition, and containing an optional 'name' or identifier.Mandatory
FTX1A segment providing implementation guide notes pertaining to the preceding definition, or to carry the text of a constraint expression.Optional
SG41SG4Optional
GRU2A segment specifying the usage of a segment group in a definition. The segment may identify one or more instances of a target segment group.Mandatory
FTX2A segment providing implementation guide notes or textual information related to the specific group in the underlying message.Optional
SG51SG5Optional
SGU2A segment specifying the usage of a segment in a message type structure for this definition. As well as defining the specific usage of a particular target segment, this segment also provides the segment context for the following element usage details. The segment may identify one or more instances of usage for any particular segment in the target data message.Mandatory
FTX2A segment providing implementation guide notes, or textual information relating to the specific segment in the underlying message.Optional
SG61SG6Optional
FNT2A segment specifying a footnote identification number that may place the relationship in the current context.Mandatory
REL2A segment specifying a relationship between the various components, typically data elements in a segment, in the current context.Optional
GIR2A segment identifying the various components in a relationship, typically data elements in a segment, in the current context.Optional
FTX2A segment carrying text notes to the preceding relationship.Optional
SG71SG7Optional
RFF2A segment identifying a reference document or a following constraint expression.Mandatory
FTX2A segment carrying the text of a constraint expression or providing implementation guide notes pertaining to the preceding constraint.Optional
SG81SG8Optional
ELU2A segment identifying the usage of a simple or composite data element in the current context. This segment starts a block of information about any one particular contextualised usage of a data element in a target data message. The data element usage determines whether this segment is defining a composite context, a simple element context or a component element context.Mandatory
ELM2A segment providing details of any variation or restriction of the current data element as used in this context. Typically this segment will convey details of restricted size or character representation.Optional
EDT2A segment providing details of any editing information such as maximum field length and status that would be used by a screen-based editor, forms input or data output process when physical representation of the data carried in a data message using this implementation guide is required.Optional
IMD2A segment providing further details of presentational information such as text alignment and style that might be used by a screen-based editor, forms input or data output process when physical representation of the data carried in a data message using this implementation guide is required.Optional
GEI2A segment providing further details of processing information such as data handling, positioning or control that might be used by a screen-based editor, forms input or data output process when data is carried, stored or collected by a data message using this implementation guide is required.Optional
FTX2A segment providing implementation guide notes, or other textual information relating to this element usage. The segment will also be used to carry the final set of information that would be used by a screen-based editor; forms input or data output process; a legend or user- recognisable description; and a help text.Optional
SG91SG9Optional
MEA2A segment to measure the number of instances of usage of a component in a message. The segment may specify minima, maxima, range or instance criteria.Mandatory
FTX2A segment providing implementation guide notes, or other textual information relating to this measurement.Optional
SG101SG10Optional
ELV2A segment identifying one or more components of an element value constraint series. It also may provide a default value for the current element context. This is expressed in a single text field so as to be used by or applicable to the broadest range of applications.Mandatory
FTX2A segment providing implementation guide notes, or other textual information related to the particular context. Such a context may include implementation guide notes for the default value.Optional
SG111SG11Optional
CDV2A segment identifying the code value, its source and usage preference.Mandatory
FTX2A segment providing implementation guide notes, or other textual information related to the particular context.Optional
SG121SG12Optional
DRD2A segment identifying an underlying data representation by tag, basic data type and size. This is the representation itself, and not a pointer to an external document.Mandatory
FTX2A segment providing implementation guide notes, or other relevant textual information.Optional
SG130SG13Optional
AUT1A segment specifying the details of any authentication (validation) procedure applied to the IMPDEF message.Mandatory
DTM1A segment specifying the date of authentication.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