My Oracle Support Banner

Incorrect Credit Profile Assigned to Accounts Post-Upgrade (Doc ID 880210.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.0]
Information in this document applies to any platform.

Goal

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


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 profiles 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.

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

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.