C1-REPC2 Getting Error For Membership With Higher End Date 12-31-9999
(Doc ID 2610453.1)
Last updated on FEBRUARY 03, 2022
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.8.0.0.0 and laterInformation in this document applies to any platform.
Goal
We will be sending a high value end date, for example 12-31-9999 to represent the open end dated membership. Membership installed from 01-01-2019 to 12-31-9998, went into error when running C1-REPC1, C1-REPC2. and C1-REPC2. Billable Charge should be created 01-01-2019 to 12-31-9999.
Why is the application generating and error and generating the expected Billable Charge?
Solution
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
| Goal |
| Solution |
| References |