DTA Manual, Appendix G: DTS & GEX Error Codes August 04, 2023
Defense Travel Management Office 85 travel.dod.mil
Chapter 4: GEX Error Codes
To perform the accounting and disbursing functions associated with defense travel, the Defense Travel System
(DTS) sends the authorizations and vouchers to the Global Exchange (GEX) system for translation into the
appropriate financial transactions (obligations and invoices). Upon translation to the appropriate data format,
the GEX routes the transaction to the intended accounting, disbursing or entitlement system for processing.
Both the DTS Payment Module (PM) and the DTS Centrally Billed Account (CBA) Module send Electronic Data
Interchange (EDI) transactions to, and receive responses from, GEX and DMDC.
The Import/Export Module supports the AUTO APPROVED process. There are no signature blobs associated
with this AUTO APPROVED stamp, which normally a lack of a signature would generate a reject from DMDC.
However, DMDC should not expect to receive digital signature blobs for AUTO APPROVED I/E transactions.
For auto-approved CBA amendments, identified by the text “Auto-approved by CBA” in the
<StatusReasonComment> field, the digital signature will be blank. Normally, DMDC rejects a document with an
APPROVED stamp without a digital signature, but in this case recognizes this as an allowed exception and will
not reject the document.
The communication between DTS and the GEX is controlled by the use of Simple Object Access Protocol (SOAP)
and Extensible Markup Language (XML) format for communicating information between the Defense Travel
System (DTS) and the Department of Defense (DOD) Accounting and Disbursement Systems (DADS) via the
Global Exchange (GEX) Services. XML is also a means to transmit data between DTS and the Defense
Management Data Center (DMDC) Archive.
If the data provided to the GEX does not match the format defined in the DTS Interface Design Document, and
the DTS Interface Requirements Specification documents, the GEX cannot interpret the document (authorization
or voucher). When this occurs, the GEX will create a ‘Translation Failure Notification” that is sent back to DTS.
The DTA receives notification of the error, and the appropriate action to take in order to correct the problem
and retransmit the document to the GEX. Most of these errors are not correctable by the traveler, or the DTA, as
they are a direct result of the systemic output of the DTS. However, in the case of missing personal profile
information those are correctable by the traveler or the DTA. The Translation Failure Notifications may also be
the result of translation failure due to business process rules. These types of errors are a result of the content of
the data not supporting the business rules. These rules may be associated with how to route the content of the
data not supporting the business rules. These rules may be associated with how to route the transaction to the
appropriate financial system, missing account information required for the payment, etc. The business rule
failures are correctable by the traveler, DTA or Help Desk (depending on the error) as they are data content
problems (not data format problems).
Translation Failure errors definitions are in the GEX logical maps listed as plain text. The traveler receives these
error definitions in an email.