Incorrect Credit Profile Assigned on Accounts Post-Upgrade

(Doc ID 880210.1)

Last updated on OCTOBER 03, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.1]
Information in this document applies to any platform.
Information in this document applies to any platform.
Checked for relevance on 05-Jun-2014
Checked for relevance on 03-Oct-2016.


After upgrading database from 6.2SP1 to 7.3.1, credit-limit errors were encountered during account creation:

E Mon Aug 10 13:25:00 2009 hostname cm:19459 fm_rate_event.c:2580 1:hostname:CustomerCenter:0:AWT-EventQueue-0:63:1249921493:0
     Credit limit exceeded
     <field num=opsflds:0,0 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
     <facility=0 msg_id=0 version=0>

The upgraded account data indicates the credit profiles assigned to upgraded accounts for custom resources look to be correct. However, when user creates a new account the custom resource does not appear to correctly identify the expected credit_profile value. It assigns one of the default credit profile values to the custom resource on creation and this had a limit which generated the credit limit error.

Updating the credit limit of the default 2 credit profile allowed user to create the account. However, this results in upgraded accounts having a different credit profile on the email resource than that of new created accounts which are defaulting to the paid quarter profile.

Question 1: The question is really how is the credit profile being identified for a resource on account creation?
Question 2: Are there any known issues if the default non-currency credit profile record (rec_id of 2) is set to a limit of null?


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