My Oracle Support Banner

Refund AD At Payment Event Level Is Not Matching All Payments (Doc ID 2905565.1)

Last updated on NOVEMBER 01, 2022

Applies to:

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

Symptoms

On RMB v2.9.0.0.0, Refund AD at payment Event level is not matching all payments.

Refund AD at payment Event level is not matching all Payments and this is resulting in unmatched payments lying orphan on excess credit even though it was refunded. Match Event is not updated against Payment FTs, when Refund is created against Payment Event having 2 payments.

ACTUAL BEHAVIOR
---------------------
Match Event was not populated for all payments when there are multiple payments under single pay event.

EXPECTED BEHAVIOR
---------------------
Product should alert/error if there are multiple payments under single pay event as this is not allowed.

STEPS
------------
1) Create a Excess payment event, it should have 2 payments for same account
2) Create refund request on that account using that payment event
3) On Submit it should give error saying "Multiple payments present in single payment event id for refund request"
4) Also check using upload refund request, it will give same error message on validate button.

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
References


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