Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.0.0 to 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 26-Sep-2010***
***Checked for relevance on 12-Mar-2012***
***Checked for relevance on 26-Dec-2013***
***Checked for relevance on 09-Aug-2015***
Q1: What is the correct procedure to customize BRM policy code to allow for custom account number generation instead of using the POID as well as the ability to pass in ACCOUNT_NO in commit customer input flist?
Q2: A user is trying to create a new account with custom ACCOUNT_NO. In case the account is migrated from a legacy billing system, the ACCOUNT_NO is given, so this value should be used. In case of creating a brand new account, a custom sequence should be used as ACCOUNT_NO. The user wants to use PCM_OP_CUST_POL_PREP_ACCTINFO to set the custom sequence for ACCOUNT_NO in case of creating a brand new account.
However, this field is automatically set to certain value (value is not NULL). So, by checking if ACCOUNT_NO is NULL or not does not tell this ACCOUNT_NO should be kept or not. How to resolve this issue?
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