Change Of SIM Does Not Update Effective_t In Uniqueness Table (Doc ID 604632.1)

Last updated on JANUARY 04, 2013

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.0.3.0 to 7.2.0.0.1 [Release 7.2.0]
Information in this document applies to any platform.

Symptoms

In a multi-db environment, when an IMSI 'A' attached to a subscriber is changed to another IMSI, say 'B', the effective_t value in uniqueness table for this of IMSI remains the same as that of IMSI A. The IMSI can be found in login field in uniqueness_t table. This might results in calls rated for this subscriber based on IMSI to be routed to a different MSISDN , which has re-used IMSI A.

The effective_t is being correctly updated in service_t , though.

OP_CUST_SET_LOGIN is being called with the following input flist to do this operation.

0 PIN_FLD_POID POID [0] 0.0.0.2 /account 40794333190 0
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.2 /service/ip/gprs 40794333894 0
0 PIN_FLD_PROGRAM_NAME STR [0] "FM_MY_PROV_IMSI_CHANGE"
0 PIN_FLD_START_T TSTAMP [0] (1204206811) Thu Feb 28 13:53:31 2008
0 PIN_FLD_END_T TSTAMP [0] (1188970628) Wed Sep 5 06:37:08 2007
0 PIN_FLD_LOGINS ARRAY [0] allocated 20, used 1
1 PIN_FLD_ALIAS_LIST ARRAY [0] allocated 20, used 1
2 PIN_FLD_NAME STR [0] "123412341234"


A sample scenario is described below :
a) Create a subscriber account using OP_CUST_CREATE_CUSTOMER
b) Ensure that the environment is Multi DB.
c) Change the IMSI attached to the subscriber using OP_CUST_SET_LOGIN
d) Verify the effective_t of the new IMSI attached to the subscriber.

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