ORMB V2.9 Upgrade - Deferred Revenue Recognition - RECOG_DT Not Populated Correctly
(Doc ID 2738009.1)
Last updated on DECEMBER 22, 2020
Applies to:Oracle Financial Services Revenue Management and Billing - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, ENV - Environment
Deferred Revenue recognition - RECOG_DT not populated correctly.
The issue can be reproduced at will with the following steps:
Customer have done all of the below configuration for achieving the Deferred Revenue recognition (DRR) functionality through the base product entities as per the v22.214.171.124 user guide:
1) Configured the "C1-REVRECSCH" algorithm on the "FT Freeze" system event of the Contract type.
2) Created a DRR template for combination of above Contract Type and Distribution code (Unearned Premium) with Recognition Schedule = "Monthly"
3) Configured all algorithms on the below system events of the above DRR template:
a) Generate Revenue Recognition Adjustment (C1-REVRECADJ)
b) Create Deferred Revenue Recognition Schedule (CM-REVRECITM)
c) Recognize Deferred Revenue (C1-REVITMREC)
4) Also we are have configured the below parameters in the "CM-REVRECITM" algo:
a) Override Default Recognition Date = "Y"
b) Override Default Monthly Recognition Date (1-31) = "1"
Then we created an enrollment today with eff date of 5/1/20 which created a bill with the below bill segments:
5/1/20 - 5/31/20
6/1/20 - 6/30/20
7/1/20 - 7/31/20
8/1/20 - 8/31/20 (since we bill 1 month in advance)
They found that the "RECOG_DT" after running the "C1-RRSMO" batch is getting defaulted to the last day of the month of the bill segment even though they have overridden the values in above algo as "1" (1st of the month)
RECOG_DT should populate the correct value.
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