Versions Compared

Old Version 7

changes.mady.by.user user-d7135

Saved on

compared with

New Version 8

changes.mady.by.user user-d7135

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Use code and description OR combi tag without description. Onetrail will use the default description to the recipient as stated in the above exception codes list.

Example 1:

<GlobalMessageExceptionCode>000E</GlobalMessageExceptionCode>
             </errorClassification>
             <errorDescription>
                           <FreeFormText xml:lang="EN">Ok</FreeFormText>


Remark: Where “000E” = exception code and Freeform text = “OK”. Freeform text will ALWAYS overrule the default description as stated in the above exception codes list.

Example 2:

<GlobalMessageExceptionCode>504E%21120</GlobalMessageExceptionCode>


Remark: Where “504E” = exception code and “21120” = Ship to address(code) “%” needs to precede the variable!

<Exceptions>
     <ExceptionDescription>
              <errorClassification>
                     <GlobalMessageExceptionCode>000E</GlobalMessageExceptionCode>
             </errorClassification>
             <errorDescription>
                    <FreeFormText lang="EN">Ok</FreeFormText>
             </errorDescription>
     </ExceptionDescription>
     <GlobalExceptionTypeCode>Receipt Acknowledgement Exception</GlobalExceptionTypeCode>
</Exceptions>

Format & Syntax

The format of the standard Onetrail XML messages is XML version 1.0.
The encoding must be UTF-8. Please refer to our OT(N)ACK XSD Documentation for default values, multiplicity of elements, attributes, business rules and an overview for mapping design purposes.

Info
For more information we refer to: Format & Syntax Acknowledgement

Communication

Info
Please refer to the communication page: Onetrail TPN™ Communication

Examples

Info
For more information we refer to: Onetrail TPN™ XML Ack Examples