Paid Through Date Incorrect if Member Cancelled as Never Effective and Re-enrolled Later
(Doc ID 3067510.1)
Last updated on JANUARY 14, 2025
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 5.1.0.0.0 to 5.1.0.0.0 [Release 5.0]Information in this document applies to any platform.
Symptoms
On RMB v5.1.0.0.0, Paid through Date (PTD) showing wrongly in UI.
PTD is being incorrectly calculated if the member was cancelled as never effective, but re-enrolled at a later date.
STEPS
-----------
1. Enroll a membership effective 05/01 to 12/31.
2. Create bills let say for 4 months, fully match each bill to payments.
3. Run PTDIND submitted online via UI.
- It calculates the correct date value.
4. Cancel the membership on 05/01.
5. Reenroll the same membership effective 10/01 to 12/31.
6. Create a refund request to move the payments on account.
7. Run PTDIND batch
- It calculates the incorrect value.
ACTUAL BEHAVIOR
----------------------------
PTD value is Oct 31st.
EXPECTED BEHAVIOR
---------------------------------
PTD value should be earlier than new Effective Date.
So here reenrollment effective date is Oct 1st and so we expect PTD should be Sep 30.
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 |