Pipeline Memory Not Refreshing With Latest Account Data After Receiving Sync Event

(Doc ID 1071815.1)

Last updated on JULY 20, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.1.0.0 to 7.2.1.0.1 [Release 7.2.1]
Information in this document applies to any platform.
***Checked for relevance on 20-Dec-2011***
*** Checked for relevance on 07-20-2016 ***


Symptoms

Pipeline memory is not being refreshed with the latest account data, when product modify and product purchase events are taking place. dm_ifw_sync is publishing the events to the queues, and they are being received by the pipeline. But pipeline is not reloading the account data. The memory dump of the account data is the same. The rating behavior is the same. i.e., the pipeline continues to rate CDRs using old rate plan, the new rate plan is not recognized.

Steps To Reproduce:

[ UTC_TIME_OFFSET = -0800 ]

1. Create a plan called "Customer Account" with no service, no deal
2. Create an Addon plan called "Usage Plan" with 2 optional deals - CLDT On Net Deal and CLDT Comtel Deal. Both deals do not have cycle fee, only including rate plan for gsm delayed sesssion event
3. On Oct 21, create an account with Customer Account plan. Backdate = Oct 1
4. On Oct 21, purchase a backdate plan - Usage Plan, and select CLDT Comtel deal from the Usage Plan.
Set Backdate Purchase from Oct 19
5. On Oct 21, rate TEL usage (usage start date = Oct 19, 03:13am) - this is successful
6. On Oct 21, set CLDT Comtel Deal cycle/purchase/usage end_t = Oct 21

e.g. account robj
nap(23703)> # number of field entries allocated 45, used 44
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 2963015 12
0 PIN_FLD_CREATED_T TSTAMP [0] (1256190722) Wed Oct 21 22:52:02 2009
0 PIN_FLD_MOD_T TSTAMP [0] (1256191430) Wed Oct 21 23:03:50 2009
...
0 PIN_FLD_PRODUCTS ARRAY [1] allocated 28, used 28
1 PIN_FLD_CREATED_T TSTAMP [0] (1255935600) Mon Oct 19 00:00:00 2009
1 PIN_FLD_CYCLE_DISCOUNT DECIMAL [0] 0
1 PIN_FLD_CYCLE_DISC_AMT DECIMAL [0] 0
1 PIN_FLD_CYCLE_END_T TSTAMP [0] (1256108400) Wed Oct 21 00:00:00 2009
1 PIN_FLD_CYCLE_FEE_AMT DECIMAL [0] 0
1 PIN_FLD_CYCLE_FEE_FLAGS INT [0] 1
1 PIN_FLD_CYCLE_START_T TSTAMP [0] (1255935600) Mon Oct 19 00:00:00 2009
...
1 PIN_FLD_PURCHASE_END_T TSTAMP [0] (1256108400) Wed Oct 21 00:00:00 2009
1 PIN_FLD_PURCHASE_FEE_AMT DECIMAL [0] 0
1 PIN_FLD_PURCHASE_START_T TSTAMP [0] (1255935600) Mon Oct 19 00:00:00 2009
...
1 PIN_FLD_USAGE_END_T TSTAMP [0] (1256108400) Wed Oct 21 00:00:00 2009
1 PIN_FLD_USAGE_START_T TSTAMP [0] (1255935600) Mon Oct 19 00:00:00 2009

And listener.log:
...
# number of field entries allocated 20, used 4
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.1 /service/telco/gsm/telephony 2962119 0
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 2963015 10
0 PIN_FLD_STRING STR [0] "UpdateServices"
0 PIN_FLD_END_T TSTAMP [0] (1256191429) Wed Oct 21 23:03:49 2009
# number of field entries allocated 20, used 3
0 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 2963015 10
0 PIN_FLD_STRING STR [0] "ProductModify"
0 PIN_FLD_END_T TSTAMP [0] (1256191429) Wed Oct 21 23:03:49 2009


7. On Oct 21, rate TEL usages (the first usage start date/time = Oct 21, 3:13 am, the second usage start date/time = Oct 21, 13:13pm)

Expected Result:
  The rating should fail because of no valid product

Actual Result:
  The rating is successful

Cause

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