Why Is the ASR NO or ASR_NUMBER on the ACCESS_SERVICE_REQUEST Table No Longer Auto-Populated with the DOCUMENT_NUMBER? (Doc ID 2180513.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

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

Symptoms

As part of ASR 53 GA release (build 23), the auto population of the ASR NO field on the ADMIN form was stopped as it created a deadlock situation against the new OBF rule that states that the ASR NO field is prohibited on initial requests. However, users would still like the application to auto populate the ASR NO field for orders received from the customers as that is the only means to search for an ASR order.

Changes

 

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