Transactions Are Erroring Out For Renewed Policy In Runout Status
(Doc ID 2807079.1)
Last updated on JANUARY 27, 2022
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 ORMB v2.7.0.1.0, Transactions are erroring out for renewed policy in Runout status.
The customer has been processed for Policy Renewal, thus creating a second policy.
Transactions are completed when the policy is active. When policies are set to runout, the same set of transactions (same dates, same amounts, price items, etc.) are inserted again to the staging table and processed through TFM.
It now returns an error even though it is before the runout end date.
ERROR
-----------------------
Multiple contracts in Active, Pending Stop, Stop status exists for same contract type against account %1, product %2 and transaction date %3.
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 |