Last updated on JULY 24, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
This problem can occur on any platform.
On Oracle Communications Billing and Revenue Management(BRM), 126.96.36.199.0 version, unable to perform any operation on /order/sim after upgrading from 6.5 To 7.3.
Steps To Reproduce:
The POID range for order_t related fields created in dd_objects_fields_t table is incorrect. For any fields under a base class [/order class in our case], the rec_ids for all the fields under it should be greater than the main field.
For example , /order class had the following definition [output of dd_objects_fields_t for obj_id0 of /order name in dd_objects_t]
It can be seen in the above, that the rec_ids are decreasing i.e PIN_FLD_NAMEINFO has rec_id of 101623 and PIN_FLD_RESULTS_DATA has a rec_id of 2139 which is less than 101623.dm_oracle does a validation for this and it fails.
BRM had POID range of 100000 and above for order related data in 65. However in 7.3.1 this range has been reserved for custom POIDs. The rec_ids 2139, 2140 were added as part of the upgrade which
introduces these fields under order.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms