Oracle Assets Retirement API Allows Excessive Retirement Cost With Zero Units
(Doc ID 2406813.1)
Last updated on JUNE 12, 2023
Applies to:
Oracle Assets - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.3 version, Retirement & Reinstatement
When attempting to retire an asset via the Retirement API by incorrectly providing an excessive cost amount and units of 0, the API allows this to occur and incorrect data
The issue can be reproduced at will with the following steps:
1. Submit the Retirement API with:
l_asset_retire_rec.units_retired := 0;
l_asset_retire_rec.cost_retired := &Some_excessive_cost;
It will process the excessive cost for the asset, which is not valid.
Due to this issue, users will see incorrect data journal entries result from such a scenario.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |