DATA Act File A Errors
(Doc ID 2503672.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle U.S. Federal Financials - Version 12.2.6 and later
Information in this document applies to any platform.
On : 12.2.6 version, FEDERAL_REPORTS
DATA Act File A Errors
1) There is Rounding Issue after applying DAIMS V1.3 patch set. This did not happen in DAIMS V1.2. The Error happens particularly for the Beginning Balance. The Actual Error Message in File A "BudgetAuthorityUnobligatedBalanceBroughtForward_FYB= value for GTAS SF-133 line #2490 from the end of the prior fiscal year." Our Technical Team, observed there is Rounding to Two Digits implemented in FV_DACT_PERIOD_BALANCES_V that is causing rounding difference. We have multiple Program Activity Allocations too.
2) The Balance calculation for File A should be at Treasury Symbol Level. However, it is currently performing at Treasury Symbol + Direct/Reimbursable Code level. To explain in detail,
For one of the TAS 75-13-0600 and USSGL 435000 (Cancelled Authority) with a PYA Code of "X - Not an Adjustment to Prior Year Reporting"; we have around ($8 Million) in Credit Balance for Direct Fund and $3 Million in Debit Balance in Reimbursable Fund. Hence the Net Balance at TAS Level is ($5 Million) Credit Balance.
However, the DATA Act Amount Definition for Amount Code# 110 (BudgetAuthorityUnobligatedBalanceBroughtForward_FYB) and USSGL 435000 with PYA Criteria of X is set up Ending-Credit Only. Though this is similar to SF133 configuration for Line Item#1029; the current balance calculation utilizes the Direct/Reimbursable Code in the grouping logic causing the Debit Balance of $3 Million (of Reimbursable) to be Ignored; leaving only the Credit Balance of ($8 Million).
When this File A is uploaded to the Treasury Broker; it gives a Critical Error that "AdjustmentsToUnobligatedBalanceBroughtForward_CPE= CPE aggregate value for GTAS SF-133 line #1010 through 1042"
The Workaround that is currently following changing the Balance Type for 43500 from "Ending-Credit Only" to "Ending" for PYA Code of X; so that netting happens across Funds. This makes it different from the SF133 and might cause unwanted impacts.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document