Depreciation Limit Amount becomes NULL after Adjusting via Adjustment API
(Doc ID 1592090.1)
Last updated on FEBRUARY 24, 2019
Applies to:
Oracle Assets - Version 12.1 and laterInformation in this document applies to any platform.
Symptoms
When the user is adjusting an asset, via Adjustment API, in which Depreciation Limit Type is "Percent" and transaction_subtype being "AMORTIZED", Depreciation Limit Amount becomes NULL.
Expected Behaviour
----------------------------
Depreciation Limit Amount is Not NULL after adjusting an asset.
Steps To Reproduce
----------------------------
1. APR-13 *** Add an asset with Depreciation Limit Type being "Percent"
Cost : 3284074
YTD depreciation amount : 0
Accumulated depreciation amount : 0
DPIS : 01-APR-2013
Deprn method : JP-DB 5YR
Salvage value : 0
Depreciation Limit Type : Percent
Depreciation Limit Percent : 95% (=164204)
2. MAY-13 *** Adjusting the asset via Adjustment API with the following parameters
API : FA_ADJUSTMENT_PUB.DO_ADJUSTMENT
---------------------------------------------------------------------------------
l_trans_rec.amortization_start_date := to_date('2013/04/30','YYYY/MM/DD');
l_trans_rec.transaction_subtype := 'AMORTIZED';
l_asset_fin_rec_adj.deprn_method_code := 'JP-DB 20YR';
l_asset_fin_rec_adj.basic_rate := 0.109;
l_asset_fin_rec_adj.adjusted_rate := 0.109;
---------------------------------------------------------------------------------
3. MAY-13 *** Confirming the asset in Asset Work Bench
Depreciation Limit
---------------------------------------------------------------------------------
Type : Percent
Limit Amount : NULL *Incorrect. The correct value is 164204
Percent : 95%
---------------------------------------------------------------------------------
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! |
In this Document
Symptoms |
Cause |
Solution |
Still Have Questions? |
References |