Incorrect Credit Profile Assigned to Accounts Post-Upgrade
(Doc ID 880210.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.3.0]
Information in this document applies to any platform.
After upgrading from 6.2SP1 to 7.3.1, credit-limit errors were encountered during account creation:
Credit limit exceeded
<location=PIN_ERRLOC_FM:5 class=PIN_ERRCLASS_SYSTEM_DETERMINATE:1 errno=PIN_ERR_CREDIT_LIMIT_EXCEEDED:81>
<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 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?
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