EAR 9.1+: Error Message (2,156) At Payment History Page When Selected Customer Has Multiple Rows In Alternate Customer Information (Doc ID 2280039.1)

Last updated on JUNE 23, 2017

Applies to:

PeopleSoft Enterprise FIN Receivables - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

ISSUE:

The Functional Team has detected an Error Message being triggered at the Payment History page (CUSTOMER_PROFILEB) when searching for existing Customer's information, when for that customer multiple Alternate Customer Information rows have been defined at the Additional General Information page (CUST_GENERAL2).

At least one of those rows has to be defined as Dun & Bradstreet type (DUNS Number).

REPLICATION STEPS:

     1.- Log into the FSCM Online Application as a Receivables User
     2.- Navigate to: Customers > Customer Information > Dun & Bradstreet
     3.- Add a new DUNS Number under Set ID SHARE, and fill in all required information in the Operations tab
     4.- Navigate to: Customers > Customer Information > General Information
     5.- Open existing Customer ID 1001
     6.- At the General Info tab, click on the drop down list the option of: 0020 - Additional General Info
     7.- At the Alternate Customer Information section, add multiple rows, with different Standard ID Qualifier values. One of the rows though should be for DUNS Number and define the Dun & Bradstreet value previously created
     8.- Once saved, query Record PS_CUST_ID_NBRS, and confirm that for that Customer ID 1001, there are at least 2 or more rows
     9.- Navigate to: Accounts Receivable > Customer Accounts > Customer Information > Payment History
     10.- Define a SetID SHARE, Business Unit US001, and Customer ID 1001
     11.- Click on the SEARCH button
     12.- The system throws an Error Message

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

ERROR MESSAGE:

     " UpdateValue: Row 2 not found in scroll level 0. (2,156) SUBCUST_PRF_WRK.CUST_PROFILE_FCN.FieldFormula Name:select_cust_id_nbrs PCPC:26023 Statement:428
       Called from: SUBCUST_PRF_WRK.CUST_PROFILEB_FCN.FieldChange Name:profileb_go Statement:231
       Called from: SUBCUST_PRF_WRK.CUST_PROFILEB_FCN.FieldChange Statement:238
       The specific row number is invalid for the indicated scroll level. This may occur with various PeopleCode built-in functions that specify a row within a scroll.
       Review the PeopleCode that is generating the message and the page definition and correct as appropriate. "

ACTUAL RESULT:

Users are unable to review the Payment History of existing customers with multiple Alternate Customer Information values, the functionality is rendered useless.

EXPECTED BEHAVIOR:

The system should be able to provide the Payment History results of the selected Customer.

 

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