Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.1 [Release 7.3.1]
Information in this document applies to any platform.
Checked for relevance on Oct 22 2010.
Checked for relevance on 03-Apr-2012.
***Checked for relevance on 24-Sep-2013***
A user could migrate non-custom and custom objects using pin_cmt -import and pin_cmt -import_custom. But, when deploying them (using pin_cmt -deploy), the only way CMT can perform this is when .ctl entries in Infranet.properties that are not at the top of the hierarchy of custom classes are removed.
For example, if the user defines an /agreement class with a nested substruct called instalments and assigns the table agreement_instalments_t to this substruct, the user would add agreement_t.ctl and agreement_instalments_t.ctl to Infranet.properties in order to migrate these custom entities.
That works fine, but in order to deploy migrated objects, the user must remove agreement_instalments_t.ctl from Infranet.properties.
Is this a bug? Or the user must change Infranet.properties by deleting .ctl entries to include only non-custom/non-extended .ctl files for deploying?
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