Error Accessing Item Charges in Customer Center (Doc ID 1350204.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.4.0.0.0 and later   [Release: 7.4.0 and later ]
Information in this document applies to any platform.

Symptoms

Error message is displayed when clicking on an item charge in Customer Center.

Steps to reproduce:
1.  Open one account which has "Bill in progress (estimate)" amount on Balance tab.
2.  Drill down the "Bill in progress (estimate)" link to item level.
3.  An error "For input string: 3agePayment.index..." pops up.

The Service name showed as <N/A>. The item is created from account level product.

The issue only happens on one environment. It doesn't matter the account is newly created or migrated. They all have the same issue.

All Customer Centers connect to this environment have this problem. But, using the same Customer Center to access other machines, it works fine.

Later the user found a workaround and it works. The workaround is to update admin_client_user_prefs_buf table USER_PREFS_BUF BLOB with the content copied from another instance.

The following is what the user did before he/she reaches the working workaround.

1. The following error was logged with customized Customer Center using extended fields at the moment when the user pressed SEARCH or F4 :
Error 04/08/11 10:41:26:0637 AM ( 1302280886637 ) T:AWT-EventQueue-0
JavaLog PSearchAction
1:curso51:CustomerCenter:0:AWT-EventQueue-0:7:1302280713:0
PSearchAction -> actionPerformed() -> Error
Error 04/08/11 10:41:26:0637 AM ( 1302280886637 ) T:AWT-EventQueue-0
JavaLog PSearchAction
1:curso51:CustomerCenter:0:AWT-EventQueue-0:7:1302280713:0
moveColumn() - Index out of range
2. As a workaround, he/she performed an update of a binary field USER_PREFS_BUF (BLOB) over the table admin_client_user_prefs_buf.

3. Internally, this BLOB record is updated with the following data:
\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000..
4. Once the insertion is performed at the time when the user executed queries over bills items, the following exception was generated:
For input string: 3agePayment.index....
5. As a workaround, the user loaded another BLOB record from another environment and the issue is solved temporarily.

The questions :
How should the field (USER_PREFS_BUF) be populated?
What is the correct data that should be there?


Cause

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