Expected Behavior With Hung CC Batch And Changed Pay Type?
(Doc ID 969806.1)
Last updated on AUGUST 29, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Consider the following chain of events:
1. run pin_collect to charge CC accounts;
2. The network connect to PTI fails and the batch is not sent;
3. A customer changes to invoice pay type;
4. pin_recover -resubmit now errors on the account that changed pay type.
What is the expected behavior at this point when performing the resubmit? Should the system not re-send accounts that have changed pay type? What if they only changed CC#?
The system already has all the cc details in /event/billing/charge/cc, so it should be able to recreate the charge info for fusa. However, the system actually drops that account from the fusas. Instead the system breaks when processing the fusas.
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