Appendix 5. Details of Processing Result Messages

Appendix 5. Details of Processing Result Messages(1) NACCS EDI Messages
1) Formats of processing result notification message and output message (inquiry result)
To set a maximum of 5 processing result codes in the case of an error occurring in a single field, thelength shall be fixed at 75 bytes. If no processing result codes are to be set, one-byte spaces must
be provided instead.
Figure A5.1 shows formats of a processing result notification message and an output message(inquiry result):Output CommonFields(398 bytes)

Figure A5.1

CLRF

Processing
resultCode 1

Processing
resultCode 2

Processing
resultCode 3

Processing
resultCode 4

Processing
resultCode 5

Procedure
CL-byRF procedure RF(15 bytes)(15 bytes)(15 bytes)(15 bytes)(15 bytes)

Field

CL

Formats of Processing Result Notification Message and Output Message (Inquiry Result)(Note) Details of procedure-by-procedure fields are given in the Procedure Specification.

When viewed in text format in software of a text editor tool, etc., an output message Figure A5.1 willappear as follows:
XXXXXXXXXXX･･････････････････････XXXXXXXXXX<CRLF>

Output Common Fields (398 bytes)

XXXXX-XXXX-XXXX XXXXX-XXXX-XXXX XXXXX-XXXX-XXXX
Processing Result
Code 1(15 bytes)

Processing Result
Code 2(15 bytes)

Processing Result
Code 3(15 bytes)

XXXXXXXXXXX･･･････････････XXXXXXXXXXXXXXXXXXX-XXXX-XXXX XXXXX-XXXX-XXXX
Processing Result
Code 4(15 bytes)<CRLF>

Processing Result
Code 5(15 bytes)<CRLF>

Procedure-By-Procedure Field(Individual procedures are prescribed in the ProcedureSpecification.)In the case of a processing result message or an output message (inquiry result) generated, thefollowing is to be set in "Subject" of output common fields: processing result code + a one-byte space+ procedure-by-procedure data.
When viewed in text format in software of a text editor tool, etc., an output message in "Subject" will
be as follows (Only Subject portion is extracted)
XXXXX-XXXX-XXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXProcessing resultcode(15 bytes)

Procedure-by procedure data (Values are predefined in theSpecification on a procedure-by-procedure basis)(17 bytes - 64 bytes)

One-byte space(1 bytes)(Note)
If warning messages are not set for "Normal Termination," (for details, see Appendix 6.2 Procedure Result Coding System) the following code must
be set at the beginning: Procedure Result Code 1=00000-0000-0000.
If warning messages are set for "Normal Termination," the following code must be set at the beginning: Procedure Result Code 2=WXXXX-XXXXXXXX.

Appendix 5-1

2) Output message (excluding inquiry result) format
Figure A5.2 shows the format of an output message (excluding inquiry result):Output Common Fields(398 bytes)

CL

Procedure-ByProcedure Field

RFFigure A5.2

CL

Procedure-By-

CLProcedure Field
RF

Procedure-By-

CLProcedure Field
RF

RFFormat of Output Message (excluding inquiry result)(Note) Details of procedure-by-procedure fields are given in the Procedure Specification.

When viewed in text format in software of a text editor tool, etc., an output message Figure A5.2 willappear as follows:XXXXXXXXXXX･･･････････・・XXXXXX<CRLF>

Output Common Fields (398 bytes)

XXXXXXXXXXX･･･････････････XXXXXXXXXXX<CRLF>

Procedure-By-Procedure Field(Individual procedures are prescribed in theProcedure Specification.)XXXXXXXXXXX･･･････････････XXXXXXXXXXX<CRLF>

Procedure-By-Procedure Field

XXXXXXXXXXX･･･････････････XXXXXXXXXXX<CRLF>

Procedure-By-Procedure Field

In the case of an output message (excluding inquiry result), procedure-by-procedure data must be set
in "Subject" of common output fields.
When viewed in text format in software of a text editor tool, etc., an output message in "Subject" will
be as follows (Only Subject portion is extracted)

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Procedure-by procedure data
(Values are predefined in the Specification on a procedure-by-procedure basis)(1 byte - 64 bytes)

Appendix 5-2

3) Format of processing result notification message output in case of error
In the NACCS Center server, the following checking procedures are implemented. When an error
occurs in a checking step, a processing result notification message will be transmitted.
Figure A5.3 shows basic patterns of processing result notification messages:

NACCS Center server(3) Pro cessing result no tificatio nmessag e (erro rs among
rele van t fie lds)
Whene ver an err or o ccurs, arele van t processi ng resu lt code
must be se t and transmitted tothe termina ls.

Erro r p rese nt

Checki ng
single fields

Cross checking among relevant fields
No error present

Erro r p rese ntCross checking
among relevant
fieldsNo error present

Processe d Normally

Figure A5.3

Basic Output Patterns of Processing Result Notification Messages

Means of checking vary depending on the procedure.

Appendix 5-3

Core processing system

Computer

A maxi mum of 5 Pro cessing Resu lt
Codes mu st b e set a nd tran smitte d
to the terminals.

No error present

Procedure processing system(2) Pro cessing result no tificatio nmessag e (single field error)

Commo nprocessing

Checki ng
single fields

Whene ver an err or o ccurs, arele van t processi ng resu lt code
must be se t and transmitted tothe termina ls.

Erro r p rese nt

Cross checkin g a mo ng
rele van t fie lds(1) Pro cessing result no tificatio nmessag e (commo n e rror)

Commo nprocessing

Sen d p rocessing req uest
messag e

The following shows the format of error message output:
1. Processing result notification message (common error)
In the case of an error detected during common processing, one processing result code is set andoutput a processing result notification message.
When viewed in text format in software of a text editor tool, etc., a processing result notification
message will be appeared as follows:
XXXXXXXXXXX･･････････････････････XXXXXXXXXX<CRLF>

Output Common Fields (398 bytes)

XXXXX-XXXX-XXXX △△△△△△△△△△△△△△△△△△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△
Processing Result
Code 1(15 bytes)(15 bytes)(15 bytes)

Common error

XXXXXXXXXXXXXXXXXXXXXXXXXXX <CRLF>
Unique Data Field 1 (30 bytes)

XXXXXXXXXXXXXXXXXXXX <CRLF>
Unique Data Field 2 (20 bytes)

XXXXXXXXXXXXXXXXXXXX <CRLF>
Unique Data Field 3 (20 bytes)(Note) Provide a space in Unique Data Field 1 to 3.

Appendix 5-4(15 bytes)△△△△△△△△△△△△△△△(15 bytes)<CRLF>

2. Processing result notification message (single field error)
In the case of an error detected during single field verification, a maximum of 5 processing result
codes must be set to output a processing result notification message.
When viewed in text format in software of a text editor tool, etc., a processing result notification
message will be appeared as follows:
XXXXXXXXXXX･･････････････････････XXXXXXXXXX<CRLF>

Output Common Fields (398 bytes)

XXXXX-XXXX-XXXX XXXXX-XXXX-XXXX XXXXX-XXXX-XXXX
Processing Result
Code 1(15 bytes)

Processing Result
Code 2(15 bytes)

Processing Result
Code 3(15 bytes)

XXXXX-XXXX-XXXX XXXXX-XXXX-XXXX
Processing Result
Code 4(15 bytes)<CRLF>

Processing Result
Code 5(15 bytes)

Single field error (to be output up to 5 errors)(Note) Values for individual procedure fields are omitted and predefined in the Specification on a procedure-by-procedure basis.

In "Subject" of common output fields, the following values are to be set:
processing result code + a one-byte space + procedure-by-procedure data.
When viewed in text format in software of a text editor tool, etc., an output message in "Subject"
will be as follows (Only Subject portion is extracted)
XXXXX-XXXX-XXXX X XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Processing resultcode(15 bytes)

Procedure-by procedure data (Values are predefined in theSpecification on a procedure-by-procedure basis)(17 bytes - 64 bytes)

One-byte space(1 byte)(Note) The forefront processing result code (Processing Result Code 1=XXXXX-XXXX-XXXX) is set.

Appendix 5-5

3. Processing result notification message (errors among relevant fields)
One or more processing result codes must be set in the case of an error detected during checkingof relationship among fields to output processing result notification message.
When viewed in text format in software of a text editor tool, etc., a processing result notification
message will be appeared as follows:
XXXXXXXXXXX･････････････････････････XXXXXXXXXX<CRLF>

Output Common Fields (398 bytes)

XXXXX-XXXX-XXXX △△△△△△△△△△△△△△△△△△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△
Processing Result
Code 1(15 bytes)(15 bytes)(15 bytes)△△△△△△△△△△△△△△△(15 bytes)(15 bytes)

Errors among relevant fields(Note) Values for individual procedure fields are omitted and predefined in the Specification on a procedure-by-procedure basis.

In "Subject" of output common fields, the following values are to be set:
processing result code + a one-byte space + procedure-by-procedure data.
When viewed in text format in software of a text editor tool, etc., an output message in "Subject"
will be as follows (Only Subject portion is extracted)
XXXXX-XXXX-XXXX X XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Processing resultcode(15 bytes)

Procedure-by procedure data (Values are predefined in theSpecification on a procedure-by-procedure basis)(17 bytes - 64 bytes)

One-byte space(1 byte)Appendix 5-6<CRLF>

(2) EDIFACT message
In the case of an error detected during common processing, one processing result code is set in"APERAK" of the EDIFACT message and send it as a processing result notification message.
If single field errors or errors among relevant fields occur, a maximum of 5 processing result codes
must be set in "CUSRES" of the EDIFACT message of procedure subjected for EDIFACT, and send
it as a processing result notification message.
(3) XML message
In the case of an error detected during common processing, one processing result code is set andsend it as a processing result notification message. For specified contents, refer to "Appendix 15
Processing Result Notification (Common Error) Mapping Table (XML)."If single field errors or errors among relevant fields occur, a maximum of 5 processing result codes
must be set and send it as a processing result notification message. For specified contents, refer to"Processing Result Notification (Common Error) Mapping Table (XML)" for procedures subjected forXML.
(4)

Procedures which treated as continued processing

For subjected procedure list (including management document information) when procedures aretreated as continued processing, refer to "Appendix Table 6.7 Subjected Procedure List."

Appendix 5-7