Autopay ID Determination Base Behavior Is Not Always the Latest Autopay ID
(Doc ID 2883383.1)
Last updated on DECEMBER 18, 2023
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 3.0.0.0.0 to 3.0.0.0.0 [Release 3]Information in this document applies to any platform.
Symptoms
On : 3.0.0.0.0 version, ENV - Environment
Autopay ID Determination Base Behavior is not always the latest Autopay ID
When a Bill is completed, CI_BILL_ACH record is created with the Autopay that is active during completion. There are scenarios where the Autopay is active when the Bill is completed, is invalid and has to be retroactively end-dated before the Autopay Extract Runs for the month.
Requesting that Oracle Revenue Management and Billing (ORMB) take the latest Autopay with respect to APAY_CRE_DT when the Autopay cycle runs instead of just relying on what is on the CI_BILL_ACH table. Similar to what it was doing in ORMB Version 2.5.
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 |