Pin_cmt Does Not Recognize Some OOB Fields
Last updated on FEBRUARY 01, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
Checked for relevance on 1-Feb-2017.
The user was trying with CMT to migrate information at account level and service level in the following OOB fields:
But there was no specification in the xsd file. It did not work even if included some information in the physical xsd, because the main problem was that pin_cmt.jar did not understand those fields.
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