My Oracle Support Banner

Correct/Recommended Way of Implementing a Prepaid Balance (Doc ID 2244763.1)

Last updated on OCTOBER 11, 2019

Applies to:

Oracle Communications Pricing Design Center - Version and later
Information in this document applies to any platform.


The business requirements for prepaid balance are as below:
1. The prepaid balance needs to have validity dates.
2. Additional bundles (e.g. Included minutes or included MBs) can be applied.
3. The ECE rating engine will be used for both postpaid and prepaid scenarios.

There are two implementation options as following:

Option 1: Implementing the main prepaid balance as a non-currency resource (resource A) and rate using resource A in the charge offer

In case the customer has an additional bundle (say implemented via resource B and a discount), this needs to refund the charge for resource A in the discount and debit resource B. In Pricing Center, this worked fine by choosing between grant/consume in the discount. However, there is no distinction in PDC. In PDC, it would have to credit 100% of the charge for resource A. But, in that case, it needs to specify validity dates which is not desired, because the expectation is to refund the charge from the charge offer.

Option 2: Implementing the main prepaid balance as a non-currency resource (resource A) and rate using currency in the charge offer

This impacts any non-currency resources using discounts. This option should technically work, but it means doing a dummy rating that will never be used (because, the pricing configuration is always refund 100% of the charge in the discount), and all rating logic is being moved to discounts.

Which is the correct/recommended way of implementing a prepaid balance?


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.