My Oracle Support Banner

Setting a Discount Model to Inactive Causes Other Discount Models to be Inactive (Doc ID 2256126.1)

Last updated on AUGUST 13, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Billing and Revenue Management, when deactivate a discount model, other discounts owned by the account stopped working resulting in the end user being charged extra.

Example scenario:

1. On a given account, there are two discount models among others:

2. When both discount models are active, there are no issues and everything operates as expected

3. When DM.1 is set to INACTIVE and a realtime event comes for discounting, DM.2 is not appliedHere are observations from the logs:

The following is observed in the logs:

1. From the cm.pinlog, there is a call to discounting:

D Sat Apr 15 09:19:49 2017  dev  cm:23404
fm_rate_and_discount_event.c:1002
2:dev:testnap:23402:-142821664:4007:1490602797:1:root.0.0.0.1:::
Re-directing to PCM_OP_RATE_DISCOUNT_EVENT input flist
# number of field entries allocated 20, used 9
0 PIN_FLD_POID           POID [0] 0.0.0.1 /event/session/telco/gprs -1 0
0 PIN_FLD_USED_BAL_GRP_OBJ   POID [0] 0.0.0.1 /balance_group 4060827817 10
0 PIN_FLD_SERV_BAL_GRP_OBJ   POID [0] 0.0.0.1 /balance_group 4060827817 10
0 PIN_FLD_BAL_INFO      ARRAY [0] allocated 20, used 15
1     PIN_FLD_BAL_GRP_OBJ    POID [0] 0.0.0.1 /balance_group 4060827817 10
..
..

2. From the discount trace file (snippet below), it is observed that DM.2 is actually calculated correctly, but there is an error at the end when it comes to evaluate the discount model DM.1 (which has been set to inactive):

evalConfigurations() obj/type:129349/2, config:150144, DM.TMHMBQ/DR.GPRSTMQ,
master: 100023, discountMode 2
mTotalC = 0.1319, mTotalQ = 1030.00000000
INFO: UTC offset in seconds is 0
..
discountImpact() --DP 2-- DISC -0.1319 to Res: 978 BG: 4060827817; (BG
evt/obj: 4060827817/4060827817)
..
..
discountImpact() --DP 3-- DISC 1030.00000000 to Res: 3000016 BG: 4060827817;
(BG evt/obj: 4060827817/4060827817)
..
..
..
evalDiscountObjs: discount model: (DM.USGL)
Discount Object Mode: 803 Discount Object: 3532153090
transaction error: flag: (0)

3. In the pipeline log, the following warning message is observed:

10.04.2017 08:45:47 dev ifw IFW WARNING [T:2854209280] 18013 - (ifw.Pipelines.DiscountPipeline0.Functions.Standard.FunctionPool.ApolloDiscountModule.Module) Cannot find configuration for discount model 'DM.USGL', date '20170410064546'.

4. As a result, in the cm.pinlog (snippet below), there is no balance impact obtained from the realtime pipeline

D Sat Apr 15 09:19:49 2017  dev  cm:23404 fm_rate_and_discount_event.c:1010 2:dev:testnap:23402:-142821664:4007:1490602797:1:root.0.0.0.1:::
Re-direction PCM_OP_RATE_DISCOUNT_EVENT output flist:
# number of field entries allocated 20, used 3
0 PIN_FLD_POID           POID [0] 0.0.0.1 /event/session/telco/gprs -1 0
0 PIN_FLD_ACCOUNT_OBJ    POID [0] 0.0.0.1 /account 4060829993 0
0 PIN_FLD_RESULT         ENUM [0] 1
D Sat Apr 15 09:19:49 2017  dev  cm:23404 fm_rate_and_discount_event.c:1985 2:dev:testnap:23402:-142821664:4007:1490602797:1:root.0.0.0.1:::

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!


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