Desingn Questions Related To Billinfo And Balance_group (Doc ID 743190.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.2.0.0.0 and later   [Release: 7.2.0 and later ]
Information in this document applies to any platform.
Checked for relevance on 31-Jan-2011

Goal

Doing design for new collection requirement to handle multiple ESN services under one account.

 

For example, one ESN service falls into collection shouldn't stop the other service, and
one prepaid ESN service falls into collection should only cancel the follow on plan instead of
stopping the service.

Currently there is only one account level balance_group and billinfo.
When an account falls into collection, create a new billinfo and a new balance_group for
each ESN service, transfer the service related charge to this new billinfo and balance_group,
modify the service to point to this new balance_group object, call bill_now to generated billed
item, and then call PCM_OP_COLLECTIONS_PROCESS_BILLINFO to put this new billinfo into collection.

Few questions on this:

1) Will multiple billinfo cause billing performance or other performance degradation?
2) Is /bal_grp and /billinfo needed for each ESN service?
3) AR opcode seems to be operating on billinfo level? Is there potential concerns in this area?
For example, payment allocation be default is to pay the oldest item first within one billinfo,
right? How will it function across multiple billinfo?
4) Is there other area needed to pay attention to? For example, if  multiple /bill
and /invoice will be created?
5) Does PCM_OP_PYMT_COLLECT opcode supports functionality for allocating a payment from one
Billinfo to another billinfo ?





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