Federal File Creation Process For "GTAS" Only Does Not Generate GTAS Interface Validation Exception Report For "Disaster Emergency Fund Code not valid for GL Account" As Expected
(Doc ID 2955166.1)
Last updated on JUNE 16, 2023
Applies to:
Oracle U.S. Federal Financials - Version 12.2 and laterInformation in this document applies to any platform.
Federal
GTAS
Exception Report
Disaster Emergency Fund Code not valid for GL Account
Symptoms
- When the Federal File Creation Process is run for "GTAS" alone it does not generate the GTAS Interface Validation Exception Report with message "Disaster Emergency Fund Code not valid for GL Account" when it should. The GTAS Interface Exception Report is not being generated and the Federal File Creation Process does not error out when a DEFC reporting code in not in the table. This only happens when selecting just 'GTAS', and this is the problem.
- When the Federal File Creation Process is run, for the identical data as above, for either "Data Act" or "GTAS and Data Act", the GTAS Interface Validation Exception Report is generated with the correct exception "Disaster Emergency Fund Code not valid for GL Account". Selecting "Data Act" or "GTAS and Data Act" produces the exception report and errors out the program as expected.
- The agency has users who only run the Federal File Creation Process for GTAS. This problem is creating issues with the GTAS bulk file not having the DEFC codes and the users not being made aware of the problem via exceptions. The user only finds out about the problem when they try to upload to Treasury.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |