SBILLNM versus SECONDARY_NAME validation in MetaSolv Solution ASR
Last updated on JULY 25, 2017
Applies to:Oracle Communications MetaSolv Solution Module - ASR - Version 41.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 25-Jul-2017***
Enter ASR import and send in a valid mixed case (SECONDARY_NAME exists on the PARTY_ROLE_ADDRESS in mixed case) SBILLNM and the ASR is created but when you view the ASR order in the GUI the SBILLNM is blank.
Enter ASR import and send in a valid all uppercase (SECONDARY_NAME exists on the PARTY_ROLE_ADDRESS) SBILLNM and if the data exists in mixed case, receive the following error:
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