APPENDIX G: DTS and GEX Error Codes

More documents

Recommendations

Info

Appendix G: DTS and GEX Error Codes Table G-25: Component Rules (Continued) Data Element Component Rule Responsible Party to Address Error Position This data element must be present. Traveler if position is not specified in personal profile information. DTS Developer if position is specified. Outline Status History Record OSH Value of data element must equal “OSH” DTS Developer 4. There are UDF errors that are sometimes not directly attributable to a specific data element in error. These general errors are usually related to communications failures or missing UDF required records. The general errors that may be present in a Translation Failure Notification are specified in Table G-23. Table G-26: DTS UDF Data Structure General Errors Error Statement Error Condition Description Responsible Party to Address Error Message is unrecognizable. The document could not be interpreted. DTS Developer This is very likely due to a required UDF record missing. Transmission was unidentifiable. The entire DTS UDF batch file could not be interpreted. This may be due to a missing or “bad” Batch Header record or Batch Trailer Record. This also could be a result of a bad file transfer. DTS Developer, DTS System Administrator, or GEX System Administrator. Transmission had an invalid or missing terminator. Transmission missing a required component. Transmission was invalid because it contained components in error. Transmission missing a required data element. The file has an invalid or missing Carriage Return – Line Feed. The file is missing a required UDF record(s). The file contains several bad or missing UDF records. The file contains several bad or missing data elements. DTS Developer DTS Developer DTS Developer DTS Developer Unexpected Transmission error. The file is incomplete. DTS Developer Transaction was unidentifiable. The transaction (authorization or voucher) DTS Developer could not be interpreted. This may be due to a required UDF record missing or missing terminator. Transaction had an invalid or missing terminator. The transaction (authorization or voucher) DTS Developer contains an invalid or missing Carriage Return – Line Feed. Transaction missing a required component. The transaction (authorization or voucher) contains several missing required UDF records. DTS Developer. Transaction was invalid because it contained components in error. Transaction missing a required data element. Unexpected Transaction error. The transaction (authorization or voucher) contains several bad UDF records. The transaction (authorization or voucher) contains several bad or missing data elements. The transaction (authorization or voucher) is incomplete. DTS Developer DTS Developer DTS Developer Page G-40 DTS Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 This document is controlled and maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete. Please check revision currency on the Web prior to use.
Appendix G: DTS and GEX Error Codes G.3.3 Business Rule Errors Business rule errors occur as a result of the data provided by the DTS not following the agreed upon business rules between the DTS and GEX. The Translation Failure Notifications resulting from business rule errors are outlined in Table G-24 below. Table G-27: Business Rule Errors Error Statement Error Description Responsible Party to Address Error Lookup Failure: Invalid Line Item Accounting Format Invalid or Unknown Accounting string in OA, OAD, or OCD record. The accounting string format must match one of the DTS published service line of accounting formats. DTA Lookup Failure: Invalid AAA/FSN/DODAAC for GS03 Lookup Cannot find accounting string in lookup tables that match Acct1 field. This value is used to determine the appropriate financial system for processing the document. DTA if Acct1 data element is invalid. Help Desk if Acct data element is valid. Lookup Failure: Inactive Routing Entry Lookup Failure: Mult Route Entry-Limit, BSN or ASN mismatch Lookup Failure: Missing Personal Account Routing Number Lookup Failure: Unrecognized Personal Account Type Lookup Failure: Missing Personal Account Number Lookup Failure: Missing Charge Card Routing Number Lookup Failure: Missing Book Number. Field not present: Both CBAInvStmntDate OCP Element & CBAAccountNo OCP Element must be present. Acct1 field passed lookup, but data has been flagged as inactive. The communications pathway from GEX to the financial system has not been established. Acct1 field passes primary lookup, but fails secondary lookup. In some cases, to determine the appropriate financial system, data in addition to the FSN must be used. The Limit, BSN, and ASN should be validated. Personal Routing Number in the OP2 record is missing. If payment is made to Traveler’s Account (checking or savings), the routing number must be supplied. Value of Personal Account Type in the OP2 record is not expected. It does not equal to “CHECKING”, “SAVINGS”, or “CHECK”. Personal Account Number in the OP2 record is missing. If payment is made to Traveler’s Account (checking or savings), the account number must be supplied. Govt Charge Card Routing Number in the OP2 record is not present. If payment is made to Traveler’s Government Credit Card, the credit card routing number must be supplied. User – 4 field (book number) is missing. If payment is made to Traveler’s Government Credit Card, the book number must be supplied. Both of these fields are required to create the invoice number. Help Desk DTA if Limit, BSN, and ASN data element are invalid. Help Desk if Limit, BSN, and ASN data element are valid. DTA if personal routing number is not specified in personal profile information. DTS Developer if personal routing number is specified. DTA if personal account type is not specified. DTS Developer if personal account type is specified. DTA if personal account number is not specified in personal profile information. DTS Developer if personal account number is specified. DTA if Govt Charge Card routing number is not specified in personal profile information. DTS Developer if Govt Charge Card routing number is specified. DTA DTS Developer DTS Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-41 This document is controlled and maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete. Please check revision currency on the Web prior to use.
Page 1 and 2: APPENDIX G: DTS AND GEX ERROR CODES
Page 3 and 4: Appendix G: DTS and GEX Error Codes
Page 39: Appendix G: DTS and GEX Error Codes

APPENDIX G: DTS and GEX Error Codes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?