pin_cmt Does Not Take Into Account Device Status Value (Doc ID 1348325.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.4.0.0.0 to 7.4.0.0.0 - Release: 7.4.0 to 7.4.0
Information in this document applies to any platform.

Symptoms

The value for <StId> tag in <Device> structure is not considered by pin_cmt. Instead it always set the device state value to 0.

Steps to Reproduce:

- Build an input xml file for pin_cmt with the value for the <ActDev><DeviceInfo><Device><StId> tag set to a vlue different than 0. For example for a /device/sim
- Load this file using pin_cmt
- Verify that STATE_ID field for the corresponding entry in DEVICE_T table is set to 0 no matter the value specified above. I.e. DEVICE_T data files have all "0" for the STATE_ID column (last one), in spite the <StId> tag had different values (either 2 or l):

more device_t_1983646.dat

1,1983654,"/device/sim",1311844662,1,"1100006814872","","","",0
1,1983655,"/device/sim",1311844662,1,"1227798275150","","","",0
1,1992848,"/device/sim",1311844663,1,"1443908453252","","","",0
1,1992849,"/device/sim",1311844663,1,"1713913415474","","","",0
1,1992850,"/device/sim",1311844663,1,"1943064198120","","","",0

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