Adjustment Rejection Deletes Data from CI_ADJ - Instead It Should Change the Status to Reject and Keep the Record

(Doc ID 2207025.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.3 and later
Information in this document applies to any platform.


On RMB v2.3.0.2 version against FW, AD - Adjustments:

Adjustment Rejection Deletes data from CI_ADJ, instead it should change the status to reject.

Create an adjustment, send it for approval and then reject it.
Record from CI_ADJ gets deleted and there is no trace/linkage of what Adjustment was rejected.

The record should not be deleted; instead status should get updated as rejected.

The issue can be reproduced at will with the following steps:
1. Login from SYSUSER and create an Adjustment and sent it to approval, notice that record shows up in CI_ADJ & CI_APPR_REG
2. Login from other BKADMIN and Reject the approval
3. Record gets deleted from CI_ADJ, but it remain in CI_APPR_REG with modified status

The issue has the following business impact:
Due to this issue, users think corrupted data get added in the database which will affect business in future.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms