Pipeline-Triggered Billing Is Not Fired
(Doc ID 1936907.1)
Last updated on APRIL 12, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
On : 7.5.0.5.0 version, Pipeline Manager, Triggered Billing is not happening
Configure system with delayed billing with delay period set to 1 and auto_triggering_limit set to 1.
STEPS
-------------
The issue can be reproduced with the following steps:
1. 29th June 2014: Creating account and purchase product
2. 1st July 2014: Run pin_bill_accts - partial billing, only cycle fees applied
3. 16th Aug 2014: Pass usage for cdr date 16th Aug 2014
ACTUAL BEHAVIOR
---------------
Triggered Billing is not happening
EXPECTED BEHAVIOR
-----------------------
Triggered Billing should happen so that finial billing can happen for the account.
NOTE: If user not run pin_bill_accts [partial billing], Pipeline-Triggered Billing is fired correctly.
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 |