Last updated on JULY 19, 2016
Applies to:Oracle Financial Services Revenue Management and Billing - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On RMB 188.8.131.52.0 version, AD - Adjustments:
Customer finds Write Off and Refund Adjustment behave differently.
They are experiencing an issue while creating a Refund Adjustment. The error happens on Refund Adjustment Freeze spot. At this point, the algorithm plugged into Refund Adjustment Freeze, tries to look for Original Related Bill Segment/Entity (BSID or ADJID) and it cannot retrieve the corresponding Entity ID from C1_REF_WO_REQ_DTLS (RefundWORequestDetails).
As per their observations, the Adjustment ID in C1_REF_WO_REQ_DTLS is not updated before the Adjustment Freeze for Refunds and this is preventing any algorithm executed at the Refund Adjustment Freeze spot from retrieving the corresponding Entity ID on the Refund Request Detail. However the same scenario is working fine for Write Off Adjustment Freeze. They are expecting the RefundAdjustmentCreationAlgComp_Impl to behave same as the Write Off Adjustment and populate the Adjustment ID prior to Adjustment Freeze.
Adjustment ID in C1_REF_WO_REQ_DTLS(RefundWORequestDetails) should be updated before invoking the Adjustment Freeze .It should be implemented same as Write Off Adjustment .
Impacted Algo :- RefundAdjustmentCreationAlgComp_Impl
The issue has the following business impact:
User did not provide any impact details, but they feel that the behavior should be same for both features.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms