APPENDIX G: DTS and GEX Error Codes
APPENDIX G: DTS and GEX Error Codes
APPENDIX G: DTS and GEX Error Codes
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>APPENDIX</strong> G:<br />
<strong>DTS</strong> AND <strong>GEX</strong> ERROR CODES<br />
<strong>DTS</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-1 . . . . . . . . . . . . . . . . . ADS System<br />
Table G-2 . . . . . . . . . . . . . . . . . CAPS-W System<br />
Table G-3 . . . . . . . . . . . . . . . . . DAI System<br />
Table G-4 . . . . . . . . . . . . . . . . . DBMS System<br />
Table G-5 . . . . . . . . . . . . . . . . . DCD System<br />
Table G-6 . . . . . . . . . . . . . . . . . DIFMS System<br />
Table G-7 . . . . . . . . . . . . . . . . . DWAS System<br />
Table G-8 . . . . . . . . . . . . . . . . . eBIZ System<br />
Table G-9 . . . . . . . . . . . . . . . . . GAFS-<strong>DTS</strong> System<br />
Table G-10 . . . . . . . . . . . . . . . . GFEBS System<br />
Table G-11 . . . . . . . . . . . . . . . . MCTFS System<br />
Table G-12 . . . . . . . . . . . . . . . . SABRS System<br />
Table G-13 . . . . . . . . . . . . . . . . SFIS System<br />
Table G-14 . . . . . . . . . . . . . . . . SOMARDS System<br />
Table G-15 . . . . . . . . . . . . . . . . SRD-1 System<br />
Table G-16 . . . . . . . . . . . . . . . . SSC-SD System<br />
Table G-17 . . . . . . . . . . . . . . . . STANFINS System<br />
Table G-18 . . . . . . . . . . . . . . . . STARS-FL System<br />
Table G-19 . . . . . . . . . . . . . . . . STARS-HCM System<br />
Table G-20 . . . . . . . . . . . . . . . . STARS-OP System<br />
Table G-21 . . . . . . . . . . . . . . . . WAAS System<br />
System Administrator <strong>Error</strong> <strong>Codes</strong><br />
Table G-22 . . . . . . . . . . . . . . . . <strong>DTS</strong> Rejects<br />
<strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-23 . . . . . . . . . . . . . . . . <strong>DTS</strong> UDF Records<br />
Table G-24 . . . . . . . . . . . . . . . . <strong>DTS</strong> UDF Data Specification <strong>Error</strong>s<br />
Table G-25 . . . . . . . . . . . . . . . . Component Rules<br />
Table G-26 . . . . . . . . . . . . . . . . <strong>DTS</strong> UDF Data Structure General <strong>Error</strong>s<br />
Table G-27 . . . . . . . . . . . . . . . . Business Rule <strong>Error</strong>s<br />
Note: Each system varies in their error codes. Ensure the correct codes are used for the applicable system.<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-1<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
G.1 <strong>DTS</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-1: ADS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
001 Missing/Invalid CTO Office Identifier No Specific Description<br />
002 Missing/Invalid Transaction Type Missing/Invalid total transaction required for appr. format<br />
003 Missing/Invalid Total Transaction Amount Missing/Invalid total transaction amount<br />
004 Missing/Invalid Disbursed Amount No Specific Description<br />
005 Missing/Invalid Transaction Date Missing/Invalid transaction date required to build SDW<br />
006 Missing/Invalid Billed Amount No Specific Description<br />
007 Missing/Invalid Voucher Number No Specific Description<br />
008 Missing/Invalid Disbursing Office/Disbursing Station Symbol Identifier No Specific Description<br />
009 Missing/Invalid Federal Organization Treasury Agency Symbol Code No Specific Description<br />
010 Missing/Invalid Transfer Dept Indicator - Transfer Agency (Transferring Missing/Invalid transferring agency required for appr. format<br />
Agency - LOA)<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
Missing/Invalid FY required to build SDW<br />
Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol Missing/Invalid fund symbol required for appr. format<br />
Code (Appropriation - LOA)<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA) Subhead required for appr. format<br />
014 Missing/Invalid Program Year No Specific Description<br />
015 Missing/Invalid Fund Code No Specific Description<br />
016 Missing/Invalid Resource Code - Object Class Code (WBS) No Specific Description<br />
017 Missing/Invalid Operating Agency Code No Specific Description<br />
018 Missing/Invalid Bureau Control Number (BCN - LOA) No Specific Description<br />
019 Missing/Invalid Allotment Serial Number No Specific Description<br />
020 Missing/Invalid Op Budget Activity Number - Op Budget Acct Number No Specific Description<br />
(Tran. Type Code - LOA)<br />
021 Missing/Invalid Sub-Allotment - Sub Allotment Number (Sub Allotment - No Specific Description<br />
LOA)<br />
022 Missing/Invalid Accounting Class Reference Number No Specific Description<br />
023 Missing/Invalid Reimbursement Billing Code No Specific Description<br />
024 Missing/Invalid Reimbursement Order Number No Specific Description<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC - No Specific Description<br />
SDN)<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) Invalid or closed job order<br />
027 Missing/Invalid Fund Administrator No Specific Description<br />
028 Missing/Invalid Work Center No Specific Description<br />
029 Missing/Invalid Cost Account Code No Specific Description<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - No Specific Description<br />
LOA)<br />
031 Missing/Invalid Budget Program Activity - Activity Identifier (Service No Specific Description<br />
Code - SDN)<br />
032 Missing/Invalid Project/Sub Project No Specific Description<br />
033 Missing/Invalid Fund Control Number/Mord Number/616 Number/MIPR No Specific Description<br />
Number<br />
034 Missing/Invalid Job Order No Specific Description<br />
Page G-2 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-1: ADS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
035 Missing/Invalid Special Ops/Management Decision Package No Specific Description<br />
036 Missing/Invalid Emergency/Special Program Code No Specific Description<br />
037 Missing/Invalid Budget Reporting Code No Specific Description<br />
038 Missing/Invalid Accounting Processing Code - Job Order Cost Code No Specific Description<br />
(Shop Number)<br />
039 Missing/Invalid Cost Allocation Code - Job Number/Local Use (Other No Specific Description<br />
Function Code)<br />
040 Missing/Invalid Project Account/Program Element Code No Specific Description<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier No Specific Description<br />
(AAA - LOA)<br />
042 Missing/Invalid IBOP No Specific Description<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
044 Missing/Invalid Pay Grade No Specific Description<br />
045 Missing/Invalid Employee Name No Specific Description<br />
046 Missing/Invalid Remit To Information No Specific Description<br />
047 Missing/Invalid Payment Method No Specific Description<br />
048 Missing/Invalid Total Amount Of Payment No Specific Description<br />
049 Missing/Invalid AO Approval Date (Date Claim Accept/Approved Date) No Specific Description<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) No Specific Description<br />
051 Missing/Invalid Estimated Obligation Amount Insufficient funds<br />
052 Missing/Invalid Per Diem/Advance/CBA Code No Specific Description<br />
053 Missing/Invalid Invoice Number No Specific Description<br />
054 Missing/Invalid ABA Routing Number No Specific Description<br />
055 Missing/Invalid Account Number No Specific Description<br />
056 Missing/Invalid Remittance Advice Number No Specific Description<br />
057 Missing/Invalid Payee Information No Specific Description<br />
058 Missing/Invalid Old Obligation Amount No Specific Description<br />
059 Missing/Invalid Credit/Debit Obligation Amount No Specific Description<br />
060 Missing/Invalid Adjusted Obligation Amount No Specific Description<br />
061 Missing/Invalid Prompt Payment Act No Specific Description<br />
062 Missing/Invalid CBA Invoice Date No Specific Description<br />
063 Missing/Invalid Date Received No Specific Description<br />
064 Missing/Invalid Gross Amount Of Payment No Specific Description<br />
065 Missing/Invalid Credit Amount No Specific Description<br />
066 Missing/Invalid Net Amount No Specific Description<br />
067 Missing/Invalid Deferred Amount No Specific Description<br />
068 Missing/Invalid Accounts Receivable No Specific Description<br />
069 Missing/Invalid Accounting Line No Specific Description<br />
070 Cost Code Frozen on MADD No Specific Description<br />
071 Cost Code, OBJ Class CD Unmatched to Matrix No Specific Description<br />
072 Transaction Unmatched to Operating Target No Specific Description<br />
073 Doc Number Exists with Different Status, Cancel <strong>and</strong> Reissue TON No Specific Description<br />
074 Doc Exists - One or More Incoming Data Elements Unmatched No Specific Description<br />
075 Doc Already Completed No Specific Description<br />
076 Doc Not On File No Specific Description<br />
077 Duplicate TON/Doc Number No Specific Description<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-3<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-1: ADS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
078 Doc Was Not Canceled No Specific Description<br />
079 Multiple Job Order Numbers on same Travel Order Number No Specific Description<br />
080 Missing/Invalid Transaction Set Control Number No Specific Description<br />
081 Missing/Invalid Header Use for duplicate file check<br />
082 Missing control number Use for duplicate file check<br />
083 Missing/Invalid DUNS/DUNS+4 No Specific Description<br />
084 Missing data to build SDN One or more of the elements required to build the st<strong>and</strong>ard<br />
document number are missing or invalid<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) Estimated trip start date are missing or not valid<br />
086 Missing/Invalid estd-complt-date No Specific Description<br />
087 No Header Record in Set No Specific Description<br />
088 No Detail Record in Set No Specific Description<br />
089 No Summary Record in Set No Specific Description<br />
090 No Header or Detail Records in Set No Specific Description<br />
091 No Summary or Detail Records in Set No Specific Description<br />
092 No Loop ID in Detail Record No Specific Description<br />
093 Invalid detail Record Order No Specific Description<br />
094 Invalid Detail Record No Specific Description<br />
095 No Header <strong>and</strong> Invalid Detail Order No Specific Description<br />
096 No Summary <strong>and</strong> Invalid Detail Order No Specific Description<br />
097 Invalid Transaction Type in Obligation/Payment Record No Specific Description<br />
098 Missing/Invalid Type Action No Specific Description<br />
099 Missing/Invalid Block Number No Specific Description<br />
100 Missing/Invalid Obligation Data Code No Specific Description<br />
101 Missing/Invalid Liquidation Indicator Code No Specific Description<br />
102 Duplicate Record No Specific Description<br />
103 Missing Invalid Project Unit No Specific Description<br />
104 Project Directive Line Item already exists for another Project Unit No Specific Description<br />
105 Project Unit Exist on another Project Directive Line Item No Specific Description<br />
106 Missing Invalid Project Directive Line Item No Specific Description<br />
107 Missing Invalid Project Directive Line Item Suffix No Specific Description<br />
108 Missing Invalid Input Type Code No Specific Description<br />
109 Missing Invalid Processing Action Code No Specific Description<br />
110 Subhead not on Chart of Accounts No Specific Description<br />
111 Requiring Financial Manager not on Chart of Accounts No Specific Description<br />
112 Project unit not on Chart of Accounts No Specific Description<br />
112 Missing Invalid Revision Number No Specific Description<br />
114 Missing Invalid Number of Days No Specific Description<br />
115 Participating Manager; Sub Allotment; Project Unit does not meet No Specific Description<br />
CMET edits<br />
116 Amount Sign does not agree with Action Code No Specific Description<br />
117 Major Comm<strong>and</strong>; Fiscal Year; Appropriation; Subhead does not meet No Specific Description<br />
CMET edits<br />
118 Requiring Financial Manager; Project Unit does not meet CMET edits No Specific Description<br />
119 Major Claimant Indicator Invalid No Specific Description<br />
120 Missing Invalid Operating Budget UIC No Specific Description<br />
Page G-4 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-1: ADS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
121 Revision Number Present with Action Code A No Specific Description<br />
122 Project Directive Line Item Suffix Invalid: Appropriation expired or No Specific Description<br />
lapsed<br />
123 Reimbursable segment missing for this Project Unit No Specific Description<br />
124 Operating Budget UIC must be 000140 for a W Subhead No Specific Description<br />
125 Major Claimant required for DARPA Appropriation No Specific Description<br />
126 Major Claimant does not match Chart of Accounts No Specific Description<br />
127 Operating Budget UIC must be 000140 for DARPA Appropriation No Specific Description<br />
128 Insufficient Funds at Appropriation Level / Living Lapsed Appropriation No Specific Description<br />
129 Appropriation No Longer Available for Travel Obligations No Specific Description<br />
130 Operating Budget UIC must be 000230 for this Requiring Financial No Specific Description<br />
Manager<br />
131 Operating Budget UIC must be 000240 for this Requiring Financial No Specific Description<br />
Manager<br />
132 Operating Budget UIC must be 000390 for this Requiring Financial No Specific Description<br />
Manager<br />
133 Operating Budget UIC must be 000190 for this Requiring Financial No Specific Description<br />
Manager<br />
134 Operating Budget UIC must be 000750 for this Requiring Financial No Specific Description<br />
Manager<br />
135 Change of OMB Object Class Invalid After Travel Disbursement No Specific Description<br />
136 Accounting Data does not meet CMET edits No Specific Description<br />
137 Unmatched Obligation Adjustment No Specific Description<br />
138 Job Order Fiscal Year unmatched to SDN Fiscal Year No Specific Description<br />
139 Missing/Invalid Obligation Transaction No Specific Description<br />
140 Missing/Invalid Cancellation Amount No Specific Description<br />
Table G-2: CAPS-W<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
005 Missing/Invalid Transaction Date Blank or future date not acceptable<br />
009 Missing/Invalid Federal Organization Treasury Agency Symbol Code Blank department ID not acceptable<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
Blank Fiscal year not acceptable<br />
Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol No Specific Description<br />
Code (Appropriation - LOA)<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA) 4-digit suffix to basic symbol, subdivision of funds tied to<br />
funding purpose<br />
015 Missing/Invalid Fund Code IDS Fund Code, Table Driven<br />
016 Missing/Invalid Resource Code - Object Class Code (WBS) Blank EOR not acceptable; FY/EOR combination must be<br />
valid in accounting edit table<br />
019 Missing/Invalid Allotment Serial Number No Specific Description<br />
022 Missing/Invalid Accounting Class Reference Number No Specific Description<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC -<br />
SDN)<br />
Customer indicator required to build an SDN is missing/<br />
invalid<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) Identifies the cost accounting code table<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-5<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-2: CAPS-W (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
029 Missing/Invalid Cost Account Code Identifies the cost accounting code table<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - Identifies general purpose <strong>and</strong> nature of product or server<br />
LOA)<br />
034 Missing/Invalid Job Order No Specific Description<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier<br />
(AAA - LOA)<br />
Identifies accounting activity responsible Organization Identifier<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
045 Missing/Invalid Employee Name No Specific Description<br />
046 Missing/Invalid Remit To Information No Specific Description<br />
047 Missing/Invalid Payment Method No Specific Description<br />
048 Missing/Invalid Total Amount Of Payment Credit invoice not acceptable; CLIN sum must equal invoice<br />
total<br />
049 Missing/Invalid AO Approval Date (Date Claim Accept/Approved Date) Approval date of trip record is invalid<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) Unique ID<br />
051 Missing/Invalid Estimated Obligation Amount Amount by line item, st<strong>and</strong>ard document number<br />
052 Missing/Invalid Per Diem/Advance/CBA Code Code identifies per diem/CBA/advance/specifics<br />
053 Missing/Invalid Invoice Number Duplicates invoice number not acceptable, A-Z <strong>and</strong>/ or 0-9<br />
only valid<br />
054 Missing/Invalid ABA Routing Number No Specific Description<br />
055 Missing/Invalid Account Number CBA account number invalid for paying office<br />
056 Missing/Invalid Remittance Advice Number No Specific Description<br />
057 Missing/Invalid Payee Information No Specific Description<br />
060 Missing/Invalid Adjusted Obligation Amount Insufficient funds<br />
061 Missing/Invalid Prompt Payment Act Terms must be valid; disc %0-99.99, disc days 0-365, net<br />
days 0-365<br />
062 Missing/Invalid CBA Invoice Date Future days not acceptable, inv. date can't be > inv.<br />
Received date<br />
063 Missing/Invalid Date Received No Specific Description<br />
064 Missing/Invalid Gross Amount Of Payment No Specific Description<br />
065 Missing/Invalid Credit Amount No Specific Description<br />
066 Missing/Invalid Net Amount No Specific Description<br />
068 Missing/Invalid Accounts Receivable No Specific Description<br />
069 Missing/Invalid Accounting Line No Specific Description<br />
070 Cost Code Frozen on MADD Cost Code is present but in a frozen status in the MADD<br />
071 Cost Code, OBJ Class CD Unmatched to Matrix Cost Code/Object Class are not in the Matrix File for the<br />
stated Basic Symbol<br />
072 Transaction Unmatched to Operating Target Transaction does not match an Activity Code, Fund Code,<br />
ASN, ORG, Cost Code, Fund Distribution Indicator (FDI) in<br />
the detail operating target line<br />
073 Doc Number Exists with Different Status, Cancel <strong>and</strong> Reissue TON If a document number with a maintenance code A, P or M<br />
(for <strong>DTS</strong> this is purpose code of 00, 01, 05, or 31) already<br />
exists on the database<br />
074 Doc Exists - One or More Incoming Data Elements Unmatched If the document already exists <strong>and</strong> any incoming data elements<br />
are different than those data<br />
075 Doc Already Completed If a document has been finalized <strong>and</strong> incoming transaction<br />
is not purpose code “31”, reject the transaction<br />
Page G-6 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-2: CAPS-W (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
076 Doc Not On File If purpose code is 01, 05, or 31 (<strong>and</strong> maintenance code is<br />
not A, P, or M) <strong>and</strong> there is not an open document number<br />
in the history file for that incoming transaction, reject the<br />
document<br />
077 Duplicate TON/Doc Number Document number has been established manually within<br />
the system. Cannot process the transaction<br />
078 Doc Was Not Canceled Amounts do not equal zero when trying to cancel document<br />
(TON)<br />
079 Multiple Job Order Numbers on same Travel Order Number Only one Job Order Number allowed per Travel Order<br />
Number<br />
080 Missing/Invalid Transaction Set Control Number Should really be missing/invalid purpose code?<br />
083 Missing/Invalid DUNS/DUNS+4 No Specific Description<br />
084 Missing data to build SDN Blank SDN not acceptable<br />
093 Invalid detail Record Order Blank Line Item (CLIN) Number not acceptable<br />
146 Missing/Invalid CBA Routing Indicator Missing/invalid CAPS-W CBA Routing Indicator<br />
147 Missing CBA Transaction ID Missing CBA Transaction ID not acceptable: No Specific<br />
Description<br />
148 Missing/Invalid Line Item (CLIN) Quantity Missing/Invalid Line Item (CLIN) Quantity<br />
Table G-3: DAI<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
002 Missing/Invalid Transaction Type No Specific Description<br />
003 Missing/Invalid Total Transaction Type The sum of the individual obligation amounts within the<br />
Detail Records of the transaction set does not equal the<br />
amount within the Header Record; Header total transaction<br />
out of balance<br />
005 Missing/Invalid Transaction Date The date or time stamp within the Header Record is invalid<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
045 Missing/Invalid Employee Name No Specific Description<br />
051 Missing/Invalid Estimated Obligation Amount Obligation amount is not numeric<br />
052 Missing/Invalid Per Diem/Advance/CBA Code No Specific Description<br />
058 Missing/Invalid Old Obligation Amount Adjusting obligation does not include previous amount<br />
060 Missing/Invalid Adjusted Obligation Amount Adjusting obligation does not include new obligation<br />
amount<br />
068 Missing/Invalid Accounts Receivable Received adjusting accounts receivable transaction <strong>and</strong> no<br />
original accounts receivable record found<br />
075 Doc Already Completed Received adjusting obligation after voucher settlement, system<br />
expects supplemental obligation<br />
076 Doc not of File Received adjusting/supplemental obligation for an accounting<br />
record not found<br />
087 No Header Record in Set No Specific Description<br />
088 No Detail Record in Set No Specific Description<br />
089 No Summary Record in Set No Specific Description<br />
090 No Header or Detail Records in Set No Specific Description<br />
091 No Summary or Detail Records in Set No Specific Description<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-7<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-3: DAI<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
102 Duplicate Record Transaction matches previously posted <strong>and</strong> acknowledged<br />
record<br />
140 Missing/Invalid Cancellation Amount Received obligation cancellation transaction that does not<br />
equal total amount previously obligated<br />
153 Duplicate Accounts Receivable Received Transaction matches previously posted <strong>and</strong> acknowledged<br />
record<br />
154 Accounts Receivable Amount is Greater than Disbursed Amount Received an accounts receivable amount that exceeds the<br />
amount previously disbursed<br />
155 Cannot cancel Accounts receivable - Accounts Receivable Already<br />
Equal to $0.00<br />
Received a cancellation for an accounts receivable for<br />
which the balance equals zero<br />
157 Missing/Invalid Receivable Amount Received an accounts receivable transaction without an<br />
amount<br />
158 Receivable Amount Previously Established Cannot Process Adjustment Transaction matches previously posted <strong>and</strong> acknowledged<br />
record<br />
170 Amount must be Greater than $225.00 Transaction received (T1); attempted to write off Out of Service<br />
Debt (OOSD) for $225.00 or greater, but existing<br />
accounts receivable amount is less than $225.00<br />
175 Write-off/Waiver/or Transfer Record not Processed Accounts Receivable<br />
Record not Found<br />
Received a debt write-off, waiver, or transfer record for<br />
which an original accounts receivable transaction does not<br />
exist in the accounting system<br />
176 Write-off Amount Exceeds Receivable Amount The amount received for a debt write-off exceeds the current<br />
balance for the accounts receivable<br />
500 Missing/Invalid Agency Accounting Identifier Code Incorrect accountable station number used, formerly known<br />
as FSN/AAA/ASN<br />
501 Missing/Invalid Department Regular Code (Acct 1) Missing/Invalid Department Regular for Cost Object used<br />
502 Missing/Invalid Department Transfer Code (Acct 1) Missing/Invalid Transfer for Cost Object used<br />
503 Missing/Invalid Main Account Code (Acct 1) Missing/Invalid Main Account for Cost Object used<br />
504 Missing/invalid Sub Account Code (Acct 2) Missing/Invalid Sub Account for Cost Object used<br />
505 Missing/Invalid Period of Availability Fiscal Year Date (Acct 2) Invalid Period of Availability for Cost Object used<br />
506 Missing/Invalid FMS Customer Code (Acct 2) Main Account equals 8242, an FMS Customer Code is<br />
required when Main Account = 8243<br />
507 Missing/Invalid FMS Case Identifier (Acct 3) Main Account equals 8242, an FMS Case Identifier is<br />
required when Main Account = 8243<br />
508 Missing/Invalid FMS Case Line Item Identifier (Acct 3) Main Account equals 8242, an FMS Case Line Item Identifier<br />
is required when Main Account = 8243<br />
509 Missing/Invalid Budget Line Item Identifier (Acct 4) Invalid Budget Line Item Identifier for Cost Object used<br />
510 Missing/Invalid Fund Center Identifier (Acct 5) Invalid Fund Center Identifier for Cost Object used<br />
511 Missing/Invalid First Instance of Cost Object (Acct 6) Invalid Cost Object/Cost Object Type<br />
512 Missing/Invalid First Instance of Cost Object Type (Acct 6) Invalid Cost Object Type for Cost Object used<br />
513 Missing/Invalid Second Instance of Cost Object (Acct 7 <strong>and</strong> 8) Invalid Cost Object/Cost Object Type<br />
514 Missing/Invalid Second Instance of Cost Object (Acct 8) Invalid Cost Object Type for Cost Object used<br />
515 Missing/Invalid Appropriation Limit (Acct 8) Invalid Limit for Agency Accounting Identifier Code<br />
516 Missing/Invalid Future Use (Acct 9) No Specific Description<br />
517 Missing/Invalid User Defined Field (Acct 10) No Specific Description<br />
518 Insufficient Funding Available Insufficient funding available for Cost Object used<br />
519 Accounting Processor <strong>Error</strong> Processor <strong>Error</strong>, contact Finance Defense Travel Administrator<br />
Page G-8 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-3: DAI<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
900 Positive Acknowledgement The code used when the accounting system positively<br />
acknowledges receipt <strong>and</strong> successful processing of the<br />
accounting transaction<br />
999 Invalid Incoming File No Specific Description<br />
Table G-4: DBMS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
005 Missing/Invalid Transaction Date Future date not acceptable<br />
009 Missing/Invalid Federal Organization Treasury Agency Symbol Code Departments<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
FY must be populated<br />
Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol No Specific Description<br />
Code (Appropriation - LOA)<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA) 4-digit suffix to basic symbol, subdivision of funds tied to<br />
funding purpose<br />
015 Missing/Invalid Fund Code IDs fund code; Table driven<br />
016 Missing/Invalid Resource Code - Object Class Code (WBS) No Specific Description<br />
019 Missing/Invalid Allotment Serial Number No Specific Description<br />
022 Missing/Invalid Accounting Class Reference Number No Specific Description<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC -<br />
SDN)<br />
Customer indicator required to build an SDN is missing/<br />
invalid<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) Identifies activity address code table<br />
029 Missing/Invalid Cost Account Code Identifies the cost accounting code table<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - Identifies general purpose <strong>and</strong> nature of product or server<br />
LOA)*<br />
034 Missing/Invalid Job Order No Specific Description<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier<br />
(AAA - LOA)<br />
Identifies accounting activity responsible for accounting service<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
049 Missing/Invalid AO Approval Date (Date Claim Accept/Approved Date) Approval date of trip record is invalid<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) Cannot process transaction<br />
051 Missing/Invalid Estimated Obligation Amount Cannot process transaction<br />
060 Missing/Invalid Adjusted Obligation Amount Insufficient Funds<br />
069 Missing/Invalid Accounting Line No Specific Description<br />
070 Cost Code Frozen on MADD Cost Code is present but in a frozen status in the MADD<br />
071 Cost Code, OBJ Class CD Unmatched to Matrix Cost Code/Object Class are not in the Matrix File for the<br />
stated Basic Symbol<br />
072 Transaction Unmatched to Operating Target Transaction does not match an Activity Code, Fund Code,<br />
ASN, ORG, Cost Code, Funds Distribution Indicator (FDI) in<br />
the detail operating target line<br />
073 Doc Number Exists with Different Status, Cancel <strong>and</strong> Reissue TON If a document number with a maintenance code A, P, or M<br />
(for <strong>DTS</strong> this is purpose code of 00, 01, 05 or 31) already<br />
exists on the database<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-9<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-4: DBMS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
074 Doc Exists - One or More Incoming Data Elements Unmatched If the Document already exists <strong>and</strong> any incoming data elements<br />
are different than those data elements existing in the<br />
report, reject<br />
075 Doc Already Completed If a document has been finalized <strong>and</strong> incoming transaction<br />
is not purpose code “31”, reject the transaction<br />
076 Doc Not On File If purpose code is 01, 05, or 31 (<strong>and</strong> maintenance code is<br />
not A, P, or M) <strong>and</strong> there is not an open document number<br />
in the history file for that incoming transaction, reject the<br />
document<br />
077 Duplicate TON/Doc Number Document number has been established manually within<br />
the system. Cannot process the transaction<br />
078 Doc Was Not Canceled Amounts do not equal zero when trying to can document<br />
(TON)<br />
079 Multiple Job Order Numbers on same Travel Order Number Only one Job Order Number allowed per Travel Order Number<br />
080 Missing/Invalid Transaction Set Control Number Should really be Missing/Invalid purpose code?<br />
157 Missing/Invalid Receivable Amount No Specific Description<br />
158 Receivable Amount Previously Established Cannot Process Adjustment No Specific Description<br />
159 Cannot Process Transaction - Disbursement Not Previously Recorded No Specific Description<br />
175 Write-off/Waiver/or Transfer record not processed. Accounts receivable Cannot process Write-off, Receivable Not Found<br />
record not found<br />
176 Write-off Amount Exceeds Receivable Amount No Specific Description<br />
177 Cannot Process Write-off Receivable not Found No Specific Description<br />
Table G-5: DCD<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
003 Missing/Invalid Total Transaction Amount Missing/Invalid total transaction amount<br />
054 Missing/Invalid ABA Routing Number No Specific Description<br />
055 Missing/Invalid Account Number CBA account number is m<strong>and</strong>atory field, must be valid<br />
102 Duplicate Record No Specific Description<br />
160 SSN Not Found in CEFT No Specific Description<br />
161 CEFT Profile is in a Deleted Status No Specific Description<br />
164 Invalid EFT information No Specific Description<br />
169 Duplicate LII The same LII was assigned to 2 different LOAs in the same<br />
Invoice; no 2 lines in an invoice can have the same LII -<br />
needs to be changed <strong>and</strong> resubmitted<br />
200 CEFT Profile is in a Suspended Status No Specific Description<br />
201 Treasury Level Line of Accounting Edits Failed No Specific Description<br />
Page G-10 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-6: DIFMS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
002 Missing/Invalid Transaction Type Action Code must be “A” or “C”<br />
003 Missing/Invalid Total Transaction Amount Total-Amt must be numeric <strong>and</strong> positive when ACTN-<br />
CD=”A”<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC - Restriction CD POS-3 must be “1”, “3” or “4”<br />
SDN)<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) IND JON Type must be P, G, or S; JON must be alphanumeric;<br />
JOB Closed - TXN Date cannot be > Close Date or<br />
Final Billed; Direct-JON-DATA-RECORD Not Found; Indirect-JON-DATA-RECORD<br />
Not Found; If ACTN-CD not “A”,<br />
RESTR-CD POS 3 Must be = 1,3,4 or 8<br />
038 Missing/Invalid Accounting Processing Code - Job Order Cost Code<br />
(Shop Number)<br />
Valid Shop Record not found; Shop Amendment must be<br />
blank for Action Code = A; CD-MFG-TYPE-CD Must Not =<br />
8 - Direct Cite CON; SHOP must be alphanumeric; AUTH<br />
SHOP REC not found; SHOP is no longer valid<br />
043 Missing/Invalid Social Security Number Name must be alphanumeric or blank or coma or period<br />
045 Missing/Invalid Employee Name name must be alphanumeric or blank or coma or period or<br />
dash; Name must be Present/Alphanumeric-BK when<br />
ACTN-CD = A<br />
048 Missing/Invalid Total Amount Of Payment Ticket-AMT must be numeric <strong>and</strong> positive when ACTN-CD<br />
= “A”; Ticket-AMT (Input-AMT + TRAV-REC-AMT) must be<br />
>=0; Ticket AMT must be numeric; SSN is m<strong>and</strong>atory when<br />
ACTN-CD is “A” or “C”<br />
049 Missing/Invalid AO Approval Date (Date Claim Accept/Approved Date) Date Accept must be numeric; Date Due must be numeric<br />
052 Missing/Invalid Per Diem/Advance/CBA Code Per-Diem-AMT must be numeric <strong>and</strong> positive when ACTN-<br />
CD = “A”; Per-Diem-AMT (INPUT-AMT + TRAV-REC-AMT)<br />
must be >=0; Per-Diem-AMT must be numeric<br />
063 Missing/Invalid Date Received Date Accept <strong>and</strong> Date Due must be blank when Action<br />
Code = A<br />
068 Missing/Invalid Accounts Receivable ACCTS-Receivable (DUE US) must be numeric (can be<br />
zero); ACRN is Required - must be alphanumeric<br />
078 Doc Was Not Canceled If Void-TR-IND = “Y” Only when SHOP-AMEND = “CAN”; If<br />
Turn In Ticket = Y Shop AMEND NBR must not be “CAN”;<br />
VOID-TR-IND must be alphanumeric; TURN-IN-TIC must<br />
be alphanumeric<br />
080 Missing/Invalid Transaction Set Control Number Invalid Transaction Set Purpose Code<br />
084 Missing data to build SDN Document Number is m<strong>and</strong>atory - must be alphanumeric;<br />
DOC NBR 9 <strong>and</strong> 10 must be “TO” or “T0”<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) Date Effect is not within calendar range; Date Effect must<br />
be numeric<br />
102 Duplicate Record Travel Accrual REC already exists for input JON<br />
114 Missing Invalid Number of Days Travel Days must be present <strong>and</strong> numeric<br />
128 Insufficient Funds at Appropriation Level / Living Lapsed Appropriation TXN CAUES CI Level Funds to be exceeded for Old JON<br />
137 Unmatched Obligation Adjustment Travel Accrual REC Not Found for INPUT JON<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-11<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-6: DIFMS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
139 Missing/Invalid Obligation Transaction Other-AMT must be numeric <strong>and</strong> positive when ACTN-CD<br />
= “A”; POV=AMT must be numeric <strong>and</strong> positive when<br />
ACTN-CD = “A”; Other-AMT (INPUT-AMT + TRAV-REC-<br />
AMT) must be >=0; POV-AMT (INPUT-AMY = TRAV-REC-<br />
AMT) must be >=0; Other AMT must be numeric; POV-<br />
AMT must be numeric<br />
140 Missing/Invalid Cancellation Amount All ACRL-AMT & ACRL-AMT-LIQD Must = 0 when<br />
AMEND-NBR='CAN'<br />
165 Void-TR-IND must be alphanumeric, only present for ACTN-CD-D Void-TR-IND must be alphanumeric, only present for<br />
ACTN-CD-D<br />
166 TURN-IN-TIC must be alphanumeric, only present for ACTN-CD-C TURN-IN-TIC must be alphanumeric, only present for<br />
ACTN-CD-C<br />
167 TRN is required - must be alphanumeric TRN is required - must be alphanumeric<br />
168 CUI-RT-ID must be “CUI EAST” CUI-RT-ID must be “CUI EAST”<br />
178 TXN-IS is required - must be alphanumeric TXN-IS is required - must be alphanumeric<br />
900 Valid Message Received Positive Acknowledgement<br />
Table G-7: DWAS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
002 Missing/Invalid Transaction Type Missing/Invalid total transaction required for appr. format<br />
003 Missing/Invalid Total Transaction Amount Missing/Invalid total transaction amount<br />
005 Missing/Invalid Transaction Date Missing/Invalid transaction date required to build SDW<br />
009 Missing/Invalid Federal Organization Treasury Agency Symbol Code Departments<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
Missing/Invalid FY required to build the SDW<br />
Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol Missing/Invalid fund symbol required for appr. format<br />
Code (Appropriation - LOA)<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA) Subhead required for appropriate format<br />
018 Missing/Invalid Bureau Control Number (BCN - LOA) No specific description<br />
021 Missing/Invalid Sub-Allotment - Sub Allotment Number (Sub Allotment -<br />
LOA)<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC -<br />
SDN)<br />
No specific description<br />
Customer indicator required to build an SDN is missing/<br />
invalid<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) Identifies activity address code table<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class -<br />
LOA)*<br />
031 Missing/Invalid Budget Program Activity - Activity Identifier (Service<br />
Code - SDN)<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier<br />
(AAA - LOA)<br />
Identifies general purpose <strong>and</strong> nature of product or server<br />
Cannot process transaction<br />
043 Missing/Invalid Social Security Number No specific description<br />
Identifies accounting activity responsible for accounting services<br />
Page G-12 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-7: DWAS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) No specific description<br />
051 Missing/Invalid Estimated Obligation Amount Cannot process transaction<br />
060 Missing/Invalid Adjusted Obligation Amount Insufficient funds<br />
083 Missing/Invalid DUNS/DUNS+4 No specific description<br />
084 Missing data to build SDN One or more of the elements required to build the st<strong>and</strong>ard<br />
document number are missing/invalid<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) Estimated trip start date missing or not valid<br />
086 Missing/Invalid estd-complt-date Estimated trip ending date missing or not valid<br />
087 No Header Record in Set No specific description<br />
088 No Detail Record in Set No specific description<br />
Table G-8: eBIZ<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
002 Missing/Invalid Transaction Type No Specific Description<br />
003 Missing/Invalid Total Transaction Amount No Specific Description<br />
005 Missing/Invalid Transaction Date Missing/Invalid Date Interchange Data<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
Missing/Invalid Budget Fiscal Year<br />
Year - LOA)<br />
028 Missing/Invalid Work Center No Specific Description<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - No Specific Description<br />
LOA)<br />
032 Missing/Invalid Project/Sub Project No Specific Description<br />
034 Missing/Invalid Job Order No Specific Description<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier No Specific Description<br />
(AAA - LOA)<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
045 Missing/Invalid Employee Name No Specific Description<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) No Specific Description<br />
051 Missing/Invalid Estimated Obligation Amount Missing/Invalid Amount<br />
069 Missing/Invalid Accounting Line No Specific Description<br />
074 Doc Exists - One or More Incoming Data Elements Unmatched No Specific Description<br />
076 Doc Not On File No Specific Description<br />
078 Doc Was Not Canceled No Specific Description<br />
080 Missing/Invalid Transaction Set Control Number No Specific Description<br />
081 Missing/Invalid Header Missing/Invalid Application Header<br />
094 Invalid Detail Record No Specific Description<br />
102 Duplicate Record No Specific Description<br />
128 Insufficient Funds at Appropriation Level / Living Lapsed Appropriation Insufficient Funds at Appropriation Level<br />
139 Missing/Invalid Obligation Transaction No Specific Description<br />
143 Missing/Invalid Defense Agency Level Organization No Specific Description<br />
144 Missing/Invalid Major Comm<strong>and</strong> Level Organization No Specific Description<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-13<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-8: eBIZ (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
145 Missing/Invalid Field Level Organization No Specific Description<br />
149 Transaction Purpose Code Not on LOA The transaction purpose code = R0, R5, W1 or W5 <strong>and</strong> the<br />
LOA elements on the incoming transaction do not match<br />
the LOA elements on the referenced document<br />
150 Transaction Purpose Code Not in the System The transaction purpose code = R0, R5, W1 or W5 <strong>and</strong> a<br />
referenced document does not exist in the accounting system<br />
(ex: eBiz)<br />
151 Cannot Process Accounts Receivable, Advance Disbursement Amount<br />
Not equal to $0.00<br />
The transaction purpose code = R0, R5, W1 or W5 <strong>and</strong> a<br />
referenced document does not exist in the accounting system<br />
(ex: e-Biz)<br />
Table G-9: GAFS-<strong>DTS</strong><br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
001 Missing/Invalid CTO Office Identifier N102 <strong>DTS</strong> CUI Name; N104 <strong>DTS</strong> CUI DUNS or DUNS +4<br />
002 Missing/Invalid Transaction Type No Specific Description<br />
003 Missing/Invalid Total Transaction Amount Header total <strong>and</strong> transaction out of balance<br />
004 Missing/Invalid Disbursed Amount Transaction out of balance<br />
005 Missing/Invalid Transaction Date No Specific Description<br />
006 Missing/Invalid Billed Amount No Specific Description<br />
007 Missing/Invalid Voucher Number No Specific Description<br />
008 Missing/Invalid Disbursing Office/Disbursing Station Symbol Identifier No Specific Description<br />
009 Missing/Invalid Federal Organization Treasury Agency Symbol Code Missing/Invalid Departments<br />
010 Missing/Invalid Transfer Dept Indicator - Transfer Agency (Transferring Missing/invalid transferring agency required for appr. format<br />
Agency - LOA)<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
Missing/Invalid Fiscal Year<br />
Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol Missing/Invalid Fund Symbol required for appr. format<br />
Code (Appropriation - LOA)<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA) Missing/Invalid Limitation<br />
014 Missing/Invalid Program Year No Specific Description<br />
015 Missing/Invalid Fund Code No Specific Description<br />
016 Missing/Invalid Resource Code - Object Class Code (WBS) Missing/Invalid EEIC/SRAN<br />
017 Missing/Invalid Operating Agency Code Missing/Invalid Operating Agency Code (OAC)<br />
018 Missing/Invalid Bureau Control Number (BCN - LOA) No Specific Description<br />
019 Missing/Invalid Allotment Serial Number No Specific Description<br />
020 Missing/Invalid Op Budget Activity Number - Op Budget Acct Number Missing/Invalid Operating Budget Account Number (OBAN)<br />
(Tran. Type Code - LOA)<br />
021 Missing/Invalid Sub-Allotment - Sub Allotment Number (Sub Allotment - No Specific Description<br />
LOA)<br />
022 Missing/Invalid Accounting Class Reference Number No Specific Description<br />
023 Missing/Invalid Reimbursement Billing Code No Specific Description<br />
024 Missing/Invalid Reimbursement Order Number Missing/Invalid sales code<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC -<br />
SDN)<br />
Customer indicator required to build a SDN is missing/<br />
invalid; No specific description<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) Missing/Invalid RCCC, only “A” accepted<br />
Page G-14 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-9: GAFS-<strong>DTS</strong> (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
027 Missing/Invalid Fund Administrator Missing/Invalid Budget Activity Code (BAC)<br />
028 Missing/Invalid Work Center No Specific Description<br />
029 Missing/Invalid Cost Account Code Missing/Invalid Cost Account Code (SMC/CSN)<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - No Specific Description<br />
LOA)<br />
031 Missing/Invalid Budget Program Activity - Activity Identifier (Service Code No Specific Description<br />
- SDN)<br />
032 Missing/Invalid Project/Sub Project Missing/Invalid Project/Sub project or BPAC Number/66<br />
Number/MIPR Number<br />
033 Missing/Invalid Fund Control Number/Mord Number/616 Number/MIPR No Specific Description<br />
Number<br />
034 Missing/Invalid Job Order Missing/Invalid Program Element Code (PEC)<br />
035 Missing/Invalid Special Ops/Management Decision Package Missing/Invalid DIFMS Object Class<br />
036 Missing/Invalid Emergency/Special Program Code Missing/Invalid ESP Code<br />
037 Missing/Invalid Budget Reporting Code Missing/Invalid DIFMS Contractual Others Code<br />
038 Missing/Invalid Accounting Processing Code - Job Order Cost Code Job Order number/BCE work order number<br />
(Shop Number)<br />
039 Missing/Invalid Cost Allocation Code - Job Number/Local Use (Other No Specific Description<br />
Function Code)<br />
040 Missing/Invalid Project Account/Program Element Code Missing/Invalid FMS data (Case, County, Line)<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier (AAA Missing/Invalid ADSN<br />
- LOA)<br />
042 Missing/Invalid IBOP Missing/Invalid International Balance of Payment Code<br />
(IBOP)<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
044 Missing/Invalid Pay Grade No Specific Description<br />
045 Missing/Invalid Employee Name No Specific Description<br />
046 Missing/Invalid Remit To Information No Specific Description<br />
047 Missing/Invalid Payment Method No Specific Description<br />
048 Missing/Invalid Total Amount Of Payment Transaction out of balance/payment amount not equal to<br />
accounting details<br />
049 Missing/Invalid AO Approval Date (Date Claim Accept/Approved Date) No Specific Description<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) No Specific Description<br />
051 Missing/Invalid Estimated Obligation Amount Transaction out of balance/total obligation amount not equal<br />
to accounting details; insufficient funds<br />
052 Missing/Invalid Per Diem/Advance/CBA Code No Specific Description<br />
053 Missing/Invalid Invoice Number No Specific Description<br />
054 Missing/Invalid ABA Routing Number No Specific Description<br />
055 Missing/Invalid Account Number No Specific Description<br />
056 Missing/Invalid Remittance Advice Number No Specific Description<br />
057 Missing/Invalid Payee Information No Specific Description<br />
058 Missing/Invalid Old Obligation Amount No Specific Description<br />
059 Missing/Invalid Credit/Debit Obligation Amount No Specific Description<br />
060 Missing/Invalid Adjusted Obligation Amount No Specific Description<br />
061 Missing/Invalid Prompt Payment Act No Specific Description<br />
062 Missing/Invalid CBA Invoice Date No Specific Description<br />
063 Missing/Invalid Date Received No Specific Description<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-15<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-9: GAFS-<strong>DTS</strong> (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
064 Missing/Invalid Gross Amount Of Payment No Specific Description<br />
065 Missing/Invalid Credit Amount No Specific Description<br />
066 Missing/Invalid Net Amount No Specific Description<br />
067 Missing/Invalid Deferred Amount No Specific Description<br />
068 Missing/Invalid Accounts Receivable No Specific Description<br />
069 Missing/Invalid Accounting Line Missing/Invalid appropriation element (includes Department,<br />
Transfer Department, Basic Symbol, <strong>and</strong> Limitation)<br />
070 Cost Code Frozen on MADD No Specific Description<br />
071 Cost Code, OBJ Class CD Unmatched to Matrix No Specific Description<br />
072 Transaction Unmatched to Operating Target No Specific Description<br />
073 Doc Number Exists with Different Status, Cancel <strong>and</strong> Reissue TON No Specific Description<br />
074 Doc Exists - One or More Incoming Data Elements Unmatched No Specific Description<br />
075 Doc Already Completed No Specific Description<br />
076 Doc Not On File No Specific Description<br />
077 Duplicate TON/Doc Number No Specific Description<br />
078 Doc Was Not Canceled No Specific Description<br />
079 Multiple Job Order Numbers on same Travel Order Number No Specific Description<br />
080 Missing/Invalid Transaction Set Control Number No Specific Description<br />
081 Missing/Invalid Header No Specific Description<br />
082 Missing control number No Specific Description<br />
083 Missing/Invalid DUNS/DUNS+4 No Specific Description<br />
084 Missing data to build SDN No Specific Description<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) No Specific Description<br />
086 Missing/Invalid estd-complt-date No Specific Description<br />
087 No Header Record in Set Incomplete file cannot process missing 01 loop<br />
088 No Detail Record in Set Incomplete file cannot process missing 02 loop<br />
089 No Summary Record in Set Incomplete file cannot process missing 03 loop<br />
090 No Header or Detail Records in Set No Specific Description<br />
091 No Summary or Detail Records in Set No Specific Description<br />
092 No Loop ID in Detail Record Incomplete file cannot process missing loop ID in 02 record<br />
093 Invalid detail Record Order No Specific Description<br />
094 Invalid Detail Record Incomplete file cannot process invalid 02 loop<br />
095 No Header <strong>and</strong> Invalid Detail Order No Specific Description<br />
096 No Summary <strong>and</strong> Invalid Detail Order No Specific Description<br />
097 Invalid Transaction Type in Obligation/Payment Record Must be 00, 01, 05, or 31 for obligations <strong>and</strong> 14, 20, 22, 25<br />
or 41 for payments<br />
098 Missing/Invalid Type Action No Specific Description<br />
099 Missing/Invalid Block Number No Specific Description<br />
100 Missing/Invalid Obligation Data Code No Specific Description<br />
101 Missing/Invalid Liquidation Indicator Code No Specific Description<br />
102 Duplicate Record No Specific Description<br />
103 Missing Invalid Project Unit No Specific Description<br />
104 Project Directive Line Item already exists for another Project Unit No Specific Description<br />
105 Project Unit Exist on another Project Directive Line Item No Specific Description<br />
106 Missing Invalid Project Directive Line Item No Specific Description<br />
107 Missing Invalid Project Directive Line Item Suffix No Specific Description<br />
Page G-16 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-9: GAFS-<strong>DTS</strong> (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
108 Missing Invalid Input Type Code No Specific Description<br />
109 Missing Invalid Processing Action Code No Specific Description<br />
110 Subhead not on Chart of Accounts No Specific Description<br />
111 Requiring Financial Manager not on Chart of Accounts No Specific Description<br />
112 Project unit not on Chart of Accounts No Specific Description<br />
113 Missing Invalid Revision Number No Specific Description<br />
114 Missing Invalid Number of Days No Specific Description<br />
115 Participating Manager; Sub Allotment; Project Unit does not meet CMET No Specific Description<br />
edits<br />
116 Amount Sign does not agree with Action Code No Specific Description<br />
117 Major Comm<strong>and</strong>; Fiscal Year; Appropriation; Subhead does not meet No Specific Description<br />
CMET edits<br />
118 Requiring Financial Manager; Project Unit does not meet CMET edits No Specific Description<br />
119 Major Claimant Indicator Invalid No Specific Description<br />
120 Missing Invalid Operating Budget UIC No Specific Description<br />
121 Revision Number Present with Action Code A No Specific Description<br />
122 Project Directive Line Item Suffix Invalid: Appropriation expired or lapsed No Specific Description<br />
123 Reimbursable segment missing for this Project Unit No Specific Description<br />
124 Operating Budget UIC must be 000140 for a W Subhead No Specific Description<br />
125 Major Claimant required for DARPA Appropriation No Specific Description<br />
126 Major Claimant does not match Chart of Accounts No Specific Description<br />
127 Operating Budget UIC must be 000140 for DARPA Appropriation No Specific Description<br />
128 Insufficient Funds at Appropriation Level / Living Lapsed Appropriation No Specific Description<br />
129 Appropriation No Longer Available for Travel Obligations No Specific Description<br />
130 Operating Budget UIC must be 000230 for this Requiring Financial Manager<br />
No Specific Description<br />
131 Operating Budget UIC must be 000240 for this Requiring Financial Manager<br />
No Specific Description<br />
132 Operating Budget UIC must be 000390 for this Requiring Financial Manager<br />
No Specific Description<br />
133 Operating Budget UIC must be 000190 for this Requiring Financial Manager<br />
No Specific Description<br />
134 Operating Budget UIC must be 000750 for this Requiring Financial Manager<br />
No Specific Description<br />
135 Change of OMB Object Class Invalid After Travel Disbursement No Specific Description<br />
136 Accounting Data does not meet CMET edits No Specific Description<br />
137 Unmatched Obligation Adjustment No Specific Description<br />
138 Job Order Fiscal Year unmatched to SDN Fiscal Year No Specific Description<br />
139 Missing/Invalid Obligation Transaction No Specific Description<br />
140 Missing/Invalid Cancellation Amount No Specific Description<br />
666 Test No Specific Description<br />
900 Valid Message Received Positive Acknowledgement<br />
999 Invalid Incoming File No Specific Description<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-17<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-10: GFEBS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
002 Missing/Invalid Transaction Type No Specific Description<br />
015 Missing/Invalid Fund Code No Specific Description<br />
028 Missing/Invalid Work Center No Specific Description<br />
029 Missing/Invalid Cost Account Code No Specific Description<br />
076 Document not on File No original document posted<br />
102 Duplicate Record No Specific Description<br />
405 Missing/Invalid Debt Amount No Specific Description<br />
500 Missing/Invalid Agency Accounting Identifier Code Incorrect accountable station used<br />
501 Missing/Invalid Department Regular Code (Acct 1) Missing/Invalid Department Regular for Cost Object used<br />
502 Missing/Invalid Transfer Code (Acct 1) Missing/Invalid Department Transfer for Cost Object used<br />
503 Missing/Invalid Main Account Code (Acct 1) Missing/Invalid Main Account for Cost Object used<br />
504 Missing/Invalid Sub Account Code (Acct 2) Missing/Invalid Sub Account for Cost Object used<br />
505 Missing/Invalid Period of Availability Fiscal Year Date (Acct 2) Invalid Period of Availability for Cost Object used<br />
506 Missing/Invalid FMS Customer Code (Acct 2) No Specific Description<br />
507 Missing/Invalid FMS Case Identifier (Acct 3) No Specific Description<br />
508 Missing/Invalid FMS Case Line Item Identifier (Acct 3) No Specific Description<br />
509 Missing/Invalid Budget Line Item Identifier (Acct 4) Invalid Budget Line Item Identifier for Cost Object used<br />
510 Missing/Invalid Fund Center Identifier (Acct 5) Invalid Fund Center Identifier for Cost Object used<br />
511 Missing/Invalid First Instance of Cost Object (Acct 6) Invalid Cost Object/Cost Object Type<br />
512 Missing/Invalid First Instance of Cost Object Type (Acct 6) Invalid Cost Object Type for Cost Object used<br />
513 Missing/Invalid Second Instance of Cost Object (Acct 7 <strong>and</strong> 8) Invalid Cost Object/Cost Object Type<br />
514 Missing/Invalid Second Instance of Cost Object Type (Acct 8) Invalid Cost Object Type for Cost Object used<br />
515 Missing/Invalid Appropriation Limit (Acct 8) Invalid Limit for Cost Object used<br />
516 Missing/Invalid Future Use (Acct 9) No Specific Description<br />
517 Missing/Invalid User Defined Field (Acct 10) No Specific Description<br />
518 Insufficient Funding Available Funding not available for Cost Object used<br />
519 Accounting Processing <strong>Error</strong> Processing <strong>Error</strong>, Contact Accounting<br />
900 Positive Acknowledgement The code used when the accounting system positively<br />
acknowledges receipt <strong>and</strong> successful processing of the<br />
accounting transaction<br />
901 <strong>GEX</strong> Automatic Positive Acknowledgement No Specific Description<br />
999 Invalid Incoming File No Specific Description<br />
Table G-11: MCTFS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
401 Duplicate Transaction Duplicate Transaction<br />
402 No Matching debt maintained in MCTFS No matching debt maintained in MCTFS or debt prev.<br />
stopped/collected in full<br />
403 No Matching SSN maintained in MCTFS; first byte of SSN not equal to ‘0’ No Matching SSN maintained in MCTFS; first byte of SSN<br />
not equal to ‘0’<br />
404 Incoming file future dated Time-stamp (transaction Date) on incoming DMPC file is<br />
future dtd<br />
Page G-18 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-11: MCTFS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
405 Missing/Invalid Amount LINE-OBL-AMT is not numeric or is not > $0.00<br />
406 Missing/Invalid Amount LINE-OBL-AMT-PER-PAY-PERIOD is not numeric or is not<br />
equal to $0.00<br />
407 Member Deceased killed in action; noncombat Member deceased<br />
408 Inactive record; SSN change; fraudulent enlistment Inactive record; SSN change, fraudulent enlistment<br />
409 Inactive reservist Inactive reservist<br />
410 Separated Separated<br />
411 Retired Retired<br />
412 Purpose Code Invalid, must be (N, S, or C) - Purpose Code invalid - not equal to N, S, or C<br />
413 Incomplete Record (LII, SDN, Routing-Indicator, Transaction-ID not populated<br />
or contains invalid data) -<br />
Incomplete Record (LII, SDN, Routing-Indicator, Transaction-ID<br />
not populated or contains invalid data)<br />
414 Member Deceased killed in action; noncombat Member deceased - returned uncollectible via MCTFS<br />
415 Inactive Reservist Inactive Reservist - returned uncollectible via MCTFS<br />
416 Separated Separated - returned uncollectible via MCTFS<br />
417 Retired Retired - returned uncollectible via MCTFS<br />
Table G-12: SABRS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
001 Missing/Invalid CTO Office Identifier Header/Vendor ID<br />
002 Missing/Invalid Transaction Type EDI-IC<br />
003 Missing/Invalid Total Transaction Amount The SUM of the LONE OBL AMOUNTS within the Detail,<br />
Records of the Transaction Set does not equal the SUM of<br />
the AMOUNT within the Header Record; Header total transaction<br />
out of balance<br />
005 Missing/Invalid Transaction Date The CENTURY or TIME STAMP within the Header Record<br />
is invalid; Header “file pull date”<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
Year - LOA)<br />
Trip received is for a Future year; CCYY, 1st year funds are<br />
available<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA) 4-digit suffix to basic symbol, subdivision of funds tied to<br />
funding purposes<br />
015 Missing/Invalid Fund Code (1) Fund Code received was not found on X FUND CODE<br />
Table 020. (2) Activity Address Code (Unit Identifier) <strong>and</strong><br />
Fund Code was not found on CIF Default Table 302<br />
016 Missing/Invalid Resource Code - Object Class Code (WBS) No Specific Description<br />
018 Missing/Invalid Bureau Control Number (BCN - LOA) 5-digit identifies distribution of funds<br />
021 Missing/Invalid Sub-Allotment - Sub Allotment Number (Sub Allotment - 1 digit identifies sub-allotment recipient<br />
LOA)<br />
022 Missing/Invalid Accounting Class Reference Number No Specific Description<br />
023 Missing/Invalid Reimbursement Billing Code Identifies reimbursement billing code table<br />
024 Missing/Invalid Reimbursement Order Number Identifies reimbursement order number table<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-19<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-12: SABRS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) (1) Activity Address Code (Unit Identifier) was not found on<br />
AAC ID Table 208. (2) Financial Information Pointer (FIP)<br />
was not found on S FIP Table 073.; Identifies activity<br />
address code table<br />
027 Missing/Invalid Fund Administrator WORK CTR ID, BUD EXEC ACTY, <strong>and</strong> BUD EXEC SUB-<br />
ACTY combination was not found on WORK CTR ID table<br />
207; Identifies the organization managing funds<br />
028 Missing/Invalid Work Center Identifies work center table; Identifies cost accounting code<br />
table<br />
029 Missing/Invalid Cost Account Code Cost Account Code (CAC) was not found on X CAC Table<br />
014<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - Identifies general purpose <strong>and</strong> nature of product or server<br />
LOA)*<br />
033 Missing/Invalid Fund Control Number/Mord Number/616 Number/MIPR No Specific Description<br />
Number<br />
037 Missing/Invalid Budget Reporting Code (1) Local Special Interest Code was not found on L SPCL<br />
INTEREST CODE Table 234. (2) Central Interest Code was<br />
not found on SPCLINTRST Table 228.<br />
039 Missing/Invalid Cost Allocation Code - Job Number/Local Use (Other<br />
Function Code)<br />
No Specific Description<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier (AAA<br />
- LOA)<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
Identifies accounting activity responsible for accounting services<br />
044 Missing/Invalid Pay Grade Identifies civilian or military level<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) St<strong>and</strong>ard Document Number Serial (Trip Record Number) is<br />
Missing or Invalid<br />
051 Missing/Invalid Estimated Obligation Amount LINE OBL AMOUNT is not Numeric or is less than $0.00<br />
052 Missing/Invalid Per Diem/Advance/CBA Code Charge Code is missing or invalid<br />
075 Doc Already Completed Processing Action Code of transaction is equal to “I”, but<br />
previous accounting record found in a Completed or Retired<br />
Status.; If a documents has been finalized <strong>and</strong> incoming<br />
transaction is not purpose code “31”, reject the transaction.<br />
076 Doc Not On File Processing Action Code of transaction is equal to “M”, but<br />
previous accounting record was not found<br />
077 Duplicate TON/Doc Number Processing Action Code of transaction is equal to “I”, but<br />
previous accounting record found (Dupe); Document number<br />
has been established manually within the system. Cannot<br />
process the transaction.<br />
078 Doc Was Not Canceled (1) Processing Action Code of transaction is equal to “I”, but<br />
current Accounting Obligation is equal to $0.00 (2) Processing<br />
Action Code of transaction is equal to “C”, but Current<br />
Accounting Record has either <strong>and</strong> Advance or Disbursement/<br />
CBA Disbursement recorded.; Amounts do not equal<br />
zero when trying to cancel document (TON)<br />
080 Missing/Invalid Transaction Set Control Number Transaction Set Control Number is Blank<br />
081 Missing/Invalid Header Use for duplicate file check<br />
082 Missing control number Use for duplicate file check<br />
Page G-20 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-12: SABRS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
083 Missing/Invalid DUNS/DUNS+4 DUNS-DUNS+4 is Blank<br />
084 Missing data to build SDN St<strong>and</strong>ard Document Number, Document Type Code does<br />
not equal “TO”<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) Missing/Invalid proceed on-or-about date<br />
086 Missing/Invalid estd-complt-date Missing/Invalid estd-complt-date<br />
087 No Header Record in Set Routing Indicator within the Header Record does<br />
088 No Detail Record in Set No Specific Description<br />
089 No Summary Record in Set No Specific Description<br />
090 No Header or Detail Records in Set No Specific Description<br />
091 No Summary or Detail Records in Set No Specific Description<br />
092 No Loop ID in Detail Record No Specific Description<br />
094 Invalid Detail Record The number of Detail Records within the Transaction Set<br />
does not equal the number within the DETAIL COUNT<br />
within the Header Record<br />
095 No Header <strong>and</strong> Invalid Detail Order No Specific Description<br />
096 No Summary <strong>and</strong> Invalid Detail Order Summary record within the transaction set is missing<br />
097 Invalid Transaction Type in Obligation/Payment Record No Specific Description<br />
098 Missing/Invalid Type Action No Specific Description<br />
102 Duplicate Record Document number already exists for another line of<br />
accounting<br />
109 Missing Invalid Processing Action Code Processing Action Code is not equal to either “I”, “S”, “M”, or<br />
“C”<br />
111 Requiring Financial Manager not on Chart of Accounts Spending General Ledger Account Table 300 value was not<br />
found<br />
115 Participating Manager; Sub Allotment; Project Unit does not meet CMET<br />
edits<br />
A two-position alphanumeric character representing an<br />
organization or individual designated as having responsibility<br />
for acceptance <strong>and</strong> execution of a Project Directive (PD)<br />
issued by a RFM<br />
116 Amount Sign does not agree with Action Code Sign must be negative for action code delete, position for<br />
action code add, <strong>and</strong> negative or minus for action code<br />
change<br />
117 Major Comm<strong>and</strong>; Fiscal Year; Appropriation; Subhead does not meet<br />
CMET edits<br />
Subhead must be valid for major comm<strong>and</strong>s, fiscal year,<br />
<strong>and</strong> appropriation <strong>and</strong> it must be also valid on CMET edits<br />
119 Major Claimant Indicator Invalid Major Claimant is a bureau, office, comm<strong>and</strong> designated as<br />
an administering office<br />
128 Insufficient Funds at Appropriation Level / Living Lapsed Appropriation Trip exceeds Available Funding <strong>and</strong> or RECTYPE 6 Key<br />
was not found on the Fund Control Spend File<br />
137 Unmatched Obligation Adjustment No Specific Description<br />
138 Job Order Fiscal Year unmatched to SDN Fiscal Year (1) Two Digit year St<strong>and</strong>ard Document Number is not<br />
Numeric. (2) St<strong>and</strong>ard Document Number Two-Digit Year<br />
does not match FY FULL. (3) Basic Symbol <strong>and</strong> FY FULL<br />
combination was not found on Basic Sym Table 206<br />
151 Cannot Process Accounts Receivable, Advance Disbursement Amount<br />
Not equal to $0.00<br />
Cannot Process Accounts Receivable, Advance Disbursement<br />
Not equal to $0.00<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-21<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-12: SABRS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
152 Cannot Process Accounts Receivable, Advance Disbursement Amount<br />
Not equal to $0.00<br />
Cannot process Accounts Receivable, Disbursement equal<br />
to $0.00<br />
153 Duplicate Accounts Receivable Received Duplicate Accounts Receivable Received<br />
154 Accounts Receivable Amount is greater than disbursed Amount Accounts Receivable Amount is greater than disbursed<br />
amount<br />
155 Cannot cancel Accounts Receivable - Accounts Receivable already<br />
equal to $0.00<br />
Cannot cancel Accounts Receivable, Accounts Receivable<br />
System already equal to $0.00<br />
156 Public Debt Type Invalid or Blank Public Debt Type invalid or Blank<br />
170 Amount must be greater than $225.00 Transaction received (WT1) attempted to write off Out of<br />
Service Debt (OOSD) for $225.00 or greater, but existing<br />
Refund Received Amount (RRE) is less than $225.00.<br />
171 Amount must be equal to $225.00 Transaction received (WT1) attempted to write off Out of<br />
Service Debt (OOSD) for $225.00 or greater, but existing<br />
Refund Received Amount (RRE) does not equal (WT1)<br />
Amount.<br />
172 Disbursement must correlate to the actual disbursed amount Transaction received (WV1, WV5, or WW1) amount is<br />
greater than existing LIQ-AMT (Funds Disbursed). ** (Would<br />
create a negative Disbursement if processed).<br />
173 Refund amount is greater than amount disbursed, refund amount need to<br />
be determined<br />
Transaction received (WW1) attempted to write off Out of<br />
Service Debt (OOSD) for less than $225.00, but Refund<br />
Received Amount (RRE) is greater than or equal to<br />
$225.00.<br />
174 Refund amount incorrect, must determine refund amount Transaction received (WW1) attempted to write off Out of<br />
Service Debt (OOSD) for less than $225.00, but Refund<br />
Received Amount (RRE) does not equal (WT1) Amount.<br />
Table G-13: SFIS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
500 Missing/Invalid Agency Accounting Identifier Code (Acct 1) No Specific Description<br />
501 Missing/Invalid Department Regular Code (Acct 1) No Specific Description<br />
502 Missing/Invalid Department Transfer Code (Acct 1) No Specific Description<br />
503 Missing/Invalid Main Account Code (Acct 1) No Specific Description<br />
504 Missing/Invalid Sub Account Code (Acct 2) No Specific Description<br />
505 Missing/Invalid Period of Availability Fiscal Year Date (Acct 2) No Specific Description<br />
506 Missing/Invalid FMS Customer Code (Acct 2) No Specific Description<br />
507 Missing/Invalid FMS Case Identifier (Acct 3) No Specific Description<br />
508 Missing/Invalid FMS Case Line Item Identifier (Acct 3) No Specific Description<br />
509 Missing/Invalid Budget Line Item Identifier (Acct 4) No Specific Description<br />
510 Missing/Invalid Fund Center Identifier (Acct 5) No Specific Description<br />
511 Missing/Invalid First Instance of Cost Object (Acct 6) No Specific Description<br />
512 Missing/Invalid First Instance of Cost Object Type (Acct 6) No Specific Description<br />
513 Missing/Invalid Second Instance of Cost Object (Acct 7 <strong>and</strong> 8) No Specific Description<br />
514 Missing/Invalid Second Instance of Cost Object Type (Acct 8) No Specific Description<br />
515 Missing/Invalid Appropriation Limit (Acct 8) No Specific Description<br />
516 Missing/Invalid Future Use (Acct 9) No Specific Description<br />
517 Missing/Invalid User Defined Field (Acct 10) No Specific Description<br />
Page G-22 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-13: SFIS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
518 Insufficient Funding Available No Specific Description<br />
519 Accounting Processing <strong>Error</strong> No Specific Description<br />
Table G-14: SOMARDS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
003 Missing/Invalid Total Transaction Amount No Specific Description<br />
004 Missing/Invalid Disbursed Amount No Specific Description<br />
005 Missing/Invalid Transaction Date No Specific Description<br />
006 Missing/Invalid Billed Amount No Specific Description<br />
007 Missing/Invalid Voucher Number No Specific Description<br />
008 Missing/Invalid Disbursing Office/Disbursing Station Symbol Identifier No Specific Description<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
No Specific Description<br />
Year - LOA)*<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol No Specific Description<br />
Code (Appropriation - LOA)*<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA)* No Specific Description<br />
014 Missing/Invalid Program Year No Specific Description<br />
017 Missing/Invalid Operating Agency Code No Specific Description<br />
019 Missing/Invalid Allotment Serial Number No Specific Description<br />
020 Missing/Invalid Op Budget Activity Number - Op Budget Acct Number No Specific Description<br />
(Tran. Type Code - LOA)<br />
021 Missing/Invalid Sub-Allotment - Sub Allotment Number (Sub Allotment - No Specific Description<br />
LOA)<br />
022 Missing/Invalid Accounting Class Reference Number No Specific Description<br />
023 Missing/Invalid Reimbursement Billing Code No Specific Description<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) No Specific Description<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - No Specific Description<br />
LOA)<br />
034 Missing/Invalid Job Order No Specific Description<br />
038 Missing/Invalid Accounting Processing Code - Job Order Cost Code No Specific Description<br />
(Shop Number)<br />
039 Missing/Invalid Cost Allocation Code - Job Number/Local Use (Other No Specific Description<br />
Function Code)<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier (AAA No Specific Description<br />
- LOA)<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
044 Missing/Invalid Pay Grade No Specific Description<br />
045 Missing/Invalid Employee Name No Specific Description<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-23<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-14: SOMARDS (Continued)<br />
046 Missing/Invalid Remit To Information No Specific Description<br />
047 Missing/Invalid Payment Method No Specific Description<br />
048 Missing/Invalid Total Amount Of Payment No Specific Description<br />
049 Missing/Invalid AO Approval Date (Date Claim Accept/Approved Date) Approval date of trip record is invalid<br />
051 Missing/Invalid Estimated Obligation Amount No Specific Description<br />
053 Missing/Invalid Invoice Number No Specific Description<br />
057 Missing/Invalid Payee Information No Specific Description<br />
059 Missing/Invalid Credit/Debit Obligation Amount No Specific Description<br />
060 Missing/Invalid Adjusted Obligation Amount No Specific Description<br />
063 Missing/Invalid Date Received No Specific Description<br />
069 Missing/Invalid Accounting Line No Specific Description<br />
109 Missing Invalid Processing Action Code No Specific Description<br />
128 Insufficient Funds at Appropriation Level / Living Lapsed Appropriation Obligation exceeds authorized funds at appropriation level<br />
129 Appropriation No Longer Available for Travel Obligations Appropriation is no longer available for travel obligations.<br />
Invalid appropriation amount.<br />
141 Sub Job Order received contains embedded blanks or special characters No Specific Description<br />
142 Missing/Invalid IFS-M No Specific Description<br />
Table G-15: SRD-1<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
001 Missing/Invalid CTO Office Identifier N102 <strong>DTS</strong> CUI Name; N104 <strong>DTS</strong> CUI DUNS or DUNS+4<br />
002 Missing/Invalid Transaction Type No Specific Description<br />
003 Missing/Invalid Total Transaction Amount No Specific Description<br />
004 Missing/Invalid Disbursed Amount Transaction out of balance<br />
005 Missing/Invalid Transaction Date No Specific Description<br />
006 Missing/Invalid Billed Amount No Specific Description<br />
007 Missing/Invalid Voucher Number No Specific Description<br />
008 Missing/Invalid Disbursing Office/Disbursing Station Symbol Identifier No Specific Description<br />
009 Missing/Invalid Federal Organization Treasury Agency Symbol Code No Specific Description<br />
010 Missing/Invalid Transfer Dept Indicator - Transfer Agency (Transferring No Specific Description<br />
Agency - LOA)<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
No Specific Description<br />
Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol No Specific Description<br />
Code (Appropriation - LOA)<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA) No Specific Description<br />
014 Missing/Invalid Program Year No Specific Description<br />
015 Missing/Invalid Fund Code No Specific Description<br />
016 Missing/Invalid Resource Code - Object Class Code (WBS)* No Specific Description<br />
017 Missing/Invalid Operating Agency Code No Specific Description<br />
Page G-24 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-15: SRD-1 (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
018 Missing/Invalid Bureau Control Number (BCN - LOA) No Specific Description<br />
019 Missing/Invalid Allotment Serial Number No Specific Description<br />
020 Missing/Invalid Op Budget Activity Number - Op Budget Acct Number No Specific Description<br />
(Tran. Type Code - LOA)<br />
021 Missing/Invalid Sub-Allotment - Sub Allotment Number (Sub Allotment - No Specific Description<br />
LOA)<br />
022 Missing/Invalid Accounting Class Reference Number No Specific Description<br />
023 Missing/Invalid Reimbursement Billing Code No Specific Description<br />
024 Missing/Invalid Reimbursement Order Number No Specific Description<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC -<br />
SDN)<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) Invalid or closed job order<br />
Customer indicator required to build an SDN is missing/<br />
invalid<br />
027 Missing/Invalid Fund Administrator No Specific Description<br />
028 Missing/Invalid Work Center No Specific Description<br />
029 Missing/Invalid Cost Account Code No Specific Description<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - No Specific Description<br />
LOA)<br />
031 Missing/Invalid Budget Program Activity - Activity Identifier (Service No Specific Description<br />
Code - SDN)<br />
032 Missing/Invalid Project/Sub Project No Specific Description<br />
033 Missing/Invalid Fund Control Number/Mord Number/616 Number/MIPR No Specific Description<br />
Number<br />
034 Missing/Invalid Job Order No Specific Description<br />
035 Missing/Invalid Special Ops/Management Decision Package No Specific Description<br />
036 Missing/Invalid Emergency/Special Program Code No Specific Description<br />
037 Missing/Invalid Budget Reporting Code No Specific Description<br />
038 Missing/Invalid Accounting Processing Code - Job Order Cost Code Invalid/missing shop code<br />
(Shop Number)<br />
039 Missing/Invalid Cost Allocation Code - Job Number/Local Use (Other No Specific Description<br />
Function Code)<br />
040 Missing/Invalid Project Account/Program Element Code No Specific Description<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier No Specific Description<br />
(AAA - LOA)<br />
042 Missing/Invalid IBOP No Specific Description<br />
043 Missing/Invalid Social Security Number No Specific Description<br />
044 Missing/Invalid Pay Grade No Specific Description<br />
045 Missing/Invalid Employee Name No Specific Description<br />
046 Missing/Invalid Remit To Information No Specific Description<br />
047 Missing/Invalid Payment Method No Specific Description<br />
048 Missing/Invalid Total Amount Of Payment No Specific Description<br />
049 Missing/Invalid AO Approval Date (Date Claim Accept/Approved Date) Approval date of trip record is invalid<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) Unique ID<br />
051 Missing/Invalid Estimated Obligation Amount Amount by line item; st<strong>and</strong>ard document number<br />
052 Missing/Invalid Per Diem/Advance/CBA Code Code identifies per diem/CBA/advances/specifics<br />
053 Missing/Invalid Invoice Number No Specific Description<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-25<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-15: SRD-1 (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
054 Missing/Invalid ABA Routing Number No Specific Description<br />
055 Missing/Invalid Account Number No Specific Description<br />
056 Missing/Invalid Remittance Advice Number No Specific Description<br />
057 Missing/Invalid Payee Information No Specific Description<br />
058 Missing/Invalid Old Obligation Amount No Specific Description<br />
059 Missing/Invalid Credit/Debit Obligation Amount No Specific Description<br />
060 Missing/Invalid Adjusted Obligation Amount Insufficient funds<br />
062 Missing/Invalid CBA Invoice Date No Specific Description<br />
063 Missing/Invalid Date Received No Specific Description<br />
064 Missing/Invalid Gross Amount Of Payment No Specific Description<br />
065 Missing/Invalid Credit Amount No Specific Description<br />
068 Missing/Invalid Accounts Receivable No Specific Description<br />
069 Missing/Invalid Accounting Line No Specific Description<br />
084 Missing data to build SDN One or more of the elements required to build the st<strong>and</strong>ard<br />
document number are missing or invalid<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) Estimated trip start date are missing or invalid<br />
086 Missing/Invalid estd-complt-date Estimated trip ending date missing or not valid<br />
Table G-16: SSC-SD<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
002 Missing/Invalid Transaction Type (1) Invalid status code in SAP input file. (2) <strong>Error</strong>s occurred<br />
during transaction FB60. (3) <strong>Error</strong> executing transaction<br />
FMX1. (4) <strong>Error</strong> executing transaction - unable to report<br />
specific error<br />
003 Missing/Invalid Total Transaction Amount REC 01 Header Total does not equal sum of REC02 line<br />
item amounts<br />
034 Missing/Invalid Job Order (1) Cost object required - missing from file. (2) Invalid cost<br />
object - does not exist. (3) Cost object not open for posting.<br />
(4) Direct cite cost object not allowed.<br />
069 Missing/Invalid Accounting Line (1) Invalid Line of Accounting. (2) Incorrect Cost Code in<br />
LOA<br />
075 Doc Already Completed Voucher has already been processed - cancellation/modification<br />
not allowed<br />
079 Multiple Job Order Numbers on same Travel Order Number Multiple Cost Objects/LOAs not allowed<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) Cost Object not effective yet<br />
086 Missing/Invalid estd-complt-date Funding dates expire prior to travel end date<br />
087 No Header Record in Set (1) Rec01 Header missing from file. (2) Rec01 Header field<br />
size is incorrect - cannot read file<br />
088 No Detail Record in Set Rec02 file size incorrect - cannot read file<br />
094 Invalid Detail Record Number of Rec02 line items does not match with Header<br />
Rec02 count<br />
128 Insufficient Funds at Appropriation Level / Living Lapsed Appropriation Insufficient Funds at Appropriation Level<br />
138 Job Order Fiscal Year unmatched to SDN Fiscal Year Fiscal year in document number is not numeric<br />
Page G-26 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-16: SSC-SD (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
139 Missing/Invalid Obligation Transaction Final Voucher not processed yet, supplemental not allowed<br />
145 Missing/Invalid Field Level Organization AAA incorrect. Transaction does not belong to organization<br />
Table G-17: STANFINS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
002 Missing/Invalid Transaction Type <strong>DTS</strong> the system has a problem. Transaction type must be<br />
“821”<br />
004 Missing/Invalid Disbursed Amount <strong>GEX</strong> misinterpreted possibly user. Amount must be populated<br />
<strong>and</strong> numeric<br />
005 Missing/Invalid Transaction Date Transaction date must be populated, numeric-mmdd format<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
FY must be populated<br />
Year - LOA)<br />
016 Missing/Invalid Resource Code - Object Class Code (WBS) EOR must exist on EOR table for site<br />
038 Missing/Invalid Accounting Processing Code - Job Order Cost Code APC must exist on APC master file for site<br />
(Shop Number)<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier FSN must be populated <strong>and</strong> validated for site<br />
(AAA - LOA)<br />
042 Missing/Invalid IBOP IBOP must be populated <strong>and</strong> valid<br />
045 Missing/Invalid Employee Name Name field must be populated<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) No Specific Description<br />
083 Missing/Invalid DUNS/DUNS+4 DUNS qualifier must be 1 or 9<br />
087 No Header Record in Set No Specific Description<br />
088 No Detail Record in Set No Specific Description<br />
098 Missing/Invalid Type Action T/A must equal “21”<br />
099 Missing/Invalid Block Number Block number must be populated <strong>and</strong> in correct format<br />
100 Missing/Invalid Obligation Data Code ODC must equal “2”<br />
101 Missing/Invalid Liquidation Indicator Code LI must equal K<br />
162 APC/FSN Not Compatible with Master File Agreement No Specific Description<br />
163 APC Has Invalid Appropriation (FSN) Not Appropriate For Transactions No Specific Description<br />
Table G-18: STARS-FL<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
005 Missing/Invalid Transaction Date Missing/Invalid transaction creation date, which is Effective<br />
Date in STARS UDF; FY required to build SDW<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol<br />
Code (Appropriation - LOA)<br />
Beg FY not matched to Beg FY in Root Job Order table<br />
Period Type Code; FY required to build the SDW<br />
Symbol not matched to Symbol in Root Job Order table<br />
Organization Treasury Basic Symbol Code<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead - LOA) Subhead not matched to Subhead in Root Job Order Table<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-27<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-18: STARS-FL (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
018 Missing/Invalid Bureau Control Number (BCN - LOA) BCN not matched to BCN in Root Job Order Table<br />
021 Missing/Invalid Sub-Allotment - Sub Allotment Number (Sub Allotment -<br />
LOA)<br />
Suballotment not matched to Suballotment in Root Job<br />
Order Table<br />
022 Missing/Invalid Accounting Class Reference Number ACRN contains space or special character<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC - DOC NR UIC not matched to STARS-FL UIC Table Code<br />
SDN)<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - LOA) JON in Cost Code not matched to Root Job Order Table<br />
Identifier<br />
028 Missing/Invalid Work Center Work Center not spaces or is not valid<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - Object Class not equal “210” Class<br />
LOA)<br />
031 Missing/Invalid Budget Program Activity - Activity Identifier (Service Code Service Designator, pos 1 of doc nr, not valid identifier<br />
- SDN)<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier (AAA AAA UIC not STARS AAA Organization Identifier<br />
- LOA)<br />
045 Missing/Invalid Employee Name Traveler's name contains numeric or special character<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) TRN contains a space or special character<br />
051 Missing/Invalid Estimated Obligation Amount Amount of amt sign not valid for new obligation (Action Code<br />
“A”)<br />
055 Missing/Invalid Account Number No Specific Description<br />
060 Missing/Invalid Adjusted Obligation Amount Amount or amt sign not valid for obligation adjustment<br />
(Action Code “C”)<br />
079 Multiple Job Order Numbers on same Travel Order Number Action Code “C” (change) transaction with JON that Number<br />
match JON of existing SND/doc nr-ACRN does not record in<br />
STARS-FL<br />
084 Missing data to build SDN One or more of the elements in the st<strong>and</strong>ard document number<br />
are missing or are not valid<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) Estimated trip start date missing or not valid<br />
086 Missing/Invalid estd-complt-date Estimate Complete Date is not valid<br />
102 Duplicate Record SDN/travel doc nr-ACRN combination already exists in<br />
STARS-FL; applies to Action Code “A”; Document number<br />
already exists for another line of accounting<br />
109 Missing Invalid Processing Action Code Code used to designate input status (“A” for new obligation<br />
or “C” for obligation adjustment) is not valid; A one position<br />
alpha indicator code used to designate the input status to<br />
the processing system in order to facilitate validation requirements<br />
<strong>and</strong> processing functions<br />
116 Amount Sign does not agree with Action Code Amount must be positive for Action Code “A” or amt for<br />
Action Code “C” would result in negative obligation amount;<br />
Sign must be negative for action code debit, position for<br />
action code, add, <strong>and</strong> negative or minus for action code<br />
change<br />
136 Accounting Data does not meet CMET edits Accounting date not matched to CMET<br />
137 Unmatched Obligation Adjustment Action Code “C” transaction not matched to existing SDN/<br />
doc nr-ACRN record<br />
138 Job Order Fiscal Year unmatched to SDN Fiscal Year Job order Fiscal Year is unmatched to St<strong>and</strong>ard Document<br />
Number<br />
Page G-28 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-19: STARS-HCM<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
005 Missing/Invalid Transaction Date Missing/Invalid Transaction Creation Date, which is effective date in<br />
STARS UDF; Required to build SDW<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Missing/Invalid FY required to build the SDW<br />
Code (Fiscal Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic<br />
Symbol Code (Appropriation - LOA)<br />
Missing/Invalid fund symbol required for appr. format<br />
013 Missing/Invalid Subhead or Limit - Limitation/Subhead (Subhead<br />
- LOA)<br />
Subhead invalid to Major Claimant Subhead Table, or Subhead is<br />
missing<br />
018 Missing/Invalid Bureau Control Number (BCN - LOA) PARM <strong>and</strong>/or RFM are missing or invalid<br />
022 Missing/Invalid Accounting Class Reference Number ACRN is missing or invalid<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. Organization Code is missing or invalid for an “A” Action Code<br />
UIC - SDN)<br />
026 Missing/Invalid Major Comm<strong>and</strong> Indicator - Unit Identifier (JON - Missing/Invalid Major Comm<strong>and</strong> indicator/Unit Identifier<br />
LOA)<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object OMB Object Class Code Invalid or not equal to either “210”, “220”<br />
Class - LOA)<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier<br />
Document Number UIC not on UIC Table<br />
(AAA - LOA)<br />
043 Missing/Invalid Social Security Number Social Security Number contains spaces or special characters<br />
045 Missing/Invalid Employee Name Traveler's name contains a numeric of special character or is missing<br />
<strong>and</strong> “A” Action Code<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # -<br />
SDN)<br />
All edits pertain to the Document Number structure with various values<br />
being invalid<br />
051 Missing/Invalid Estimated Obligation Amount Insufficient Funds; invalid total amount or invalid value<br />
052 Missing/Invalid Per Diem/Advance/CBA Code Insufficient Per Diem amount, or Transaction amount, or invalid<br />
value<br />
053 Missing/Invalid Invoice Number No Specific Description<br />
069 Missing/Invalid Accounting Line LOA missing or invalid<br />
085 Missing/Invalid proceed on-or-about date (Fiscal Year - SDN) Estimated trip start date missing or not valid '121', '122', or '257'<br />
102 Duplicate Record Document Number-ACRN already exists; applies to Action Code “A”;<br />
Document number already exists for another line of accounting<br />
103 Missing Invalid Project Unit Project Unit is invalid or missing<br />
104 Project Directive Line Item already exists for another Project Duplicate Project Directive Line Item<br />
Unit<br />
105 Project Unit Exist on another Project Directive Line Item Duplicate Project Unit<br />
106 Missing Invalid Project Directive Line Item Project Directive Line Item is either missing or invalid on the chare of<br />
accounts<br />
107 Missing Invalid Project Directive Line Item Suffix Project Directive Line Item Suffix is either missing or invalid on the<br />
chare of accounts<br />
108 Missing Invalid Input Type Code Input Type Code is either missing or invalid on the chart of accounts<br />
109 Missing Invalid Processing Action Code A one position alpha indicator code used to designate the input status<br />
to the processing system in order to facilitate validation requirements<br />
<strong>and</strong> processing functions<br />
110 Subhead not on Chart of Accounts A subhead is used to identify the budget activity, major claimant, <strong>and</strong><br />
expenses limitation holder <strong>and</strong> it has to be valid on the chart of<br />
accounts<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-29<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
111 Requiring Financial Manager not on Chart of Accounts Requiring Financial Manager (RFM) are termed Project Managers or<br />
Program Managers on funds usage Headquarters Procurement<br />
Requests. RFMs must be valid on the chart of accounts<br />
112 Project unit not on Chart of Accounts Project Unit does not exist on the chart of accounts<br />
112 Missing Invalid Revision Number Revision number assigned sequentially to identify an instrument to<br />
change a document<br />
114 Missing Invalid Number of Days Number of days does not exist on the travel document<br />
115 Participating Manager; Sub Allotment; Project Unit does not<br />
meet CMET edits<br />
Table G-19: STARS-HCM (Continued)<br />
A two-position alphanumeric character representing an organization<br />
or individual designated as having responsibility for acceptance <strong>and</strong><br />
execution of a Project Directive (PD) issued by a RFM<br />
116 Amount Sign does not agree with Action Code Negative on an “A” Action Code, or not equal to 'blank', negative '-' or<br />
positive '+'; Sign must be negative for action code delete, position for<br />
action code add <strong>and</strong> negative or minus for action code change<br />
117 Major Comm<strong>and</strong>; Fiscal Year; Appropriation; Subhead does not<br />
meet CMET edits<br />
118 Requiring Financial Manager; Project Unit does not meet CMET<br />
edits<br />
Subhead must be valid for major comm<strong>and</strong>s, fiscal year, <strong>and</strong> appropriation<br />
<strong>and</strong> it must be also valid on CMET edits<br />
Requiring Financial Manager & Project Unit must be valid on CMET<br />
edits<br />
119 Major Claimant Indicator Invalid Major Claimant is bureau, office, or comm<strong>and</strong> designated as an<br />
administering office<br />
120 Missing Invalid Operating Budget UIC A code used to identify an organizational unit must be valid on the<br />
chart of accounts<br />
121 Revision Number Present with Action Code A Revision number cannot be present with Action Code “A”<br />
122 Project Directive Line Item Suffix Invalid: Appropriation expired<br />
or lapsed<br />
A one position alphanumeric character added to the PDLI to permit a<br />
further subdivision of a specific line item<br />
123 Reimbursable segment missing for this Project Unit Assigning Reimbursable segment to Project Unit to indicate whether<br />
it is classified as automatic or other<br />
124 Operating Budget UIC must be 000140 for a W Subhead UIC is required <strong>and</strong> must be 000140 for a “W” subhead ONR with a<br />
“W” subhead<br />
125 Major Claimant required for DARPA Appropriation Major claimant is required for DARPA appropriation (0400 & 1304)<br />
126 Major Claimant does not match Chart of Accounts Major claimant has to be valid on the chart of accounts<br />
127 Operating Budget UIC must be 000140 for DARPA Appropriation<br />
128 Insufficient Funds at Appropriation Level / Living Lapsed Appropriation<br />
UIC is required <strong>and</strong> must be 000140 for DARPA appropriations<br />
(0400 & 1304)<br />
Obligation exceeds authorized funds appropriation level<br />
129 Appropriation No Longer Available for Travel Obligations Appropriation is no longer available for travel obligation. Invalid<br />
appropriation number<br />
130 Operating Budget UIC must be 000230 for this Requiring Financial<br />
Manager<br />
131 Operating Budget UIC must be 000240 for this Requiring Financial<br />
Manager<br />
132 Operating Budget UIC must be 000390 for this Requiring Financial<br />
Manager<br />
133 Operating Budget UIC must be 000190 for this Requiring Financial<br />
Manager<br />
134 Operating Budget UIC must be 000750 for this Requiring Financial<br />
Manager<br />
Operating Budget UIC must be 000230 for this Requiring Financial<br />
Manager.<br />
Operating Budget UIC must be 000240 for this Requiring Financial<br />
Manager.<br />
Operating Budget UIC must be 000390 for this Requiring Financial<br />
Manager.<br />
Operating Budget UIC must be 000190 for this Requiring Financial<br />
Manager.<br />
Operating Budget UIC must be 000750 for this Requiring Financial<br />
Manager.<br />
Page G-30 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-19: STARS-HCM (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
135 Change of OMB Object Class Invalid After Travel Disbursement OMB Object Class in an OMB-controlled classification that identifies<br />
the nature of resources acquired/consumed<br />
139 Missing/Invalid Obligation Transaction No Specific Description<br />
140 Missing/Invalid Cancellation Amount No Specific Description<br />
175 Write-off/Waiver/or Transfer record not processed. Accounts<br />
receivable record not found<br />
No Specific Description<br />
Table G-20: STARS-OP<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
048 Missing/Invalid Total Amount Of Payment Either there is no Amount in the Invoice Gross Amount Field<br />
or there is Something Other than Numeric in the Gross<br />
Amount Field<br />
053 Missing/Invalid Invoice Number Invoice number field is Alpha Numeric. Either the field was<br />
blank or it contained special characters<br />
062 Missing/Invalid CBA Invoice Date Either the date was not formatted YYMMDD or the date was<br />
greater than the system date<br />
102 Duplicate Record One Pay does not duplicate payment match or PIIN, SPINN,<br />
invoice number, invoice date <strong>and</strong> gross amount. If all five of<br />
those fields on an incoming invoice match all five of those<br />
fields on an invoice already in one pay, the invoice will flag<br />
as a duplicate invoice<br />
143 Missing/Invalid Defense Agency Level Organization PIIN on the invoice record is a required field <strong>and</strong> must be at<br />
least 13 positions with no special characters. Document<br />
number on the INV CLIIN record must be at least 13 positions<br />
with no special characters. Based on the error message,<br />
either the PIIN <strong>and</strong>/or document number was wither<br />
less than 13 positions or contained special characters.<br />
Table G-21: WAAS<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
005 Missing/Invalid Transaction Date No Specific Description<br />
007 Missing/Invalid Voucher Number No Specific Description<br />
008 Missing/Invalid Disbursing Office/Disbursing Station Symbol Identifier No Specific Description<br />
011 Missing/Invalid Beginning Fiscal Year Indicator - Period Type Code (Fiscal<br />
No Specific Description<br />
Year - LOA)<br />
012 Missing/Invalid Basic Symbol Number - FAO Treasury Basic Symbol No Specific Description<br />
Code (Appropriation - LOA)<br />
014 Missing/Invalid Program Year No Specific Description<br />
016 Missing/Invalid Resource Code - Object Class Code (WBS) 4931/4950 Object Class of 2525 must have Document Type<br />
of WO <strong>and</strong> Document Type of WO must have Object Class<br />
of 2525<br />
025 Missing/Invalid Customer Indicator - Organization Code (Req. UIC -<br />
SDN)<br />
No Specific Description<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-31<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-21: WAAS (Continued)<br />
<strong>Error</strong> <strong>Error</strong> Name<br />
<strong>Error</strong> System Description<br />
Code<br />
030 Missing/Invalid Object Class - Object/Sub Object Class (Object Class - No Specific Description<br />
LOA)<br />
032 Missing/Invalid Project/Sub Project 0833 must have DOC CODE of ER or Program Project FYR<br />
of 1 or 2<br />
041 Missing/Invalid Accounting Station Number - Organization Identifier (AAA No Specific Description<br />
- LOA)<br />
050 Missing/Invalid Trip Record Number (Trip # - LOA/Serial # - SDN) No Specific Description<br />
051 Missing/Invalid Estimated Obligation Amount Missing/Invalid Amount<br />
052 Missing/Invalid Per Diem/Advance/CBA Code No Specific Description<br />
055 Missing/Invalid Account Number No Specific Description<br />
069 Missing/Invalid Accounting Line No Specific Description<br />
076 Doc Not On File No Specific Description<br />
080 Missing/Invalid Transaction Set Control Number No Specific Description<br />
101 Missing/Invalid Liquidation Indicator Code No Specific Description<br />
109 Missing Invalid Processing Action Code No Specific Description<br />
Page G-32 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
G.2 System Administration <strong>Error</strong> <strong>Codes</strong> <strong>and</strong> Specific Description*<br />
Table G-22: <strong>DTS</strong> Rejects<br />
NOMATCH System desc: RejectedTransactionID + “<strong>and</strong>/or “+ TANUM + “cited in an 824/820 originating from your system<br />
does not match any travel document in <strong>DTS</strong><br />
DUPLICATE System desc: <strong>DTS</strong> has identified an 824/820 originating from your system as a duplicate transaction based<br />
on the “+ RejectedTransactionID + “<strong>and</strong> “+ TANUM + “cited in the 824/820<br />
PAY_AMOUNT_DIF System desc: Advice of payment amount cited in the 820 originating from your system does not match the<br />
<strong>DTS</strong> request for payment<br />
SSN_NOT_MATCH System desc: TravelerSSN + “cited in an 824/820 originating from your system with “+ RejectedTransactionID<br />
+ “<strong>and</strong> “+ TANUM + “, does not match any travel document in <strong>DTS</strong><br />
* <strong>DTS</strong> Rejects are the Electronic Commerce/Electronic Data Interchange (EC/EDI) 864 transactions that<br />
are transmitted to the financial systems via <strong>GEX</strong>. The <strong>GEX</strong> sends an email to the respective system, indicating<br />
the type of reject encountered by <strong>DTS</strong>.<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-33<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
G.3 <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
This is an excerpt from the Defense Travel System Finance Guide, September 2001, Version 9.<br />
G.3.1 Introduction<br />
To perform the accounting <strong>and</strong> disbursing functions associated with defense travel, the Defense Travel<br />
System (<strong>DTS</strong>) sends the authorizations <strong>and</strong> vouchers to the Global Exchange (<strong>GEX</strong>) system for translation<br />
into the appropriate financial transactions (obligations <strong>and</strong> invoices). Upon translation to the<br />
appropriate data format, the <strong>GEX</strong> routes the transaction to the intended accounting, disbursing or entitlement<br />
system for processing.<br />
The communications between the <strong>DTS</strong> <strong>and</strong> the <strong>GEX</strong> are governed by the <strong>DTS</strong> User Defined File<br />
(UDF) format document (Document Control Number <strong>DTS</strong>-AA10-UDF-U-003). This <strong>DTS</strong> UDF document<br />
specifies the data format that is provided from the <strong>DTS</strong>, <strong>and</strong> is the basis for the <strong>GEX</strong> to ‘interpret’<br />
the authorization <strong>and</strong> voucher documents. If the data provided to the <strong>GEX</strong> does not match the<br />
format defined in the <strong>DTS</strong> UDF document, the <strong>GEX</strong> cannot interpret the document (authorization or<br />
voucher). When this occurs, the <strong>GEX</strong> will create a ‘Translation Failure Notification’ that is sent back<br />
to the <strong>DTS</strong>. The DTA will be notified of the error, <strong>and</strong> the appropriate action must be taken to ensure<br />
the problem is corrected <strong>and</strong> the document is retransmitted to the <strong>GEX</strong>. Most of these errors are not<br />
correctable by the traveler, or the DTA, as they are a direct result of the output of the <strong>DTS</strong>; however,<br />
some of these errors are a result of missing personal profile information <strong>and</strong> are correctable by the<br />
traveler or the DTA. The Translation Failure Notifications may also be the result of translation failure<br />
due to business process rules. These types of errors are a result of the content of the data not supporting<br />
the business rules. These rules may be associated with how to route the transaction to the appropriate<br />
financial system, missing account information required for payment, etc. The business rule failures are<br />
correctable by the traveler, DTA or Help Desk (depending on the error) as they are data content problems<br />
(not data format problems).<br />
The rest of this document describes the errors that are provided in Translation Failure Notification<br />
messages. The description is provided in a table with the error message, a brief description/explanation,<br />
<strong>and</strong> who is responsible for correcting the error. The table is divided into sections, grouping similar<br />
errors together for ease of reference.<br />
G.3.2 Translation Failure Notification <strong>Error</strong> Messages<br />
G.3.2.1 <strong>DTS</strong> UDF Structure <strong>Error</strong>s<br />
As described in Section 1, the <strong>DTS</strong> UDF structure as defined in the <strong>DTS</strong> UDF document is the<br />
key to <strong>GEX</strong>’s capability to interpret the authorization <strong>and</strong> voucher documents. If the data format<br />
received at the <strong>GEX</strong> does not conform to the specification, then <strong>GEX</strong> will return a Translation<br />
Failure Notification to the <strong>DTS</strong>.<br />
In order to underst<strong>and</strong> or interpret the UDF structure errors, one must be familiar with the<br />
actual <strong>DTS</strong> UDF data structure. The UDF is the exported batch of data (ASCII file) for a<br />
selected group of travel documents from the <strong>DTS</strong>. Each of these travel documents is composed<br />
of a group of records. The group of records representing each travel document (authorization<br />
or voucher) that are sent to the <strong>GEX</strong> are as defined in Table G-20.<br />
Page G-34 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-23: <strong>DTS</strong> UDF Records<br />
Travel Authorization<br />
Record Type Number of Occurrences Required<br />
Batch Header (BH) One per batch Yes<br />
Outline Header (OH) One per document Yes<br />
Outline Accounting (OA) One or More per document Yes<br />
Outline Extended Accounting (OEA)<br />
Zero or More per Outline Accounting<br />
No<br />
Record<br />
Outline Status History (OSH) One or More per document Yes<br />
Outline Personal Information, Set 1 (OP1) One per document Yes<br />
Outline Personal Information, Set 2 (OP2) One per document Yes<br />
Outline Comment (OC) One per document No<br />
Outline Advance (OAD) Zero or One per document No<br />
Outline Extended Advance (OED)<br />
Zero or More per Outline Advance No<br />
Record<br />
Batch Trailer (BT) One per batch Yes<br />
Travel Voucher<br />
Record Type Number of Occurrences Required<br />
Batch Header (BH) One per batch Yes<br />
Outline Header (OH) One per document Yes<br />
Outline Accounting (OA) One or More per document Yes<br />
Outline Extended Accounting (OEA)<br />
Zero or More per Outline Accounting<br />
No<br />
Record<br />
Outline Status History (OSH) One or More per document Yes<br />
Outline Personal Information, Set 1 (OP1) One per document Yes<br />
Outline Personal Information, Set 2 (OP2) One per document Yes<br />
Outline Comment (OC) One per document No<br />
Outline Advance (OAD) Zero or One per document Yes (for advances only)<br />
Outline Extended Advance (OED)<br />
Zero or More per Outline Advance No<br />
Record<br />
Batch Trailer (BT) One per batch Yes<br />
CBA Voucher<br />
Record Type Number of Occurrences Required<br />
Batch Header (BH) One per batch Yes<br />
Outline CBA Primary (OCP) One per CBA Invoice Yes<br />
Outline CBA Detail (OCD) One or more per CBA Invoice Yes<br />
Batch Trailer (BT) One per batch Yes<br />
Each of the <strong>DTS</strong> UDF Record Types is made up of a series of fields. Each field consists of one<br />
of the following data types: Character, Constant, Integer, Decimal, Date, Time, or Logical.<br />
Refer to the <strong>DTS</strong> UDF document for a detailed list of data fields that are contained in each<br />
record specified in Table 1 above. These data fields are described by the location in the record,<br />
data type, size, <strong>and</strong> a list of valid values. If any of the data elements in the UDF do not match<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-35<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
its specification, the <strong>GEX</strong> will generate an error based on that discrepancy. Since this type of<br />
error may occur for any data element in the UDF, each possible error is not listed. Instead, the<br />
following is an explanation on how to interpret these errors:<br />
1. The format of the error descriptions are “Data Element Name” “Record Type” “<strong>Error</strong><br />
Type” “Value in <strong>Error</strong>”<br />
Data Element Name = Name of data element in error<br />
Record Type = Record (Listed in Table 1) containing data element in error<br />
<strong>Error</strong> Type = Data specification which is violated<br />
Value in <strong>Error</strong> = Actual Value provided in UDF<br />
Example: The UDF document specifies the traveler SSN in the OH record as a Character Field<br />
with a maximum length of 12. If the UDF received has a SSN with a length of 15 characters<br />
(value = 012345678901234), the following error messages would be provided in the Translation<br />
Failure Notification:<br />
SSN of OH Record Exceeds Size Restrictions 01234568901234<br />
In the above example:<br />
Data Element Name = SSN<br />
Record Type = OH<br />
<strong>Error</strong> Type = Exceeds Size Restrictions<br />
Value in <strong>Error</strong> = 012345678901234<br />
2. The error types that may occur for violating the specification of the data are shown in<br />
Table G-21. The following error types may occur for UDF Specification violations:<br />
Table G-24: <strong>DTS</strong> UDF Data Specification <strong>Error</strong>s<br />
<strong>Error</strong> Statement <strong>Error</strong> Description Responsible Party to<br />
Address <strong>Error</strong><br />
Object failed restriction<br />
Element contains value that are not in a list of acceptable values.<br />
<strong>DTS</strong> Developer<br />
(e.g. valid values for DocType = AUTH, LATH, VCH,<br />
LVCH)<br />
Object failed presentation<br />
Element does not meet presentation expectations (i.e. valid <strong>DTS</strong> Developer<br />
date = 09/19/1999 – invalid date due to presentation = 09/a3/<br />
87).<br />
Object failed size check Element is larger or smaller than expected value <strong>DTS</strong> Developer<br />
Invalid or missing terminator Object’s terminator is not what is expected (e.g. Character field <strong>DTS</strong> Developer<br />
is enclosed in quotes; therefore terminator is “--- If it is any<br />
other symbol or not there, this error will occur)<br />
Invalid or missing initiator<br />
Object’s initiator is not what is expected (e.g. Character field is <strong>DTS</strong> Developer<br />
enclosed in quotes; therefore initiator is “--- If it is any other<br />
symbol or not there, this error will occur)<br />
Object missing required component Sometimes the data is described as a group of objects. An<br />
example is the Accounting Data. The accounting data fields 2 –<br />
10 may consist of multiple data values grouped in the one field.<br />
In the case of grouped data, this error will occur if one of the<br />
items in the group is missing or in error.<br />
DTA or <strong>DTS</strong> Developer<br />
Page G-36 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-24: <strong>DTS</strong> UDF Data Specification <strong>Error</strong>s (Continued)<br />
<strong>Error</strong> Statement <strong>Error</strong> Description Responsible Party to<br />
Address <strong>Error</strong><br />
Object failed partitioning<br />
Sometimes the data is described as a group of objects. An DTA or <strong>DTS</strong> Developer<br />
example is the Accounting Data. The accounting data fields 2 –<br />
10 may consist of multiple data values grouped in the one field.<br />
This error occurs when grouped objects are not found within<br />
expected results<br />
Object failed component rule. A component rule is a specific requirement associated with<br />
each of the data fields in order to successfully translate the<br />
UDF document (authorization or voucher) into the corresponding<br />
financial transaction (obligation or invoice). Reference Table<br />
3 for the list of specific Component Rules.<br />
Traveler, DTA or <strong>DTS</strong> Developer<br />
as defined in Table 3.<br />
3. The <strong>DTS</strong> UDF data specification errors contain an error type of “Object failed component<br />
rule”. As defined earlier, the error message details which data element <strong>and</strong> record are in<br />
error. The component rule errors are detailed by record & data element within Table G-22.<br />
Table G-25: Component Rules<br />
Data Element Component Rule Responsible Party to Address <strong>Error</strong><br />
Batch Header Record<br />
Batch Header Value of data element must equal “BH” <strong>DTS</strong> Developer<br />
Batch Type Value of data element must equal “OUT” <strong>DTS</strong> Developer<br />
Format<br />
Value of data element must equal “Fixed” or “Variable”<br />
<strong>DTS</strong> Developer<br />
Batch Date A value in Batch Date is required <strong>DTS</strong> Developer<br />
Batch Trailer Record<br />
Batch Trailer Value of data element must equal “BT” <strong>DTS</strong> Developer<br />
Outline Accounting Record<br />
Outline Accounting Value of data element must equal “OA” <strong>DTS</strong> Developer<br />
Acct1 There must be a value provided in Accounting 1. DTA<br />
This element is used to identify the intended<br />
recipient of the financial transaction.<br />
Acct2 through Acct10<br />
The Accounting String format must match one of DTA<br />
the <strong>DTS</strong> published service line of accounting formats.<br />
Expense code If the document is an authorization (DocType =<br />
“AUTH” or “LATH”), a value for expense code<br />
must be present.<br />
<strong>DTS</strong> Developer<br />
Cost If the document is an authorization (DocType =<br />
“AUTH” or “LATH”), a value for cost must be present.<br />
This reflects the amount that will be obligated<br />
against the specified LOA.<br />
Reimb Cost<br />
If the document is a voucher (DocType = “VCH”<br />
or “LVCH”), a value for cost must be present. This<br />
reflects the amount that will be paid against the<br />
specified LOA.<br />
Outline Advance Record<br />
OAD<br />
If the travel involves an advance, an OAD<br />
record will be supplied in the UDF. Value of<br />
data element must equal “OAD”.<br />
DTA or Traveler if no amount was specified<br />
when travel arranged. <strong>DTS</strong> Developer if<br />
amount was specified but not contained in<br />
UDF.<br />
DTA or Traveler if no amount was specified<br />
when voucher was approved. <strong>DTS</strong> Developer<br />
if amount was specified but not contained<br />
in UDF.<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-37<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Acct1<br />
There must be a value provided in Accounting<br />
DTA<br />
1 for an advance voucher. This element<br />
is used to identify the intended recipient of<br />
the financial transaction.<br />
Data Element Component Rule Responsible Party to Address <strong>Error</strong><br />
Acct1 through Acct10<br />
The Advance Accounting String format DTA<br />
must match one of the <strong>DTS</strong> published service<br />
line of accounting formats.<br />
Advance Request If the document is a voucher (DocType = DTA<br />
“VCH” or “LVCH”), a value for cost must be<br />
present. This reflects the amount that will<br />
be paid against the specified LOA.<br />
Advance Type If the document is a voucher (DocType = DTA<br />
“VCH” or “LVCH”), the value of data element<br />
must be present.<br />
Outline Comment Record<br />
OC Value of data element must equal “OC” <strong>DTS</strong> Developer<br />
Outline CBA Detail Record<br />
OCD Value of data element must equal “OCD” <strong>DTS</strong> Developer<br />
Trip Record Number<br />
There must be a trip record number present.<br />
<strong>DTS</strong> Developer<br />
Billed Amount<br />
US$ Amount Credited<br />
US$ Advance Credits<br />
US$ Airport Credit<br />
US$ Previously Applied Credit<br />
At least one of the listed data elements<br />
must have a value present.<br />
<strong>DTS</strong> Developer<br />
Outline CBA Primary Record<br />
OCP Value of data element must equal “OCP” <strong>DTS</strong> Developer<br />
Transaction ID There must be a Transaction ID present. <strong>DTS</strong> Developer<br />
To (Destination)<br />
The destination (routing indicator) data element must <strong>DTS</strong> Developer<br />
be present.<br />
Century – Invoice Received at The century data element must be present.<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong><br />
Date – Invoice Received at <strong>DTS</strong> The date must be present. <strong>DTS</strong> Developer<br />
Net CBA Payment Amount There must be a value supplied in this data element. <strong>DTS</strong> Developer<br />
Outline Extended Accounting Record<br />
OEA Value of data element must equal “OEA” <strong>DTS</strong> Developer<br />
Outline Extended Advance Record<br />
OED Value of data element must equal “OED” <strong>DTS</strong> Developer<br />
Outline Header Record<br />
OH Value of data element must equal “OH” <strong>DTS</strong> Developer<br />
SSN<br />
Table G-25: Component Rules (Continued)<br />
A valid SSN (greater than 8 characters)<br />
must be present.<br />
Doc Type A data value for Doc Type must be present. <strong>DTS</strong> Developer<br />
Current Status Date A current status date must be present. <strong>DTS</strong> Developer<br />
Dep Date<br />
For Doc Type “AUTH”, the estimated departure<br />
<strong>DTS</strong> Developer<br />
date of the trip. For Doc Type “VCH”,<br />
the actual departure date of trip.<br />
Auth Num An authorization number must be present. <strong>DTS</strong> Developer<br />
Ret Date A return date must be present <strong>DTS</strong> Developer<br />
Traveler if SSN not supplied in personal<br />
profile information. <strong>DTS</strong> Developer if SSN<br />
is supplied in personal profile information.<br />
Page G-38 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Data Element Component Rule Responsible Party to Address <strong>Error</strong><br />
Cost<br />
For an authorization (Doc Type = “AUTH” or<br />
“LATH”), a cost must be present. This represents<br />
the entire expected trip costs that<br />
will be obligated by the financial system.<br />
<strong>DTS</strong> Developer<br />
Net to Traveler<br />
Gov’t Charge Card Amount<br />
Traveler’s Account Amount<br />
Transaction Type<br />
Settlement Type<br />
For a voucher (Doc Type = “LVCH” or<br />
“VCH”), the net due to traveler must be<br />
present. This represents the total payment<br />
to be disbursed to the traveler.<br />
For a voucher (Doc Type = “LVCH” or<br />
“VCH”), an amount must be present in<br />
either Gov’t Charge Card Amount or Traveler’s<br />
Account Amount (or both). This represents<br />
how the payment will be disbursed<br />
to the traveler.<br />
For an authorization (Doc Type = “AUTH” or<br />
“LATH”), a transaction type must be present.<br />
For a voucher (Doc Type = “LVCH” or<br />
“VCH”), a settlement type must be present.<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Developer<br />
Transaction ID A transaction id must be present <strong>DTS</strong> Developer<br />
Amendment Number<br />
An amendment number must be present for <strong>DTS</strong> Developer<br />
an authorization (Doc Type = “AUTH” or<br />
“LATH”) which is not the original authorization<br />
(in other words, Transaction Type =<br />
“Amendment” or “Cancel” or “Supplement”)<br />
Invoice Number<br />
For a voucher (Doc Type = “LVCH” or <strong>DTS</strong> Developer<br />
“VCH”), an invoice number is required to be<br />
present.<br />
Outline Personal Information Record, Set 1<br />
OP1<br />
Value of data element must be equal to <strong>DTS</strong> Developer<br />
“OP1”<br />
Last Name<br />
A last name for the traveler must be present.<br />
Traveler if last name is not specified in personal<br />
profile information.<br />
<strong>DTS</strong> Developer if last name is specified.<br />
First Name<br />
Home Address1<br />
Home City<br />
Home State<br />
Home Zip Code<br />
Table G-25: Component Rules (Continued)<br />
A first name for the traveler must be present.<br />
For a voucher (Doc Type = “LVCH” or<br />
“VCH”), a home address must be present.<br />
For a voucher (Doc Type = “LVCH” or<br />
“VCH”), a home city must be present.<br />
For a voucher (Doc Type = “LVCH” or<br />
“VCH”), a home state must be present.<br />
For a voucher (Doc Type = “LVCH” or<br />
“VCH”), a home zip code must be present.<br />
Outline Personal Information Record, Set 2<br />
OP2 Value of data element must equal “OP2” <strong>DTS</strong> Developer<br />
Traveler if first name is not specified in personal<br />
profile information.<br />
<strong>DTS</strong> Developer if first name is specified.<br />
Traveler if home address is not specified in<br />
personal profile information. <strong>DTS</strong> Developer<br />
if home address is specified.<br />
Traveler if home city is not specified in personal<br />
profile information.<br />
<strong>DTS</strong> Developer if home city is specified.<br />
Traveler if home state is not specified in<br />
personal profile information.<br />
<strong>DTS</strong> Developer if home state is specified.<br />
Traveler if home zip code is not specified in<br />
personal profile information.=<strong>DTS</strong> Developer<br />
if home zip code is specified.<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-39<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
Table G-25: Component Rules (Continued)<br />
Data Element Component Rule Responsible Party to Address <strong>Error</strong><br />
Position This data element must be present. Traveler if position is not specified in personal<br />
profile information.<br />
<strong>DTS</strong> Developer if position is specified.<br />
Outline Status History Record<br />
OSH Value of data element must equal “OSH” <strong>DTS</strong> Developer<br />
4. There are UDF errors that are sometimes not directly attributable to a specific data element<br />
in error. These general errors are usually related to communications failures or missing<br />
UDF required records. The general errors that may be present in a Translation Failure<br />
Notification are specified in Table G-23.<br />
Table G-26: <strong>DTS</strong> UDF Data Structure General <strong>Error</strong>s<br />
<strong>Error</strong> Statement <strong>Error</strong> Condition Description Responsible Party to Address <strong>Error</strong><br />
Message is unrecognizable.<br />
The document could not be interpreted. <strong>DTS</strong> Developer<br />
This is very likely due to a required UDF<br />
record missing.<br />
Transmission was unidentifiable.<br />
The entire <strong>DTS</strong> UDF batch file could not be<br />
interpreted. This may be due to a missing<br />
or “bad” Batch Header record or Batch<br />
Trailer Record. This also could be a result<br />
of a bad file transfer.<br />
<strong>DTS</strong> Developer, <strong>DTS</strong> System Administrator,<br />
or <strong>GEX</strong> System Administrator.<br />
Transmission had an invalid or missing terminator.<br />
Transmission missing a required component.<br />
Transmission was invalid because it contained<br />
components in error.<br />
Transmission missing a required data element.<br />
The file has an invalid or missing Carriage<br />
Return – Line Feed.<br />
The file is missing a required UDF<br />
record(s).<br />
The file contains several bad or missing<br />
UDF records.<br />
The file contains several bad or missing<br />
data elements.<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Developer<br />
Unexpected Transmission error. The file is incomplete. <strong>DTS</strong> Developer<br />
Transaction was unidentifiable.<br />
The transaction (authorization or voucher) <strong>DTS</strong> Developer<br />
could not be interpreted. This may be due<br />
to a required UDF record missing or missing<br />
terminator.<br />
Transaction had an invalid or missing terminator.<br />
The transaction (authorization or voucher) <strong>DTS</strong> Developer<br />
contains an invalid or missing Carriage<br />
Return – Line Feed.<br />
Transaction missing a required component. The transaction (authorization or voucher)<br />
contains several missing required UDF<br />
records.<br />
<strong>DTS</strong> Developer.<br />
Transaction was invalid because it contained<br />
components in error.<br />
Transaction missing a required data element.<br />
Unexpected Transaction error.<br />
The transaction (authorization or voucher)<br />
contains several bad UDF records.<br />
The transaction (authorization or voucher)<br />
contains several bad or missing data elements.<br />
The transaction (authorization or voucher)<br />
is incomplete.<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Developer<br />
Page G-40 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
G.3.3 Business Rule <strong>Error</strong>s<br />
Business rule errors occur as a result of the data provided by the <strong>DTS</strong> not following the agreed upon<br />
business rules between the <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong>. The Translation Failure Notifications resulting from business<br />
rule errors are outlined in Table G-24 below.<br />
Table G-27: Business Rule <strong>Error</strong>s<br />
<strong>Error</strong> Statement <strong>Error</strong> Description Responsible Party to Address<br />
<strong>Error</strong><br />
Lookup Failure: Invalid Line Item Accounting<br />
Format<br />
Invalid or Unknown Accounting string in OA, OAD,<br />
or OCD record. The accounting string format must<br />
match one of the <strong>DTS</strong> published service line of<br />
accounting formats.<br />
DTA<br />
Lookup Failure: Invalid AAA/FSN/DODAAC<br />
for GS03 Lookup<br />
Cannot find accounting string in lookup tables that<br />
match Acct1 field. This value is used to determine<br />
the appropriate financial system for processing the<br />
document.<br />
DTA if Acct1 data element is<br />
invalid. Help Desk if Acct data element<br />
is valid.<br />
Lookup Failure: Inactive Routing Entry<br />
Lookup Failure: Mult Route Entry-Limit,<br />
BSN or ASN mismatch<br />
Lookup Failure: Missing Personal Account<br />
Routing Number<br />
Lookup Failure: Unrecognized Personal<br />
Account Type<br />
Lookup Failure: Missing Personal Account<br />
Number<br />
Lookup Failure: Missing Charge Card Routing<br />
Number<br />
Lookup Failure: Missing Book Number.<br />
Field not present: Both CBAInvStmntDate<br />
OCP Element & CBAAccountNo OCP Element<br />
must be present.<br />
Acct1 field passed lookup, but data has been<br />
flagged as inactive. The communications pathway<br />
from <strong>GEX</strong> to the financial system has not been<br />
established.<br />
Acct1 field passes primary lookup, but fails secondary<br />
lookup. In some cases, to determine the appropriate<br />
financial system, data in addition to the FSN<br />
must be used. The Limit, BSN, <strong>and</strong> ASN should be<br />
validated.<br />
Personal Routing Number in the OP2 record is<br />
missing. If payment is made to Traveler’s Account<br />
(checking or savings), the routing number must be<br />
supplied.<br />
Value of Personal Account Type in the OP2 record<br />
is not expected. It does not equal to “CHECKING”,<br />
“SAVINGS”, or “CHECK”.<br />
Personal Account Number in the OP2 record is<br />
missing. If payment is made to Traveler’s Account<br />
(checking or savings), the account number must be<br />
supplied.<br />
Govt Charge Card Routing Number in the OP2<br />
record is not present. If payment is made to Traveler’s<br />
Government Credit Card, the credit card routing<br />
number must be supplied.<br />
User – 4 field (book number) is missing. If payment<br />
is made to Traveler’s Government Credit Card, the<br />
book number must be supplied.<br />
Both of these fields are required to create the<br />
invoice number.<br />
Help Desk<br />
DTA if Limit, BSN, <strong>and</strong> ASN data<br />
element are invalid. Help Desk if<br />
Limit, BSN, <strong>and</strong> ASN data element<br />
are valid.<br />
DTA if personal routing number is<br />
not specified in personal profile<br />
information.<br />
<strong>DTS</strong> Developer if personal routing<br />
number is specified.<br />
DTA if personal account type is not<br />
specified.<br />
<strong>DTS</strong> Developer if personal account<br />
type is specified.<br />
DTA if personal account number is<br />
not specified in personal profile<br />
information.<br />
<strong>DTS</strong> Developer if personal account<br />
number is specified.<br />
DTA if Govt Charge Card routing<br />
number is not specified in personal<br />
profile information.<br />
<strong>DTS</strong> Developer if Govt Charge<br />
Card routing number is specified.<br />
DTA<br />
<strong>DTS</strong> Developer<br />
<strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08 Page G-41<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.
Appendix G: <strong>DTS</strong> <strong>and</strong> <strong>GEX</strong> <strong>Error</strong> <strong>Codes</strong><br />
THIS PAGE<br />
INTENTIONALLY<br />
LEFT BLANK.<br />
Page G-42 <strong>DTS</strong> Release 1.7.1.12B, DTA Manual, Version 4.4.16, Updated 9/02/08<br />
This document is controlled <strong>and</strong> maintained on the www.defensetravel.dod.mil Website. Printed copies may be obsolete.<br />
Please check revision currency on the Web prior to use.