Transfer Transaction in IAC Book Causes Corruption And Depreciation Failure If Code Combination Is Invalid
(Doc ID 1307573.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Public Sector Financials (International) - Version 220.127.116.11 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
Form:FAXASSET.FMB - Assets
When entering a Transfer transaction for an IAC (Inflation Accounting for Assets) asset, if one of the IAC code combinations needed for the Transfer accounting is invalid in any way, the Transfer transaction will apparently save (from the front end), but in fact the Transfer fails to commit all expected data. Data corruption is introduced which later can cause Calculate Gains & Losses or Depreciation to end in error.
The corruption may become apparent in the following ways:-
1. If the User re-queries the asset assignments, they may notice that the asset was not actually transferred to the expected new expense account in the last attempt, and if they try to re-enter the transfer, the following error will appear on screen:-
APP-OFA-48398: Program exited with errors:
ORA-01086: savepoint 'TRANSFER_PUB' never established.
ORA-06510: PL/SQL: unhandled user-defined exception.
2. The Depreciation program will subsequently error with the following errors:
o In the concurrent program log file:
'APP-OFA-47314: Error: Error in routine IAC:Do_Depreciation'
o In the FND log file:
*** Error in fetching the latest transaction
Latest transaction for the asset could not be retrieved
The corruption may appear differently in the asset trace depending on whether the transfer transaction was entered with a current period date or a prior period date.
If current period dated, it can be seen that the transfer transaction doesn't commit to fa_transaction_headers or igi_iac_transaction_headers, but a new adjustment_id_out gets created for the transfer and closes off the prior row in igi_iac_transaction_headers, but doesn't create a new row. This leaves the asset with no active row in igi_iac_transaction_headers.
If prior period dated, the transfer transaction may have committed to fa_transaction_headers but not igi_iac_transaction_headers.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|