Error Code #011

Information Paper:
Error Code #011
DEFENSE TRAVEL
MANAGEMENT OFFICE
Reject Missing/Invalid Beginning Fiscal Year Indicator – Period
Type Code
Defense Business Management System (DBMS) Accounting System Reject: Missing/Invalid
Beginning Fiscal Year Indicator – Period Type Code (Fiscal Year – LOA)
The document is being rejected because Fiscal Year must be populated per Appendix G, Table G-3:
DBMS. This element is located in Account Field 2, Positions 4-7 of the LOA according to Appendix
R.6 DBMS LOA Formats (DBMS).
Fiscal Year (FY): This is a four position alphanumeric code that designates the year funds are
available for obligation. Validate this LOA with your Finance Defense Travel Administrator (FDTA) for
DBMS accounting transactions. The corrective action to take for this type of REJECT depends on the
source of the error. The FDTA should verify with the accounting system where the problem is. There
are two possible reasons:
1. Accounting system table mismatch. The DBMS FY in the document is correct, but is not valid
in DBMS.
• The appropriate DBMS table must be updated.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required.
2. The DBMS FY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system.
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
Defense Working Capital Accounting System (DWAS) Reject: Missing/Invalid Beginning
Fiscal Year Indicator – Period Type Code (Fiscal Year – LOA)
The document is being rejected for a Missing/Invalid Fiscal Year required to build the SDW per
Appendix G, Table G-6: DWAS. This element is located in Account Field 2, Position 7-10 of the LOA
according to Appendix R.9 DWAS LOA Format (DWAS).
Fiscal Year (FY): This is a four-position alphanumeric code that designates the first year funds are
available for obligation. “XXXX” is used for DoD Revolving funds. Validate this LOA with your
Finance DTA for DWAS accounting transactions. The corrective action to take for this type of
REJECT depends on the source of the error. The FDTA should verify with the accounting system
where the problem is. There are two possible reasons:
1. Accounting system table mismatch. The FY in the document is correct, but is not valid in
DWAS.
• The appropriate DWAS tables must first be updated.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required
2. The FY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
E-Biz Accounting System Reject: Missing/Invalid Beginning Fiscal Year Indicator – Period
Type Code (Fiscal Year – LOA)
The document is being rejected for a Missing/Invalid Budget Fiscal Year per Appendix G, Table G-7:
eBiz. This element is located in Account Field 2, Positions 4-7 of the LOA according to Appendix R.8
eBiz LOA Format (eBiz).
Fiscal Year (FY) - This is a four character alphanumeric code that designates the year funds are
available for obligation. The ‘Accounting Data Element A3’ in Record 05 is not valid on the E-Biz
Defense Agency Level Organization (DALO) reference table, or is not populated. Please validate the
FY data element in the LOA with your Finance DTA for eBiz transactions. The corrective action to
take for this type of REJECT depends on the source of the error. The FDTA should verify with the
accounting system where the problem is. There are two possible reasons:
1. Accounting system table mismatch. The FY in the document is correct, but is not valid on the
eBiz Function, or Task reference table, or is not populated.
• GS0039E – The Defense Agency Level Organization value is not valid in the database.
• The appropriate EBIZ tables must first be updated.
• . Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required
2. The FY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
General Accounting and Finance System GAFS Base Level (GAFS BQ) Reject: Missing/Invalid
Beginning Fiscal Year Indicator – Period Type Code (Fiscal Year – LOA)
The document is being rejected for Missing/Invalid Fiscal Year per Appendix G, Table G-8: GAFS-
DTS. This element is located in Account Field 2, Position 7 of the LOA, according to Appendix R.1
Air Force LOA Format (GAFS-DTS).
Fiscal Year (FY): This is a one-position alphanumeric code that designates the year funds are
available for obligation. Validate this LOA with your Finance DTA for GAFS (BQ) accounting
transactions. The corrective action to take for this type of REJECT depends on the source of the
error. The FDTA should verify with the GAFS accounting system where the problem is. There are
two possible reasons:
1. Accounting system table mismatch. The FY in the document is correct, but is not valid in
GAFS (BQ).
• The appropriate GAFS (BQ) tables must first be updated.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required.
2. The FY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system.
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
Standard Accounting, Budgeting, and Reporting System (SABRS) Reject: Missing/Invalid
Beginning Fiscal Year Indicator – Period Type Code (Fiscal Year – LOA)
The document is being rejected because the Trip received is for a Future year; CCYY, 1st year funds
are available per Appendix G, Table G-10: SABRS. This is due to an inappropriate FY element,
which is located in Account Field 2, Positions 4-5 of the LOA, according to Appendix R.5 USMC LOA
Format (SABRS).
Fiscal Year (FY): This is a two position alphanumeric code that designates the year funds are
available for obligation. Validate this LOA with your Finance DTA for SABRS accounting
transactions. The corrective action to take for this type of REJECT depends on the source of the
error. The FDTA should verify with the SABRS accounting system to determine where the problem
is. There are two possible reasons:
1. Accounting system table mismatch. The FY in the document is correct, but is not valid in
SABRS.
• The appropriate SABRS tables must first be updated.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required
2. The FY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
Standard Finance System (STANFINS) Reject: Missing/Invalid Beginning Fiscal Year Indicator
– Period Type Code (Fiscal Year – LOA)
The document is being rejected because the FY must be populated per appendix G, Table G-14:
STANFINS. This element is located in Account Field 2 Positions 4-7 of the LOA, according to
Appendix R.2 Army LOA Format (SOMARDS, STANFINS).
Fiscal Year (FY): This is a four position alphanumeric code that designates the year funds are
available for obligation.
NOTE: In Appendix R.2, the ARMY LOA format map is used by both SOMARDS and STANFINS
accounting system. Validate this LOA with your Finance DTA for STANFINS accounting
transactions. The corrective action to take for this type of REJECT depends on the source of the
error. The FDTA should verify with the accounting system where the problem is. There are two
possible reasons:
1. Accounting system table mismatch. The FY in the document is correct, but is not valid in
STANFINS.
• The appropriate STANFINS tables must be updated.
• The accounting system has the LOA data element loaded correctly.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required
2. The FY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system.
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
Standard Accounting and Reporting System Field Level (STARS-FL) Accounting System
Reject: Missing/Invalid Beginning Fiscal Year Indicator – Period Type Code (Fiscal Year –
LOA)
The document is being rejected because the Beg FY not matched to Beg FY in Root Job Order table
Period Type Code: FY required to build the SDW per Appendix G, Table G-15: STARS-FL. This
element is located in Account Field 3, Position 1, according to Appendix R.3 Navy LOA Format
(STARS-FL, STARS-HCM, STARS-OP).
Fiscal Year [Beginning] (BFY): A one-position alphanumeric code that designates that year funds are
available for obligation. Please validate this LOA with your Finance DTA for STARS-FL accounting
transactions. The corrective action to take for this type of REJECT depends on the source of the
error. The FDTA should verify with the STARS-FL accounting system where the problem is. There
are two possible reasons:
1. Accounting system table mismatch. The (BFY) in the document is correct, but is not valid in
STARS-FL.
• The appropriate STARS-FL tables must first be updated.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required
2. The BFY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system.
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
Standard Accounting and Reporting System Headquarters Claimant Module (STARS –HCM)
Reject: Missing/Invalid Beginning Fiscal Year Indicator – Period Type Code (Fiscal Year –
LOA)
The document rejected because of a Missing/Invalid FY required to build the SDW per Appendix
G, Table G-16: STARS-HCM. This element is required to build the SDW, which is located in
Account Field 3 Position 1 of the LOA, according to Appendix R.3 Navy LOA For-mat (STARS-FL,
STARS-HCM, STARS-OP).
Fiscal Year [Beginning] (BFY): This is a one-position alphanumeric code that designates the first
year funds are available for obligation. Please validate this LOA with your Finance DTA for
STARS-HCM accounting transactions. The corrective action to take for this type of REJECT
depends on the source of the error. The FDTA should verify with the STARS-HCM accounting
system where the problem is. There are two possible reasons:
1. Accounting system table mismatch. The BFY in the document is correct, but is not valid in
STARS-HCM.
• The appropriate STARS-HCM tables must first be updated.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required.
2. The BFY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system.
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.