Appendix 6. Codes

Appendix 6 Codes
1. Output Information Code System
Output Information Code is added to all Processing Result Messages and Output Messages.
For the list, refer to "Appendix Table 6.7 Subjected Procedure List" and "Appendix Table 6.8 Output
Information Code List."(1) Output Information Code System for Processing Result Messages
Appendix Table 6.1 shows output information code system for processing result messages.

Field nameIdentifier ofProcessing Result
Message
Air/Sea Identifier

DigitsAppendix Table 6.1 Output Information Code System for Processing Result Messages
Outline1 "*" is added for all Processing Result Messages.

1 System Identifier Code is shown.
A: AirS:

Procedure CodeSea

C: Common
5 Procedure Code which is the cue of the Processing Result
Message is shown.

e.g.) * AOLT: Notification of result of calling process for bonded transportation
declaration (general)( stands for one-byte space)* SNVC01:

Notification of result of house cargo information registration (registration,correction, deletion)* CCMSG: Process Result Notification with System Common Message (System
Common Error)( stands for one-byte space)

Appendix 6-1

(2) Output Information Code System for Output Messages
Appendix Table 6.2 shows output information code system for output messages.

Field name

DigitsAppendix Table 6.2 Output Information Code System for Output Messages
Outline

Air/Sea Identifier

1 System Identifier Code is shown.
A: Air
S: SeaC: Common

Classification ofprocessing by theCenter

1 Information code of source of generation of a message isassigned.
A: Processing result
B: statistic report
R: Processing result (only when the message is output
through re-output procedure).
1 Procedure classification
is assigned.
K: Trade Control or for other
A: Vessel
systems
Entrance/Clearance L: Common (including medical)
related
Q: System (mode)
B: After-hours related S: Import cargo
D: Import customs
T: Export cargo
clearance
X: Import clearance (for dual
E: Export customs
output)clearance
Y: Export Clearance (for dual
F: Receipt
output)
G: Food
H: Plant protection
J: Animal quarantine

Procedureclassification

Information code
No.
Information No.
Historicalinformatione.g.)

3 No. is assigned to output information.
1 Historical information of output information template is
assigned. "0" to "9"* At the commencement of 6th NACCS service, historicalinformation of 5th NACCS is kept on as is, and only
information where messages are changed in 6th NACCS ischanged (added).

SAD0CA0:

Import declaration input copy (C) information

AAF0010:

Payment slip information (direct payment)

Appendix 6-2

2. Processing Result Code System
Processing Result Code is added to Processing Result Messages [R], Output Messages (inquiry
result) [M] [R] and In-Storage Delivery Message [U].
XXXXX - XXXX - XXXX
Individual Number
Input Field ID
Error Code (Type + Serial Number)
Each Processing Result Code is 15 digits length, consisted with Error Code, Input Field ID and
Individual Number.
When process is correctly completed, the following Processing Result Code would be set;

00000-0000-0000(1) Error Code Type (Alphanumeric 1-digit letter)
Indicating Error Type. (See Appendix Table 6.3)
(2) Error Code / Serial Number (Alphanumeric 4-digit letters)
Indicating sequential number in Error Code Type.
(3) Input Field ID (Alphanumeric 4-digit letters)
Indicating Input Field ID, which has an error, in 4-digit format.
For screen template used in software package, "Input Field ID", which is unique information
name, is assigned to each input field. During errors, information stored in this screen template
will be linked to "Input Field ID", which displays the area of error specified by the Center in theprocessing result code, and "Input Field ID" will be highlighted.
When input field related to the error cannot be identified, "0000" would be set. (e.g.
Authentication error for the user)e.g.) 1. When input field related to the error is identified;

S0001-PCS-0000
2. When input field related to the error is NOT identified;

A0005-0000-0000(4) Individual Number (4-digit numbers)
When error occurs in input field of the individual fields of procedures where multiple individual
fields are input, such as "import declaration registration (IDA)", this indicates what number
from the top in individual field (what number from the top in above-mentioned "Input Field ID").
Depending on procedures, there are some cases where "Input Field ID" itself indicates what
number of individual fields is error. (See (Note))
For the procedure without the individual field, "0000" is set.

Appendix 6-3

(Note) For how to specify "Input Field ID" and "Individual Number" specified in fields where input
can be carried out repeatedly, there are the following 2 ways.
1. When, in the same Input Field ID, what number of individual field is error position isindicated with individual number.
e.g.) a. In case error has occurred in 1st repeat.

XXXXX-SHB-0001└─ 1st itemb. In case error has occurred in 1005th repeat.

XXXXX-SHB-1005└─ 1005th item
2. When error position is indicated with Input Field ID itself.
e.g.) a. In case error has occurred in 1st repeat.

XXXXX-S001-0000└─ 1st itemb. In case error has occurred in 150th repeat.

XXXXX-S150-0000└─150th item
(Note) This example shows that error item is indicated with 2nd to 4th digits.
However, error could be indicated for some fields with 3rd and 4th digits,
or only 4th digit.
! Expression in the Procedure Specifications
In the List of Input Fields described in the Procedure Specifications, fields
where "Repeat 1" column, "Repeat 2" column, or " * " is written are subject forabove-mentioned 2. In this case, this indicates what number of digits is "_"column (Input Field ID).
e.g.) IDA procedure: In the case of "B/L No./AWB No."For "B/L No./AWB No.", Field ID for the List of Input Fields is "BL_", so "_"portion becomes No. of repeat.
In the case of 1st repeated field of "B/L No./AWB No.", "BL1"
In the case of 2nd repeated field of "B/L No./AWB No.", "BL2"
When applied to processing result codes, it will become as follows.
S0046-BL1-0000(B/L No./AWB No. of repeated 1st field is not appropriate)S0046-BL2-0000(B/L No./AWB No. of repeated 2nd field is not appropriate)
Replacing "_" with number of repeat enables classification.
However, it depends on each Procedure Specifications and characters, etc. of
repeated fields, all is not necessarily applied to this example.

Appendix 6-4

Appendix Table 6.3 Error Code (Type)Classification

Error

Description

U

User Qualification Error Output when the error is related to user
qualification such as User Information,
terminal, or business type occurs.

S

Single Field Error

Output when the error related to attribute ofsingle field occurs.

R

Correlation Error

Output when the error related to correlation inseveral fields occurs.

E

Procedure Condition
Error(1) Output when a mismatch between input
data and registered data occurs.
(2) Output when message length is incorrect.

W

Warning Message

Output when the procedure processing iscompleted successfully but a warning isrequired.

M

Direction Message

In case this code is output, message
indicating complete correctly would be shownas Processing Result Code 1 and warning
message would be shown as Processing
Result Code 2.
At the same time as an error message, amessage instructing measures for later is
output.
In case this code is output, error message
would be shown as Processing Result Code 1
and direction message would be shown as
Processing Result Code 2.

L

Logical Error

Output when logical mismatch between data
in DB tables occurs.

A

System Message(Common Error)

K

Output when an error occurs before
procedure processing.
(See "Appendix Table 6.4")

ebMS Server Detection This will be output when error occurs at the
ErrorebMS server before processing is forwarded(Common Error)
to the core processing system.

(Reference) Details of processing result notification message (common error)
Appendix Table 6.4 shows details of processing result notification message (common error)
generated during checking phase of common process.
(Refer to "Appendix 5.1 (3) Format of processing result notification message output in case oferror")

Appendix 6-5

ErrorCode

Appendix Table 6.4 Details of processing result notification message (common error)
Input
Item
Content
Solution
Field ID

A0001

Procedure Code0000

The input procedure does notexist in the procedure codetable. Or no procedure program
exists.

Enter a correct procedure
code.

A0002

Procedure Code

0000

A0003

User code

0000

The procedure is in a forbidden
state.
The user code is incorrect.

Try again after theforbidden state is released.
Enter a correct user code.

A0004

Password

0000

The password is incorrect.

Enter a correct password.

A0005

User code

0000

The user code/Identifying
Number does not exist.

Enter a correct user
code/Identifying Number.

A0006

N/A

0000

A0007

N/A

0000

The service has not beenlaunched yet.
The processing in the center isabandoned.

Wait until the launch of theservice.
Report to NACCS center.

A0008

N/A

0000

Investigate causes.

A0009

N/A

0000

The length of the message isincorrect.
The telegram header (Input
Common Fields) has incorrectcharacter(s).

A0010

N/A

0000

It's out-of-service.

A0011

N/A

0000

The operation center is busy.

Wait until the launch of theservice.
Send the message later.

A0012

User code

0000

A0013

N/A

0000

A0014

N/A

0000

The user is unauthorized for this N/Aservice.
The user information and theReport to NACCS center.
telegram header (Input Common
Fields) information areinconsistent.
The user is restricted to use.
N/A

A0015
*1

N/A

0000

The service is restricted at thistime.

Try again at an unrestricted
time.

A0016

N/A

0000

Create a correct telegram
header (Input Common
Fields) and send themessage.

A0017

N/A

0000

The telegram header (Input
Common Fields) protocol isincorrect. Or the telegram
header (Input Common Fields)
has incorrect character(s). Or
only a space is inserted in"System Identifier" field in thetelegram header (Input Common
Fields).
The protocol header format
and/or the message format
is/are incorrect.

Appendix 6-6

Investigate causes.

Create and send amessage in a correct
protocol header format andin a correct message
format.

Error
Code

Item

Input
Field ID

Content

Solution

A0018

Terminal Access 0000
Keyor
Mail Addressor
Logical Terminal
Name• In interactive processing mode
(interactive or netNACCS), theaccess key is incorrect.

Enter a correct value.

A0019

Logical Terminal
Name

0000

The terminal name is incorrect.

Enter a correct terminal
name.

A0020

Attachment File
Acquisition Key

0000

Retrieving an attached file, thespecified attached file does notexist.

Enter a correct acquisition
key for the attached file.

A0021

Attachment File
Acquisition Key

0000

The user has no authority toretrieve the specified attached.

Enter a correct acquisition
key for the attached file.

A0022

N/A

0000

The content of the message in
XML format is incorrect.

Enter a correct message in
XML format.

A0023

N/A

0000

XML conversion service issuspended.

Send the message later.

A0024

N/A

0000

Relevant ministries' systems are
suspended.

Send the message later.

A0025

N/A

0000

Correct the combination ofprocedure code and system
identifier (1,2, or 4), andsend the message.

A0026
*2

N/A

0000

A0027
*2

N/A

0000

The combination of procedure
code and system identifier (1,2,or 4) in the telegram header(Input Common Fields) is
incorrect.
Error occurs and it preventsusers from keeping a logged instate.
・The user's authentication
certification does not exist.
Screen transition does not work
properly.

A0028
*2

N/A

0000

UVO (User Value Object) does
not exist in the session.

Retry to login.

A0029
*2

N/A

0000

User’s authentication certificate
has expired.

Retry to login.

Appendix 6-7

Retry to login.

Retry to login.

Error
Code

Item

Input
Field ID

Content

Solution

A0031*3

User Code for
the System (DIand SMTP
two-way)0000

The input user code for thesystem is incorrect.

Enter a correct user codefor the system.

A0032
*3

Password forUser Code for
the System (DIand SMTP
two-way)0000

The password for input user
code for the in-house system isincorrect.

Enter a correct password.

A0033

Attachment File
Name
(Extension)

0000

Files with extension whichcannot be used in NACCS are
attached.

Create an attachment file infile format with extension
shown in the EDI
Specifications once again,
and attach this.

Appendix 6-8

Error
Code

Item

Input
Field ID

Content

Solution
Check the limits describedin the ProcedureSpecifications for theprocedure, and review files
to be attached.
Delete or review attachment
file with 0 byte.

A0034

Attachment file
(Size (entire))

0000

Total size of entire attachment
file exceeds the upper limit sizeof file which can be attached in
the procedure.

A0035

Attachment file(Size
(individual))

0000

There is an attachment file withfile size of 0 byte.

A0036

Attachment file(Size
(individual))

0000

There is a file of which file size
exceeds the upper limit of theprocedure for one file which canbe attached.

A0037

Attachment File
Name

0000

Character code of theattachment file name isincorrect.

A0038
*2

Attachment File
Name

0000

Attachment file is not selected.

A0039
*2

Attachment File
Name

0000

A0040

Attachment File
Name

0000

Total numbers of attachment
files exceed the upper limit
numbers of files which can be
attached in the procedure.
The attachment file name length
exceeds 190 bytes

A0070

N/A

0000

Currently, output messages (forprinter) stored in the terminal isbeing retrieved.

Keep the attachment filename length within 190
bytes
Retrieve transaction output
messages after a brief
interval.

A0071

N/A

0000

Currently, there is no output
message (for printer) for theterminal.

Retrieve transaction output
messages after a brief
interval.

K0007

N/A

0000

ebMS server failed while
processing.

Report to NACCS center.

K0008

N/A

0000

The length of the message isincorrect.

Send a message with acorrect message length.

Appendix 6-9

Check the limits describedin the ProcedureSpecifications for theprocedure, and review files
to be attached.
(1) Encode attachment filename with "ISO-2022-JP(JIS code)".
(2) Change the file namespecified in processing
request message andchange the attachment filenames and carry out theprocedure once again.
Select the attachment files.

Check the numbers of
attachment files.

Error
Code

Item

Input
Field ID

Content

Solution

K0016

N/A

0000

System identifier is incorrect.

Specify correct system
identifier and send themessage.

K0022
*3

N/A

0000

Attachment file is incorrect.
Specify attachment files(size, number, extension, format) correctly.

*1 A0015 is used for 4th NACCS and is not used for 5th NACCS or later, so this should be treated as themissing number.
*2 This is output only if the mode is the WebNACCS processing mode.
*3 A0031, A0032, and K0022 are used for 5th NACCS and are not used for 6th NACCS, so they shouldbe treated as the missing number.

Appendix 6-10

3. User Codes and Identifying Numbers, etc.
(1) User codes used in NACCS
User codes used in NACCS are issued and managed by the NACCS Center.
(2) User Codes, Identifying Numbers, and User Passwords
User code system used in NACCS composed of total of 5 digits of "alphanumeric (2 digits)+
abbreviated company name (3 digits)".
In NACCS, in order to identify use utilization forms and categories of business, etc., Identifying
Numbers (3 digits) are assigned according to "System of User Codes and Identifying Numbers" and"System of Identifying Numbers", and user passwords are issued in User ID (8 digits) of "User Code
(5 digits) + Identifying Numbers (3 digits)".
In addition, passwords can be changed by user.
Also, if the password is forgotten and is reset, the user should change the password.
(Reference) Relationship between User Code, Identifying Numbers, and User Password
1A 
A01
Identifying No. (3 digits)
Abbreviated company
name (3 letters)

Alphanumeric (2-digit letters)

User code"User Password" isassigned in form ofUser ID (8 digits).

a. Alphanumeric (2-digit letters)
2 digits of Alphanumeric are assigned. (For assignment policy for the top 1 digit, refer to thenext page)b. Abbreviated company name (3 letters)
One abbreviated company name is assigned in 3 digits for one company (each legal entity).
* Only when alphabetical characters become shortage, numeric characters are assigned to 2nd
and 3rd digits.

Appendix 6-11

! Assignment of 1st digit from the top of 2 digits of alphanumeric characters

1st digit from the top should be assigned for each Customs having jurisdiction over branches andoffices of a company according to the following standards. In addition, for users who cannot
identify Customs, such as importer/exporter, etc., code of "Other" should be assigned.
* These standard for assignment of 1st digit from the top is aimed for management and operationof User Code, so systematic checking is not automatically carried out. Also, these are thestandards for operation, so it is not guaranteed that all users comply with the standards
described below.
Customs ofjurisdiction forlocation of
1st digit from the top
branches andofficesTokyo Customs
1→ T→A→J
Yokohama Customs

2→Y→B→L

Kobe Customs

3→K→C→P

Osaka Customs

4→S→D

Nagoya Customs

5→N→E→R

Moji Customs

6→M→F→U→X

Nagasaki Customs

7→G

Hakodate Customs

8→H→Z

Okinawa Regional
Customs

9→W

Others

Q→V(For user of Procedure for Trade Control,"V" is used in 1st digit from the top)
* For 1st digit from the top of User Code, "I" should be reserved value and be used when User
Code assigned to each Customs of jurisdiction become running out.

Appendix 6-12

Appendix Table 6.5 User Codes for Each User Type and Identifying Numbers

SMTP Two-Way User

Software Package User /WebNACCS User /GW (SMTP/POP3) User

User
Type

User Codes and Identifying Numbers

1A NAC 001(1) (2)(3)(1) Alphanumeric (2 digits)(2) Abbreviated company name (3 digits)
Alphanumeric (3 digits) (1 code for each company (legal entity))(3) Identifying Numbers(3 digits)○ netNACCS user, WebNACCS user →Only alphanumeric is used for 3rd digit.
○ EDIFACT user → 1st digit is fixed as "Z".
(For standards for assignment for each category of business, refer to "System of
Identifying Numbers")○ When using SMTP two-way (in-house system)(When software package is used in a office at the same time)
J9NAC
Y01
(1)
(2)
(1) User Code when a procedure is carried out using software package (5 digits)(2) Identifying Numbers (3 digits)[SMTP two-way] "Y" in 1st digit is fixed.
* When SMTP user server fails, the error message directed to the SMTP server can be retrievedby using above-mentioned User Code and Identifying Numbers when retrieving the error
message stored in the Error message queue relating to the User Code (QFL).

Appendix 6-13

Appendix Table 6.6 System of Issuing of Identifying Numbers (Reference)
Identifying Numbers

Utilization Form
Categories ofBusiness

Software package(Interactive)
GW(SMTP/POP3)
ebMS (Note 1)

AirlineCo-captainAir cargo agent
A01 - A99
Customs broker(For co-captain,(including"H" is used forregistered customs
1st digit)
specialists)
Aircraft’s Stores
Agent
Forwarder
Importer/Exporter
NVOCC
Forwarding agent
100 - 998
General-purpose
application user

Software package(netNACCS)
WebNACCSEDIFACT

SMTP two-way

General (except registered customs specialists)
A0A - A9Z
(3rd digit isalphanumeric)(For co-captain,"H" is used for 1st
digit)-

Y01 - Y10
(1st digit is "Y")Registered customs specialist

10A - 99Z
(3rd digit isalphanumeric)-Y26 - Y99
YA0 - YZ9
(1st digit is "Y")Customs
Warehouse
CY
Vanpool
General-purpose
application user

B01 - B99

B0A - B9Z
(3rd digit isalphanumeric)Z01 - Z25
(1st digit is "Z")Y11 - Y15
(1st digit is "Y")

Carriers
General-purpose
application user

C01 - C99

C0A - C9Z
(3rd digit isalphanumeric)Z26 - Z50
(1st digit is "Z")Y16 - Y20
(1st digit is "Y")Shipping agents
General-purpose
application user

D01 - D99

D0A - D9Z
(3rd digit isalphanumeric)Z51 - Z75
(1st digit is "Z")Y21 - Y25
(1st digit is "Y")Nonlife insurancecompany

E01 - E99

E0A - E9Z
(3rd digit isalphanumeric)-Y26 – Y99
YA0 – YZ9
(1st digit is "Y")General-purpose
application user
User of Procedure
for Trade Control
F0A - F9Z
Z76 to 99
Other categories of F01 - F99(3rd digit is(1st digit is "Z")businessalphanumeric)(Relevantministries'
procedure, etc.)(Note 1) Identifying Numbers issued to users of ebMS processing mode are only A01 to A99, 100 to 998, and
B01 to B99.

Appendix 6-14