► Directory D11B
Messages Segments Data Elements
Leave a message

D11B

Message D11B/APERAK

Application error and acknowledgement message

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.

Message description

UNH

M(1) : Message header

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 11B 0051 UN

BGM

M(1) : Beginning of message

A segment to indicate the type and function of the message and to transmit the identifying number.

DTM

C(9) : Date/time/period

A segment to specify related date/time.

FTX

C(9) : Free text

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.

CNT

C(9) : Control total

A segment to provide message control totals.

SG1 C(99) : DOC-DTM

A segment group to provide information on the document being acknowledged.

DOC

M(1) : Document/message details

A segment to provide the necessary identification information about the document being acknowledged.

DTM

C(99) : Date/time/period

A segment to provide the relevant dates concerning the document being acknowledged.

SG2 C(9) : RFF-DTM

A group of segments to specify the document/message to which the current message relates, and related date and time.

RFF

M(1) : Reference

A segment to indicate the reference number of the document/message.

DTM

C(9) : Date/time/period

A segment to specify the date and time of the referenced document/message.

SG3 C(9) : NAD-CTA-COM

A group of segments to specify the identifications of message sender and message receiver with their contacts and communication channels.

NAD

M(1) : Name and address

A segment to specify the identification of the message issuer and message receiver.

CTA

C(9) : Contact information

A segment to specify a person or department inside the party's organization, to which communication should be directed.

COM

C(9) : Communication contact

A segment to indicate communication channel type and number inside the party's organization, to which communication should be directed.

SG4 C(99999) : ERC-FTX-SG5

A group of segments to identify the application error(s) within a specified received message and to give specific details related to the error type or to precise the type of acknowledgement.

ERC

M(1) : Application error information

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).

FTX

C(1) : Free text

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.

SG5 C(9) : RFF-FTX

A group of segments to specify the functional entity reference (e.g. goods item level, equipment level) relating to the specified error; further details can be added to identify the error more precisely.

RFF

M(1) : Reference

A segment to provide a reference relating to the acknowledgement type or the specified error (e.g. functional entity reference such as equipment level).

FTX

C(9) : Free text

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).

UNT

M(1) : Message trailer

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.

Message structure

UNH, Message header                           M        1
BGM, Beginning of message                     M        1
DTM, Date/time/period                         C        9
FTX, Free text                                C        9
CNT, Control total                            C        9

--- Segment Group 1 ------------------------- C       99 -------+
DOC, Document/message details                 M        1        |
DTM, Date/time/period                         C       99        |
---- -----------------------------------------------------------+

--- Segment Group 2 ------------------------- C        9 -------+
RFF, Reference                                M        1        |
DTM, Date/time/period                         C        9        |
---- -----------------------------------------------------------+

--- Segment Group 3 ------------------------- C        9 -------+
NAD, Name and address                         M        1        |
CTA, Contact information                      C        9        |
COM, Communication contact                    C        9        |
---- -----------------------------------------------------------+

--- Segment Group 4 ------------------------- C    99999 -------+
ERC, Application error information            M        1        |
FTX, Free text                                C        1        |
                                                                |
--- Segment Group 5 ------------------------- C        9 ------+|
RFF, Reference                                M        1       ||
FTX, Free text                                C        9       ||
---- ----------------------------------------------------------++
UNT, Message trailer                          M        1