Error Code #011

Error Code #011 Error Code #011

defensetravel.dod.mil
from defensetravel.dod.mil More from this publisher
16.10.2014 Views

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.

DEFENSE TRAVEL<br />

MANAGEMENT OFFICE<br />

Standard Accounting and Reporting System Headquarters Claimant Module (STARS –HCM)<br />

Reject: Missing/Invalid Beginning Fiscal Year Indicator – Period Type <strong>Code</strong> (Fiscal Year –<br />

LOA)<br />

The document rejected because of a Missing/Invalid FY required to build the SDW per Appendix<br />

G, Table G-16: STARS-HCM. This element is required to build the SDW, which is located in<br />

Account Field 3 Position 1 of the LOA, according to Appendix R.3 Navy LOA For-mat (STARS-FL,<br />

STARS-HCM, STARS-OP).<br />

Fiscal Year [Beginning] (BFY): This is a one-position alphanumeric code that designates the first<br />

year funds are available for obligation. Please validate this LOA with your Finance DTA for<br />

STARS-HCM accounting transactions. The corrective action to take for this type of REJECT<br />

depends on the source of the error. The FDTA should verify with the STARS-HCM accounting<br />

system where the problem is. There are two possible reasons:<br />

1. Accounting system table mismatch. The BFY in the document is correct, but is not valid in<br />

STARS-HCM.<br />

• The appropriate STARS-HCM tables must first be updated.<br />

• Once the accounting table is updated, an amendment is created, apply the SIGNED or<br />

T-ENTERED stamp, and it will go through the rest of the routing cycle until the<br />

APPROVED stamp is applied. No updates to the document LOA or the organization’s<br />

LOA in DTS is required.<br />

2. The BFY in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.<br />

• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct<br />

the erroneous LOA data element. This ensures no new documents are created with the<br />

bad LOA.<br />

• The next step is to either create a new Budget Item or update the existing Budget Item<br />

in the Budget module. Please note that when creating a new Budget Item you cannot<br />

use the same label name as the previous Budget Item. Another option is to “Mass<br />

Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into<br />

the account field of the erroneous data element. Both the LOA and Budget must have<br />

the same LOA details (including #wildcards) in order for the document to be<br />

APPROVED.<br />

• Create an amendment, remove the incorrect LOA on the Accounting screen, and select<br />

the corrected LOA (which may or may not have the same name). Apply the SIGNED or<br />

T-ENTERED stamp, and process through the routing list until the APPROVED stamp is<br />

applied. The updated LOA will be sent to the accounting system.<br />

Defense Travel Management Office Revised April 2011<br />

This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.<br />

Please check revision currency on the web prior to use.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!