R12.1: FA Projections (Depreciation Projection) Errors With APP-FND-01564: ORACLE Error 1403 In Fajsup
(Doc ID 1566860.1)
Last updated on SEPTEMBER 16, 2024
Applies to:
Oracle Assets - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.3 version, Depreciation, Rollback, Projection, What-If
FA Projections (FADEPR) completes with APP-FND-01564: ORACLE error 1403 in fajsup
ERROR
-----------------------
At beginning of Depreciation Projections program
APP-OFA-48208: max_extent has the value of 600.
APP-OFA-47705: Book: XXXX
APP-FND-01564: ORACLE error 1403 in fajsup
Cause: fajsup failed due to ORA-01403: no data found
.
The SQL statement being executed at the time of the error was: and was executed from the file .
APP-OFA-47460: Error: Unable to get the first period in the projection
Cause: You have a database problem.
Action: Contact your system administrator.
APP-OFA-47715: Error: function fajsup returned failure (called from fajprj)
APP-OFA-47715: Error: function fajprj returned failure (called from FAPROJ)
Module Depreciation Projections ended with error
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
Steps to replicate:
Menu path: Depreciation -- Projections
Complete parameters:
a) Projection Calendar
b) Number of Periods (in the projection)
c) Starting Period -- Chose a closed period for which Depreciation has already been run
d) Currency
e) Asset Book Name(s)
Choose to report at Cost Center level or Asset level.
Submit.
Changes
In R12, Depreciation Projections has been enhanced to use actual data for closed periods and project only periods for which depreciation has not been run. This issue occurs only when that enhanced code is present. See Cause for longer discussion.
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! |