My Oracle Support Banner

Subsidy Discount Is Not Working After Ending Earlier Employer Association And Attaching New Employer (Doc ID 2932402.1)

Last updated on MARCH 22, 2023

Applies to:

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

Symptoms

On RMB v4.0.0.0.0, Subsidy discount is not getting recalculated properly

ACTUAL BEHAVIOR
------------------------------
After ending earlier employer association and attaching a new employer, subsidy discount is not getting recalculated properly.
Subsidy discount charges for the period when new employer is active are still getting created on old employer’s account.

EXPECTED BEHAVIOR
----------------------------------
Billable Charges for period (when New Employer got added with a new Start/End Date) should have got created against the New Employer Account

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Membership is enrolled for subsidy discount
2. Employer association has End Date as 11-21-2023
3. Inbound updates successfully updated for the Membership
4. Both subsidies 1(retiree) & 2(non retiree) are applicable for the Employer
5. Person, Account, Contract & Billable Charges for the Employer updated and reflect the Subsidy Price Item info
6. Now process the eligibility change json message by changing subsidy type from 2 to 1
7. End earlier Employer at 10312022 and attach new Employer effective from 11012022
8. Subsidy 1 (retiree) is applicable for the Employer as well as Old one
9. Inbound msg updated after eligibility change provided - earlier records are in status - C
10. Run Batch C1-recp2 - All the subsidy records are completed. Some records for adjustment type 3 went into error due to not finding rate
11. All earlier record entries are invalidated
12. Run C1-fibcr - All the records in pending are Completed.
  - But one of the Billable charge End Date is updated as 08-31-2022 while Start Date 09-01-2022 (greater than end date).
  - All the entries related to billable charge in ci_prce_calc table are in status I – invalid.
  - All the sponsor billable charges for period 11-01-2022 onwards got created against the Old employer
  - Charges from 09-01-2022 – 10-31-2022 should have got created for the Old employer and sponsor billable charges for period 11-01-2022 onwards should have got created for the New employer
  - Only one billable charge is associated to new employer

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.