My Oracle Support Banner

E1: 12: User Defined Depreciation (R12855) Incorrectly Calculates Year-to-Date and Adjustments Balances for a Fully Depreciated Asset If Processing Option 8 On Process Tab is set to 1 (Doc ID 2891938.1)

Last updated on AUGUST 26, 2022

Applies to:

JD Edwards EnterpriseOne Fixed Assets - Version 9.2 and later
Information in this document applies to any platform.


The depreciation method that is used is set up as follows:

An asset was fully depreciated as of 2017.

When User Defined Depreciation (R12855) is run for this asset in preliminary mode and processing option 8 on the Process tab is set to 1 (one), the UBE incorrectly calculates balances for this asset in the Year-to-Date and Adjustments columns.

When this processing option is set to blank, no balances are calculated in these columns for this asset.



  1. P12851: set up a depreciation method as follows:
    1. Initial term apportionment: A
    2. Compute Direction: I (Inception-to-Date)
    3. Life Period: 36 months
    4. Conventions tab should show a blank in the 'Allows Over Depreciation' field, meaning that over depreciation is NOT allowed.
    5. Use these formulas: 102, 103, 501
  2. P1204: create an asset with a start date in 2014
  3. P12130: set up a beginning balance for the asset
  4. Depreciate it every month so that it is fully depreciated in 2017
  5. Run R12855 for it in proof mode with PO 8 on the Process tab set to 1 for July 2022
  6. Run R12855 for it in proof mode with PO 8 on the Process tab set to blank for July 2022



R12855 should not calculate balances in the Year-to-Date and Adjustments columns for a fully depreciated asset if the depreciation method used for this asset does not allow over-depreciation.





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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.