Pipeline Memory Is Not Updated Using Custom Rollover Event (Doc ID 2143504.1)

Last updated on FEBRUARY 22, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.5.0.0.0 [Release 7.3.1 to 7.5.0]
Information in this document applies to any platform.

Goal

On :  7.3.1.0.0 version, Account Sync

Issue :
Pipeline data memory is not getting updated while billing an account.


Scenario :
- custom rollover event is created with poid_type = /event/billing/cycle/rollover/monthly/inng
- 15/06 : creation of a new customer (BDOM = 15) with cycle-forward granting 20 on a non currency balance (101030100) and the above custom rollover event to rollover the unused resource.
- 17/07 : run billing
        The billing grants a new period for the non currency balance and creates a rollover on the unused previous balance
        The problem is that the rollover is not known to the DAT_Balance data module
        Thus, it is not possible for the customer to rate usages on the rollover.

Observation :
1) If one stops and starts the rating pipeline, then the rollover will be correctly known in the DAT_balance data module, and then rating in rollover resource is correct.
2) If one modifies the rollover event in order to use standard poid_type (/event/billing/cycle/rollover/monthly) then the issue does not occur (that is, pipeline memory is correctly updated after 15/07 billing).


Question :
Why pipeline memory is not updated when using custom rollover?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms