Passing Contract ID Before Calling "generateAndFreeze" on Bill Class API is Causing Issues
(Doc ID 2486017.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Passing Contract ID before calling "generateAndFreeze" on the com.splwg.ccb.domain.billing.bill.Bill class API is causing issues.
We have a Bill segment amount proration algorithm on the Contract Type - PostProcessing (Billing) spot that prorates the Bseg amount in case the User signs up for a Policy which is effective mid of the month. This algo is getting invoked properly if we call the "generateAndFreeze" method of the Bill class API instead of just the "generate" method.
I am finding that if I pass the SAID to the Bill object before calling this method, it is giving inconsistent results, it doesn't invoke this algo at all. But if I do not pass the SA ID before calling "generateAndFreeze", it is invoking this same algo spot correctly and it is creating the correct prorated Bseg amount on the Bill. We have only 1 Standard account per customer account (the other being Excess credit SA).
This article confirms the exact reason why passing a Standard SAID in the API can cause an issue.
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