Oracle Revenue Management and Billing (ORMB) Processes Transactions Only For Bill Levels That Have a Maximum Effective Date
(Doc ID 2599843.1)
Last updated on OCTOBER 21, 2019
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.7.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
On : 2.7.0.1.0 version, BI - Billing
ORMB processes transactions only for bill levels that have a maximum effective date.
For example, if there are 11 Bill Levels (with different Group/Section) out of which 10 Bill Levels have an effective date of 11/01/2014 and 1 has an effective date of 06/01/2019 (which is the maximum effective date), only transactions (claims, enrollment etc.) that are mapped to this Bill Level (Group/Section) will get successfully processed. All other transactions will go into error.
This issue has a major impact on billing as a large number of transactions will fail at the TFM (transactions processing) stage.
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 |