EDI CASRESLegal administration response in civil proceedings message

Transaction set

This specification provides the definition of the legal administration response in civil proceedings message (casres) 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.
Mandatory
AtMax 9
40
ERC
Application error information
To identify the type of application error within a message.
Opt
AtMax 9
50
LOC
Place/location identification
To identify a place or a location and/or related locations.
Opt
AtMax 9
60
RFF
Reference
To specify a reference.
Opt
AtMax 9
70
MOA
Monetary amount
To specify a monetary amount.
Opt
AtMax 99
80
FTX
Free text
To provide free form or coded text information.
Opt
AtMax 9
1LOOPOpt
AtMax 99
100
NAD
Name and address
To specify the name/address and their related function, either by co82 only and/or unstructured by co58 or structured by co80 thru 3207.
Mandatory
AtMax 1
110
SEQ
Sequence details
To provide specific details related to the delivery sequence.
Opt
AtMax 1
120
FTX
Free text
To provide free form or coded text information.
Opt
AtMax 9
2LOOPOpt
AtMax 99
140
DOC
Document/message details
To identify documents and details directly related to it.
Mandatory
AtMax 1
150
GIR
Related identification numbers
To specify a related set of identification numbers.
Opt
AtMax 99
160
PAT
Payment terms basis
To specify the payment terms basis.
Opt
AtMax 1
170
DTM
Date/time/period
To specify date, and/or time, or period.
Opt
AtMax 9
180
MOA
Monetary amount
To specify a monetary amount.
Opt
AtMax 99
190
FTX
Free text
To provide free form or coded text information.
Opt
AtMax 9
200
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