6.2 Procedures for Retrieving Management Document Information(Using the Own System)
6.2.1 Communication Specification
As the communication protocol for retrieving management document information in NACCS,
TCP/IP is used for the network transport layer and HTTP for the upper layer.

6.2.1.1 Specification for Sending/Receiving HTTP
(1) HTTP Request/Response
Table 6-2-1 shows HTTP request methods that can be used when sending to the NACCS
Center server in management document information retrieval.
Table 6-2-1 Methods Used for Retrieving Management Document Information
Response of the
management document
Item
information
MethodOutlineNo.
retrieval server in theCenter(normal response)
1
POST
Make
a
processing
requestto
the As a normal response,management document information retrieval 200 and the processing
server in the Center and obtain the results.
results are returned.
In this specification, a processing request
message of 6.2.1.1 (2) also exists, but ineither case a processing request is madeusing the POST method.
(Note) The HTTP request method used in this specification is the only Post method.

(2) Types of Processing Request Messages
In management document information retrieval, processing request messages shown in
Table 6-2-2 exist in the user system and management document information retrieval
server in the Center. For each processing request message, a corresponding processing
result message exists and is sent to the user system as a response to the HTTP request.
Table 6-2-2 Types of Processing Request Messages
Item
No.
1

Message type

Description

Management document
information list request

2

Management document
information retrieval
requestObtain a list of management document information stored in
the management document information retrieval server in
the Center.
Retrieve management document information stored in the
management document information retrieval server in theCenter.

3

Management document
information re-retrieval
requestRe-retrieve management document information stored in the
management document information retrieval server in theCenter.

6-2-1

6.2.1.2 Sequence of Management Document Information Retrieval(1) Procedure Sequence
Figure 6-2-1 shows the sequence of retrieving management document information fromthe user system, and Figure 6-2-2 shows the sequence of re-retrieving management
document information.

The management
document informationthat the user wants toobtain is set from thelist of management
documents obtained.

Processing request message(Management document information list request(NACCS EDI message))
Response(Management document information list message(NACCS EDI message))

Processing request message(Management document information retrieval request(NACCS EDI message))

Response(Management document information message(attachment file message))...
Processing request message(Management document information retrieval request(NACCS EDI message))

Management
document
information
retrieval server

Response(Management document information message(attachment file message))

NACCS Center
serverUser system

Figure 6-2-1 Sequence of Management Document Information Retrieval[1] The user system sends a request message for retrieving a list of management
document information to the management document information retrieval server.
[2] The management document information retrieval server receives a request from theuser system and obtains the names and sizes of management document information
files.
[3] The management document information retrieval server returns the results to the user
system.
[4] From the management document list obtained, the user system sets the management
document information to retrieve.
[5] Based on the request from the user system [4], a management document information
retrieval request message is sent to the management document information retrieval
server.
[6] The management document information retrieval server obtains the management
document information based on the request message.
[7] The management document information retrieval server sends the management
document information obtained to the user system.
6-2-2

The management
document informationthat the user wants toobtain is set from the listof management
documents (for reretrieval) obtained.

Processing request message(Management document information list for re-retrieval(NACCS EDI message))
Response(Management document information list message for re-retrieval(NACCS EDI message))

Processing request message(Management document information re-retrieval request(NACCS EDI message))
Response(Management document information message(attachment file message))...
Processing request message(Management document information re-retrieval request(NACCS EDI message))

Management
document
information
retrieval server

Response(Management document information message(attachment file message))

NACCS Center
ServerUser system

Figure 6-2-2 Sequence of Management Document Information Re-retrieval[1] In order to re-retrieve management document information, the user system sends arequest message for retrieving a list of management document information for
re-retrieval to the management document information retrieval server.
[2] The management document information retrieval server receives a request for a list
from the user system and searches for files.
[3] The management document information retrieval server returns the search results tothe user system.
[4] From the management document list obtained, the user system sets the management
document information to re-retrieve.
[5] Based on the request from the user system, a management document information
re-retrieval request message is sent to the management document information retrieval
server.
[6] The management document information retrieval server obtains the management
document information already retrieved based on the request message.
[7] The management document information retrieval server sends the management
document information obtained to the user system.

6-2-3

(2) Important Notes(A) Message format in management document information retrieval procedures• The message format used in management document information retrieval
procedures shall be the attachment file message format.
See "6.2.2.1 Message Structure (2) Case of Attachment File Messages" for thedetails of attachment file messages.
• The management document information retrieval procedures and the
management document information re-retrieval procedures shall be of different
procedure codes.
(B) File compression format
Management document information is stored in the GZIP compression format in the
NACCS Center server and is transmitted as it is. Therefore, the user system must
decompress GZIP compressed files.
(C) Authentication at the time of management document information retrieval
The management document information retrieval server performs user
authentication using the user code (5 digits) + Identifying Number (3 digits) andpassword set in the message (NACCS EDI message) received from the user system.
Management document information can only be retrieved using the said user code.
In case of authentication error, a message indicating the authentication error isreturned to the user system.
(D) Management document information retrieval function
Management document information can be retrieved by implementing the interface
for retrieving management document information designed by NACCS center in theown system and by using HTTP connection.

6-2-4

6.2.2 Message Specification
In management document information retrieval, the NACCS EDI message format and theattachment file transmission message format are used.

6.2.2.1 Message Structure
Outline of structure of each message format is as follows.
(1) Case of NACCS EDI Messages
In management document information retrieval, NACCS EDI message format is used forprocessing request messages and processing result messages. Figure 6-2-3 shows theoutline of NACCS EDI messages.
NACCS EDI message

NACCS EDI message
Communication
protocol header(HTTP header)

Input (output)
commonfieldsProcedure-by-procedure
fieldsMax. 700,000 bytes (Note)
See "3. Message Format and Structure"(See "6.2.2.2 Content of Settings for Each Message")
Figure 6-2-3 Outline of NACCS EDI Messages

6-2-5

[1] Processing request messages
Figure 6-2-4 shows the format used when the user system sends processing request
messages (management document information list request, management document
information retrieval request, management document information re-retrieval request) tothe management document information retrieval server in the Center.
Communication protocol header(HTTP header)
POST
/XXX
HTTP/1.
1CR
C L Host: C L
R F XXX:80 R F

Content-type:Text/plain;charset="EUC-JP"C L Content
RF-Length:nnn

C L
RF

LF

NACCS EDI message
Input common fields

Procedure-by-procedure fields

CL
RF

…

CL
RF

…

–

…

CL
RF

Figure 6-2-4 Message Content[2] Processing result messages
Figure 6-2-5 shows the format used when the user system returns processing result
messages (management document information list message / management document
information message (error)) to the management document information retrieval server inthe center in response to processing request messages.
See Figure 6-2-6 below for processing result messages that include management
document information since management document information is returned to the user
system as compressed attachment files.
Communication protocol header(HTTP header)
CL
Content-Type:RFHTTP/1.
CL
CL
CL
Text/plain;C L Content-length: C L
1 200
Date:XXX
Server:XXXRFRFR F charset="EUC-J R F
nnn
RF
OK
P"

NACCS EDI message
Output common fields

…

CL
RF

Procedure-by-procedure fields
CL
RF

…

Figure 6-2-5 Message Content
6-2-6

–

…

C L
R F

(For reference) When the above message structure is viewed in a text format using text editor,
etc., it looks like the following.
Processing request messages
POST /XXX HTTP/1.1<CRLF>
Host:XXX:80<CRLF>

Communication protocolheader (HTTP header)Content-type:Text/plain;charset="EUC-JP"<CRLF>
Content-Length:nnn<CRLF><CRLF>
Input common fields
XXXXXXXXXXXX...XXX<CRLF>
Procedure-by-procedure
XXXX...XXX<CRLF>
fieldsXXXX...XXX<CRLF>

NACCS EDI message

Processing result message
HTTP/1.1 200 OK <CRLF>

Communication protocolheader(HTTP header)Date:XXXXX…XXX <CRLF>
Server:XXXXX…XXX<CRLF>
Content-type:Text/plain;charset="EUC-JP"<CRLF>
Content-Length:nnn<CRLF><CRLF>XXXXXXXXXXXX...XXX<CRLF>
Output common fields
XXXX...XXX<CRLF>
Procedure-by-procedure
XXXX...XXX<CRLF>
fields

NACCS EDI message(Note) "<CRLF>" may be seen differently depending on text editors, etc. used.

6-2-7

(2) Case of Attachment File Messages
Management document information is returned to the user system as an attachment filetransmission message. Figure 6-2-6 shows the outline of attachment file messages.

Communication
protocol header(HTTP header)

NACCS EDI message

Attachement data

(attachement fileinformation, etc.)(management
document information)

Max. 30,000,000 bytes(See "6.2.2.2 Content of Settings for Each Message")
Figure 6-2-6 Outline of Attachment File Messages

When the management document information retrieval server in the Center sends
management document information to the user system, the following format is used.
Figure 6-2-7 shows the details.
[1] Creating method
In NACCS, MIME (Multipurpose Internet Mail Extensions) is used when sending
management document information. Management document information is created inattachment file format.
The detailed specification for sending attachment file messages are as follows.







1.0 is set for the MIME version.
Content-Type shall be Multipart/mixed, and Text/plain is set for the NACCS
message part and application/octet-stream for the attachment file part.
BASE64 is set to Content-Transfer-Encoding of the attachment file part.
"Attachment" is set to Content-Disposition and a file name to "filename".
A file is composed of one management document information.
1 file is used as attachment data for each attachment file transmission message.

[2] Message image
 An attachment file transmission message is composed of communication
protocol header and body.
 NACCS EDI message and the body of attachment file encoded using BASE64
are set after <CRLF> following the HTTP header.

6-2-8

Communication protocol header(HTTP header)
Date
HTTP/1.
Server:Content
Mime
Content-Type::XX
1200 C L X
C L XXXC L -length: C L -Version C L multipart/mixed;
C LCL
OK
RF
RF
R F nnn
R F :1.0
R F boundary="YYYYY R F R F
Y"

Body
Text
-

-

(Hyphen)(Hyphen)YYY

Content-Type:TeYYY C L xt/plain;

Content
C L -Transfer

R F charset="EUC-JP R F -Encoding:"

8bit (Note)

Text
See
C L NACCS
C
C L
C L
EDI
R F
RL
message. R F
R F
F

Body
-

(Hyphen)(Hyphen)Attachment file part
- YYY
CLContent-Type:applicati
Content-T
Content-Dispo
YYY C L on/octet-stream;name= C L ransfer
C L sition:attachme C L R F
R F "File name";

R F -Encoding R F nt;filename="Fi R F:BASE64le name"Body
Attachment file part

-

-

YYY

-

-

Attachment file body C L(Hyphen)(Hyphen)YYY(Hyphen)(Hyphen)

R F(Note) The setting value of this item depends on the e-mail software used. "8bit" is just an
example.
Figure 6-2-7 Example of Structure of Attachment File Messages

6-2-9

<For reference>
When the message structure of the previous page is viewed in a text format using text
editor, etc., it looks like the following.
HTTP/1.1 200 OK<CRLF>
Date:XXXXX…XXX <CRLF>
Server:XXXXX…XXX<CRLF>
Content-length:nnn
Mime-Version:1.0<CRLF>
Content-Type:multipart/mixed; boundary="YYYYYY"<CRLF><CRLF>--YYYYYY<CRLF>
Content-Type:XX…X;charset="EUC-JP"<CRLF>
Content-Transfer-Encoding:8bit<CRLF><CRLF>

Communication
protocol header(HTTP header)

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX…XXX<CRLF><CRLF>--YYYYYY<CRLF>
Content-Type:application/octet-stream;name="File name"<CRLF>
Content-Transfer-Encoding:BASE64<CRLF>
Content-Disposition:attachment;filename="File name"<CRLF><CRLF>NACCS EDI
message

No repetition

ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ…ZZ
Body of attachment file
<CRLF>--YYYYYY-[3] Name and format of attachment file
• File name: See management document information file name in "Appendix Table
6-2-8 Procedure-By-Procedure Fields (Management Document Information List
Message)".
• Data format: The extension of ".edi" is set for NACCS EDI format, and ".csv" for CSV
format. Since files are compressed to GZIP format, the extension of ".gz" is used after
the compression.

6-2-106.2.2.2 Content of Settings for Each Message
The content of settings for each message is as follows.
(1) Settings for Management document Information List Request Messages[1] HTTP header
Table 6-2-3 shows the content of settings for HTTP header in management document
information list request messages.
Table 6-2-3 HTTP Header (Management document Information List Request Message)
Item
Item
SettingNo.
1
Request line
POST /naccs/os HTTP/1.1<CRLF>
POST shall be set to the request method.
HTTP/1.1 shall be set to the HTTP version.
If not, an error will result.
2

HOST

3

Content-Type

4

Content-length

HOST:IP address 80<CRLF>
80 shall be set to the port number.
If not, an error will result.
Content-Type:Text/plain;charset="EUC-JP"<CRLF>
Fixed.
Content-length:nnn<CRLF>
The message size of shall be set in place of "nnn".
If not, an error will result.

6-2-11

[2] Input common fields
Table 6-2-4 shows the content of settings for input common fields inmanagement document information list request messages.
Table 6-2-4 Input Common Fields(Management Document Information List Request Message)
Item
No.
1

Field name

Length(Reserved area)

3(Space is set as a fixed value)

2

Procedure Code5

?LST△ (△ indicates a single-byte space)3(Reserved area)

21(Space is set as fixed value)

4

User code

5

5

3

6

Identifying
Numbers
User password

User code, Identifying Number, and user password
are set and used for user identification

7(Reserved area)

319(Space is set as a fixed value)8

System identifier

1(2 is set as a fixed value)

9(Reserved area)

27(Space is set as fixed value)10

Message length

6

Indicates the length of NACCS EDI message(including input common fields)
000409 (Fixed)

Settings

8[3] Procedure-by-procedure fields
Table 6-2-5 shows the content of settings for procedure-by-procedure fields inmanagement document information list request messages.
Table 6-2-5 Procedure-By-Procedure Fields(Management Document Information List Request Message)
Item
No.
1

2

Field namelengthSettings

Outputinformation code

7

Delimiter2

A space shall be set in case of normal retrieval.
The output information code subject to re-retrieval
shall be set in case of re-retrieval (Note).
<CRLF> shall be set.

(Note) Since the volume of the information subject to re-retrieval is assumed to be large, theinformation subject is extracted by output information code.
Therefore, the output information code shall be set in case of re-retrieval.

6-2-12

(2) Settings for Management Document Information List Messages[1] HTTP header
Table 6-2-6 shows the content of settings for HTTP header in management document
information list messages.
Table 6-2-6 HTTP Header (Management Document Information List Message)
Item
Item
Settings
No.
1
Status line
HTTP/1.1 200 OK<CRLF>
HTTP/1.1 shall be set to the HTTP version.
2
Date
The date and time when the message is generated shallbe set. ((day of the week), dd MMM YYYY HH:mm:ss
GMT format (Example: Thu, 28 May 2018 23:59:45
GMT))
3
Server
The information of the transmitting server shall be set.
4

Content-Type

5

Content-length

Content-Type:Text/plain;charset="EUC-JP"<CRLF> is
Fixed.
Content-length:nnn<CRLF>
The message size of transmission message shall be set
in place of "nnn".

6-2-13

[2] Output common fields
Table 6-2-7 shows the content of settings for output common fields in management
document information list messages.
Table 6-2-7 Output Common Fields (Management Document Information List Message)
Item
Field name
LengthSettings
No.
1(Reserved area)
3(Note 1)
2

Procedure Code5

The same procedure code as that forprocessing request messages shall be set(?LST△ (△ indicates a single-byte space))3

Output information code

7

4

Date of Message Receipt

14

5

User code

5

6(Reserved area)

211

Normal case: CAQ0160
Procedure error case: *C?LST△
Common error case: *CCMSG△(△ indicates a single-byte space)
The message reception date and time shall beset(yyyymmddhhmm△△)
The user code of the user who receives themessage shall be set(Note 1)7

Message Divisioncontrolsequence
information number
Termination

3

Normal case: 001
Error case: 000

1

E (Fixed)

Message
type(Reserved
area)(Reserved area)

1
3

Normal case: M
Error case: R(Note 1)110(Note 1)

8
9
10
11
12

1

Q (Fixed)

13

Message
destination
control format(Reserved area)

28(Note 1)14

Message length

6

Indicates the NACCS EDI message length
000400–700000(The maximum message length is 700,000)(Note 1) The reserved area is used for the system control.

6-2-14

[3] Procedure-by-procedure fields
Table 6-2-8 shows the content of settings for procedure-by-procedure fields inmanagement document information list messages (normal case).
Table 6-2-8 Procedure-By-Procedure Fields(Management Document Information List Message)
Item
No.
1

2

Field name

LengthSettings

Processing result code75

Delimiter

200000-0000-0000△–△(The processing result code shall be
set to the leading 15 digits andspaces to the following 60 digits)<CRLF>

3

Outputinformation
code (Note 2)

7

4

Target date

65

Delimiter

1

The output information code
indicating the management
document information shall be set.
The date of data subject to editing
shall be set (yymmdd format)_ (Underscore)

65

The destination user shall be set

7

Destination
user
code
Delimiter (Note 4)

1_ (Underscore)

8

Subject (Note 3)

910Management
document
file name

Max.
64
1

Delimiter (Note 4)

The importer/exporter
shall be set_ (Underscore)

code,

etc.

Copy source user
code (Note 5) (Note6)
Delimiter5

The user code for the copy source
shall be set

1_ (Underscore)

12

Creation
time

14

13

Extension

4

The system date and time when thetransmission file is edited in the
NACCS Center server shall be set(yyyymmddhhmmss format).csv or .edi shall be set

14

Extension3.gz shall be set

15(Reserved area)

16(Note 1)
11

date

and

16

Delimiter (Note 1)

2<CRLF>

17

Size (Note 1)

8

File size (Unit: byte)

18

Delimiter (Note 1)

2<CRLF>(Note 1)

When there are multiple management document files, item no. 3 to 18 are
repeated.item no.3 to 14 are variable length.

(Note 2)

When packaged software is used to retrieve management document
information, the packaged software converts the output information code into
6-2-15

Procedure Specification number + management document information name
(Japanese), and therefore the following naming scheme is used.
Procedure Specification number + Management document information name
(Japanese) + Target date + _+ Destination user code + _ + Division sequence number + _ + Importer/exporter
code, etc. + _ + Copy source user code, etc. + _ + Creation date and time.csv(Example of file name of management document information converted by packaged
software)
I99 Management document information retrieval data181100_3ANTT_001_ABCDE0000000_1ANTT_20181208091024.csv(Note 3)This field is used when the same management document information is output asingle destination by splitting it into multiple files and for reports created on
as-needed basis.
(Note 4) "_"s (underscores) in front of and following the field 8 "Subject" are output withthe "Subject" and are not output when "Subject" is not output.
(Note 5) This field is used only when the management document information transmitted
to a user is to be transmitted to another user. When "_Subject_" is included in
the management document information of copy source user code, its content is
output in front of this field.
(Note 6) When the field 8 "Subject" is output and the copy source user code is not output,
2 underscores may be output side-by-side.

6-2-16

Table 6-2-9 shows the content of settings for procedure-by-procedure fields in management
document information list messages (error case).
Table 6-2-9 Procedure-By-Procedure Fields(Management Document Information List Message)
Item
No.
1
2

Field name

LengthSettings

Processing
result code75

Delimiter

2

Processing result code indicating the error(15-digit processing result code is repeated atmost 5 times.)<CRLF>

6-2-17

(3) SettingsforManagement
Document
Information
RetrievalRequestMessage/Management document Information Re-Retrieval Request Messages[1] HTTP header
Settings are the same as that for management document information list request
messages. (Table 6-2-3)[2] Input common fields
Table 6-2-10 shows the content of settings for input common fields in management
document information retrieval request messages/management document
information re-retrieval request messages.
Table 6-2-10 Input Common Fields (Management Document Information Retrieval Request
Message/Management Document Information Re-Retrieval Request Message)
Item
Field name
LengthSettings
No.
1(Reserved area)
3(Space is set as fixed value)
2

Procedure Code5

Management document information retrieval request
message: ?GTN△ (△ indicates a single-byte space)
Management document information re-retrieval
request message: ?GTP△ (△ indicates a single-byte space)(Space is set as fixed value)

3(Reserved area)

21

4

User code

5

5

3

6

Identifying
Numbers
User password

7(Reserved area)

319(Space is set as a fixed value)8

System identifier

1(2 is set as a fixed value)

9(Reserved area)

27(Space is set as fixed value)10

Message length

6

Indicates the length of NACCS EDI message(including input common fields)
000530 (Fixed)

User code, Identifying Number, and user password
are set and used for user identification

8[3] Procedure-by-procedure fields
Table 6-2-11 shows the content of settings for procedure-by-procedure fields inmanagement document information retrieval request messages/management
document information re-retrieval request messages.
Table 6-2-11 Procedure-By-Procedure Fields(Management Document Information Retrieval Request Message/Management
Document Information Re-Retrieval Request Message)
Item
No.
1

2

Field name

LengthSettings

File name

128

Delimiter

2

The file name of the management document
information file to be retrieved shall be set. At
most 128 bytes in accordance with the field"Document information file name" in management
document information list messages.
<CRLF>

6-2-18

(4) Settings for Management Document Information Messages[1] HTTP header
Table 6-2-12 shows the content of settings for HTTP header in management
document information messages.
Table 6-2-12 HTTP Header (Management Document Information Message)
Item
Item
Settings
No.
1
Status line
HTTP/1.1 200 OK<CRLF>
HTTP/1.1 shall be set to the HTTP version.
In case of normal response, 200 shall be set to thestatus code.
2

Date

3

Server

The date and time of the message generation shall beset. ((day of the week), dd MMM YYYY HH:mm:ss
GMT format (Example: Thu, 28 May 2015 23:59:45
GMT))
The information of the transmitting server shall be set.

4

MIME-version

In NACCS, "1.0" shall be set.

5

Content-Type

6

Content-length

In normal case, multipart/mixed;boundary = "Arbitraryvalue" shall be set.
In
case
of
error,"Content-Type:Text/plain;charset=EUC-JP<CRLF>" shall be set.
Content-length:nnn<CRLF>
The message size of shall be set in place of "nnn".

6-2-19[2] Output common fields
Table 6-2-13 shows the content of settings for output common fields in management
document information messages.
Table 6-2-13 Output Common Fields (Management Document Information Message)
Item
Field name
LengthSettings
No.
1(Reserved area)
3(Note 1)
2

Procedure Code53

Output information code

7

4

Date of Message Receipt

14

5

User code

5

6(Reserved area)

211

7

8
9
10
11

Messagecontrol
information

The same procedure code as that forprocessing request messages shall be
set.
• Normal response or procedure error
response of management document
information
retrievalrequestmessages: *C?GTN△• Commonerror
responseofmanagement document information
retrievalrequestmessages:*CCMSG△• Normal response or procedure error
response of management document
information
re-retrieval
requestmessages: *C?GTP△• Commonerror
responseofmanagement document information
re-retrieval
requestmessages:*CCMSG△(△ indicates a single-byte space)
The message reception date and timeshall be set(yyyymmddhhmm△△)
The user code of the user that receives
the message shall be set(Note 1)Divisionsequence
number3

Termination

1

Message type1

000–999
The serial number shall be set
according to the number of divisions of
the management document.
If the document is not divided, 000 shallbe set.
"E" shall be set for the last message.
A single-byte space shall be set
otherwise.
R (Fixed)

3(Note 1)

110

(Reserved
area)(Reserved area)

1

13

Message destination control
format(Reserved area)

The information set for the processing
request message shall be output as it is.
Q (Fixed)

28(Note 1)14

Message length

6

12

Indicates the NACCS EDI message
length000477 (Fixed)(Note 1) The reserved area is used for the system control.

6-2-20[3] Procedure-by-procedure fields
Table 6-2-14 shows the content of settings for procedure-by-procedure inmanagement document information messages.
Table 6-2-14 Procedure-By-Procedure Fields (Management Document Information Message)
Item
Field name
LengthSettings
No.
1
Processing
75
Normal case: 00000-0000-0000
result code
(The processing result code shall be set to theleading 15 digits and spaces to the following 60
digits)Error case: Processing result code indicating the
error

2

Delimiter2(15-digit processing result code is repeated atmost 5 times)<CRLF>[4] Attachment File
Normal case: Management document information encoded using BASE64 shall be
attached.
Error case: No attachment file exists.

6-2-21

6.2.2.3 Naming Scheme of Management Document Information Files
The file name of CSV format private management document information is described asfollows.
(1) File Name of CSV Format Management Document Information
Output information code ([1]) + Target date ([2]) + _ +Destination user code ([3]) + _ + Division sequence number ([4]) + _ +Importer/exporter code, etc. ([5])+ _ + Copy source user code, etc. ([6]) + _ + Creation date and time ([7]).csv(2) File Name of Management Document Information Retrieved by Packaged Software(After the retrieval, packaged software converts the file name and then stores it)
Procedure Specification number + Management document information name
(Japanese) ([1]') + Target date ([2]) + _ +Destination user code ([3]) + _ + Division sequence number ([4]) + _ +Importer/exporter code, etc. ([5])+ _ + Copy source user code, etc. ([6]) + _ + Creation date and time ([7]).csv
[1]:
[1]':
[2]:
[3]:
[4]:
[5]:

[6]:

[7]

Indicates the output information code of the management document information.
Indicates the document number of Procedure Specification, which describes the
specification of management document information, and Japanese name of the
management document information.
Indicates the date of the data subject to editing.
YYMMDD model (YY indicates the lower 2 digits of the year).
* YYMM00 is used for monthly reports, and YY0000 for annual reports.
Indicates the destination user.
Indicates the serial number when output is divided. "Serial number + E" shall be output
for the last file.
Indicates the importer/exporter code, etc. (Optional output)* This field is used when the same management document information is output asingle destination by splitting it into multiple files. In addition, for management
document information for which reports are created on as -needed basis,"ZUIJI_Serial No. of Receipt", "ZUIJI_Serial No. of Receipt_Serial number", or"ZUIJI_Importer/exporter code, etc._Serial No. of Receipt_Serial number" is added.
The content of output shall be set according to each output. See the "ProcedureSpecification" for management documents that are output as multiple files and theunit of output. See "Appendix Table 6-9-2 List of Private Management document
Information" for management document information for which reports are createdon as-needed basis.
Indicates the copy source user code. (Optional output)* This field is used when the management document information transmitted to auser is to be transmitted to another user. When "_Importer/exporter code, etc._" isincluded in the file name of copy source management document information,"_Importer/exporter code, etc._" is output in front of this field.
Management documents transmitted to other users are those specified in theProcedure Specification or those set by NACCS Center according to the requests
from the users.
* When the importer/exporter code, etc. ([5]) is output and this field ([6]) is not out put, 2underscores may be output side-by-side. (See below (Example 3))
Indicates the system date and time when the transmission file is edited in the NACCS
Center server.
(Note) "_" (underscore) in front of the item [4] is output with the item [4] and is not
output when the item [4] is not output.
(Note) "_"s (underscores) in front of and following the item [5] are output with the item
[6] and are not output when the item [5] is not output.

6-2-22

Examples of the file name of CSV format private management document information
retrieved by the own system are described as follows.
(Example 1) Case of normal daily transmission management document information(Management document information edited on December 9, 2018 at 04:50:12 to betransmitted to 1ANAC(Daily report) (Data is of December 8))
AAA9990181208_1ANAC_20181209045012.csv└Output information code
(Example 2) Case of transmitting the management document information of the user of(Example 1) also to 3ANAC
AAA9990181208_3ANAC1ANAC_20181209045012.csv(Example 3) Case of monthly transmission management document information for which
importer/exporter code, etc. is set for the file name(Management document information edited on Saturday, December 08, 2018 at 09:10:24
to be transmitted to 1ANAC(Monthly report) (Data is of November))
AAA9990181100_1ANAC_ABCDEFGHIJKL__20181208091024.csv: Management document information of the importer ABCDEFGHIJKL
AAA9990181100_1ANAC_MNOPQRSTUVWX__20181208091024.csv: Management document information of the importer MNOPQRSTUVWX(Example 4) Case of transmitting the management document information of the user of(Example 3) also to 3ANAC
AAA9990181100_3ANAC_ABCDEFGHIJKL_1ANAC_20181208091024.csv: Management document information of the importer ABCDEFGHIJKL
AAA9990181100_3ANAC_MNOPQRSTUVWX_1ANAC_20181208091024.csv: Management document information of the importer MNOPQRSTUVWX(Example 5) Case of transmitting the management document information of the user of(Example 1) by dividing it into 3 files
AAA9990181208_1ANAC_001_20181209045012.csv
AAA9990181208_1ANAC_002_20181209045012.csv
AAA9990181208_1ANAC_003E_20181209045012.csv

6-2-23

6.2.3 Handling Errors(1) Errors due to the Settings for HTTP Header
Table 6-2-15 shows handling errors occurred at the time of HTTP request.
Table 6-2-15 Handling Errors at the Time of HTTP Request
Item
No.
1

MethodPOST

Assumed errors and handling them
HTTP request is made, but no response is returned from the management
document information retrieval server in the Center.
<Causes and handling>• The destination port number is incorrect→ Confirm that a connection to the port number 80 is requested.
• The NACCS Center server is under maintenance.
→ Check the information on the maintenance of the NACCS Center
server disclosed on the NACCS Information. If it is under maintenance,
try re-connecting after the completion of the maintenance.
• The NACCS Center server and/or network is in failure.
→ Try re-connecting after some time. If it is not recovered for a long time,
request for investigation to the help desk in NACCS Center.
The failure information is also disclosed on the NACCS Information.
Since the information on the maintenance and failure of the server for
testing connection is not disclosed on the NACCS Information however,consult NACCS Center for the status of the NACCS Center server when aconnection to the server fails for a long time during the hours whenconnection tests can be performed.
An error response (other than the normal response (200)) is returned.
<Causes and handling>[1] The destination URL is incorrect. (403 or 404)
→ Confirm that the URL notified by NACCS Center is specified.
[2] The HTTP header is incorrect. (400)→ Create the correct HTTP header and retry.

6-2-24

6.2.4 Others(1) Limits
When performing management document information retrieval in the user system, thefollowing must be met.
[1] Management document information retrieval in the user system is available only
when leased connection or optical broadband connection is used for the access line.
[2] Due to the restrictions on the capacity of the management document information
retrieval server, the information must promptly be retrieved on (or after) thetransmission date and time in the user system.
[3] In order to avoid delay in response associated with the concentration of retrieval
requests from some users, users of the own system must meet the following
conditions.
 Retrieval requests from the same own system shall not be made by multiple
users at the same time.
 Retrieval requests for multiple reports shall not be made by the same user at thesame time.
(2) Other notes
Users of management document information retrieval (in the own system) need to pay
attention to the following.
[1] Under heavy load of the system, operational restrictions such as not accepting
messages from all users may be enforced. In this case, NACCS Center will notify
users via telephone, FAX, or the NACCS Information, etc.
[2] The environment for conducting a connection test shall be set up within thepremises of a backup site. Therefore, in the event that the primary site is affected bya large-scale failure or a large-scale disaster, etc., normal operation will be
implemented at the backup site and a connection test at the backup site may be
unavailable.

6-2-25

6.2.5 Values of Various Timers
Table 6-2-16 shows the timer values specified for management document information retrieval(in the own system). In addition, Figure 6-2-8 shows the location of setting each timer.

Table 6-2-16 Timer Values
Monitoring content
Timer value
T01
HTTP connection between the user terminal and the Specified by the user
management document information retrieval server in theCenter when transmitting from the user side.
(Note) T01 in the ID column of Table 6-2-16 indicates the ID of the timer shown in Figure 6-2-8.
ID

HTTP Client of theuserManagement document
information retrieval
server in NACCS Center
Processing request

T01

Figure 6-2-8 Timer Setting during Normal Connection

6-2-26