3.5 Message Control Items
In using NACCS, the following items are used to identify processing results messages responding toprocessing request message and to construct messages.
Table 3.5.1 summarizes the outline of message control items.
Table 3.5.1 Outline of Message Control Items
Field name
Input Message ID

Outline"Input Message ID" set in theprocessing request message isreflected in the processing result
message responding to theprocessing request message.

Usage
To identify processing result
messages responding toprocessing request
messages.

Message Tag

To match Processing request
message and its corresponding
processing result message.

To identify processing result
messages responding toprocessing request
messages and to identify aseries of processing result
messages responding toprocessing request message.

Index Tag

In inquiry processing, if theprocessing result message exceeds
the maximum message length
specified in ProcedureSpecifications, and does not fit in asingle processing result message,
and there is consecutive
information, the tag will be output
from the NACCS Center server.
Continued processing enables theuser to retrieve complete data.

To continue processing toretrieve all query results.

Note: Refer to Appendix
Table 6.8 "Output Information
Code List".

3-5-1＜2019.03 Update＞

Table 3.5.2 shows Input Message ID, and Message Tag in a processing request message (upstreamtransmission message), and Input Message ID and Message Tag set in the downstream transmission
message.
Table 3.5.2 Input Message ID and Message Tag
INQ Type (Note 1)

○

○

○

Space

[C]

○

○

Query result[M](successful completion)○○

Query result (error)

○

○

[R]

Output Message

For printer [P, A]
Non-query result, forscreen[R]

Message for filing [F, P](Note 3)Message for storage[U]

Message for user's own
interface[T]○Spaces＼EXC Type (Note 1)

Input
Input
Input
Message
Message
Message
Message
Message
MessageTag
TagTag
IDIDID

Message Type

Processing result notification
message

EXZ Type (Note 1)○SpaceSpace(Note 2)Space

Input Message ID: Space
Message Tag: Message tag which the user set in the input
common fields of the processing request message.
○○SpaceSpaceor Space○SpaceSpaceSpace

Data set in the processing request message is reflected as it is.
Spaces are to be set.
Not applicable.

(Note 1)
(Note 2)For details of INQ type, EXZ type and EXC type, see "5 Message Destination Control".
Usually spaces are to be set. However, for some output messages which are output
during automatic activation during office operating hours, or when a message is output
to shared terminals, there are some cases where the Input Message ID which is set in
the processing request message is set as is.
(Refer to EXC column for Message Destination Control Format specified in "Appendix
Table 6.8 Output Information Code List."(Note 3)

INQ type, EXZ type and EXC type are not applicable to messages for filing.
(However, in order to specify a destination type for an In-File delivery message, avalue of 'K' is used as a formality in Message Destination Control Format in the output
common fields in the message for filing [P]. By doing so, 'K' is specified in Message
Class in the incoming message list on the personal computer software package.)

3-5-2＜2019.03 Update＞

3.5.1

Input Message ID

In NACCS, a value specified in Input Message ID in user's processing request message isautomatically transferred to the corresponding processing request message.
The user can randomly choose a value for Input Message ID. If the user maintains a unique
numbering system of Input Message ID in a certain period of time, the user can match a processing
result message with its corresponding processing request message.
However, because spaces are filled in Input Message ID in the EXC type message, another data
element in the output common fields or the process specific segment elements (such as B/L number /AWB number and declaration number) needs to be used for matching a processing request and its
corresponding response message.
Table 3.5.3 shows setting of Input Message ID in a response message.
Table 3.5.3 Setting of Input Message ID in a response message
Message
Input Message ID
Destination
Control Format
INQ Type
A value in Input Message ID in the processing request
message is specified.
EXZ Type
A value in Input Message ID in the processing request
message is forwarded and specified.(Note)
EXC Type
Spaces are specified.
Note that for some types of output messages, and message
type [U] transaction status notice messages during transaction
processing for cargo transportation declarations or for
declarations during office operating hours, a value for Input
Message ID in the processing request message is forwarded
and specified.(Note)(Note)
EXZ type messages and EXC type messages are output in response to a third party
event. However, these are not "Input Message ID" for processing request messages, which
are specified by a third party.
Figure 3.5.1 describes a sample usage of Input Message ID (10 digits) in NACCS.
User system

NACCS Center serverTransaction Request(Input Message ID: B)

BB

Transaction
Processing Result Notification

B

Transferred to the
response as it is

INQ TypeTransferred to theresponse as it is

INQ Type

Output Information

B☆

Output Information

Transferred to theresponse as it is
EXZ Type

B

Depending on atransaction type, spaces
are specified. Refer toTable 3.5.3 for details.

☆

Output Information
Spaces arespecified△△△

EXC Type

Figure 3.5.1 Sample usage of Input Message ID
3-5-3＜2019.03 Update＞

3.5.2Message Tag, Message Control Information (Division Sequence Number,Termination, Message Type)

Users may receive more than one transaction output message for a single processing request message. Inorder to identify the multiple outputs as a group, values in Message Tag and Message Control Information(Division Sequence Number, Termination, Message Type) in the output common fields in a response
message are used in NACCS.
Table 3.5.4 describes Message Tag, and Table 3.5.5 describes Message Control Information (DivisionSequence Number, Termination, Message Type). And the numbering rule of Division Sequence Number isdescribed in Table 3.5.6, and a sample usage of Input Message ID, Message Tag and Message ControlInformation is described in Figure 3.5.2.

Table 3.5.4 Message Tag
Message TypeMessage
TypeProcessing result
notification message[R][C]

Output Information
Message[M][P], [A](Note 1)

(Note 2)

NameDivision
Sequence
NumberTermination

Description
In a processing result message (For screen [R], [C], [M]), the value in theMessage Tag set in the input common fields of its corresponding processing
request message is specified as is.
If a user maintains a unique numbering system of Message Tag, the user canretrieve a series of processing result messages. (Note 1)
In a processing result message (For printer [P], [A]), Message Tag is filledwith spaces. (Note 2)

When using a personal computer with a software package provided by NACCS, a uniquevalue is automatically allocated to Message Tag in the input common fields when transmitting
a processing request message. In this case, the value in Message Tag allocated by thesoftware is specified in the corresponding processing result message (For screen [R], [C], [M]).
Setting of Message Tag in management documents (Message for filing [F]) is the same as theone for printer [P], [A].

Length31Message
Type1

Reservedarea

3

Table 3.5.5 Message Control Information
Description
A sequence number for the processing result message for the processing request message
is allocated based on the definitions in Table 3.5.6.
'E' for the final message; otherwise a space.
To indicate a message class.
[R] (for screen)
Processing Result Notification, output message (errors in query)[P], [A] (for printer) Output message, management document (fixed-length delimiter format)
Output message (excluding query result and message for interface for[C] (for screen)
intraoffice communications)[M] (for screen)
Output message (query result)[T] (for user's own
Output message (for user's own interface)interface)[F] (for file)
Management document (CSV format)
In-Storage message (transaction response in automatic transaction[U] (for storage)
processing for declaration during office operating hours in the interactive
processing mode)
The reserved areas are used to control the system.

Table 3.5.6 Numbering rule of Division Sequence Number
Division
Message Type
Sequence
Number
Processing result
R000 (fixed)
notification message
In-Storage delivery
Umessage
Query result (with error)
ROther output messages
P, A, C, M, F, T (other than R, U)
001 (fixed)

Remarks

3-5-4＜2019.03 Update＞

User system

NACCS Center server

Only a transaction status notice is generated for aprocessing request message.

(Main Processor)<Processing Request Message>
Input Message ID: 123
Message Tag: AAA<Processing Request Message>
Input Message ID: 123
Message Tag: AAA<Processing result notification
message>
Input Message ID: 123
Message Tag: AAA
Division Sequence No.: 000
Termination: E
Message Type: R
Output Information Code: *SXXXTransaction

A processing result notification message, an output
for screen and an output for printer (INQ type) are
generated for a transaction request.

(Main Processor)<Processing Request Message>
Input Message ID: 789
Message Tag: BBB<Processing Request Message>
Input Message ID: 789
Message Tag: BBB< Processing result notification
message >Input Message ID: 789
Message Tag: BBB
Division Sequence No.: 000
Termination: △Message Type: R
Output Information Code: *SXXX01

Transaction<Output Information Message(For screen)>
Input Message ID: 789
Message Tag: BBB
Division Sequence No.: 001
Termination: E
Message Type: COutput Information Code: SAAXXX0<Output information Message(For printer)>
Input Message ID: 789
Message Tag: △Division Sequence No.: 001
Termination: E
Message Type: P
Output Information Code: SAAYYY0(Note: △ denotes a one-byte space.)

Figure 3.5.2 Sample usage of Input Message ID, Message Tag and Message Control Information

3-5-5＜2019.03 Update＞

3.5.3

Continued processing (Index Tag)In NACCS, there are procedures that user continuously repeats transaction request. If user carries out
those procedures, the Index Tag in processing result message will be specified in "Input commonfields" without any change, so that the transaction request will be made again. (Sequential processing)
Besides, if there is no continuous query result, spaces will be specified in the Index Tag.
If gateway users (whose companies develop software by themselves) carry out the sequential
processing procedure, their companies will need to build and add the function for executing thesequential processing by themselves.
Output configuration of the sequential processing is described in Table 3.5.7.
Table 3.5.7 Output configuration of the Continued Processing
OutlineSpecified content of processing request message sending from the second

Pattern 1

Because of restrictions in thesystem load, the information
volume which can be retrievedin 1 inquiry procedure is limited,
and all the necessary
information will be retrieved byrepeating the transaction
request.

Pattern 2

Registration procedure

Inquiry proceduretime

Call the information in center
server so that new information
will be added to that information
and will be registered.

Index Tag

Procedure Code

Procedure-by-Index tag specified inprocessing result
message from center
server (100 digits) ispresented in transaction
request message
without any change.
If the procedure
processing gets faulty,
the Index Tag will not be
specified in the error ofprocessing result
message.

Specify the procedure
code being executed(no change inprocedure code).

procedure fieldSpecify the content ofprocessing request
message being sent
the first time or theprevious time without
any change.

The procedure codewhen sending the firsttransaction request
message is different
from the one whensending the second
transaction request
message and therequest message afterthat.

Input item prescribing
in Procedure
specifications.

! In case the procedure processing gets faulty• Pattern 1 (inquiry procedure)Specify the Index Tag of processing result message which is received when thelast reference had been normally completed.
• Pattern 2 (registration procedure)
If the error occurs in the first time of registration procedure, there is no need tocall to carry out the procedure again, just specify the Index Tag of processing
result message when the call has been normally completed. If the error occurs
after the first time of the registration procedure, specify the Index Tag ofprocessing result message which is received when the last registration had
been normally completed.
(Note) Refer to the sequential processing column of Appendix Table 6.8 "Output Information code
List" for the message being subject of sequential processing.
Output configuration of sequential processing for each pattern is described in Figure 3.5.3, andFigure 3.5.4.
In terminal software for personal computer which NACCS center provides, the function for
executing sequential processing automatically is added.

3-5-6＜2019.03 Update＞

(Main Processor)<Processing Request Message>

Execute continuation processing with the same procedure code

Procedure Code: IIE
Index Tag: △△△Procedure-By-Procedure Field: XXXX

<Output Information Message(Query Result)>

Transaction

Procedure-by-procedure field
is specified with specified
content of processing request
message which was sent thefirst time or the previous time.

Index Tag = AAA(When executing the calling
procedure, it must be specified inserver)

Procedure Code: IIE
Index Tag: AAA
Procedure-By-Procedure Field: YYYY
Index tag is specified withspecified content of output
message (query result)
without any change.

<Processing Request Message>Procedure Code: IIE
Index Tag: AAA
Procedure-By-Procedure Field: XXXX

Transaction
Index Tag = BBB(If there is continuous data, it will bespecified in the server)<Output Information Message(Query Result)>
Procedure Code: IIE
Index Tag: BBB
Procedure-By-Procedure Field: ZZZ<Processing Request Message>
Procedure Code: IIE
Index Tag: BBB
Procedure-By-Procedure Field: XXXX

<Output Information Message(Query Result)>
Procedure Code: IIE
Index Tag: △△△Procedure-By-Procedure Field: WWWW

Transaction

If there is no continuous queryresult, spaces will be specified
in the index tag.

User system

Index Tag = △△△(No continuous data)

NACCS Center Server(Note: △ denotes a one-byte space.)

Figure 3.5.3 Flow of sequential processing (Pattern 1)

3-5-7＜2019.03 Update＞

<Processing Request Message>

Change the procedure code and execute continuation processing.

Procedure Code: EXM
Index Tag:

Transaction

Calling

Index Tag = AAA(When executing the calling
procedure, it must be specified inserver)<Processing Result Notification Message>
Processing Result Notification: *AEXM<Output Information Message (Screen)>

In the server, an inde x
tag is specifie d in thetransaction ou tpu t
information message(scre en)Procedure Code: EXM
Index Tag: AAAIndex tag is specified wi th specifie dcontent of output information messag e(scre en) with out an y ch ange. (*)(*) Index tag is not specified in transaction
response notification message.

<Processing Request Message>

Pro ced ure co de whe n send ing the firsttransaction re quest messag e i sdiffe rent from the on e when sendi ng
the second pr oce ssing requ est
messag e a nd the req uest messag eafte r that.

Registration

The procedure code will be changed from the time whenprocessing request message to be registered is sent. (Ifindex tag of registration procedure is sent with spaces, it will
be judged to be not continuous)

Procedure Code: EXM01
Index Tag: AAATransaction
Index Tag = BBB(If there is continuous data, it will bespecified in the server)<Processing Result Notification Message >Processing Result Notification: *AEXM01
In the server, an inde xtag is specifie d in thetransaction ou tpu t
information message(scre en)<Output Information Message (Screen)>
Procedure Code: EXM01
Index Tag: BBB
Index tag is specified wi th specifie dcontent of output information messag e(scre en) with out an y ch ange. (*)(*) Index tag is not specified in transaction
response notification message.

<Processing Request Message>
Transaction

Registration

Procedure Code: EXM01
Index Tag: BBB

Index Tag =(No continuous data)<Transaction Status Notice>
Processing Result Notification: *AEXM01<Output Information Message (Screen)>

If th ere is no continuous
data, spaces will bespecifie d i n the indextag.

Procedure Code: EXM01
Index Tag:NACCS Center server

User system(Note:denotes a one-byte space.)

Figure 3.5.4 Flow of sequential processing (Pattern 2)(Note) "Procedure-by-procedure item" in Pattern 2 shall be input following the items prescribed ineach procedure in Procedure specifications.
3-5-8＜2019.03 Update＞