My Oracle Support Banner

Write Off And Refund Adjustment: Error in Creating Refund Request on Accounts without a Person Address (Doc ID 2160652.1)

Last updated on MARCH 07, 2019

Applies to:

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


On RMB 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.


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

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