In Oracle fixed assets, depreciation program is the one which touches each and every asset in an asset book and calculates depreciation for each of these assets. So with huge number of assets in a book, depreciation program completing with a reasonable time is a challenge for every organization.

The following provides some tips and suggestions which might help to reduce the overall runtime of the Depreciation Request Set :

1. Debug Profiles – Check the following profile options making sure they are NOT checked or enabled, as these can all affect performance:

  • FA: Deprn Single

  • FA: Print Debug

  • FA: Print Timing Diagnostics

  • FND: Debug Log Enabled

2. Concurrent Program Tracing – Check that you do NOT have the ‘Trace’ option checked on any of the concurrent programs in the Depreciation Request Set (Generate Accounts, Calculate Gains & Losses, Depreciation, Journal Entry Reserve Ledger Report).

You can check this in the Concurrent > Program > Define form, from the System Administrator responsibility.

3. Security Profile and Parallel Processing – Check the following profile options which can impact the performance: 

FA: Security Profile

If this profile is set, it means that security is enabled for the responsibility and this should be expected to slow down the processing slightly.

FA: Number of Parallel Requests

You may wish to consider setting this profile to improve the performance. Please see the ‘Oracle Assets Profile Options’ Chapter in the Oracle Assets User Guide, for more information about this profile option.

4. Latest Code Level – Consider applying more recent code for any of the programs which seem to be taking the most time in the Depreciation Request Set. In particular, it is recommended to be on the latest FA rollup patch for your patchset level.

Refer to the following note for the Latest FA Rollup Patch numbers:

Doc ID 466607.1 – R12 / 11i FA.M-P RECOMMENDED PATCH LIST

5. Data base Setup – Are all required init_SID.ora parameters set correctly according to the script in Note 174605.1?

Refer to: Doc ID 174605.1 – bde_chk_cbo.sql – EBS initialization parameters – Healthcheck

6. Running Gather Schema Statistics Program – Ensure you run ‘Gather Statistics’ for the FA Schema on a regular basis; particularly important after any big data load.

7. Pr-Processing – Take advantage of the ability to do pre-processing before the period end time, by running ‘Generate Accounts’ and ‘Calculate Gains and Losses’ as standalone processes, as often as required during the month.

This will ensure as much pre-processing as possible is done before the Depreciation Request Set is run, and will reduce the time of those elements of the request set.

8. Bulk Data Upload – Be aware, the runtime for the first depreciation run after a big data load should be expected to take considerably longer than for subsequent periods.

The Depreciation Program (FADEPR) part of the request set has much greater processing than normal to achieve in such runs, as the addition rows for every new asset must be entered, as well as the depreciation rows.