Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
1 Change of
specification(abolishment of aprocessing mode)

Sub-item

Changes from Fifth NACCS

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Correction on EDI Specification

Relevant location in EDI Specification

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

Table of contents of the EDI specification

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

Remarks(Deletion)- Delete the description of the direct interface.

2

3

Change ofdescription

Name ofprocessing
mode

Explicit provision of the description
content- (None)Change the name of the processing mode as follows:

Table of contents of the EDI specification--

Provide the content of the major descriptions of the EDI Table of contents of the EDI specification
specification (main body and appendixes) andprocedure specifications in an organized way.
Provide the user with the descriptions of the contents ofdifferent documents so that the user can easily find the
document to look at.

-

-

-

Add definitions of other terms
if any.

(Before change)
Interactive processing modeWebNACCS (using a
Web browser)(After change)
WebNACCS processing mode
* Add "(Use a Web browser)" to the description to alignthe description with other descriptions.

- (None)* EDI specification
Main body: Describe the EDI specification of NACCS.
Appendixes: Describe the following about the EDI
specification of NACCS:- List of information about the EDI specification of
NACCS- Examples of the EDI specification of NACCS- Correspondence between the EDI specification of
NACCS and procedures* Procedure specifications
Describe specifications specific to procedures.

4

Change ofdescription

Definition of - (None)
terms(related
government
systems, andothers)

Add the following definitions of terms:

Table of contents of the EDI specification(After addition)
Related government systems: Trade control subsystemand crew landing permission support system
Related government procedures: Animal quarantine
procedure, plant quarantine procedure, imported foodsupervision support procedure, port-related procedures
Customs clearance government procedures: Animal
quarantine procedure, plant quarantine procedure,
imported food supervision support procedure

1 /61

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
5 Change ofdescription

6

Sub-item

Changes from Fifth NACCS

Change of- (None)specification(change ofrecommend
OS)

Package software Abolishmentof the e-mailstyle
processing
mode

Correction on EDI Specification

Relevant location in EDI Specification

Correct the trademarks as follows to align them with the Table of contents of the EDI specification
changes in the description of recommend OS and the
EDI specification.
(Before change)
Microsoft, Windows, Windows NT, Windows2000,
Windows ME, Windows98, Windows XP, Windows Vista,
Windows7(After change)
Microsoft, Windows, Windows 7 Professional (Service
Pack 1), Windows 8.1 Pro

Abolish basically the package software of the e-mail style processing mode for 1.1 Data processing mode
Abolish basically the package
computers. So change the description in the example of directly
software of the e-mail style processing personal
1.2 Connection configuration between user andconnecting to NACCS using the package software of e-mail style processing
mode for personal computers.
NACCS
mode for personal computers.
However, deliver the package
1.3 Relationships between connection modes andMain descriptions to be deleted are as follows:
software to the users under thedata transmission/receipt modes* Delete only descriptions related to the package software of e-mail style
gateway as it is with the fifth NACCS. processing mode for personal computers.
1.4 Example of using NACCS information andexample of message overtaking(Deletion)

Envisaged Impact on Users in Migration
Remarks
to Sixth NACCS (Assumption)
The operating systems recommend by The trademark descriptions
the NACCS center will be changed, so represent the run-timethat the users who are using otherenvironment of the terminal
operating systems must consider
package software.
replacing them.

Users who are using the package
software of the e-mail style processing
mode must use another package
software.

-- Figure 1-2-1 Comprehensive Connection Configuration Between User and
NACCS- Table 1-3-1 Relationship Between Connection Modes and Data
Transmission/Receipt Modes- 1.2.1.1 Peer-to-peer connection- 1.2.1.2 Router connection(Change)- Figure 1-1-1 Interactive Processing Mode and E-mail Style Processing Mode
* Add a supplemental explanation.
- Figure 1-1-2 Outline of Data processing mode on NACCS System* Change it to under the gateway.
- Figure 1-4-1 Example of using the file internal information and example ofmessage overtaking* Change them to other processing modes.

7

Change ofdescription
location

Types andfunctions of
packagesoftware- (None)Consolidate the description on the package software for 1.1 Data processing mode
personal computers in Chapter 7 of the EDI
specification of fifth NACCS into the Commercial
Package Software Operation Manual.
Also correct descriptions that refer to that chapter.

Users that have been referring to thedescription of the package software for
personal computers in Chapter 7 for thefifth NACCS must refer to Commercial
Package Software Operation Manual.

(Deletion)
Chapter 7 Package Software, EDI Specification

8

Change ofdescription

Name ofprocessingmode- (None)Change the name of the processing mode as follows:(Before change)
Interactive processing modeWebNACCS (using a
Web browser)(After change)
WebNACCS processing mode
* Add "(Use a Web browser)" to the description to alignthe description with other descriptions.

2 /61

1.1 Data processing mode
1.2 Connection configuration between user and
NACCS
1.3 Relationships between connection modes anddata transmission/receipt modes--

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
9 Change of
specification(abolishment of aprocessing mode)

Sub-item

Changes from Fifth NACCS

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Correction on EDI Specification

Relevant location in EDI Specification

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.
Main descriptions to be deleted are as follows:* Delete only descriptions related to the direct interface.
(Deletion)- Figure 1-1-2 Outline of Data processing mode on
NACCS System- Figure 1-2-1 Comprehensive Connection Configuration
Between User and NACCS- Table 1-3-1 Relationship Between Connection Modes
and Data Transmission/Receipt Modes

10

Specification
change(abolishment of
message
reception
software)Message
reception
software oftheWebNACCS
processing
mode

11

Network

12

Change ofdescription

Reconsiderat Abolish the dial-up line access.
ion of accesslines(abolishmentof dial-up
lines)
Unification of - (None)
terms

1.1 Data processing mode
1.2 Connection configuration between user and
NACCS
1.3 Relationships between connection modes anddata transmission/receipt modes

Stop providing the message reception Delete the description of the message reception
1.1 Data processing mode
software that has been provided in the software that has been provided for receiving forms in
fifth NACCS for receiving forms in
the WebNACCS processing mode because the
WebNACCS processing mode.
provision of the software will be stopped.
In the sixth NACCS, forms will bereceived via Web browsers.
(Deletion)"Message reception software" is a software package for
personal computers provided by the NACCS center. For
functional details on the message reception software,see "11. WebNACCS Client."
Process result message (for printer) is a message typeof NACCS.
For NACCS message types, see "3.4 Message Types."

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

Users that have been retrieving form
messages using the message reception
software of the WebNACCS processing
mode will have to retrieve forms using a
web browser.

About access line types, delete the description of theaccess by dial-up line.

1.2 Connection configuration between user and
NACCS
1.3 Relationships between connection modes anddata transmission/receipt modes

Users who are using the access line
type under reconsideration must use
another access line.

-

Unify terms as below.

1.2 User connection modes
1.3 Relationship between connection modes anddata exchange processing modes
1.4 Example of using NACCS information andexample of message overtaking--(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server

3 /61Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
13 Network

Sub-item

Changes from Fifth NACCS

Encryption
method- (None)(Reflect the specification of the fifth
NACCS.)
Change the encryption method usedin ebMS processing mode.
(Change from SSL3.0 to TLS1.0.)

Correction on EDI Specification

Relevant location in EDI Specification

Change the encryption method used in the ebMS
1.2 User connection modes
processing from SSL3.0 to TLS1.0 for the support of thefifth NACCS.
Change the description of the encryption method as
follows:

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Before change)
SSL(After change)
TLS
14

Change ofdescriptionFile- (None)Old systems (the fourth and earlier versions of NACCS) 1.4 Example of using NACCS information andused files, but the fifth and later versions use DB, andexample of message overtaking
therefore, some descriptions need to be corrected.

--(Before change)
File internal information(After change)
Information

15

Change ofspecification(abolishment of aprocessing mode)

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

2.1 Network overview
2.2 Private IP address
2.3 Overview of NACCS router

Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

About access line types, delete the description of theaccess by dial-up line.

2.1 Outline of Network
2.2 Private IP address
2.3 Outline of NACCS router

Users who are using the access line
type under reconsideration must use
another access line.

-

Unify terms as below.

2.1 Outline of Network
2.2 Private IP address
2.3 Outline of NACCS router--

Main descriptions to be deleted are as follows:* Delete only descriptions related to the direct interface.
(Deletion)- Figure 2-1-1 Outline of User Network- Figure 2-2-15 Liability Coverage for Possible Failures- Description on the router connected to NACCS (fordirect interface)

16

Network

17

Change ofdescription

Reconsiderat Abolish the dial-up line access.
ion of accesslines(abolishmentof dial-up
lines)
Unification of - (None)
terms(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server

4 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-item
Changes from Fifth NACCS
Correction on EDI SpecificationNo.
Add a description that the user system can convert IP addresses based on
18 Security measures Reconsiderat Reconsider the possibility of IP
ion of theaddress conversion (NAT conversion). one-to-one static conversion.
possibility of(Addition)
Allow the user network to convert IP addresses assigned by the NACCS
IP address
center to other IP addresses and then to assign them to user computers,
conversion

Relevant location in EDI Specification
2.2 Private IP addressprovided that any converted address uniquely corresponds to a private IP
addresses assigned by the NACCS center. When a user uses a converted IP
address, the user must be able to promptly indicate the correspondence
between the address assigned by the NACCS center and the converted IP
address upon the request of the NACCS center.
For example, if the user uses the NAT function of a communication device of
the user for IP address conversion, the user must configure the device tomake static conversion (in which each IP address is always converted to thesame IP address) and must be able to indicate the setting details to the
NACCS center.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Allow the user system to covert IP
addresses provided that one-to-one
static conversion is used.
This allows the user to make IP address
setting and network configuration thatwere not allowed because of theprohibition of IP address conversion.

Delete a description that refers to the description of prohibiting IP address
conversion.
(Deletion)
See “2.2.8 Prohibition on IP Address Translation” and “(2) IP Address
Translation on Gateway Computer” for setting up a gateway computer.

19

Change ofdescription

Add the- (None)description of
the NACCS
information
provided for
WebNACCS
users.

Mention WebNACCS users to "Table 2-2-3 Types of
NACCS NACCS information and User Authentication
Methods."

2.2 Private IP address

-

-

20

Change ofdescription

Reconsiderat - (None)ion of the IP
addressarchitecture

Different IP address schemes were used for users of
Air-NACCS, users of Sea-NACCS, and users of SeaNACCS and Air-NACCS, but now the same addresses
are used for them. So delete the related descriptions.

2.2 Private IP address--

Change half-width katakanas to full-width katakanas as 2.2 Private IP address
shown below.

--

Make the following changes:(Change)- Table 2-2-1 IP address architecture
21

Change ofdescription

Reconsiderat - (None)ion of the useof half-width
katakanas(Example)(Before change)
Protocol header(After change)
Protocol header* Do not make this change for descriptions in tables andfigures in which half-width characters make thedescription easy to read.

5 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
22 Change ofdescription

23

24

25

26

Change ofdescription

Change ofdescription

Change ofdescription

Change ofdescription
location

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

2.2 Private IP address

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

2.3 Outline of the router connected to NACCS-

2.4 Access from user computers to NACCS

If the access method to NACCS ischanged so that DNS is used instead of
specifying the IP address, the user canuse NACCS without changing the IP
address configured in the in-housesystem at the time of NACCS switchover(main center <-> backup center).

3.1 NACCS EDI messages

The maximum size of a NACCS EDI
message is 700,000 bytes, and the
maximum size of attachment files is
10,000,000. So the maximum size of amessage with attachment files is
10,700,000. So change the description
accordingly.

3.1 NACCS EDI messages

Users that have been referring to thedescription of the retrieval of statistic
report information in Appendix 11 for thefifth NACCS must refer to Chapter 6.

Relevant location in EDI Specification

Changenames sothat they
becomesuitable for
EDI.

- (None)Because NACCS EDI specification includes thedescription of the procedures of related government
systems, change the procedure names as follows:

Change ofthedescription
on theNACCS
router- (None)Change of
NACCS
connection
methodWhen users access a server, they do
not directly specify the IP address.
Instead, they retrieves an IP address
corresponding to the domain namefrom the DNS server, and then makeaccess to that IP address.

Add the following new description about access to
NACCS from a user computer:Maximum
size of amessagewithattachment
files- (None)

The maximum size of a message with attachment files
is described as 10,000,000 bytes, but it actually is
10,700,000 bytes. So change the description.

(Before change)
Customs clearance(After change)
Procedures related to trade and ports

Change the specification of the router connected to
NACCS.

-(Before change)
WAN/ETH port: WAN-side Ethernet port. This port is notmade available for users.
(After change)
WAN/ETH port: This becomes the center serverinterface when the line speed is 1 Mbps or faster.

Change of a - (None)
document
locationbeing
referred to(change of a
description
location of
the statistic
reportinformation)(Addition)- The user obtains IP addresses for the access to
NACCS servers.
- In the event of switchover from the main center to the
backup center, the user does not have to be aware of
the switchover.

(Before change)
With attachment files: 10,000,000 bytes(After change)
With attachment files: 10,700,000 bytes

Change a document location being referred to as
follows due to the change of the structure of the EDI
specification. (The description on the statistic report
information described in Appendix 11 for the fifth
NACCS was moved to Chapter 6.).
(Before change)
Appendix 11 Retrieval of Statistic Report Information(After change)
6. Retrieval of Statistic Report Information

6 /61

-

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
27 Change of
specification(change ofmessage length)

Sub-item

Changes from Fifth NACCS

NACCS EDI Change the maximum message
messagelength of a NACCS EDI message.
length(Change from 500 KB to 700 KB)

Correction on EDI Specification

Relevant location in EDI Specification

Change the maximum length of a NACCS EDI message 3.1 NACCS EDI messages
from 500 KB to 700 KB.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
For a process result message that had to be segmented to multiple messages
due to the 500 KB restriction of the fifth
NACCS, the messages can be received
in decreasing times because themaximum length becomes 700 KB in
the sixth NACCS.
Any in-house system specification must
be checked whether it does not have
500 KB restriction.

28

Change ofConsolidation Consolidation of the port subsystem
specificationof a(consolidation of a subsystem
subsystem)(port
subsystem)

Change the description related the port subsystembecause it will be consolidated with NACCS..

3.1 NACCS EDI messages--

3.1 NACCS EDI messages
3.4 Message Types--

3.1 NACCS EDI messages--(Before change)
Table 3-1-1 Length of messages exchanged withgovernment systems(After change)- (Delete: Because it is consolidated with NACCS)(Before change)* It required one or two days to update data in the portsystem when a password was changed by theprocedure of user information registration (URY), but it
will be done on the same day.
(After change)- (Delete: Because it will be consolidated with NACCS,
and the description will be changed)

29

30

Deletion ofReports of- (None)procedure-specific special
information
patterns ofstatistic
reportinformation
output format

Delete descriptions of procedure-specific information
except when necessary for explanation.
Also, add a reference as below.

Change ofdescription

Correct the text as follows:

Other
government
agencies- (None)(Before change)
Note that most of the management documents,
excluding some documents such as lump-sum payment
statements, are created in CSV format.
(After change)
For the output format, see "Table 6-9-2 List ofCommercial Statistic Reports."
For the messaging method of statistic reports, see "6.
Retrieval of Management Document Information."(Before change)
Other government agencies(After change)
Related government agencies

7 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
31 Change ofdescription

32

Change ofdescription

Sub-item
Systemidentifier

Changes from Fifth NACCS
Consolidation of the port subsystem

Air- (None)
NACCS/SeaNACCS

Correction on EDI Specification

Relevant location in EDI Specification

A description is added in the EDI specification that any 3.1 NACCS EDI messages
user of an in-house system (excluding EDIFACT users)
must set the system identifiers corresponding toindividual procedures with reference to "Table 6-7 List of
Target Procedures", which lists system identifier forindividual procedures for the sixth NACCS.

Although words "Air-NACCS" and "Sea-NACCS" were 3.1 NACCS EDI messages
deleted when the sea system and the air system were
3.2 MIME format messages
consolidated in the fifth NACCS, there are some that still
remain. So change those descriptions.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Any user who builds an in-house system (excluding EDIFACT users) must refer
to "Table 6-7 List of Target Procedures"
when they set system identifiers.

--

Make the following changes:(Change)- Item 13 of "Table 3-1-2 Input Common Fields"
Change the words "Air" and "Sea" to Japanese words
for explanation (in the Japanese version of the
document).
(Deletion)- Starting phrases "Sea-NACCS" and "For Sea-NACCS"* Because the use of EDIFACT messages is not
restricted to the sea system
33

Change ofspecification(abolishment of aprocessing mode)

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

3.1 NACCS EDI messages
3.3 XML format messages
3.7 File exchange block and retrieval procedure

Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

3.1 NACCS EDI messages-

Main descriptions to be deleted are as follows:* Delete only descriptions related to the direct interface.
(Deletion)- Item 1 "Processing control code" of "Table 3-1-2 Input
Common Fields"- List of transmission/reception messages (interactive
processing mode) in "Table 3-3-1 XML Format
Messages"- Three areas in "Table 3-7-1 Report Message Table"- Description on the retrieval of the report message tableusing the direct interface

34

Change ofdescription

Systemidentifier- (None)Correct the description of "Item 13 System identifier" of"Table 3-1-2 Input Common Fields" as follows:(Before change)
Set a value for identifying a message destination whencommunicating with other relevant ministries’
systems.For NACCS process, set either sea or air.
(After change)
Set the identifies of procedures and systems to be used.
For NACCS procedures: Set either "air" or "sea."
For related government procedures: Set the identifier ofthe message destination.

8 /61

-

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
35 Change ofdescription

Sub-itemWordprocessor
software

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

Correct the description of the application software usedfor viewing NACCS EDI messages so that thedescription better represents the reality.

3.1 NACCS EDI messages

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Before change)
In word processing software or text editor tool, a text
format NACCS EDI message (processing request
message)(After change)
In text editor tool, a text format NACCS EDI message(processing request message)

36

Change ofdescription-- (None)

Improve the description as follows:
3.1 NACCS EDI messages* In a description in Section 3.1, phrase "message type"
is used. But message types are explained Section 3.4,
which is before the description. So add a reference tothe latter section.

-

-

-

-

(Before change)
Message type [R] is ...
(After change)
Message type [R] is ...
For message types, see "3.4 Message types."

37

Change ofdescription

Entering data - (None)
Add the description as follows for the case of the
3.1 NACCS EDI messages
in procedure- (Reflecting the specification of the fifth character attribute being sn.
specific fields NACCS)* Add a description of the difference of an and sn in the* Reflect the addition of the sn
explanation of an.
attribute added in the fifth NACCS.
(Addition)
Description sn
Attribute Single-byte alphanumeric or symbol(including lowercase letters)
Input rule Left aligned
Input condition The character string can be shorter
than the specified length, but the string must be paddedby spaces (single-byte) in that case.

9 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-itemNo.
38 Package software Abolishmentof the e-mailstyle
processing
mode

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Abolish basically the package
The package software of the e-mail style processing
3.1 NACCS EDI messages
software of the e-mail style processing mode for personal computers will not basically be
3.2 MIME format messages
mode for personal computers.
distributed to users anymore. So change the description 3.3 XML format messages
However, deliver the packagein the example of directly connecting to NACCS using
software to the users under thethe package software of e-mail style processing mode
gateway as it is with the fifth NACCS. for personal computers.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who are using the package
software of the e-mail style processing
mode must use another package
software.

Main descriptions to be deleted are as follows:* Delete only descriptions on the personal computer
package software for e-mail style processing mode.
(Deletion)- Table 3-1-5 Output Common Fields- Table 3-3-2 List of Transmitted/Received Messages of
XML Format (Mail Processing Mode)

39

Change ofspecification(abolishment of aprocessing mode)

Interactive
With abolishment of the interactive
processing
processing mode (direct interface)?
mode (direct A2, ? A3 messages are abolished.
interface)

With the abolishment of the direct interface, the output
common fields (RTP tag) used for ?A2 and ?A3
messages will not be used anymore. So mark theseareas as reserved areas.

3.1 NACCS EDI messages

Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

3.1 NACCS EDI messages--

3.2 MIME format messages

Any user (Airline) who uses the PNR01
procedure must send messages in the
PADIS EDIFACT format.

-(Before change)
Item No.10
Field name RTP tag(After change)
Item No.10
Field name Reserved area

40

Change ofdescription

Correction of - (None)a past date inexamplesThe date of the fifth NACCS update is currently used inexamples. Change it to the date of the sixth NACCS
update.
Example:(Before change)
20051010(After change)
20181010

41

Change of current
descriptions(reflecting thechange of the
EDIFACT format)

Addition of
the PADISEDIFACT
format- (None)
Add the following explanation on the PADIS EDIFACT(Reflecting the specification of the fifth format, which started to be used in the fifth NACCS.
NACCS)The PADIS EDIFACT format are used (Locations of addition)
for NACCS, so add the relevant EDI - Messages used
specification.
- Syntax rule
- Message version- Unit of message transmission- Message format

10 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
42 Change ofdescription
location

43

Change ofdescription

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Change of- (None)the locationof thedescription of
the EDIFACT
specification(Appendix E)

Change a description in Appendix E as follows:- Description of the NACCS EDI specification related to
EDIFACT: Move it to Section 3.2.
- Procedure-specific descriptions related to EDIFACT:
Move it to procedure specifications.

Addition of a - (None)
comment(Among the description moved from Appendix E to
Section 3.2)
Add a supplemental explanation to the description of
PAXLST as follows because there are no commercial
use procedures.

3.2 MIME format messages

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users that have been referring to thedescription of EDIFACT in Appendix E
for the fifth NACCS must refer to
Chapter 3.2 and procedure
specifications.

(Before change)
Appendix E Information Related to EDIFACT(After change)
NACCS EDI specification: to Section 3.2
Procedure-specific information: to procedure
specifications

3.2 MIME format messages--

3.2 MIME format messages--

3.2 MIME format messages
3.6 Code system

The server that has the EDIFACT
function is changed in the sixth NACCS,
but the function itself is not changed. So
the change does not affect the users.
Let the in-house system users(EDIFACT users) know that the name ofthe server has changed in the EDI
specification of the sixth NACCS.

(Addition)(PAXLST cannot be sent from a communication line
other than those provided by an aeronauticalcommunication company.)

44

Change ofdescriptionVia- (None)aeronauticalcommunicati
on(In the descriptions moved from Appendix E to Section
3.2)
Change a phase as follows because it is not concreteenough.
(Before change)
Via aeronautical communication(After change)
Via a communication line provided by an aeronauticalcommunication company

45

Change ofspecification(server
consolidation)

ServerAbolish the EDIFACT server andconsolidation divide its function into the mail server
and the XML conversion server.

Correct the text as follows:(Before change)
EDIFACT server(After change)
Mail server* "EDIFACT conversion processing" depending on thelocation in the document

11 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
46 Change ofdescription

47

Change ofdescription
location

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Reconsiderat - (None)ion of the useof half-width
katakanas

Change half-width katakanas to full-width katakanas as 3.2 MIME format messages
shown below.

Multimessage of
EDIFACTmessagepacketThere are duplicated description in the NACCS EDI specification 3.2 MIME format messagesof the fifth NACCS. So move and consolidate these descriptions
to one place in the document.

- (None)Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Example)(Before change)
Protocol header(After change)
Protocol header* Do not make this change for descriptions in tables andfigures in which half-width characters make thedescription easy to read.
-

-

-

-

A new procedure is added for related
government agencies, in which fileattachment is possible.
The user will be able to send
attachment files to related government
agencies by NACCS procedures.

-(Locations of the duplicated descriptions for the fifth NACCS)"(old) Appendix E" and "(old) 3.2.1.2.3.2 Multi-message
processing mode "(New location of the description)"3.2.1.2.2.2 Transmission units of single message and multimessage"(Description content)
In Sea-NACCS, multiple EDIFACT messages can be sent in one
EDIFACT message packet (multi-message packet). When using
multi-message packets, the maximum number of EDIFACT
messages in one EDIFACT message packet is 99 due to therestriction of the performance of the NACCS center server.

48

Change ofdescription
location

Multi B/L
messagepacket of
EDIFACTmessagepacket- (None)There are duplicated description in the NACCS EDI specification 3.2 MIME format messagesof the fifth NACCS. So move and consolidate these descriptions
to one place in the document.
(Locations of the duplicated descriptions for the fifth NACCS)"(old) Appendix E" and "(old) 3.2.1.2.3.3 Multi B/L message
processing mode "(New location of the description)"3.2.1.2.2.3 Transmission units of single B/L message and multi
M/L message"(Description content)
In Sea-NACCS, a CUSCAR message can hold multiple B/L data
blocks and multiple container data blocks (multi B/L message
packet) for the cargo manifest registration procedure (MFR) andcargo manifest correction procedure (before cargo manifest
submission) (CMF01). However, use only single-message
packets for the transmission of multi BL message packet due tothe restriction of the performance of the NACCS center server.

49

Attachment file

Method of file Provide a method of file attachment
attachment for related government agencies.
for related
government
agencies

In order to provide a method of file attachment for
related government agencies, describe an outline in anexisting figure (the sequence of file attachment) in the
EDI specification.

12 /61

3.2 MIME format messages

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-itemNo.
50 Deletion of
Description
procedure-specific of
information
proceduresthat support
fileattachment

51

Change ofspecification(change of the
maximum size ofattachment files)

Check of thesize ofattachment
files

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

Delete the description of the possibility of file attachment 3.2 MIME format messages
from the NACCS EDI specification because thepossibility depends on the specifications of individual
procedures.
(Deletion)
Procedures that support file attachment are theattachment file registration procedure, generaldeclaration procedure, and the vessel/aircraft
qualification change declaration procedure. (Note 1)(Note 1) For the related government agency
procedures, see the specifications of the related
government agency procedures.

In the NACCS EDI specification,change the maximum size of theattachment files allowed in one
execution of a procedure.
(Change from 3MB to 10MB)

In the NACCS EDI specification, change the maximum
size of the attachment files (the maximum size of theattached data part) allowed in one execution of aprocedure from 3 MB to 10 MB.

3.2 MIME format messages(Remark 1)
In a procedure that can have multiple attachment files,
the sum of the file sizes must be equal to or smaller
than the maximum size.

53

Change ofspecification(change of the
maximum size ofattachment files)

Change ofdescription

Check of thesize ofattachment
files

Attachment
file retrieval
procedure

Along with the change of the overall
The maximum size of attachment files allowed in one
maximum size of attachment files
execution of a procedure can be specified for individual
allowed in one execution of aprocedure. Add a description in the NACCS EDI
procedure, change the maximum size specification that the maximum values are specified inof attachment files for individual
individual procedure specifications.
procedures.
(Addition) 3.2 MIME format message
Check the procedure specification in question because
the maximum size of a message depends on theprocedure specification.

- (None)Some procedures had to make multiple transmissions in the fifth NACCS due to
the NACCS EDI specification, which
restricts the size of the attachment files
allowed in one execution of a procedure
to 3 MB. In the specification of the sixth
NACCS, those procedures can send an
attachment file of 10 MB at a maximum.
Any in-house system specification must
be checked whether it does not have
3MB restriction.

(Remark 2)
Although the maximum size of attachment files is 10 MB
in the NACCS EDI specification, the actual maximum
size of attachment files allowed in one execution of aprocedure varies depending on the procedure. So theuser must check the specification of the procedure inquestion.
52

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

3.2 MIME format messages

Users other than the users of customs (users of related 3.2 MIME format messages
government agencies) can also use the attachment file
retrieval procedure. So add a figure and change therelevant explanation.

In the NACCS EDI specification of thesixth NACCS, the maximum size ofattachment files allowed in one
execution of a procedure is 10 MB.

-

On the other hand, the actual maximum
size of attachment files allowed in one
execution of a procedure varies
depending on the procedure. So for
details, the user should refer to thespecification of the procedure inquestion.
-(Change location)
3.2.2.4 Processing sequence54

Change ofdescription

Attachment
file retrieval
procedure- (None)Users other than the users of customs (users of related 3.2 MIME format messages
government agencies) can also use the attachment file
retrieval procedure. Change the figure to show thatgovernment users can retrieve attachment files directly
on to their terminals.

13 /61--

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-item
No.
55 Change of location Procedures
being referred to supporting
the ebMS
processing
mode

56

Change ofdescription

Old system

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

List the procedures supporting ebMS in Table 6-7.

3.3 XML format messages(Before change)
See "Table 6-13 List of procedures supporting the ebMS
processing mode and related information."(After change)
See "Table 6-7 List of supporting procedures."- (None)(Reflect the specification of the fifth
NACCS.)In the fifth NACCS, delete a temporary description of
NACCS consolidation.

3.3 XML format messages

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users that have been referring to the listof XML-related information in Table 613 for the fifth NACCS must refer to"Table 6-7 List of supporting
procedures."--(Deletion)(* Invoice packing list registration (IVA) is also included
until October 2013.
57

58

59

Change ofspecification(abolishment of aprocessing mode)

Interactive
With abolishment of the interactive
processing
processing mode (direct interface)?
mode (direct A2, ? A3 messages are abolished.
interface)

Change of location Procedures
being referred to supporting
the ebMS
processing
mode

Change ofdescription- (None)Operation- (None)examples fordifferent
message
types

Delete the description of ?A2 and ?A3 messages due to 3.3 XML format messages
the abolishment of the direct interface.
(Deletion)- Description on the direct interface and ?A2 and ?A3
messages in the list of transmission/reception messages(interactive processing mode) in "Table 3-3-1 XML
Format Messages"
Move the following description to Appendix 15 andprocedure specifications.

3.3 XML format messages(Before change)
For the specification of messages (mapping table) of
XML format messages, see Appendix X-1.
(After change)
For the specification of messages (mapping table) of
XML format messages, see Appendix 15 and procedure
specifications.
Change the text as follows because the current text does not well explain the use of 3.4 Message types
message types.
(Before change)[Message type] indicates a value specified in Message Control Information in the
output common fields in a message transmitted from the NACCS Center server toa user system (inbound message).
Report and Screen types for NACCS EDI messages are used to classify suchmessages into the following output scenarios when using packaged software
provided by NACCS Center: (1) "For printer" is to print a NACCS EDI message
using templates(2) "Screen" is to display a NACCS EDI message using
templatesIn gateway connection environments (using user’s own software), users
do not have to be familiar with this part.
(After change)[Message type] indicates a value specified in Message Control Information in the
output common fields in a message transmitted from the NACCS Center server toa user system (inbound message).
Printer and Screen types for NACCS EDI messages are used by the package
software of personal computers provided by the NACCS center to determine
whether to display the massage in the printer layout or in the screen layout. Users
do not have to be aware of this classification when they develop their own softwarethat runs in a gateway connection environment.
Example: For printer [P]: The package software of personal computers opens thereport template for the message, and displays the report image on the computer ofthe user.
Example: For screen [C]: The package software of personal computers opens thescreen template for the message, and displays the screen image on the computerof the user.

14 /61

Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

Users that have been referring to thedescription of XML in Appendix X for thefifth NACCS must refer to Appendix 15
and procedure specifications.

--Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
60 Change ofdescription

Sub-item

Changes from Fifth NACCS

Difference- (None)betweenmessagetypes [P] and[A]

Correction on EDI Specification

Relevant location in EDI Specification

Explain the difference between message types [P] and [A]

3.4 Message types(Addition)
The package software of personal computers uses message
types (for printer [P] and [A]) to determine the format used formessage storage. The user does not have to be aware of thedifference of message types [P] and [A]. (Message type [P]: Text
format, Message type [A]: CSV format)
Example of printer format [P]: The package software of personal
computers stores the message in the text format.
Example of screen format [A]: The package software of
personal computers stores the message in the CSV format.

Envisaged Impact on Users in Migration
Remarks
to Sixth NACCS (Assumption)* Describe the difference
There is no report of message type [A] between [P] and [A] for the
to be sent to commercial users.
clarification of thespecification although theusers do not have to beaware of this difference.

[Information]
In the current procedure specifications, there is no information to
be output in message type [A] for NACCS users.

61

Change ofdescription

Difference- (None)betweenmessagetypes [M] and[R]

Correct the explanation of the difference of message types [M] and [R] as
follows:

3.4 Message types--

3.4 Message types--(Before change)
If an inquiry procedure has been successfully processed (message type [M]),a processing result message (including the code for successful completion) is
sent , while if processing has failed (message type [R]), the code indicatingprocessing has failed is sent instead of an inquiry result message.
Figure 3-4-3 shows a flow of procedure processing (inquiry result) (forscreen).
(After change)(1) When the main processing part finishes the procedure successfully, it
outputs a message of screen information (message type (M)).
This message contains the processing result code of successful terminationand the inquiry result. The package software of personal computers displays
the inquiry result screen and the processing result code of successful
termination.
Figure 3-4-3 shows the flow of this case.
(2) When the main processing part has an error termination
It outputs a processing result notification message (message type [R]).
This type of message contains only a processing result code of an error. The
package software of personal computers displays an input screen and anerror processing result code.

62

Change ofdescription

Change oftheexplanationof message
type [T]- (None)Correct the explanation of message type [T](Before change)
This type of message is to be imported into and used on
the user's own system, which does not support
templates (for screen or printer) of the packaged
software provided by NACCS Center.
(After change)
This type of message is to be imported into and used on
the in-house system.
So there is no screen or printing image for displaying
by the package software of personal computers
because there is no template (for screen or printer).
(The message is displayed as a text.)

15 /61

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-itemNo.
63 Deletion ofProcedures
procedure-specific that output
information
messagetype [T]Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

Delete descriptions of procedure-specific information
3.4 Message types
from the NACCS EDI specification except when they are (Table 6 List of output information codes)
necessary for explanation of the NACCS EDI
specification.
Instead, indicate as a reference the procedure that
outputs message type [T].

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

Remarks(Before change)
Types of output information include the following:-Warehousing information-Cargo loading ULD
information-Cargo transfer information(After change)
For the information being output, see "Table 6-9 List of
output information codes"
64

65

66

Change of
Statistic
specification
report(change of thesize of the statistic
reports to be
retrieved)

Change the maximum size ofcommercial statistic reports to be
retrieved at a time.
(Change the size from 1 MB to 30
MB.)

Change the restriction (the maximum size) ofcommercial statistic reports to be retrieved at a timefrom 1 MB to 30 MB.

Change ofdescription

Add adescription
on thecapacity ofthe statistic
report.

- (None)State explicitly that the indicated capacity of statistic
reports is the maximum capacity.

Add adescription
on thereference ofthe statistic
report.

- (None)Change ofdescription

3.4 Message types

In the fifth NACCS, the maximum size of (Supplemental explanation)
the statistic report was 1 MB, so that
The maximum size ofsome statistic reports had to wait forcustoms statistic reports is
operational transmission of the NACCS also changed to 30 MB.
center. In the sixth NACCS, however,
The maximum size (MB) of
maximum of 30 MB can be retrieved by one transfer can be specified
one file transfer.
in a table, which is coded by
the customs station.
Any in-house system specification must A statistic report that needed
be checked whether it does not haveto be divided into several files
1MB restriction.
for transfer in the fifth NACCS
may become able to be
retrieved at a time.

3.4 Message types

The change of the maximum capacity is
described in a separate item.
This item is provided only for providing a
concrete description.

3.4 Message types

This item is provided only for indicatingthat a description is an example.

(Before change)
A Maximum size of messages allowable fortransmission is 10,000,000 bytes after file compression.
(After change)
The maximum size of messages allowable fortransmission is 30,000,000 bytes after file compression.

(Before change)
A Maximum size of messages allowable fortransmission is 30,000,000 bytes after file compression.
(After change)
The maximum size of messages allowable fortransmission is 30,000,000 bytes after file compression
at a maximum.

Indicate that the description of a reference to a statistic
report is an example.
(Before change)
Management documents are sent primarily in CSV
format, allowing the user to edit or perform calculations
on such documents using commercially available
spreadsheet software.
(After change)
Management documents are sent primarily in CSV
format, allowing the user to edit or perform calculations
on such documents using software such ascommercially available spreadsheet software.

16 /61-

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
67 Change ofdescription

Sub-item-

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

Change the description of the application software forviewing statistic report (csv file) so that it does not
specify a version.

3.4 Message types

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Before change)
Microsoft Excel 2003
(After change)
Microsoft Excel

68

69

Providing moredetailed
description

Change ofdescription

About the- (None)setting of the
input
message ID
for EXC
messagesdestined tosharedterminals.
- (None)Make a special remark (detailed specification) about the 3.5 Message control items
input message ID in the case of shared terminals.

--

3.5 Message control items--

3.5 Message control items--

Add a usage example of the input message ID in Figure 3.5 Message control items
3-5-2 to show the difference between the input message
ID and the message tag.

--

(Addition)
An input message ID is set also for an EXC-typemessage if the message is destined to a sharedterminal. Add a description meaning above.

Correct the description on the message tag setting in"In-File delivery message [F, P]" of Table 3-5-2.
(Before change)
Message tag: Server(After change)
Message tag: Message tag that the user set in the input
common fields of the processing request message.

70

Change ofdescription

Change ofdescription
on EXZ- (None)Add a supplemental explanation to provide more
concrete description on the input message ID being set
in process result messages sent by the destination
management processing for types EXZ or EXC.
(Before change)
The input message ID being set in the processing
request message is set(After change)
The input message ID being set in the processing
request message is set in turn**An EXZ message or an EXC message is output when
triggered by a third party input. But it is not the input
message ID that the third party has set in the processing
request message.

71

Change ofdescription

Explanation - (None)of input
informationand messagetag(Addition) Add a usage example of the input message
ID in Figure 3-5-2.
* Figure 3-5-2 has a usage example of the message tag.
So the user will be able compare it with the input
message ID to understand the difference.

17 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
72 Change ofdescription

Sub-item
Old system

Changes from Fifth NACCS- (None)Correction on EDI Specification

3.5 Message control items

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

3.7 Report message table and retrieval procedure

-

-

-

-

Relevant location in EDI Specification

Delete an explanation about the old system* Delete the description on the restriction in the oldsystem (the fourth NACCS) in comparison with the fifth
NACCS.
(Deletion)
The procedure which is not suitable for mail (theprocedure which is described in Appendix 10, EDI
Specifications, Former Air-NACCS) for sequential
processing in the previous system, with the prolongationof message length in this system where procedure
processing can be done without using the sequential
processing, the procedure specifications is being revisedso that it will get suitable with e-mail style processing
mode.

73

74

Change ofdescription

Change ofdescription

List ofsupported
processingmodes- (None)Fileexchangeblock- (None)

Improve the description as follows:
Add the description on the interactive processing mode(package software of personal computers) because themessage is stored in the report message table and REQ
is used also in the case of using the interactive
processing mode (package software of personal
computers).

Change some descriptions because the old systems
3.7 File exchange block and retrieval procedure(the fourth and earlier versions of NACCS) used the file
exchange block but the fifth and later versions do notuse it.
*
The file exchange block is changed to the reportmessage table during the fifth NACCS update. So
reconsider the remaining description in order to express
the difference from the old system and to avoid
confusion.
(Before change)
File exchange block(After change)
Report message table

18 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
75 Change ofdescription

Sub-item-

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

Improve the description as follows:

3.7 Report message table and retrieval procedure

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Before change)
The SYG procedure must be executed periodically toretrieve ... messages. However, do not execute theprocedure too frequently because doing so overloads
the NACCS center.
(After change)
The SYG procedure must be executed periodically toretrieve ... messages. However, do not execute theprocedure too frequently because doing so overloads
the NACCS center.
(For the guideline of the retrieval interval, see T08 of"(5) Timers" in "4.2.6 Others.")

76

Change ofspecification(change of the
supported
processing
modes)

Change ofIn the fifth NACCS, the e-mailFrom the sixth NACCS, processing modes other than
4.1 Interactive processing mode (for packagethetransmission function can be usedthe ebMS processing mode can be used for the e-mail software of personal computers)
supported
only in ebMS processing mode.
transmission function.
4.2 Interactive processing mode (SMTP two-way)processing
However, in the sixth NACCS, it can
So move the description on the e-mail transmission from 4.3 E-mail style processing mode
modes of the be used in other processing modes as "4.5 ebMS processing mode" to "4.6 Others" in the EDI 4.4 WebNACCS processing mode (for web
e-mailwell.
specification.
browser)transmission
Also, add the following description in the chapters of thefunctionprocessing modes in which e-mail transmission
becomes possible:

E-mail is sent to the e-mail address
specified by the user on the procedurescreen.
* To an Internet e-mail address

-

-

-

(Addition)
For e-mail transmission, see "4.6.1 e-mail transmission."

77

Change ofdescription

Old system- (None)Delete an explanation about the old system* Delete the description on the processing details in theold system (the fourth NACCS) in comparison with thefifth NACCS.
(Deletion) Outline of deleted content
In the old system (the fourth NACCS), the user must
manually issue a processing request message (report
retrieval request) to retrieve information stored in thereport message table. In the fifth NACCS, however, theuser can retrieve information in one of the following
ways:- Issuing a processing request message (report retrieval
request) by a timer- Issuing a processing request message (report retrieval
request) manually- Issuing a processing request message (report retrieval
request) upon receipt of a process result message (forscreen)19 /61

4.1 Interactive processing mode (for package
software of personal computers)

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
78 Attachment fileSub-item

Changes from Fifth NACCS

Method of file Provide a method of file attachment
attachment for related government agencies.
for related
government
agencies

Correction on EDI Specification

Relevant location in EDI Specification

Users other than the users of customs (users of related 4.1 Interactive processing mode (for package
government agencies) can also use the attachment file software of personal computers)
retrieval procedure. So add a figure and change therelevant explanation.
(Change location)
4.1.3.4 Example of a procedure sequence forattachment file message in this system

79

Deletion ofDeletion ofprocedure-specific theinformation
description
on theattachment
file storage
period- (None)Delete descriptions of procedure-specific information from the
NACCS EDI specification except when they are necessary for
explanation of the NACCS EDI specification.
Instead, add an reference.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
A new procedure is added for related
government agencies, in which fileattachment is possible.
The user will be able to send
attachment files to related government
agencies.

4.1 Interactive processing mode (for package
software of personal computers)
4.2 Interactive processing mode (SMTP two-way)Users who want to know the attachment
file storage periods should look at
NACCS information, although they havenot changed.

4.1 Interactive processing mode (for package
software of personal computers)
4.2 Interactive processing mode (SMTP two-way)--

4.2 Interactive processing mode (SMTP two-way)--(Deletion)
Delete the descriptions on attachment file storage periods forindividual procedures.
(Addition)
For the attachment file storage periods of different procedures,
see the pages of procedure specifications on the NACCS
information.
(Information)
This document is disclosed to users on the NACCS center's
information as a document related to procedure specifications.
The document is currently available at "Storage periods ofdifferent DBs" at http://www.naccscenter.com/system/ref/.
* The document is also posted on other NACCS information thatusers of the NACCS dedicated line can look at.

80

Change ofdescription

Change ofwording- (None)

Improve the wording as follows:(Before change)user system must be built so that the transaction
response notification messages are executed first.
(After change)
The user system must not be built based on theassumption that the processing result notification isprocessed first.

81

Change ofdescription

Old system- (None)Delete an explanation about the old system* Delete the description on the restriction in the oldsystem (the fourth NACCS) in comparison with the fifth
NACCS.
(Deletion)
The procedure which is not suitable for mail (theprocedure which is described in Appendix 10, EDI
Specifications, Former Air-NACCS) for sequential
processing in the previous system, with the prolongationof message length in this system where procedure
processing can be done without using the sequential
processing, the procedure specifications is being revisedso that it will get suitable with e-mail style processingmode.
20 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
82 Change of
specification(abolishment of aprocessing mode)

Sub-item

Changes from Fifth NACCS

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Correction on EDI Specification

Relevant location in EDI Specification

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

4.2 Interactive processing mode (SMTP two-way)

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

(Deletion)- Delete the interface description that the direct interface
should conform to.

83

Change ofdescription

Change ofdescription
on EXZ- (None)Add a pointer to Section 3.5 that provides more concrete 4.2 Interactive processing mode (SMTP two-way)description on the input message ID being set in process
result messages sent by the destination management
processing for types EXZ or EXC.

--

User must change the settings

-

-

-

-

-

(Addition)* For the content of input message ID being output, see"3.5 Message control items."

84

Network

E-mailaddress

Change the domain of e-mailaddresses.

The domains of the center and user e-mail addresses
are changed.

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode1.
before：naccs.customs
after：naccs6
2.
before：main.naccs.customs
after：prod.naccs6

85

Change ofdescriptionFileexchangeblock- (None)Change some descriptions because the old systems
4.2 Interactive processing mode (SMTP two-way)(the fourth and earlier versions of NACCS) used the file
exchange block but the fifth and later versions do notuse it.
*
The file exchange block is changed to the reportmessage table during the fifth NACCS update. So
reconsider the remaining description in order to express
the difference from the old system and to avoid
confusion.
(Before change)
File exchange block(After change)
Report message table

86

Change ofdescription

Other
government
agencies- (None)Correct the text as follows:

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode
4.5 ebMS processing mode

(Before change)
Other government agencies(After change)
Related government agencies

21 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
87 Change of
specification(change ofmessage length)

Sub-item

Changes from Fifth NACCS

NACCS EDI Change the maximum message
messagelength of a NACCS EDI message.
length(Change from 500 KB to 700 KB)

Correction on EDI Specification

Relevant location in EDI Specification

Change the maximum length of a NACCS EDI message 4.2 Interactive processing mode (SMTP two-way)from 500 KB to 700 KB.
4.3 E-Mail style processing mode
4.5 ebMS processing mode

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
For a process result message that had to be segmented to multiple messages
due to the 500 KB restriction of the fifth
NACCS, the number of required
messages is reduced because themaximum length becomes 700 KB in
the sixth NACCS.
Any in-house system specification must
be checked whether it does not have
500 KB restriction.

88

Change ofdescription

Word
processor
software- (None)Correct the description of the application software usedfor viewing NACCS EDI messages so that thedescription better represents the reality.

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode--

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode

Some procedures had to make multiple transmissions in the fifth NACCS due to
the NACCS EDI specification, which
restricts the size of the attachment files
allowed in one execution of a procedure
to 3 MB. In the specification of the sixth
NACCS, those procedures can send an
attachment file of 10 MB at a maximum.

(Before change)
In word processing software or text editor tool, a text
format NACCS EDI message (processing request
message)(After change)
In text editor tool, a text format NACCS EDI message(processing request message)

89

Change ofspecification(change of the
maximum size ofattachment files)

Check of thesize ofattachment
files

In the NACCS EDI specification,change the maximum size of theattachment files allowed in one
execution of a procedure.
(Change from 3MB to 10MB)

In the NACCS EDI specification, change the maximum
size of the attachment files (the maximum size of theattached data part) allowed in one execution of aprocedure from 3 MB to 10 MB.
(Remark 1)
In a procedure that can have multiple attachment files,
the sum of the file sizes must be equal to or smaller
than the maximum size.
(Remark 2)
Although the maximum size of attachment files is 10 MB
in the NACCS EDI specification, the actual maximum
size of attachment files allowed in one execution of aprocedure varies depending on the procedure. So theuser must check the specification of the procedure inquestion.

22 /61

Any in-house system specification must
be checked whether it does not have
3MB restriction.

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
90 Change ofdescription

91

Change ofdescription

Sub-item
Change ofnames ofattachment
files

Change ofthe formats
ofattachment
files

Changes from Fifth NACCS
Change the character codes of thenames of files that can be used byattachment files procedures.

Change the file extensions of thenames of files that can be used byprocedures having attachment files.

Correction on EDI Specification

Relevant location in EDI Specification

Change the character strings that can be used in file names ofattachment files as follows:

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode

(Before change)
Encode any file name having Japanese characters by the B
encoding method (Base64). Use one of the following charactercodes for encoding:- EUC-JP- ISO-2022-JP- Shift_JIS- UTF-8(After change)
Encode any file name having Japanese characters by the B
encoding method (Base64). The character code for encoding ofJapanese characters depends on the procedure as follows:[For procedure codes MSX and MSY01]- ISO-2022-JP[Other procedures that can use attachment files]- EUC-JP- ISO-2022-JP- Shift_JIS- UTF-8
Change the extensions that can be used in file names of attachment files as follows:(Before change)<Text data>- Text format- Microsoft Word format (without macro and the like)- XML format<Table data>- Microsoft Excel format (without macro and the like)- CSV format<Image data>- JPEG format- TIFF format- Windows bitmap format- PDF format

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Character codes that can be used forfile names of attachment files ofprocedures MSX and MSY01 have beenchanged. So users of an in-housesystem who use these procedures must
use the new character codes.

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode

Extensions that can be used for
attachment files are clarified. So theusers of an in-house system who use
relevant procedures must not send files
of extensions that are not specified.

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode

Users that have been referring to thedescription of XML in Appendix X for thefifth NACCS must refer to Appendix 15
and procedure specifications.

(After change)<Text data>- TEXT format (extension: txt)
- Microsoft Word format (without macro and the like) (Extension: doc, docx)- Microsoft PowerPoint format (without macro and the like) (Extension: ppt, pptx)- XML format (Extension: xml)
- HTML format (Extension: htm, html)- Rich text format (Extension: rtf)
- Just System Ichitaro format (Extension: jtd)
<Table data>- Microsoft Excel format (without macro and the like) (Extension: xls, xlsx)- CSV format (Extension: csv)
<Image data>- JPEG format (Extension: jpeg, jpe, jpg)
- TIFF format (Extension: tif, tiff)- Windows bitmap format (Extension: bmp)
- GIF format (Extension: gif)
- PDF format (Extension: pdf)
<Others>- Trade control system application format (Extension: jet)

92

Change of location Procedures
being referred to supporting
the ebMS
processingmode- (None)Move the following description to Appendix 15 andprocedure specifications.
(Before change)
For the specification of messages (mapping table) of
XML format messages, see Appendix X-1.
(After change)
For the specification of messages (mapping table) of
XML format messages, see Appendix 15 and procedure
specifications.

23 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
93 Change of
specification(change of XML
message length)

Sub-item
MessagelengthChanges from Fifth NACCS
Change the maximum message
length of XML-format messages.
(Change from 500 KB to 700 KB)

Correction on EDI Specification

Relevant location in EDI Specification

Modify the NACCS EDI specification to change themaximum length of XML messages for one procedurefrom 500 KB to 700 KB.

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode
4.5 ebMS processing mode

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
In the fifth NACCS, the maximum size of XML-format messages was 500 KB, so
a message had to be segmented andsent in multiple transmissions. In thesixth NACCS, however, maximum of
700 KB can be sent by one file transfer.
Any in-house system specification must
be checked whether it does not have
500 KB restriction.

94

Switchover at
disaster

Restriction

For the sixth NACCS, change therestriction condition at the time of
backup center switchover so as toprohibit connection test after backup
center switchover.

Correct the text as follows:

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode

The users cannot conduct a connection test at the time of a serious fault and awide-scale disaster.

(Before change)"great disaster" "connection test will be partly limited"(After change)"a serious fault and wide-scale disaster" "the connection
test is prohibited"* Switchover to the backup center happens not only in awide-scale disaster but also in a serious fault.
In the EDI specification of the fifth NACCS, there is a
description that connection test will be partly limited. In
the sixth NACCS, however, the connection test is
stopped at the time of backup center switchover, andthis condition will be reflected in the specification.

95

Change ofrestriction values

Change ofthe timervalues formessageretrievalinterval

Review the timer values.

Review the timer values for the next version.
Use the current values during the basic design phase,study the details during the detailed design phase, anddetermine the final values during the integrated
operation test.

4.2 Interactive processing mode (SMTP two-way)
4.3 E-Mail style processing mode

The current values are used as ofMarch 25, 2015.

-

96

Change ofdescription-- (None)Unify the expressions used at the end of sentences.
(This change is for the Japanese version only.)

4.2 Interactive processing mode (SMTP two-way)--

24 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-itemNo.
97 Package software Abolishmentof the e-mailstyle
processing
mode

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Abolish basically the package
Abolish basically the package software of the e-mail4.3 E-mail style processing mode
software of the e-mail style processing style processing mode for personal computers. So
mode for personal computers.
change the description in the example of directly
However, deliver the package
connecting to NACCS using the package software of esoftware to the users under the
mail style processing mode for personal computers.
gateway as it is with the fifth NACCS.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who are using the package
software of the e-mail style processing
mode must use another package
software.

Main descriptions to be deleted are as follows:* Delete descriptions on the personal computer package
software for e-mail style processing mode only.
(Deletion)- Figure 4-3-1 Outline of E-mail Processing Mode for Processing
NACCS EDI Messages- Figure 4-3-15 Mailbox Operation- Figure 4-3-16 Cautionary Notes for Cases Where Mailbox isShared Between Multiple Computers- Figure 4-3-23 Arrival order of more than one transaction
response message (Example)(Change)- Figure 4-3-22 Processing Sequence* Change the figure to illustrate the gateway.

98

Network

Switchover at At the time of NACCS switchover,
Delete descriptions that the user or the system
disastersystems connecting to NACCS also
connecting to NACCS must switch the connection
switch over without having to be aware destination when NACCS switches over to the backupof the NACCS switchover.
center.
* When NACCS switches over to the backup center, asystem connecting to NACCS automatically switches
over by querying DNS for the center server IP address.
So the user does not have to be aware of the NACCS
switchover.

4.3 E-mail style processing mode

* Add a description after the network
vendor decides on the policy.

-

4.3 E-mail style processing mode

The server that has the EDIFACT
function is changed in the sixth NACCS,
but the function itself is not changed. So
the change does not affect the users.
Let the in-house system users(EDIFACT users) know that the name ofthe server has changed in the EDI
specification of the sixth NACCS.

* Add a description after the network vendor decides on
the policy.

99

Change ofspecification(server
consolidation)

ServerAbolish the EDIFACT server andconsolidation divide its function into the mail server
and the XML conversion server.

Correct the text as follows:(Before change)
EDIFACT server(After change)
Mail server* "EDIFACT conversion processing" depending on thelocation in the document

25 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
100 Change ofdescription

Sub-item-

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

In the fifth NACCS, there was a misunderstanding that 4.3 E-mail style processing mode
mailbox usage can be restricted for individual users as acountermeasure for mailbox overflow. So correct thedescription.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Before change)
In NACCS, if the mailbox is likely to overflow, the actual
overflow can be prevented through the followings:(After change)
In NACCS, an email is deleted when the user retrieves itfrom a mailbox. An email that remains in a mailbox
without any activity is deleted after seven days.
Therefore, it is unlikely that emails accumulate in a
NACCS mailbox, and the possibility of mailbox overflow
is very small.
However, in the event of any possibility of mailbox
overflow, avoid it by the following way:

101 Network

Reconsiderat Abolish the dial-up line access.
ion of accesslines(abolishmentof dial-up
lines)

About access line types, delete the description of theaccess by dial-up line.

4.3 E-mail style processing mode

Users who are using the access line
type under reconsideration must use
another access line.

-

102 Change of
specification(adding a
processing mode)

Addition of
WebNACCS
processingmode

Add a description on WebNACCS
processing mode, which is
WebNACCS that consolidates thefunctions of the port subsystem and
WebAPS.

Add a description on WebNACCS processing mode,
which is WebNACCS that consolidates the functions of
the port subsystem and WebAPS.

4.4 WebNACCS (for web browser)

A WebNACCS user can get an outlineof the WebNACCS processing mode
from the EDI specification.
Users should refer to the operation
manual or the user manual for usage
details.

-

103 Change ofdescription

Name ofprocessingmode- (None)Change the name of the processing mode as follows:

4.4 Interactive processing mode WebNACCS (using a web browser)(Before change)
Interactive processing modeWebNACCS (using a
Web browser)(After change)
WebNACCS processing mode
* Add "(Use a Web browser)" to the description to alignthe description with other descriptions.

26 /61-

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
104 Specification
change(abolishment of
message
reception
software)Sub-item
Message
reception
software oftheWebNACCS
processing
mode

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Stop providing the message reception Delete the description of the message reception
software that has been provided in the software that has been provided for receiving forms in
fifth NACCS for receiving forms in
the WebNACCS processing mode because the
WebNACCS processing mode.
provision of the software will be stopped.
In the sixth NACCS, forms will be
Describe in "4.4 Interactive processing mode
received via Web browsers.
WebNACCS processing mode (for web browser)" thatreport retrieval is made from a web browser instead.

4.4 Interactive processing mode WebNACCS
processing mode (using a web browser)

105 EXC messages in Outputting an The procedure check processing
WebNACCS
EXC
returns an error against any entry thatprocessing mode message to a makes an output of an EXC message
user who
destined to a user who uses only
uses
WebNACCS.
WebNACCS
only

Add a description that a procedure has an error if there
is any entry that makes the output of an EXC message
destined to a user who uses only WebNACCS

106 Adding a
Adding a- (None)description on the description
certificate in ebMS on certificate
processing mode

Add a description on the electronic certificate (server
certificate and electronic signature certificate) used inebMS processing mode.
Describe that these certificates must be those provided
by the NACCS center.

107 Change ofdescription
location

Move the information on ebMB in Appendix K to Section 4.5 ebMS processing mode
4.6.
Appendix K: Deleted

Reconsiderat - (None)ion of thedescription of
the ebMS
specificationin Appendix K

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users that have been retrieving form
messages using the message reception
software of the WebNACCS processing
mode will have to retrieve forms using a
web browser.

4.4 WebNACCS processing mode (for web
browser)--

4.5 ebMS processing mode--

Users that have been referring to thedescription of ebMS in Appendix K forthe fifth NACCS must refer to Chapter
4.6.

-(Addition)
With the abolishment of the message reception softwarein the sixth NACCS, a procedure has an error if a
NACCS package software outputs an EXC message
destined to a user who uses only WebNACCS.
When a user who uses only WebNACCS needs toreceive a report output from a NACCS package
software procedure, the user must use a processing
mode other than WebNACCS such as netNACCS.

(Before change)
Appendix K About ebMS
(After change)
Move the description to "4.6 ebMS processing mode."

27 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
108 Change of
specification(change of the
supported
processing
modes)

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Change ofIn the fifth NACCS, the e-mailFrom the sixth NACCS, processing modes other than
4.5 ebMS processing modethetransmission function can be usedthe ebMS processing mode can be used for the e-mailsupported
only in ebMS processing mode.
transmission function.
processing
However, in the sixth NACCS, it can
So move the description on the e-mail transmission frommodes of the be used in other processing modes as "4.5 ebMS processing mode" to "4.6 Others" in the EDI
e-mailwell.
specification.
transmission
Also, add the following description in the chapters of thefunctionprocessing modes in which e-mail transmission
becomes possible:

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
E-mail is sent to the e-mail address
specified by the user on the procedurescreen.
* To an Internet e-mail address(Addition)
For e-mail transmission, see "4.6.1 e-mail transmission."

109 Change ofdescription-

Abolish the international interoperation With the change of the server in which to install theacceptance server and implement the international interoperation function, change theebMS server.
description as follows:

4.5 ebMS processing mode

(Before change)
International interoperation acceptance server(After change)ebMS server

110 Network

Encryption
method- (None)(Reflect the specification of the fifth
NACCS.)
Change the encryption method usedin ebMS processing mode.
(Change from SSL3.0 to TLS1.0.)

Change the encryption method used in the ebMS
4.5 ebMS processing mode
processing from SSL3.0 to TLS1.0 for the support of thefifth NACCS.
Change the description of the encryption method as
follows:

The server that has the international
interoperation function is changed in thesixth NACCS, but the function itself is
not changed. So the change does notaffect the users.
Let the in-house system users (users of
the international interoperation function)know that the name of the server haschanged in the EDI specification of thesixth NACCS.

--(Before change)
SSL(After change)
TLS
111 Change ofdescription
location

Procedures
supporting
the ebMS
processingmode- (None)Consolidate the description being refer to, and change
the description as follows:(Before change)
For procedures that support XML-format messages, see"Appendix 6 Table 6-13 List of procedures supporting
the ebMS processing mode and related information."(After change)
For procedures that support XML-format messages, see"Table 6-7 List of supporting procedures."28 /61

4.5 ebMS processing mode

Users that have been referring to thedescription of ebMS in Table 6-13 forthe fifth NACCS must refer to Table 6-7.

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-item
Changes from Fifth NACCS
No.
112 Adding a message Attachment Allow the attachment of files toformat for which
possible for messages of the NACCS EDI format
file attachment is ebMS
in ebMS processing mode.
allowedprocessing
mode/NACC
S EDI
messageformatWith the support of the ebMS processing mode for
medication-related procedures, a description must be
added about "how to attach files to NACCS-EDI
message format."
The maximum size of an attachment file is 10 MB.

4.5 ebMS processing mode

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
A-004

113 Deletion of
Change of- (None)procedure-specific the location
informationof thedescription
on the e-mailsetting

Review the descriptions on the outline of e-mailtransmission and information being sent by e-mail, andmove descriptions on procedure-specific matters toprocedure specifications.

4.6 Others--

114 Providing moredetailed
description

Change of- (None)the locationof thedescription
on the e-mailsetting

Add an explanation on the cases in which compressed
files, pdf files, transmitted message files, andattachment files are attached.
Also, add an explanation on the difference of thesecases.

4.6 Others--

115 Adding the list of
supporting
procedures

Adding the- (None)list ofprocedures
supporting emailtransmission

Add the list of procedures supporting e-mailtransmission.

4.6 Others--

116 Change of
Adding input Add input e-mail address checking to
specification:
check
prevent e-mail transmission errors.
Adding e-mailaddress check at
the transmission ofan e-mailAdd a description on major check items of e-mailaddresses.

4.6 Others

Disclose the major check items of email address.
A user e-mail address containing a
special character string may result in an
input check error for NACCS even if thee-mail address can be used in someother environment.

117 Change of
specification(changing thenumber oftransmission
destinations)

Change as follows:

4.6 Others

E-mail transmission was possible only in ebMS processing mode. But e-mailtransmission will become possible forother processing modes and the
maximum number of destinations thatcan be specified will be increased to
five.

Change ofthe numberof e-mailaddressesthat can beentered for
each
procedure

Change the maximum number of email transmission destinations thatcan be entered for each procedure.

Correction on EDI Specification

Relevant location in EDI Specification(Addition)- The number of "@" (at mark) must be 1. (There mustbe "@" (at mark).)- "." (period) must not be repeated.
- There must not be "." (period) just before or just after"@" (at mark).
- There must not be "." (period) at the beginning or at
the end of the address.
- There must be a character just before and just after"@" (at mark).

(Before change)
Maximum of 3 destinations(After change)
Maximum of 5 destinations

Users must refer to the procedure
specifications for details.

29 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
118 Change ofdescription
location

Sub-item

Changes from Fifth NACCS

Change of- (None)the locationof thedescription
on the e-mailsetting

Correction on EDI Specification

Relevant location in EDI Specification

Delete descriptions of procedure-specific information
4.6 Othersfrom the NACCS EDI specification except when they arenecessary for explanation of the NACCS EDI
specification.
Move the following descriptions to proceduredescriptions because they are procedure-specificmatters.
Make a table of the list of e-mail-related information andreferences.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
The e-mail setting information will be
moved. Users who have been looking at
Section 4.6 must refer to procedure
specifications as well as Section 4.6.

(Deletions)4.6.7.1 Generating E-mail transmission information[1] E-mail destination[2]E-mail subject[3] E-mail body
4.6.7.2 Generating an E-mail attachment file[1] Name of the attachment file sent by an e-mail[2] Compression file password

119 Deletion ofTypes of- (None)procedure-specific information
information
sent by email (XMLdocument filenames)

120 Change ofdescription

Character- (None)strings thatcan be usedin file namesofattachment
files(Addition)
Table descriptionsof the list ofofe-mail-related
information
Deleteprocedure-specificinformationandfrom the4.6 Others

NACCS EDI specification except when they are necessary for
explanation of the NACCS EDI specification.
Move the following descriptions to procedure descriptions
because they are procedure-specific matters.
(1) XML document
Edited content under the <Header> tag and the <BODY> tagwithin the XML declaration tag (<?xml version="1.0"
encoding="EUC-JP"?) and the <RootElement> tag in aprocedure message (XML format) received from a user system
Also, delete "SenderID (user password)" from the edited content.
The file name is "<number> + .xml", where <number> is thenumber set in the message tag (information in Header >Document Identification > UniqueReferenceNo tag) in the
NACCS header part.
(*) Do as follows when a message tag is not available:- Invoice packing list information (e-mail)Set "Electronic invoice acceptance number + .xml".
- Ship loading instruction (S/I) information (e-mail)Set "N-S/I number + .xml".
- S/I information (e-mail)Set "N-S/I number + .xml".

Consolidate descriptions on attachment file names.
4.6 Others(Add Section 4.6.2 and consolidate descriptions related
to attachment files in this section.)
Refer to the section from P.4-2-19, P.4-4-21, and soforth.

30 /61The description on types of information
sent by e-mail will be moved. Users who
have been looking at Section 4.6 mustrefer to procedure specifications.

Users must look at Section 4.6 fordescriptions on attachment files.

-

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
121 Change ofdescription

122 Adding adescription

123 Change ofdescription

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Change ofthe formats
ofattachment
files

Change the file extensions of thenames of files that can be used byattachment files procedure.

Add extensions that can be used in file names of attachment files 4.6 Others
as follows:

Charactersthat can beused in filenames ofattachment
files being
registered in
Declaration
Attachment
Registration(MSX) andDeclaration
Attachment
Correction(MSY01)

Only the following characters can beused in file names of attachment files
being registered in Declaration
Attachment Registration (MSX) and
Declaration Attachment Correction(MSY01):- Single-byte alphanumeric- Hyphen- Underbar- Period (only for extensions)

Consolidate descriptions on attachment file names.
(Add Section 4.6.2 and consolidate descriptions related
to attachment files in this section.)-- (None)Providing a more concrete description(Addition): Adding in <image data>- PNGF format (extension: png)

Clearly state that there is a difference between
procedures MSX and MSY01 and other procedures.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Extensions that can be used for
attachment files are clarified. So theusers of an in-house system who use
relevant procedures must not send files
of extensions that are not specified.

The file names are changed for
attachment files being registered in
Declaration Attachment Registration(MSX) and Declaration Attachment
Correction (MSY01). So the users must
check the impact on their in-housesystems.

5.1 Outline of destination management--

Change some descriptions because the old systems
5.1 Outline of destination management(the fourth and earlier versions of NACCS) used the file
exchange block but the fifth and later versions do notuse it.
*
The file exchange block is changed to the reportmessage table during the fifth NACCS update. So
reconsider the remaining description in order to express
the difference from the old system and to avoid
confusion.

--(Before change)
The destination management processing described inthis document is not used for WebNACCS processing
mode. See the relevant procedure specification and theuser manual because the processing varies dependingon the procedure.
(After change)
The destination management processing described inthis document is not used for WebNACCS processing
mode. The information of the WebNACCS processing
mode is applicable or not applicable depending on theprocedure, so see the relevant procedure specificationand the user manual.

124 Change ofdescriptionFileexchangeblock- (None)(Before change)
File exchange block(After change)
Report message table

31 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
125 Change of
specification(abolishment of aprocessing mode)

Sub-item

Changes from Fifth NACCS

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Correction on EDI Specification

5.1 Outline of destination management
5.2 Address setting of process result messages

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

5.1 Outline of destination management--

5.1 Outline of destination management--

Relevant location in EDI Specification

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.
Main descriptions to be deleted are as follows:* Delete only descriptions related to the direct interface.
(Deletion)- Delete the description on destination management forthe direct interface- Table 5-2-1 Patterns of processing modes that can set
destinations- Table 5-2-2 Destination management setting ofdifferent destination management schemes (INQ andEXZ)- Table 5-2-3 Destination management setting ofdifferent destination management schemes (EXC)

126 Change ofdescription

Unification of - (None)
terms

Unify terms as below.
(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server

127 Change ofdescription-- (None)

Improve the description and align the description levels
as follows:(Before change)
Note 1: A user computer is a personal computer if it isconnected in peer-to-peer connection mode or via arouter, or it is a user SMTP server (for each email
address) if it is connected via a gateway (two-waySMTP).
(After change)(Note 1) A user computer is a personal computer (foreach logical terminal name) if it is connected in peer-topeer connection mode or via a router, or it is a user
SMTP server (for each email address) if it is connected
via a gateway (two-way SMTP).

32 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
128 Change ofdescription

Sub-item-

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

Add a description that errors (message type [R]) of
5.2 Address setting of process result messages
output information message (for screen (inquiry result))
is also out of the scope of destination management.
(Without this description, the reader may misunderstandthat it is subject to destination management.)

129 Change of
specification(server
consolidation)

ServerAbolish the EDIFACT server andconsolidation divide its function into the mail server
and the XML conversion server.

Correct the text as follows:

130 Change ofdescription

Old system

Delete an explanation about the old system
5.2 Address setting of process result messages* Delete the description on the processing details in the oldsystem (the fourth NACCS) in comparison with the fifth NACCS.

- (None)

5.2 Address setting of process result messages(Before change)
EDIFACT server(After change)
Mail server* "EDIFACT conversion processing" depending on thelocation in the document

Envisaged Impact on Users in Migration
Remarks
to Sixth NACCS (Assumption)(List of check points ofprocedure
specifications_2014.01.28_ite
m No. 24 (2))

The server that has the EDIFACT
function is changed in the sixth NACCS,
but the function itself is not changed. So
the change does not affect the users.
Let the in-house system users(EDIFACT users) know that the name ofthe server has changed in the EDI
specification of the sixth NACCS.

-

-

-

-

(Deletion)
The old version of the EDI specification of the sea cargo customs
information processing system contained the following
description, but it is deleted because the checking is done within
the procedure processing so that the description is not applicableto this system.
Description in the old version of the EDI specification of the sea
customs information processing system:
Even if "Input: Sea-NACCS EDI message -> Output: EDIFACT"
is registered in the destination control table, the system discards
the EDIFACT message (process result message) during creation
if a procedure-specific item in the Sea-NACCS EDI message
such as "Marks and Numbers" and "Remark" contains acharacter (such as "\") that is not included in the level A characterset.

131 WebNACCS
processing mode

Change of- (None)thedescription of
the
WebNACCS
processingmode

In the fifth NACCS, WebNACCS was described as a
5.2 Address setting of process result messages
kind of the interactive processing mode. But for the sixth
NACCS, add a separate description of the WebNACCS
processing mode.
So change the description of the following table.
(To be changed)
Table 5-2-1 Patterns of processing modes that can set
destinations

33 /61

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-itemNo.
132 Package software Abolishmentof the e-mailstyle
processingmode

133 Specification
change(abolishment of
message
reception
software)Message
reception
software oftheWebNACCS
processing
mode

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Abolish basically the package
Abolish basically the package software of the e-mail5.2 Address setting of process result messages
software of the e-mail style processing style processing mode for personal computers. So
mode for personal computers.
change the description in the example of directly
However, deliver the package
connecting to NACCS using the package software of esoftware to the users under the
mail style processing mode for personal computers.
gateway as it is with the fifth NACCS.
Main descriptions to be deleted are as follows:* Delete only descriptions related to the package
software of personal computers of e-mail styleprocessing mode.
(Deletion)- Table 5-2-1 Patterns of processing modes that can set
destinations- Table 5-2-2 Destination management setting ofdifferent destination management schemes (INQ andEXZ)- Table 5-2-3 Destination management setting ofdifferent destination management schemes (EXC)

Stop providing the message reception Delete the description of the message reception
software that has been provided in the software that has been provided for receiving forms in
fifth NACCS for receiving forms in
the WebNACCS processing mode because the
WebNACCS processing mode.
provision of the software will be stopped.
In the sixth NACCS, forms will bereceived via Web browsers.
With the change of procedure specifications, there will
be no message that requires address management
setting in the WebNACCS processing mode. So delete
the description of that content.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who are using the package
software of the e-mail style processing
mode must use another package
software.

5.2 Address setting of process result messages

Users that have been retrieving form
messages using the message reception
software of the WebNACCS processing
mode will have to retrieve forms using a
web browser.

(Deletion)(Note 2) The setting is possible when the message
reception software is used.

134 Change of section Explanation
structureof statistic
reports

The explanation of the statistic report Change Appendix 11 to Chapter 6.
retrieval was in Appendix 11 in the EDI Change the section structure of Chapter 6 inspecification of the fifth NACCS, butaccordance with other EDI specification texts.
move it to Chapter 6 for the sixth* This item describes only about the section structure.
NACCS.
The content of the EDI specification is not changed byWith this change of the description
this item.
location, reorganize the structure(chapter, sections, and subsections)of Chapter 6.

6 Retrieval of Statistic Report Information

Users that have been referring to thedescription of the retrieval of statistic
report information in Appendix 11 for thefifth NACCS must refer to Chapter 6
and procedure specifications.
The section structure is different from
Appendix 11.

135 Change ofdescription- (None)

6.1 Retrieval of Statistic Report Information-

Old system

Delete an explanation about the old system* Delete the description on the processing details in theold system (the fourth NACCS) in comparison with thefifth NACCS.
(Deletion)
For this system, the procedure in the old Sea-NACCS
for retrieving messages accumulated in QDS (deliverytype message queue) using the DST procedure must bechanged to use the following retrieval method.

34 /61-

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
136 Change insegmented
deliverySub-item
Statistic
reportChanges from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Allow NACCS users to receive a
Add a description that a commercial statistic report thatcommercial statistic report by dividing it into exceeds the size limitation is segmented and delivered
multiple files if the size of the statistic report in multiple files.
exceeds the limitation (the maximum size of
one retrieval defined by the system side).

6.1 Retrieval of Statistic Report Information* Fifth NACCS:
NACCS users: The NACCS center
retrieves the data and delivers it to the
NACCS user.
Customs users: The data is transmitted in
multiple files.

A statistic report that exceeds the size limitation issegmented and delivered in multiple files.
For the maximum value of the limitation, see "(3)Messages for filing (statistic report) (for filing [F], forprinter [P])" in "3.4 Message type."
A statistic report that was delivered in the past is notsegmented again when the limitation value is changed.

138 Change ofdescription

Change ofstatistic
reportcounting- (None)-- (None)Change the counting of statistic reports in the example
of segmentation.

-* Fifth NACCS:
The NACCS center retrieves the data anddelivers it to the NACCS user by e-mail orother method.
* Sixth NACCS:
The NACCS center server sends the data in
multiple files to the NACCS users.
*
In-house system users must check if the file
reception mechanism needs to be revised forthe multi-file delivery of statistic reports.

* Sixth NACCS:
NACCS users: The data is transmitted in
multiple files.
Customs users: The data is transmitted in
multiple files.

137 Change ofdescription

In the sixth NACCS, NACCS users canretrieve statistic reports that exceed the size
limitation.

Remarks

Described below is the difference between thefifth and sixth systems in the case of delivering
an oversized statistic report to a NACCS user.

(Addition)
The way of retrieving oversized data differs 6.6 Segmentation of statistic reports
between the fifth NACCS and the sixth
NACCS as follows:

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)

6.1 Retrieval of Statistic Report Information--

6.1 Retrieval of Statistic Report Information--

6.1 Retrieval of Statistic Report Information--(Before change)
First sheet, second sheet(After change)
First file, second file

Change the description of the application software forviewing statistic report (csv file) so that it does not
specify a version.
(Before change)
Microsoft Excel 2003
(After change)
Microsoft Excel

139 Deletion ofReports of- (None)procedure-specific special
information
patterns ofstatistic
reportinformation
output format

Delete descriptions of procedure-specific information
except when necessary for explanation.
Also, add a reference as below.
(Before change)
Note that most of the management documents,
excluding some documents such as lump-sum payment
statements, are created in CSV format.
(After change)
For the output format, see "Table 6-9-2 List ofCommercial Statistic Reports."
For the messaging method of statistic reports, see "6.
Retrieval of Management Document Information."

35 /61

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-item
Changes from Fifth NACCS
No.
140 Deletion of
List of bond - (None)
procedure-specific statistic
information
reports to be
output again

Correction on EDI Specification

Relevant location in EDI Specification

Delete descriptions of procedure-specific information from the NACCS EDI
specification except when they are necessary for explanation of the NACCS EDI
specification.
The section indicated below described the outline of a procedure-specific matter.
So change the description to refer to the procedure specification and the list of
statistic reports.

6.1 Retrieval of Statistic Report Information

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

Remarks(Before change)
6.8 Request of bond statistic report re-output
6.8.1 Outline of Procedure
For bond statistic reports, the specified statistic report is output again by thebond statistic report re-output processing that is automatically started basedon a re-output request registered by procedure "Bond statistic report re-output
information registration and change (DLH01)." Table 6-1 lists the relevantbond statistic reports.
Table 6-1 List of bond statistic reports to be re-output(After change)
6.8 Request of bond statistic report re-output
NACCS stores some delivered statistic reports in the statistic report retrieval server
for a certain period. After executing "bond statistic report re-output information
registration and change (DLH01)", the user can retrieve a report by using "statistic
report retrieval" of the package software of personal computers to specify a statistic
report that the user wants to output again.
For the detailed of "bond statistic report re-output information registration andchange (DLH01)", see procedure specifications. For statistic reports that can be
output again, see "Table 6-9-2 List of Commercial Statistic Reports."

141 Change of
specification(change ofmessage length)

NACCS EDI Change the maximum message
messagelength of a NACCS EDI message.
length(Change from 500 KB to 700 KB)

Change the maximum length of a NACCS EDI message 6.2 Procedure of retrieving statistic reports (using an For a process result message that hadfrom 500 KB to 700 KB.
in-house system)
to be segmented to multiple messages
due to the 500 KB restriction of the fifth
NACCS, the number of required
messages is reduced because themaximum length becomes 700 KB in
the sixth NACCS.

-

Any in-house system specification must
be checked whether it does not have
500 KB restriction.

142 Change ofdescription

Word
processor
software- (None)Correct the description of the application software usedfor viewing NACCS EDI messages so that thedescription better represents the reality.

6.2 Procedure of retrieving statistic reports (using an in-house system)-(Before change)
In word processing software or text editor tool, a text
format NACCS EDI message (processing request
message)(After change)
In text editor tool, a text format NACCS EDI message(processing request message)
143 Change of
Statistic
specification
report(change of thesize of the statistic
reports to be
retrieved)

Change the maximum size ofcommercial statistic reports to be
retrieved at a time.
(Change the size from 1 MB to 30
MB.)

Change the restriction (the maximum size) ofcommercial statistic reports to be retrieved at a timefrom 1 MB to 30 MB.

36 /61

6.2 Procedure of retrieving statistic reports (using an In the fifth NACCS, the maximum size of The maximum size of
in-house system)
the statistic report was 1 MB, so that
customs statistic reports issome statistic reports had to wait foralso changed to 30 MB.
operational transmission of the NACCS The maximum size (MB) ofcenter. In the sixth NACCS, however,
one transfer can be specified
maximum of 30 MB can be retrieved by in a table, which is coded by
one file transfer.
the customs station.
A statistic report that needed
Any in-house system specification must to be divided into several files
be checked whether it does not havefor transfer in the fifth NACCS
1MB restriction.
may become able to be
retrieved at a time.

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
144 Change ofdescription

Sub-item

Changes from Fifth NACCS

Correction of - (None)a past date inexamplesCorrection on EDI Specification

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
6.2 Procedure of retrieving statistic reports (using an in-house system)
Relevant location in EDI Specification

The date of the fifth NACCS update is currently used inexamples. Change it to the date of the sixth NACCS
update.
Example:(Before change)
20051010(After change)
20181010

145 Change of setting Statistic
values of output
reportcommon fields

Allow NACCS users to receive astatistic report by dividing it into
multiple files if the size of the statistic
report exceeds the limitation.

Along with the segmentation of statistic reports, change 6.2 Procedure of retrieving statistic reports (using an A user who has implemented thethe output content in Table 6-14 Output common fields in-house system)
retrieval of statistic reports in the in(statistic report message).
house system must check if the system
can receive a statistic report when it is(Before change)
delivered with segmentation.
Along with this change, also change Message control information
the output content of output common Division sequence number: 000 (Fixed)
Example of checking:fields "message control information"
Termination: E (Fixed)- Whether the in-house system usesof messages of a segmented statistic
division sequence numbers andreport.
(After change)
termination in the message control
Message control information
information for the processing of the inDivision sequence number: 000 to 999
house system.
The serial numbers are set according to the number of- How the in-house system behavessegments.
when it receives a segmented statistic
In the case of no segmentation, this field is set to 000.
reportTermination: "E" is set in the last message.
A space is set in other messages.

146 Change of setting Statistic
values of output
reportcommon fields

Allow NACCS users to receive astatistic report by dividing it into
multiple files if the size of the statistic
report exceeds the limitation.
Also change the file names ofsegmented statistic reports.

Change the scheme of file names of statistic reports as follows and add an
explanation and an example.

6.2 Procedure of retrieving statistic reports (using an A user who has implemented thein-house system)
retrieval of statistic reports in the inhouse system must check if the system(After change):(1) Name of CSV-format statistic report
can receive a statistic report when it is
Output information code (1)+Date (2)+_+Destination user code(3)+_+Divisiondelivered with file segments whose file
sequence number (4)+_+Importer/exporter code, etc. (5)+_+Copy source
names are different from before.
user code, etc. (6)+_+Date and time (7).csv(2) File name of statistic report retrieved by the package software of personal
computers(After retrieval, the package software converts the file name before saving it.)
Procedure specification No.+Statistic report name (Japanese) (1')+Date(2)+_+Destination user code (3)+_+Division sequence number(4)+_+Importer/exporter code, etc. (5)+_+Copy source user code, etc.
(6)+_+Date and time (7).csv(Addition)(4): Serial number for a segmented output. "Serial number+E" is set in the last
file.
Example 5: When the statistic report of the user in example 1 is divided into
three files
AAA9990181208_1ANAC_001_20181209045012.csv
AAA9990181208_1ANAC_002_20181209045012.csv
AAA9990181208_1ANAC_003E_20181209045012.csv

37 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
147 Change ofdescription

148 Network

149 Switchover at
disasterSub-item
Adding adetailed
explanationon the filenames ofstatistic
reports

Changes from Fifth NACCS- (None)Correction on EDI Specification

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
6.2 Procedure of retrieving statistic reports (using an in-house system)
Relevant location in EDI Specification

Add a detailed explanation to the explanation of the filenames of statistic reports.
(After change): Add the underlined text(4): Importer/Exporter code, etc. (Optional output)* Use this field when outputting multiple files of a statistic
report to one destination. Set the output content inaccordance with the output unit.
For details on statistic reports being output in multiple
files and their output units, see procedure specifications.

(5): User code of the copy source (Optional output)* Use this field to deliver a statistic report that has beendelivered to a user to another user. When a statistic
report file name of the user code of the copy source
contains an importer/exporter code, etc., the content of
the importer/exporter code, etc. is output before thisfield.
Statistic reports being delivered to a different user are
those specified in the procedure specification or thosethatthedescriptions
NACCS center
response
to a request 6.2 Procedure of retrieving statistic reports (using an When NACCS switches over to the
Switchover at At the time of NACCS switchover,
Deletethathasthe setuserinorthe system
disastersystems connecting to NACCS also
connecting to NACCS must switch the connection
in-house system)
backup center, a system connecting toswitch over without having to be aware destination when NACCS switches over to the backup
NACCS automatically switches over byof the NACCS switchover.
center.
querying DNS for the center server IP* When NACCS switches over to the backup center, aaddress. So the user does not have tosystem connecting to NACCS automatically switches
be aware of the NACCS switchover.
over by querying DNS for the center server IP address.
So the user does not have to be aware of the NACCS
switchover.

Restriction

For the sixth NACCS, change therestriction condition at the time of
backup center switchover so as toprohibit connection test after backup
center switchover.

Correct the text as follows:(Before change)"great disaster" "connection test will be partly limited"(After change)"a serious fault and wide-scale disaster" "the connection
test is prohibited"-

6.2 Procedure of retrieving statistic reports (using an The users cannot conduct a connection in-house system)
test at the time of a serious fault and awide-scale disaster.

* Switchover to the backup center happens not only in awide-scale disaster but also in a serious fault.
In the EDI specification of the fifth NACCS, there is a
description that connection test will be partly limited. In
the sixth NACCS, however, the connection test is
stopped at the time of backup center switchover, andthis condition will be reflected in the specification.

150 Change ofrestriction values

Change ofthe timervalues formessageretrievalinterval

Review the timer values.

Review the timer values for the next version.
Use the current values during the basic design phase,study the details during the detailed design phase, anddetermine the final values during the integrated
operation test.

38 /61

6.2 Procedure of retrieving statistic reports (using an in-house system)
The current values are used as ofMarch 25, 2015.

-

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
151 Network

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
6.2 Procedure of retrieving statistic reports (using an The NACCS center assumes that inin-house system)
house systems connect to the centerusing DNS name resolution.
In-house systems should not directly
specify the IP address. Instead, theyshould use DNS name resolution.
Relevant location in EDI Specification

Switchover at At the time of NACCS switchover,
Delete descriptions that the user or the system
disastersystems connecting to NACCS also
connecting to NACCS must switch the connection
switch over without having to be aware destination when NACCS switches over to the backupof the NACCS switchover.
center.
* When NACCS switches over to the backup center, asystem connecting to NACCS automatically switches
over by querying DNS for the center server IP address.
So the user does not have to be aware of the NACCS
switchover.
(Deletion)(2) Connect to the statistic report retrieval server for the
backup center when NACCS is operating in the backup
center due to a wide-scale disaster or other reason.

152 Network

153 Change of
specification(server
consolidation)

154 Change of
specification(abolishment of aprocessing mode)

Switchover at At the time of NACCS switchover,
Delete descriptions that the user or the system
disastersystems connecting to NACCS also
connecting to NACCS must switch the connection
switch over without having to be aware destination when NACCS switches over to the backupof the NACCS switchover.
center.
* When NACCS switches over to the backup center, asystem connecting to NACCS automatically switches
over by querying DNS for the center server IP address.
So the user does not have to be aware of the NACCS
switchover.

7.1 Center hardware* Add a description after the network vendor decides on
the policy.
ServerAbolish the international interoperation Correct
the text as follows:
7.1 Center hardware
consolidation acceptance server and implement theebMS server.
(Before change)
International interoperation acceptance server(After change)ebMS serverInteractive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.
Main descriptions to be deleted are as follows:* Delete only descriptions related to the direct interface.
(Deletion)- Method of switchover to the backup center in an inhouse system- Table 7-4-1 Security requirements to be observed byusers- Figure 7-4-1 Log of import (export) declaration andother customs procedure executed on a personal
computer under the gateway computer- Restrictions on the use of the router (for the directinterface) of NACCS connection

39 /617.1 Center hardware
7.4 User security measures* Add a description after the network
vendor decides on the policy.

-

The server that has the international
interoperation function is changed in thesixth NACCS, but the function itself is
not changed. So the change does notaffect the users.
Let the in-house system users (users of
the international interoperation function)know that the name of the server haschanged in the EDI specification of thesixth NACCS.
Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
155 Network

156 Change ofdescription

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

Reconsiderat Abolish the dial-up line access.
ion of accesslines(abolishmentof dial-up
lines)

Revise descriptions in the EDI specification about
routers and other devices in accordance with theabolishment of the dial-up lines.

Unification of - (None)
terms

Unify terms as below.

Relevant location in EDI Specification
7.2 Network
7.4 User security measures

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who are using the access line
type under reconsideration must use
another access line.

(Change locations)Figure 7-2-2 NACCS connection router(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server

157 Security measures Number ofdigits ofpasswords,
and othermatters

Reinforce the security by adding thefollowing password checking:Describe the following as the password specification of
the sixth NACCS.

- Minimum number of the characters in a
password- Types of characters included in a
password- Password log management(Addition)
User passwords must satisfy the following conditions:- The minimum number of characters of each password
is between 6 and 8.
- Each password contains at least one single-byte
uppercase character and one single-byte number.
- A new password is not any of three most recent
passwords recorded in the password change log.

158 Security measures Initialization
when a user
forgets the
password

In the fifth NACCS, a user who has
forgotten the password must inquire
the NACCS center and wait for the
NACCS center to perform
initialization. For the sixth NACCS,
consider an improvement by whichusers can initialize their passwords bythemselves.

A new function is added in the URY procedure. So add
the following description accordingly.
(Addition)
To initialize a password, use one of the following ways:- When one user code has two or more identifying
numbers, the user can perform initialization. For details,
see the procedure specification of "User Information
Registration (URY)."- In other cases, ask the NACCS center.

40 /61

7.2 Network
7.4 User security measures
7.5 netNACCS and WebNACCS processing modes
and ebMS processing mode-

7.3 Qualification check

Revise the NACCS password
requirements for stronger security.
Users must understand the security
requirements (checking) of passwords,
and consider if their passwords need to
be changed.

7.3 Qualification check

A user who has forgotten the password can initialize it using the URY procedure
if one user code has two or more
identifying numbers.

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
159 Change ofdescription

Sub-item
Old system

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

Delete an explanation about the old system* Delete the description on the processing details in theold system (the fourth NACCS) in comparison with thefifth NACCS.

7.3 Qualification check7.5 netNACCS and WebNACCS processing modes
and ebMS processing mode

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Deletion)
To login to the old NACCS, a user who was involved in
multiple types of business had to login separately using
different pairs of user codes and identifying numbers.
(Deletion)
To login to the old NACCS, a user of package softwareof e-mail style processing mode had to perform two
authentication procedures, one for the user and one forthe mailbox ID.

160 Addition ofbusiness types(single sign-ongroups)Group
structure

Correct the description by adding a
new business type added in the sixth
NACCS. (Damage insurancecompany)

Do not make overall group restructuring from the fifth
NACCS.
Correct the description by adding a new business typeadded in the sixth NACCS.

7.3 Qualification check--(Change location)
Figure 6-3-3 Diagram of the single sign-on groupstructure for users involved in multiple business types

161 Package software Abolishmentof the e-mailstyle
processing
mode

Abolish basically the package
Abolish basically the package software of the e-mail7.3 Qualification checksoftware of the e-mail style processing style processing mode for personal computers. So
mode for personal computers.
change the description in the example of directly
However, deliver the package
connecting to NACCS using the package software of esoftware to the users under the
mail style processing mode for personal computers.
gateway as it is with the fifth NACCS.
Main descriptions to be corrected are as follows:* Delete a description related to the package software of
personal computers of e-mail style processing mode,and replace it with a description for users who build thee-mail style processing mode in the in-house system.
(Deletion)- 7.3.5.2 Single sign-on in e-mail style processing mode
(using package software)

Users who are using the package
software of the e-mail style processing
mode must use another package
software.

-

162 Change of screen Logon
image
screen- (None)--

163 Change ofdescription- (None)-Change the screen image, which is currently the XP
7.3 Qualification checkversion, to the Windows 8 standard screen, which isrecommended for the package software of personal
computers in the sixth NACCS.
Delete the description on the implementation application 7.4 User security measures
for wireless LAN.

41 /61In the fifth NACCS, a user who wants to use wireless LAN must submit an
implementation application for wireless
LAN to the NACCS center to assure thesecurity. This application becomes
unnecessary in the sixth NACCS.

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
164 Change ofdescription

Sub-item

Changes from Fifth NACCS

Change of- (None)records to beobtained for
logging by
users

Correction on EDI Specification

Relevant location in EDI Specification

Change the records to be obtained for logging, for theimport (export) declaration procedure conducted by apersonal computer under the gateway computer asfollows:

7.4 User security measures

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Passwords and IP addresses will be
excluded from the set of records to beobtained for logging. So the user mustchange the in-house system setting for
obtaining log records.

(Before change)
Records to be obtained for logging at the time of message
transmission is different between customs procedures and othercases (at transmission of messages of all other procedures).
The user password and the IP address of the personal computeror equivalent address information are retrieved only for customs
procedures.
(After change)
Abolish the difference in the information to be obtained for
logging.
Abolish the acquisition of the user password and the IP addressof the personal computer or equivalent address information.
Also, delete and add some descriptions as follows:(Deletion)
Note 1 and Note 2 of Table 7-4-6.

165 Change ofdescription

Change of- (None)records to beobtained for
logging by
users

Change the records to be obtained for logging, for theimport (export) declaration procedure conducted by apersonal computer under the gateway computer asfollows:

7.4 User security measures

Passwords and IP addresses will be
excluded from the set of records to beobtained for logging. So the user mustchange the in-house system setting for
obtaining log records.

-

7.4 User security measures

Passwords and IP addresses will be
excluded from the set of records to beobtained for logging. So the user mustchange the in-house system setting for
obtaining log records.

-(Before change)- User code
- Identifying number (only for transmitted messages)- Procedure code
- Date and time
- User password (only for transmitted messages)- IP address or equivalent address information of thepersonal computer that conducted a costumes
procedure (only for transmitted messages)(After change)- User code
- Identifying number (only for transmitted messages)- Procedure code
- Date and time
166 Change ofdescription

Change of- (None)records to beobtained for
logging by
users

Change the log management as follows for the casewhen a personal computer conducting a procedure
sends a message via a procedure server (a proxy
server, etc.).
(Before change)- User code, identifying number- Procedure code
- Date and time
- IP address of personal computer- User password(After change)- User code, identifying number- Procedure code
- Date and time

42 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
167 Change ofdescription

Sub-item
NACCS
connecting
routerChanges from Fifth NACCS- (None)Correction on EDI Specification

7.4 User security measures

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
A precaution is added for the connection
to the NACCS connecting router.

7.4 User security measures-

Relevant location in EDI Specification

Add a description on the handling of the NACCS
connecting router.
(Addition)
The console port is used for the setting of the NACCS
connecting router by the NACCS center. Users must notconnect any device to the console port.

168 Change ofdescription

Correction of - (None)a past date inexamplesThe date of the fifth NACCS update is currently used inexamples. Change it to the date of the sixth NACCS
update.

-Example:(Before change)
20051010(After change)
20181010

169 Network

Encryption
method(Reflect the specification of the fifth
NACCS.)
Change the encryption method usedin ebMS processing mode.
(Change from SSL3.0 to TLS1.0.)

Change the encryption method used in the ebMS
7.5 netNACCS and WebNACCS processing modes The network vendor will consider
processing from SSL3.0 to TLS1.0 for the support of the and ebMS processing mode
whether to indicate the SSL/TLS version
fifth NACCS.
in the EDI specification.
(February 16, 2015)
Indicate only TLS. Do not indicate theversion.

170 Change ofdescription

Change oftheencryption
method- (None)Change the encryption method as follows:(Before change)
128bit RC4 or 128-bit AES(After change)
128-bit AES

7.5 netNACCS and WebNACCS processing modes A user of an in-house system that usesand ebMS processing mode
128-bit RC4 must check the impact of
the change to 128-bit AES, and modify
the in-house system as necessary.

-

7.5 netNACCS and WebNACCS processing modes and ebMS processing mode
The currently practiced rule on thecertificates of the ebMS processing
mode has been explicitly described.

-

Add a description as follows:(Addition)
Review the encryption method in accordance with thesecurity condition.

171 Change ofdescription

Certificate in - (None)
ebMS
processingmode

Add the following two descriptions on the certificates in
ebMS processing mode.
(Addition)(4) Digital signature in ebMS processing mode
Use an electronic signature certificate provided by the
NACCS center.
(5) ebMS processing mode
Uses a server certificate provided by the NACCS center.

43 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
172 Change ofdescription

173 Change ofdescription

Sub-item

Changes from Fifth NACCS

User security - (None)measures

Audit targets - (None)

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Add the following two points on user security measures. 7.5 netNACCS and WebNACCS processing modes and ebMS processing mode
(Addition)(3) Anti-virus measures for mobile devices(4) Anti-theft and anti-loss measures for mobile devices
Correction on EDI Specification

Relevant location in EDI Specification

Add the following about user security measures.

7.6 System audit--(Addition)
Mobile devices are also audited.

174 WebNACCS
processing mode

Addition of a Allow NACCS users to access someconnection
procedures from mobile devices
example(smartphones and tablets).

175 Specification
change(abolishment of
message
reception
software)Message
reception
software oftheWebNACCS
processingmode

176 Change of
specification(abolishment of aprocessing mode)

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)Among connection examples of the webNACCS
7.5 netNACCS and WebNACCS processing modes Users will be able to use smartphones processing mode, add an example of connection from a and ebMS processing modeand tablets for the procedures that canmobile device (smartphone or tablet).
be performed in WebNACCS
processing mode.
* Mobile devices (smartphones andtablets) to be used for procedures musthave security measures specified
separately.

Stop providing the message reception Delete the description of the message reception
software that has been provided in the software that has been provided for receiving forms in
fifth NACCS for receiving forms in
the WebNACCS processing mode because the
WebNACCS processing mode.
provision of the software will be stopped.
In the sixth NACCS, forms will bereceived via Web browsers.
(Deletion)
Figure 7-5-7 Example of using both WebNACCS
processing mode and the netNACCS software

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.
Main descriptions to be deleted are as follows:* Delete only descriptions on the direct interface.
(Deletion)- Description on the connection test of the directinterface- Table 8-2-1 Hardware and software prepared by users

44 /61

7.5 netNACCS and WebNACCS processing modes Users that have been retrieving formand ebMS processing mode
messages using the message reception
software of the WebNACCS processing
mode will have to retrieve forms using a
web browser.

8.1 Outline and details of connection test
8.2 Preparation for connection test when joining
NACCS

Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
177 Change ofdescription

Sub-item

Changes from Fifth NACCS

Unification of - (None)
terms

Correction on EDI Specification

Relevant location in EDI Specification

Unify terms as below.
(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server

178 Switchover at
disaster

Restriction

For the sixth NACCS, change therestriction condition at the time of
backup center switchover so as toprohibit connection test after backup
center switchover.

Correct the text as follows:

8.1 Outline and details of connection test
8.2 Preparation for connection test when joining
NACCS

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

8.1 Outline and details of connection test

The users cannot conduct a connection test at the time of a serious fault and awide-scale disaster.

9.1 Outline of online change of settings made by
users

-

-

9.2 Flow of setting information from initialization tostart of procedure processing--(Before change)"great disaster" "connection test will be partly limited"(After change)"a serious fault and wide-scale disaster" "the connection
test is prohibited"*
In the EDI specification of the fifth NACCS, there is a
description that connection test will be partly limited. In
the sixth NACCS, however, the connection test is
stopped at the time of backup center switchover, andthis condition will be reflected in the specification.

179 Change ofConsolidation Consolidation of the port subsystem
specificationof a(consolidation of a subsystem
subsystem)(port
subsystem)

Change the description related the port subsystembecause it will be consolidated with NACCS..

180 Change ofdescription

The date of the fifth NACCS update is currently used inexamples. Change it to the date of the sixth NACCS
update.

Correction of - (None)a past date inexamples(Before change)* It required one or two days to update data in the portsystem when a password was changed by theprocedure of user information registration (URY), but it
will be done on the same day.
(After change)- (Delete: Because it will be consolidated with NACCS,
and the description will be changed)

Example:(Before change)
20051010(After change)
20181010

45 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-item
No.
181 Package software Abolishmentof the e-mailstyle
processing
mode

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Abolish basically the package
Abolish basically the package software of the e-mailAppendix 1 Matters Related to Connection Methods Users who are using the package
software of the e-mail style processing style processing mode for personal computers. So
and Processing Modes (Overview)
software of the e-mail style processing
mode for personal computers.
change the description in the example of directly
mode must use another package
However, deliver the package
connecting to NACCS using the package software of esoftware.
software to the users under the
mail style processing mode for personal computers.
gateway as it is with the fifth NACCS.
Main descriptions to be deleted are as follows:* Delete only descriptions on the personal computer
package software for e-mail style processing mode.
(Deletion)- Table 1-1 Matters related to connection methods andprocessing modes (overview)
Changes from Fifth NACCS

182 Network

Reconsiderat Abolish the dial-up line access.
ion of accesslines(abolishmentof dial-up
lines)
183 Change ofInteractive
Abolishment of the interactive
specification
processing
processing mode (direct interface)(abolishment of a mode (directprocessing mode) interface)

Correction on EDI Specification

Relevant location in EDI Specification

About access line types, delete the description of theaccess by dial-up line.

Appendix 1 Matters Related to Connection Methods Users who are using the access line
and Processing Modes (Overview)type under reconsideration must use
another access line.

-

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

Appendix 1 Matters Related to Connection Methods Users who use the interactive
and Processing Modes (Overview)processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

The following are major deletions:* Delete only descriptions related to the direct interface.
(Deletion)- Table 1-1 Matters related to connection methods andprocessing modes (overview)

184 Change ofdescription

Unification of - (None)
terms

Unify terms as below.

Appendix 1 Matters Related to Connection Methods and Processing Modes (Overview)(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server

46 /61-

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
185 Change ofdescription
location

Sub-item

Changes from Fifth NACCS

Change of a - (None)referenced
point.

Correction on EDI Specification

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Appendix 1 Matters Related to Connection Methods and Processing Modes (Overview)
Users that have been referring to thedescription of the retrieval of statistic
report information in Appendix 11 for thefifth NACCS must refer to Chapter 6.
Relevant location in EDI Specification

Change a document location being referred to as
follows due to the change of the structure of the EDI
specification. (The description on the statistic report
information described in Appendix 11 for the fifth
NACCS was moved to Chapter 6.).
(Before change)
Appendix 11Retrieval of Statistic Report Information(After change)
6. Retrieval of Statistic Report Information

186 Change ofdescription

Other
government
agencies- (None)Correct the text as follows:

Appendix 1 Matters Related to Connection Methods and Processing Modes (Overview)

187 Providing a more ebMS
concrete example processingof connectionmode- (None)188 Package software Abolishmentof the e-mailstyle
processing
mode

Abolish basically the package
Abolish basically the package software of the e-mailAppendix 2 Example of connection involving a data
software of the e-mail style processing style processing mode for personal computers. So
transmission/reception processing mode and amode for personal computers.
change the description in the example of directly
connection mode
However, deliver the package
connecting to NACCS using the package software of esoftware to the users under the
mail style processing mode for personal computers.
gateway as it is with the fifth NACCS.
Main descriptions to be deleted are as follows:* Delete only descriptions on the package software of
personal computers for e-mail style processing mode
(Deletion)- Table 2-1 One personal computer using two different
data transmission/reception processing modes- Table 2-2 Using two different datatransmission/reception processing modes on one
communication line
- Table 2-3 Using two different datatransmission/reception processing modes and different
connection modes on one communication line-

(Before change)
Other government agencies(After change)
Related government agencies
Add a connection example of a user who uses the ebMS Appendix 2 Example of connection involving a dataprocessing mode.
transmission/reception processing mode and aconnection mode

47 /61

To provide a more concrete description.

Users who are using the package
software of the e-mail style processing
mode must use another package
software.

-Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
189 Change of
specification(abolishment of aprocessing mode)

Sub-item

Changes from Fifth NACCS

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Correction on EDI Specification

Relevant location in EDI Specification

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

Appendix 2 Example of connection involving a datatransmission/reception processing mode and aconnection mode

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

(Deletion)- Appendix 2-4 Using router connection and the directinterface on one communication line
- Appendix 2-5 Using the direct interface and gateway
connection (SMTP/POP3) on one communication line
- Appendix 2-6 Using router connection, the directinterface, and gateway connection (SMTP two-way) on
one communication line

190 Network

191 Change ofdescription

192 Change ofdescription

Reconsiderat Abolish the dial-up line access.
ion of accesslines(abolishmentof dial-up
lines)
Deletion of- (None)description
on NACCSdedicatedterminals

About access line types, delete the description of theaccess by dial-up line.

Appendix 3 Example of System Construction

Users who are using the access line
type under reconsideration must use
another access line.

-

Change the description as follows because there is no
NACCS-dedicated terminal in the fifth NACCS.

Appendix 3 Example of System Construction--

Old system

Correct an explanation about the old system* Correct the description on the condition of the oldsystem (the fourth NACCS) in comparison with the fifth
NACCS.

Appendix 3 Example of System Construction--- (None)(Before change)
Dedicated to NACCS(After change)
For NACCS(Before change)
Example of an office constructing a system that uses
multiple NACCS-dedicated terminals for the old NACCS(After change)
Example of an office constructing a system that uses
multiple NACCS-dedicated terminals

48 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
193 Change ofdescription

Sub-item

Changes from Fifth NACCS

Unification of - (None)
terms

Correction on EDI Specification

Relevant location in EDI Specification

Unify terms as below.

Appendix 3 Example of System Construction

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server
194 Change ofdescription

Air- (None)
NACCS/SeaNACCS

Although words "Air-NACCS" and "Sea-NACCS" were Appendix 3 Example of System Constructiondeleted when the sea system and the air system wereconsolidated in the fifth NACCS, there are some that still
remain. So change those descriptions.
* The system names are prefixed by "air" or "sea" whennecessary for explanation.

--* Texts before and after deleted texts are not indicatedhere because there are many of them.

195 Change of
specification(abolishment of aprocessing mode)

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

Appendix 3 Example of System Construction

Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

(Deletion)- Figure 3-5 Example of a direct interface

196 Package software Abolishmentof the e-mailstyle
processing
mode

Abolish basically the package
Abolish basically the package software of the e-mailAppendix 3 Example of System Construction
software of the e-mail style processing style processing mode for personal computers. So
mode for personal computers.
delete the description in the example of directly
However, deliver the package
connecting to NACCS using the package software of esoftware to the users under the
mail style processing mode for personal computers.
gateway as it is with the fifth NACCS.
(Deletion)- Figure 3-6 Example of a personal computer shared by
Sea-NACCS and Air-NACCS (connection via a router)49 /61

Users who are using the package
software of the e-mail style processing
mode must use another package
software.

-Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
197 Adding adescription

198 Change ofdescription

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Describe that - (None)
the PNR01
procedure
can connect
to NACCS
with proper
constructionof an inhousesystem.

Add a description that the PNR01 procedure can be
performed in NACCS without using SITA/ARINC if an inhouse system (e-mail style processing mode / EDIFACT
messages) is properly constructed.

-

Correct the text as follows:- (None)Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

Appendix 4 Access Lines and Access Points--(Before change)
Center host
(After change)
Center server

199 Network

Reconsiderat Abolish the dial-up line access.
ion of accesslines(abolishmentof dial-up
lines)

About access line types, delete the description of theaccess by dial-up line.

Appendix 4 Access Lines and Access Points

Users who are using the access line
type under reconsideration must use
another access line.

-

200 Change ofdescription

Word
processor
software

Correct the description of the application software usedfor viewing NACCS EDI messages so that thedescription better represents the reality.

Appendix 5 Details of Processing Result Messages--- (None)(Before change)
In word processing software or text editor tool, a text
format NACCS EDI message (processing request
message)(After change)
In text editor tool, a text format NACCS EDI message(processing request message)

201 Change ofdescription-- (None)Examples of processing result codes of XML messages Appendix 5 Details of Processing Result Messages
are moved to one location. So change the description
location as follows:
Do not use "Appendix X."(Before the change of description location)
Appendix X(After the change of description location)
Appendix 5

50 /61

Users who were referring to Appendix X
about XML messages for the fifth
NACCS must refer to a different
appendix.

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
202 Change ofdescription

Sub-item

Changes from Fifth NACCS

Air- (None)
NACCS/SeaNACCS

Correction on EDI Specification

Relevant location in EDI Specification

Although words "Air-NACCS" and "Sea-NACCS" were Appendix 6 Codes
deleted when the sea system and the air system wereconsolidated in the fifth NACCS, there are some that still
remain. So change those descriptions.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Change)- Sea/Air classification in "Table 6-1 Output Message
Code system for Processing Result Messages"- Sea/Air classification in "Table 6-2 Output Message
Code system for Output Information Messages"* Change it to "Air/Sea" for explanation.

203 Change ofdescription-

Abolish the international interoperation Correct the text as follows:
acceptance server and implement theebMS server.
(Before change)
International interoperation acceptance server(After change)ebMS server

204 Change of
specification(abolishment of aprocessing mode)

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

Appendix 6 Codes

The server that has the international
interoperation function is changed in thesixth NACCS, but the function itself is
not changed. So the change does notaffect the users.
Let the in-house system users (users of
the international interoperation function)know that the name of the server haschanged in the EDI specification of thesixth NACCS.

Appendix 6 Codes

Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

Appendix 6 Codes-

Main descriptions to be deleted are as follows:* Delete only descriptions related to the direct interface.
(Deletion)- Table 6-4 Content of processing result notification
messages (common errors)- Table 6-5 User codes and identifying numbers fordifferent types of users- Table 6-6 System of identifying numbers

205 Change of error
codes

Deletion oferror codes

Delete an error code that is currently
not used.

Delete error code A0015 because it is not used in thefifth NACCS.
* Do not use the error code for another new error.

206 Change of error
codes

Change oferrors of
attachment
files- (None)Common error A0008 is output when an attachment file Appendix 6 Codes
exceeds the maximum size, but the error description"Invalid message size" is not easy to understand. So use
a new error code.
(Addition)
A0034: Attachment file (size (overall))
A0035: Attachment file (size (individual))
A0036: Attachment file (size individual))

51 /61-

Common errors are added. So a user of an in-house system that retrievescommon errors must check the system
for any impact.

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
207 Change ofdescription

208 Change ofdescription

Sub-item

Changes from Fifth NACCS

Other
government
agencies- (None)Old system- (None)Correction on EDI Specification

Relevant location in EDI Specification

Correct the text as follows:

Appendix 6 Codes

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

Remarks(Before change)
Other government agencies(After change)
Related government agencies
Delete an explanation about the old system
Appendix 6 Codes* Delete a description of the fifth NACCS that remains
for comparison with the old system (the fourth NACCS).

--(Deletion)* The old Air-NACCS, which had been online until
February 20, 2010, assigned user codes ("user codes
for in-house systems" hereafter) for DI or bidirectional
SMTP for users of in-house systems as necessary.
However, in-house system user codes cannot be used
for procedures of others government agencies. So use
only identifying numbers for identification from thecurrent NACCS. So five-digit user codes will be thesame as the codes for package software users, and inhouse system user codes will be basically abolished.

209 Security measures Initialization
when a user
forgets the
password

In the fifth NACCS, a user who has
forgotten the password must inquire
the NACCS center and wait for the
NACCS center to perform
initialization. For the sixth NACCS,
consider an improvement by whichusers can initialize their passwords bythemselves.

A new function is added in the URY procedure that
Appendix 6 Codes
enables the users to perform initialization and forces theusers to change the password after initialization. So add
the following description accordingly.

A user who has forgotten the password can initialize it using the URY procedure
if one user code has two or more
identifying numbers.

(Addition)
If a user forgets the password and initializes it, the user
must change the password.

210 Abolishment of in- house system user
codes (user codesfor DI and user
codes for SMTP)

Abolishment of in-house system user In-house system user codes (user codes for DI and user Appendix 6 Codes
codes (user codes for DI and user
codes for SMTP) are abolished, so delete relevant
codes for SMTP)
descriptions accordingly.

Users who were using the directinterface in the fifth NACCS will not beable to use it in the sixth NACCS.

* User IDs for SMTP were notused in the fifth NACCS.

211 Change ofdescription- (None)---

The number allocation orders for Sea-NACCS and Air- Appendix 6 Codes
NACCS were described but only the number allocation
order for Sea-NACCS were actually used. So delete thefollowing description from the EDI specification.
(Deletion)
Appendix 6 Codes- "First digit of two-alphanumeric-digit code"- Description on the number allocation order for AirNACCS* Because only the number allocation order of SeaNACCS is actually used
Other number allocation "I"* Because this number allocation is not actually used,
and will be used only when numbers are exhausted(Information)
NSS is implemented as described in the table. The
program must be changed if you want to modify thetable.
52 /61

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-itemNo.
212 Package software Abolishmentof the e-mailstyle
processingmode

213 Addition ofbusiness types(identifying
number)Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Abolish basically the package
Abolish basically the package software of the e-mailsoftware of the e-mail style processing style processing mode for personal computers. So
mode for personal computers.
delete the description of directly connecting to NACCS
However, deliver the package
using the package software of e-mail style processing
software to the users under themode for personal computers.
gateway as it is with the fifth NACCS.
(Deletion)- Table 6-6 Allocation of identifying numbers

Assignment Correct the description by adding aof identifying new business type added in the sixth
numbers
NACCS. (Damage insurancecompany)

Do not make an overall change from the fifth NACCS
about the allocation scheme of identifying numbers.
Correct the description by adding a new business typeadded in the sixth NACCS.

Appendix 6 Codes

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who are using the package
software of the e-mail style processing
mode must use another package
software.

Remarks

Appendix 6 Codes--

Table 6-7 List of supporting procedures
Table 6-8 List of output information codes
Table 6-9-2 List of commercial statistic reports--(Check List of Content ofProcedureSpecifications_2014.01.28_Ite
m No. 5)
Do not describe the tradecontrol subsystem because it
is not a NACCS procedure.

(Change location)
Table 6-6 Identifying number system* Use the numbering system of the old bank users as
the system of the identifying numbers of damage
insurance companies.
214 Change ofdescription-- (None)Change the formats of the following tables:
Table 6-7 List of supporting procedures
Table 6-8 List of output information codes
Table 6-9-2 List of commercial statistic reports

215 Reflecting thedesign content-

Add the procedures of the port
subsystem in different lists.

Add the procedures of the port subsystem in "Table 6-7 Appendix 6 Codes
List of supporting procedures" and "Table 6-8 List of
Table 6-7 List of supporting procedures
output information codes."Table 6-8 List of output information codes* Those are not provided for NACCS users because
they are government procedures. But list them forinternal uses.

-

216 Reflecting theresult of detailed
design-Add and delete accumulative
processing procedures and output
information codes.

Reflect the change in accumulative processing
procedures.

Users who use accumulative processing procedures and output information
codes that are to be changed must
understand the changes and modify
their in-house systems as necessary.

Appendix 7 Accumulative Processing Procedures

53 /61

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
217 Change of
specification(abolishment of aprocessing mode)

Sub-item

Changes from Fifth NACCS

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Correction on EDI Specification

Relevant location in EDI Specification

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

Appendix 8 Relationship between IP Addresses,
User Codes, Mailbox IDs, and Passwords

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

Main descriptions to be deleted are as follows:* Delete only descriptions related to the direct interface.
(Deletion)
Table 8-1 Content of IP addresses, user codes, mailbox
IDs, passwords, logical terminal names, and terminal
access keys
Table 8-2 Relationship between connection modes and
IP addresses, user codes, user passwords, mailbox IDs,
mailbox passwords, logical terminal names, andterminal access keys
Figure 8-1 Relationship between connection modes and
IP addresses, user codes, user passwords, mailbox IDs,
mailbox passwords, logical terminal names, andterminal access keys

218 Package software Abolishmentof the e-mailstyle
processing
mode

Abolish basically the package
Abolish basically the package software of the e-mailAppendix 8 Relationship between IP Addresses,
software of the e-mail style processing style processing mode for personal computers. So
User Codes, Mailbox IDs, and Passwords
mode for personal computers.
delete the description in the example of directly
However, deliver the package
connecting to NACCS using the package software of esoftware to the users under the
mail style processing mode for personal computers.
gateway as it is with the fifth NACCS.
(Deletion)- Table 8-2 Relationship between connection modes
and IP addresses, user codes, user passwords, mailbox
IDs, mailbox passwords, logical terminal names, andterminal access keys-> Description on the e-mail style processing mode forpeer-to-peer connection and connection via a router

Users who are using the package
software of the e-mail style processing
mode must use another package
software.

-219 WebNACCS
processing mode

Although they were received by themessage reception software in thefifth NACCS, abolish the message
reception software.

--

Logicalterminal
names andterminal
access keys
for
WebNACCSusers

The description on WebNACCS was made in the same Appendix 8 Relationship between IP Addresses,
place as netNACCS for the fifth NACCS. For the sixth
User Codes, Mailbox IDs, and Passwords
NACCS, however, we provide separate descriptions for
netNACCS and WebNACCS because the reportmessage reception software is abolished and theAccordingly, do not assign a logicalassignment of a logical terminal name and a terminal
terminal name and a terminal access access key becomes unnecessary for WebNACCS.
key to a user of WebNACCS only.
(Description location)
Table 8-2 Relationship between connection modes and
IP addresses, user codes, user passwords, mailbox IDs,
mailbox passwords, logical terminal names, andterminal access keys
Figure 8-1 Relationship between connection modes and
IP addresses, user codes, user passwords, mailbox IDs,
mailbox passwords, logical terminal names, andterminal access keys

54 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
220 Network

Sub-item

Changes from Fifth NACCS

Reconsiderat Abolish the dial-up line access.
ion of accesslines(abolishmentof dial-up
lines)

221 Package software Abolishmentof delivery of
the e-mailstyle
processing
mode

Abolish basically the user delivery of
the package software of the e-mailstyle processing mode for personal
computers.
However, deliver the package
software to the users under the
gateway as it is with the fifth NACCS.

Correction on EDI Specification

Relevant location in EDI Specification

About access line types, delete the description of theaccess by dial-up line.

Appendix 8 Relationship between IP Addresses,
User Codes, Mailbox IDs, and Passwords

The package software of the e-mail style processing
mode for personal computers will not basically be
distributed to users anymore. So delete the description
in the example of directly connecting to NACCS using
the package software of e-mail style processing modefor personal computers.

Appendix 9 Examples of Address Management ofProcess Result Messages (INQ, EXZ, and EXC
messages)

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who are using the access line
type under reconsideration must use
another access line.

Users who are using the package
software of the e-mail style processing
mode must use another package
software.

---(Deletion)- Table 9-1 Address management patterns for different
data transmission/reception processing modes

222 WebNACCS
processing mode

EXC
Although they were received by themessage to a message reception software in theuser who
fifth NACCS, abolish the message
uses
reception software.
WebNACCS
processing
Accordingly, add an advancemode only
checking that determines an EXC
message output to a WebNACCSonly user as an error.

Add a description that an input from NACCS package
Appendix 9 Examples of Address Management ofsoftware or an in-house system is determined an error if Process Result Messages (INQ, EXZ, and EXC
it makes an EXC message output for a WebNACCSmessages)
only user.
Add the following description as a note of "Table 9-1
Address management patterns for different datatransmission/reception processing modes."(Note 3) An input that makes an EXC message output
for a WebNACCS-only user is determined an error by
the processing of the procedure before the address
retrieval processing. Therefore, it is not possible to
make an address setting that outputs an EXC message
to a user of the WebNACCS processing mode.

55 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
223 Change of
specification(abolishment of aprocessing mode)

Sub-item

Changes from Fifth NACCS

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Correction on EDI Specification

Relevant location in EDI Specification

Delete the description of the interactive processing mode (direct interface) orchange it to another processing because the direct interface is abolished.
Main descriptions to be deleted are as follows:* Delete only descriptions related to the direct interface.
(Deletion)- Table 9-1 Address management patterns for different datatransmission/reception processing modes- Description on the output destination systems of the direct interface- Figure 9-6 Example of designating the second output destination to aterminal of a user (with conversion to in-house system user (ID of DI user)) of
the interactive processing mode (direct interface)

Appendix 9 Examples of Address Management ofProcess Result Messages (INQ, EXZ, and EXC
messages)

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

Following are the main change points:-> Changing to the setting example of bidirectional SMTP
(Addition)- Figure 9-3 Setting the destination of EXC mode information to a user of theinteractive processing mode (direct interface)- Figure 9-4 Example of setting the destination of EXC mode information to a
specific terminal of a user of the interactive processing mode (direct interface)- Figure 9-5 Example of setting the second output destination to a terminal ofa user of the interactive processing mode (bidirectional SMTP)

224 Network

E-mailaddress

Change the domain of e-mailaddresses.

The domains of the center and user e-mail addresses
are changed.

Appendix 9 Examples of Address Management ofProcess Result Messages (INQ, EXZ, and EXC
messages)

User must change the settings-

Appendix 9 Examples of Address Management ofProcess Result Messages (INQ, EXZ, and EXC
messages)

For input item tables of online
maintenance procedures, users shouldrefer to procedure specifications.

1.
before：naccs.customs
after：naccs6
2.
before：main.naccs.customs
after：prod.naccs6
225 Deletion of
Tables of- (None)procedure-specific input items of
information
on-linemaintenanceprocedures

Delete descriptions of procedure-specific information from the
NACCS EDI specification except when they are necessary for
explanation of the NACCS EDI specification.
Also, add a reference as below.
(Deletion)
Tables of input items of online maintenance procedures- Table 9-2 EXC-type destination management registration(UOC)- Table 9-3 Destination management registration for dual output
of export/import permission notifications etc. (UON)- Table 9-4 Email-type destination management registration(UOM)(Before change)
For details on the setting items of different patterns, see input
item tables of online maintenance procedures, which are Table
9-2 to 9-4.
(After change)
For details on the setting items of different patterns, see theprocedure specifications of online maintenance procedures.

56 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
226 Network

Sub-itemE-mailaddress

Changes from Fifth NACCS
Change the domain of e-mailaddresses.

Correction on EDI Specification

Relevant location in EDI Specification

The domains of the center and user e-mail addresses
are changed.

Appendix 10 Purposes of Mailboxes for Incoming
Messages

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
User must change the settings-

Remarks

1.
before：naccs.customs
after：naccs6
2.
before：main.naccs.customs
after：prod.naccs6

227 Package software Abolishmentof the e-mailstyle
processing
mode

Abolish basically the package
Abolish basically the package software of the e-mailUsers who are using the package
Appendix 10 Purposes of Mailboxes for Incoming Messages
software of the e-mail style processing style processing mode for personal computers. So
software of the e-mail style processing
mode for personal computers.
delete the description of directly connecting to NACCS
mode must use another package
However, deliver the package
using the package software of e-mail style processing
software.
software to the users under themode for personal computers.
gateway as it is with the fifth NACCS.
(Deletion)
Examples of the use of a mailbox of incoming messages
when using the package software of personal
computers (e-mail style processing mode)

228 Broadcast
messages

Review which processing modes use
broadcast messages, and clearly
indicate the relevant messages.

-

Review which processing modes use broadcast messages, andclearly indicate the relevant messages.
Also, refer the reader to relevant procedure specifications.

-

Appendix 11 Sending Broadcast Messages

WebNACCS users can view notifications A-301 Consideration on user
by clicking a link displayed on the
notification methods in the
WebNACCS login screen.
sixth NACCS

Appendix 11 Sending Broadcast Messages

Users who use the interactive
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

(Relevant processing modes being reviewed: deletion)- Interactive processing mode (direct interface)* Because the processing mode is abolished- Interactive processing mode (WebNACCS)* Because the message reception software is abolished- E-mail style processing mode (package software of personal
computers)* Because the provision of the package software is abolished(Addition)
NACCS EDI messages are supported. XML messages and
EDIFACT messages are not supported. For output content
details, see the output item table of the specification of thebroadcast procedure (accumulative processing) (1XB).
In the interactive processing mode (WebNACCS), however, theuser can view notifications by clicking a link displayed on the
WebNACCS login screen.

229 Change of
specification(abolishment of aprocessing mode)

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.
(Deletion)- Delete the description on broadcast message
transmission for the direct interface.

57 /61

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
Sub-item
No.
230 Package software Abolishmentof the e-mailstyle
processingmode

231 Change ofdescription

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Abolish basically the package
Abolish basically the package software of the e-mailAppendix 11 Sending Broadcast Messages
software of the e-mail style processing style processing mode for personal computers. So
mode for personal computers.
change the description in the example of directly
However, deliver the package
connecting to NACCS using the package software of esoftware to the users under the
mail style processing mode for personal computers.
gateway as it is with the fifth NACCS.
Main descriptions to be deleted are as follows:* Delete only descriptions on the personal computer
package software for e-mail style processing mode.
(Deletion)- Figure 11-1 Processing of broadcast messages

Unification of - (None)
terms

Unify terms as below.

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)
Users who are using the package
software of the e-mail style processing
mode must use another package
software.

Appendix 11 Sending Broadcast Messages--

Change the description to refer the reader to theprocedure specification about the layout, the reportformat, and the output item table of broadcast
messages.

Appendix 11 Sending Broadcast Messages

A user who wants to find out about the layout, the report format, and the output
item table of broadcast messages
should look at the procedure
specification.

Delete the description of the interactive processing
mode (direct interface) or change it to anotherprocessing because the direct interface is abolished.

Appendix 12 Dual Output Function of Export/Import Users who use the interactive
Permission Notification Etc.
processing mode (direct interface) mustchange the processing mode to anotherprocessing mode.

(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server

232 Change ofreferences-

Change the description to refer thereader to the procedure specificationof broadcast messages.

233 Change of
specification(abolishment of aprocessing mode)

Interactive
Abolishment of the interactive
processing
processing mode (direct interface)mode (directinterface)(Deletion)- Description on the dual output for the direct interface(Change)- Figure 12-2 Example of the output of importpermission notification (connection via the directinterface gateway)-> Change it to a setting example of bidirectional SMTP.

234 Change ofdescription-- (None)

EXC-type and EXZ-type messages are shown in the
figure explaining dual output. Because the output of
EXC-type and EXZ-type message requires a third party
input as a trigger, clearly indicate "end of examination"
as a third party input.

58 /61

Appendix 12 Dual Output Function of Export/Import Permission Notification Etc.

-

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
235 Change of
specification

236 Change ofdescription

Sub-item

Changes from Fifth NACCS

Correction on EDI Specification

Relevant location in EDI Specification

Envisaged Impact on Users in Migration
Remarks
to Sixth NACCS (Assumption)
A user who wants to use dual output of (*)
an item on the left must set the
The NACCS center must
requirement in the system setting inquiry correct the system setting
sheet (*).
inquiry sheet.

-

Allowing dual output of
Add the following as items for dual output.
unaccompanied article export- Unaccompanied article export permission notification
permission notification etc. (item 325) (Simple)- Unaccompanied article export permission notification(Document/Inspection)- Unaccompanied article export permission change
notification (Simple)
Unaccompanied article export permission change
notification (Document)

Table 12-3 List of export/import permission
notifications etc. for dual output-- (None)Appendix 12 Dual Output Function of Export/Import Permission Notification Etc.
Table 12-3 List of export/import permission
notifications etc. for dual output-

Unify the description of the information type of dual
output to A001A.
(Correction made for allowing dual output of
unaccompanied article export permission notification
etc.)(Before change)"Related to export declaration", "related to importdeclaration", and "related to import declaration of
petroleum product transport (total export)"(After change)"Related to export of exported articles andunaccompanied articles", "related to import", and"related to warehousing"

237 Reflecting theresult of detailed
design-Change online change procedures,
and add and abolish target items.

Reflect the changes of procedure specifications about
settings that can be changed online by users.

Appendix 13 List of Settings That Can Be Changed
Online by Users

Users who use online change
procedures and target items that are to
be changed must understand thechanges and modify their in-housesystems as necessary.

-

238 Change ofdescription-- (None)Delete the following description, which is not directly
related to the NACCS EDI specification.

Appendix 14-1 Outline of EDIFACT--(Deletion)- What is EDI?
- What is the benefit of EDI?

239 Change of current
descriptions(reflecting thechange of the
EDIFACT format)

Addition of
the PADISEDIFACT
format(Reflecting the specification added in Add the following explanation on the PADIS EDIFACT
the fifth NACCS)
format, which started to be used in the fifth NACCS.
The PADIS EDIFACT format are used
for NACCS, so add the relevant EDI (Locations of addition)
specification.
- Outline of EDIFACT- Mapping rule
- Message structure- Service segments- Subset names of EDIFACT-enabled procedures

59 /61

Appendix 14-1 Outline of EDIFACT
Any user (Airline) who uses the PNR01
Appendix 14-2-1 How to read the segment tableprocedure must send messages in theand the mapping table
PADIS EDIFACT format.
Appendix 14-2-2 Table 14-2-3 Message structure
Appendix 14-2-3 Service segments
Appendix 14-2-4 Table 14-4-1 List of subset namesof EDIFACT-enabled procedures-

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
240 Change ofdescription

Sub-item

Changes from Fifth NACCS

Correction of - (None)a past date inexamplesCorrection on EDI Specification

Relevant location in EDI Specification

The date of the fifth NACCS update is currently used inexamples. Change it to the date of the sixth NACCS
update.

Appendix 14-1 Outline of EDIFACT

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-

Example:(Before change)
20051010(After change)
20181010
241 Change of
specification(server
consolidation)

ServerAbolish the EDIFACT server andconsolidation divide its function into the mail server
and the XML conversion server.

Correct the text as follows:

242 Change ofdescription

Unification of - (None)
terms

Unify terms as below.

Appendix 14-2 EDIFACT mapping rule

The server that has the EDIFACT
function is changed in the sixth NACCS,
but the function itself is not changed. So
the change does not affect the users.
Let the in-house system users(EDIFACT users) know that the name ofthe server has changed in the EDI
specification of the sixth NACCS.

Appendix 14-2 EDIFACT mapping rule--

(Before change)
EDIFACT server(After change)
Mail server* "EDIFACT conversion processing" depending on thelocation in the document(Before change)
Customs clearance information processing system
Customs clearance information processing center
ServerRouterWeb serverCenter server(After change)
Nippon Automated Cargo and Port Consolidated
System
Nippon Automated Cargo and Port Consolidated
System,Inc or NACCS center
ServerRouterWeb server
NACCS center server
243 Change ofdescription-- (None)

Add the explanation on CUSRES and the unit ofprocessing results to be returned in the multi-format.

Appendix 14-2 EDIFACT mapping rule--

244 Change ofdescription-- (None)Consider deleting the outline on matters to beconsidered by any in-house system vendor when they
introduce EDIFACT.

Appendix 14-5 Introduction of EDIFACT messages

The user of an in-house system should
consult the vendor of the system about
how they develop the system.

-

Target: Appendix E-5 Introduction of EDIFACT
messages

60 /61

Remarks

Main Changes of EDI Spec
Appendix 16_1Main Changes of EDI Specification for NACCS (Reference)
Item
Item
No.
245 Change ofdescription

Sub-item-

Changes from Fifth NACCS- (None)Correction on EDI Specification

Relevant location in EDI Specification

Change "SITA" in the EDI specification as follows.

All over Appendix 14 (Description related to
EDIFACT messages)

Envisaged Impact on Users in Migration
to Sixth NACCS (Assumption)-(Before change)
SITA(After change)
Communication line provided by an aeronauticalcommunication company

246 Mapping table(XML)

Reading the
mapping
table (XML)- (None)Add an explanation on how to read the mapping table(XML).

61 /61

Appendix 15 XML Messages--

Remarks