EDI APERAKApplication error and acknowledgement message

Transaction set

This specification provides the definition of the application error and acknowledgement message (aperak) to be used in electronic data interchange (edi) between trading partners involved in administration, commerce and transport.

Segments

Position
Segment
Name
Max use
10
UNH
Message header
To end and check the completeness of an interchange
Mandatory
AtMax 1
20
BGM
Beginning of message
To indicate the type and function of a message and to transmit the identifying number.
Mandatory
AtMax 1
30
DTM
Date/time/period
To specify date, and/or time, or period.
Opt
AtMax 9
40
FTX
Free text
To provide free form or coded text information.
Opt
AtMax 9
50
CNT
Control total
To provide control total.
Opt
AtMax 9
1LOOPOpt
AtMax 99
70
DOC
Document/message details
To identify documents and details directly related to it.
Mandatory
AtMax 1
80
DTM
Date/time/period
To specify date, and/or time, or period.
Opt
AtMax 99
2LOOPOpt
AtMax 9
100
RFF
Reference
To specify a reference.
Mandatory
AtMax 1
110
DTM
Date/time/period
To specify date, and/or time, or period.
Opt
AtMax 9
3LOOPOpt
AtMax 9
130
NAD
Name and address
To specify the name/address and their related function, either by c082 only and/or unstructured by c058 or structured by c080 thru 3207.
Mandatory
AtMax 1
140
CTA
Contact information
To identify a person or a department to whom communication should be directed.
Opt
AtMax 9
150
COM
Communication contact
To identify a communication number of a department or a person to whom communication should be directed.
Opt
AtMax 9
4LOOPOpt
AtMax 99999
170
ERC
Application error information
To identify the type of application error within a message.
Mandatory
AtMax 1
180
FTX
Free text
To provide free form or coded text information.
Opt
AtMax 1
5LOOPOpt
AtMax 9
200
RFF
Reference
To specify a reference.
Mandatory
AtMax 1
210
FTX
Free text
To provide free form or coded text information.
Opt
AtMax 9
220
UNT
Message trailer
To end and check the completeness of a message.
Mandatory
AtMax 1

Elements

PositionElementNameRequirementTypeMin/MaxRepeat
10
Message reference numberMandatoryAlphanumeric1/1AtMax 1
20
Message identifierMandatoryAtMax 1
10
Message type identifierMandatoryAlphanumeric1/1Exact 1
20
Message type version numberMandatoryAlphanumeric1/3Exact 1
30
Message type release numberMandatoryAlphanumeric1/3Exact 1
40
Controlling agencyMandatoryAlphanumeric1/3Exact 1
50
Association assigned codeOptAlphanumeric1/6Exact 1
60
Code list directory version numberOptAlphanumeric1/6Exact 1
70
Message type sub-function identificationOptAlphanumeric1/6Exact 1
30
Common access referenceOptAlphanumeric1/35AtMax 1
40
Status of the transferOptAtMax 1
10
Sequence of transfersMandatoryNumber1/2Exact 1
20
First and last transferOptAlphabet1/1Exact 1
50
Message subset identificationOptAtMax 1
10
Message subset identificationMandatoryAlphanumeric1/14Exact 1
20
Message subset version numberOptAlphanumeric1/3Exact 1
30
Message subset release numberOptAlphanumeric1/3Exact 1
40
Controlling agencyOptAlphanumeric1/3Exact 1
60
Message implementation guideline identificationOptAtMax 1
10
Message implementation guideline identificationMandatoryAlphanumeric1/14Exact 1
20
Message implementation guideline release numberOptAlphanumeric1/3Exact 1
30
Message implementation guideline release numberOptAlphanumeric1/3Exact 1
40
Controlling agencyOptAlphanumeric1/3Exact 1
70
Scenario identificationOptAtMax 1
10
Scenario identificationMandatoryAlphanumeric1/14Exact 1
20
Scenario release numberOptAlphanumeric1/3Exact 1
30
Scenario release numberOptAlphanumeric1/3Exact 1
40
Controlling agencyOptAlphanumeric1/3Exact 1