Problem Supping CAs Via API
(Doc ID 1961143.1)
Last updated on MARCH 08, 2019
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
When creating a 'PSR' via the importNGN corba 'API' or 'GUI' and later supplement correct (SuppTypeEnum.stcorrect) the 'PSR' via the 'API' the new dependent custom attribute (CA) values are not populating. The existing CA
value is updated on the SRSI_CA_VAL table but the dependent ones added in the API structure are not added. If you open the 'PSR' in the 'GUI', the new CA value that was updated is not displayed in the order even though the
SRSI_CA_VAL table is updated.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document