After Migration From 7.2 To 7.3.1 The Cycle_end_t Shows Incorrect Value For Product
Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 184.108.40.206.0
This problem can occur on any platform.
After the migration from 7.2.1 to 7.3.1 few of the pricing list data are not loaded properly to the database which causes problem for the client tool (Pricing Center).
This Pricing data are migrated automatically during the data migration when we do the normal upgrade. As per the feature change from 7.2 to 7.3.1, the cycle/usage/purchase START_T & END_T will be converted and stored as cycle_usage/purchase START_DETAILS & END_DETAILS. But after migration to 7.3.1 from 7.2 few discrepancies were found as below:
For one of the deal the cycle_end was as
PIN_FLD_CYCLE_END_T TSTAMP  (31536000) 01/01/1971 01:00:00:000 AM
After the migration it is converted to
PIN_FLD_CYCLE_END_DETAILS INT  -2142109178
which seems to be correct as described in the conversion rule in migration script.
-- -- 31457221 to 62914500 ==> The range of prior releases value in seconds in fields
(PURCHASE/CYCLE/USAGE)_(START/END)_T which can be converted to the DETAILS as negative encoded value with UNIT as minutes
(i.e (value_range/60)*4096+516 > 2147483647 should be stored as -ve in 32bit)
But the problem here is that if we check the deal through pricing center, the cycle end is showing as 'NEVER' instead of the original date as '01/01/1971'.
This problem occurs not only for cycle_end_t but also for purchase/usage END_T where
PIN_FLD_USAGE_END_T TSTAMP  (31536000) 01/01/1971 01:00:00:000 AM
PIN_FLD_PURCHASE_END_T TSTAMP  (31536000) 01/01/1971 01:00:00:000 AM.
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