APERAK Application error and acknowledgement
TBG3 Transport
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.
Header
- 00010Message headerMandatoryMax 1
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 14A 0051 UN
1. Data element S009/0057 is retained for upward compatibility. The use ofS016 and/or S017 is encouraged in preference.2. The combination of the values carried in data elements 0062 and S009 shallbe used to identify uniquely the message within its group (if used) or ifnot used, within its interchange, for the purpose of acknowledgement. - 00020Beginning of messageMandatoryMax 1
A segment to indicate the type and function of the message and to transmit the identifying number.
- 00030Date/time/periodConditionalMax 9
A segment to specify related date/time.
- 00040Free textConditionalMax 9
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.
- 00050Control totalConditionalMax 9
A segment to provide message control totals.
- Segment group 1Repeat 99
- 00070Document/message detailsMandatoryMax 1
A segment to provide the necessary identification information about the document being acknowledged.
- 00080Date/time/periodConditionalMax 99
A segment to provide the relevant dates concerning the document being acknowledged.
- 00070Document/message detailsMandatoryMax 1
- Segment group 2Repeat 9
- 00100ReferenceMandatoryMax 1
A segment to indicate the reference number of the document/message.
- 00110Date/time/periodConditionalMax 9
A segment to specify the date and time of the referenced document/message.
- 00100ReferenceMandatoryMax 1
- Segment group 3Repeat 9
- 00130Name and addressMandatoryMax 1
A segment to specify the identification of the message issuer and message receiver.
- 00140Contact informationConditionalMax 9
A segment to specify a person or department inside the party's organization, to which communication should be directed.
- 00150Communication contactConditionalMax 9
A segment to indicate communication channel type and number inside the party's organization, to which communication should be directed.
- 00130Name and addressMandatoryMax 1
- Segment group 4Repeat 99999
- 00170Application error informationMandatoryMax 1
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).
- 00180Free textConditionalMax 1
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.
- Segment group 5Repeat 9
- 00200ReferenceMandatoryMax 1
A segment to provide a reference relating to the acknowledgement type or the specified error (e.g. functional entity reference such as equipment level).
- 00210Free textConditionalMax 9
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).
- 00200ReferenceMandatoryMax 1
- 00170Application error informationMandatoryMax 1
- 00220Message trailerMandatoryMax 1
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.