PSR Order Created via The API Does Not Populate CNAM / LIDB On Global Products (Doc ID 1487563.1)

Last updated on SEPTEMBER 05, 2012

Applies to:

Oracle Communications MetaSolv Solution - Version 6.0.15 and later
Information in this document applies to any platform.

Symptoms

When a PSR order is created via the API (i.e. importPSR, createOrderByValueRequest, etc) for Telephone Numbers assigned to a global product the CNAM and LIDB do not populate. Works fine for service location products via API and when done to global products through the MetaSolv (TBS.exe) GUI

Cause

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