My Oracle Support Banner

WS: 12: Troubleshooting Compute Depreciation (P12850 and P12855) (Doc ID 1536226.1)

Last updated on JULY 07, 2021

Applies to:

JD Edwards World Fixed Assets - Version A7.3 cume 4 and later
Information in this document applies to any platform.


To describe the errors or issues you might encounter when you run Compute Depreciation (P12850) and Compute UDD Depreciation (P12855).

Troubleshooting Steps

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
Troubleshooting Steps
 Issue 1:  The program did not compute depreciation for a specific asset or ledger.
 Issue 2:  The system prints the message, "Invalid Accum Dep Acct/Post Edit Code Error", on the depreciation journal.
 Issue 3:  After upgrading from release A7.3 to A9.x, depreciation batches appear in a Pending status even though the processing option is set to automatically submit the post.
 Issue 4: The system did not calculate depreciation based on the date entered in the Date Depreciation Started field (DSD) that displays for the asset on the Depr & Accounting Values screen (P1202). 
 Issue 5: The system uses the net book value (NBV) as the basis for depreciation instead of cost. 
 Issue 6:  The system prints the message, "This depreciation start date is invalid", on the depreciation journal. 
 Issue 7: The system did not calculate depreciation based on the life months that display for the asset on the Depr & Accounting Values screen (P1202).
 Issue 8: Why is the error " Depreciation G/L Date is in prior year or prior period for this company" displaying?
 Issue 10: Compute UDD Depreciation (P12855) uses the wrong cost value.
 Issue 11: Depreciation calculation incorrect or message, *** Date pattern missing for asset ***, prints on the Depreciation Journal when you run Compute Depreciation (P12850) using processing option 3.
 Issue 12: Current year assets do not appear on the Depreciation Journal until you run it for mid-year, even though the apportionment code (ITAC) assigned to the asset’s F1202 record does not use a mid-year convention. Additionally, when you run Compute Deprecation (P12850) in final mode, the program updates the value of ITAC to Y (mid-year convention) on the asset’s F1202 record for the AA ledger. Why?
 Issue 13: Compute UDD Depreciation (P12855) returns error Asset Number . . . . # DM= 01 Special Handling code in UDC 12/DM not 1. Why?
 Issue 14: When you run Compute UDD Depreciation (P12855), the program calculates negative depreciation on some assets.  In other words, the value of net book value (NBV) increases.

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