USELATESTPRODUCTANDDISCOUNT DOES NOT WORK AS DOCUMENTED (Doc ID 1070342.1)

Last updated on AUGUST 11, 2010

Applies to:

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

Goal

Pipeline document 7.3.1 mentioned if set UseLatestProductAndDiscont as true,
pileline will only check start_t and end_t. But rating result is not as expected.

online documents says:
You can use the DAT_Account module UseLatestProductAndDiscount registry entry to configure validity checking for account products and discounts.
If you enable this entry, when rating EDRs, DAT_AccountBatch retrieves account product and discount information based only on their start and end dates.

Example
On 1,Jan, 2010, customer purchase plan A
On 15,Jan, 2010, customer cancelled the plan with future data to 1,Feb, 2010.
In purchased_product_t
the record is as (effective_t 2010/2/1, usage_start_t 2010/1/1, usage_end_t 2010/2/1).

On 16,Jan, a cdr with data of 16, Jan, comes and be rejected.

If pipeline only checkes start/end dates, the CDR shall be rated. As Start_t is 2010/1/1,
and end_t is 2010/2/1. But the result is the CDR be rejected.

If UseLatestProductAndDiscount is set, does it check effective_t also ?

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