3.3

XML Format Message

3.3.1

Message format for XML format message

For the message format for XML format message used in NACCS, both system header and procedure
data are XML format text messages. In addition, the number of processing request messages
contained in 1 XML format message is 1 message.
Also, refer to "Appendix Table 6.7 Subjected Procedure List" for subjected procedure.

3.3.1.1

Format/version for XML format messages

Format/version for XML format messages used in NACCS is PAA (Pan Asian e-commerce Alliance)
Standard/Superset Message Structure V2.0.

3.3.2Message structure for XML format messages

A communications protocol header and a trailer are added to a XML format message.
Figure 3.3.1 and Figure 3.3.2 show message structure.
Note that, when SMTP is used as the communications protocol, it is necessary to make a new line after
each end tag not to exceed 1000 bytes per 1 line of transmit data.

Communications protocol
Trailer

Header

XML message

Sent to NACCS
Center (processingrequest message)

Communications protocol
XML message

HeaderTrailer

Received fromNACCS Center(processing resultmessage)

Figure 3.3.1 XML format message
Protocol header/trailer
System header
XMLHeader

NACCS
Messagestart tag

NACCSHeader
start tag

Field 1
Start tag

Field 1*

Field 1
End tag

Field 2Start tag

Field 2*

Field 3
End tag

Field nStart tag

Field n*Field nEnd tag

NACCSheader
End tagProtocol header/trailer
Procedure data
Data
Data
Data 1
Hierarchy 1 Hierarchy 2 Start tag
Start tag
Start tag

Data 1

Data 1
End tag

Data 2Start tag

Data 2

Data
Data 2
End tag Hierarchy 2
End tag

Data
Hierarchy2
Start tag

Data nStart tag

Data nData nEnd tagData
Data
NACCS
Hierarchy Hierarchy 1 Message
2
End tagend tag
End tag* Subject fields for input/output common fields (input/output common fields have multiple fields andhave hierarchical structure)
Figure 3.3.2 Example of XML Format Message Structure
3-3-1

3.3.3

Types of Transmit/Receive Message of XML Format Message

Table 3.3.1 and Table 3.3.2 show the list of messages used in transmit/receive of XML format
messages.
Table 3.3.1 List of Transmit/Receive Messages of XML Format Messages (Interactive Processing Mode)
Interactive processing modeMessage type
Processing Request Message
Output Information Message
Processing Result Notification
Message

Software package
(N1)
-○○

ebMS processing
mode○○○○

SMTP two-way-Table 3.3.2 List of Transmit/Receive Messages of XML Format Messages (E-Mail Style ProcessingMode)
E-mail style processing mode
Message type
Processing Request Message
Output Information Message
Processing Result Notification Message

Gatewaycomputer○○○(Note 1) The software package can handle only NACCS EDI messages (XML format messages cannot
be used).

3.3.4

Message specifications for XML format messages

Refer to "Appendix 15" and "Procedure Specifications" for specifications for XML format messages(Mapping Table).
Note that the length of each field is different in PAA standards and Processing Request
Message/Output Information Message and it is handled as described in Table 3-3-3. (Note 2)
To set the tag (except hierarchy tag) which does not have description in [ Field Name] in theProcessing Request Message, set the tag as an empty tag. (If the tag is set, the content of XML
message is deemed invalid and an error is output (Error code: A0022).

3-3-2Table 3-3-3 Handling of length difference in PAA standards and Processing Request
Message/Output Information Message

Relation of length
PAA standards > Processing Request
Message(Length of PAA standards is long)
PAA standards < Processing Request
Message(Length of PAA standards is short)
Output Information Message > PAA
standards(The length of Output Information
Message is long.)
Output information Message < PAAstandards(The length of Output Information
Message is short.)

Details of handling
Length of Processing Request Message is processed
as valid data.
Length of PAA standards is processed as valid data.

Length of PAA standards is processed as valid data.

Length of Output Information Message is processed asvalid data.

(Note 2) When an input message exceeds the length specified in PAA standards, the range of length of
PAA standards is treated as valid data.

3-3-3