The function of this message is: a) to inform a message issuer that his message has been received by the addressee's application and has been rejected due to errors encountered during its processing in the application. b) to acknowledge to a message issuer the receipt of his message by the addressee's application.
A service segment starting and uniquely identifying a message. The message type code for the Application error and acknowledgement message is APERAK. Note: Application error and acknowledgement messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 APERAK 0052 D 0054 20B 0051 UN
A segment to indicate the type and function of the message and to transmit the identifying number.
A segment to specify related date/time.
A segment to specify free form or processable supplementary information related to the whole message. In computer-to-computer exchanges free form text will normally require the receiver to process this segment manually.
A segment to provide message control totals.
A segment to provide the necessary identification information about the document being acknowledged.
A segment to provide the relevant dates concerning the document being acknowledged.
A segment to indicate the reference number of the document/message.
A segment to specify the date and time of the referenced document/message.
A segment to specify the identification of the message issuer and message receiver.
A segment to specify a person or department inside the party's organization, to which communication should be directed.
A segment to indicate communication channel type and number inside the party's organization, to which communication should be directed.
A segment identifying the type of application error or acknowledgement within the referenced message. In case of an error, the error code may specify the error in detail (e.g. a measurement relating to a piece of equipment is wrong) or as a rough indication (e.g. a measurement is wrong).
A segment to provide explanation and/or supplementary information related to the specified application error or acknowledgement. For example, the explanation may provide exact details relating to a generic error code.
A segment to provide a reference relating to the acknowledgement type or the specified error (e.g. functional entity reference such as equipment level).
A segment to provide additional details relating to the reference, e.g. the content of the wrong data (and its exact place in the message).
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.
