EAR 9.2: Error Message Field Does Not Exist – AR_DOC_SEQ_WRK.BUSINESS_UNIT_GL. (2,104) at Direct Debit Worksheet Customer Bank Details Page When Changing MICR ID Value
(Doc ID 2740439.1)
Last updated on DECEMBER 28, 2020
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
An Error Message is being triggered by the system at the Customer Bank Account Details Page (CUST_BANKINFO_SEC) from a Pending Direct Debit Worksheet transaction when changing the defaulted MICR ID value from the Customer Bill To Options configuration, with a different and yet valid MICR ID value.
1.- Log into the FSCM Online Application as a Receivables User
2.- Define two different MICR ID values with Bank Account Details for a particular Customer
3.- Set up the Bill To Options of the Customer for Direct Debit Payment Method, and select one of the MICR ID values previously defined
4.- Create a new Pending Item Group, with a transaction under the Customer ID in question, and set it to Post Action Batch Standard
5.- Launch AR Update for Pending Items option
6.- Confirm that the new Item has been successfully posted against the Customer Account, with a Payment Method of Direct Debit
7.- Launch the Direct Debit Creation process for the Direct Debit Profile ID being tested on
8.- Go to the Direct Debit Worksheet created, and click on the DD ID link to review its details
9.- At the Worksheet Detail page, click on the Pencil icon to edit the information
10.- Click on the 'Customer Bank Details' link
11.- Confirm that the MICR ID value is the one defaulted from the Customer's Bill To Options configuration
12.- Use the MICR ID look-up feature to search, and select the second MICR ID to change the Customer's Bank Account Details
13.- The system throws an Error Message
" Field does not exist -- AR_DOC_SEQ_WRK.BUSINESS_UNIT_GL. (2,104) AR_DOC_SEQ_SBR.DOC_TYPE.FieldChange Name:SetGLBU PCPC:137 Statement:3
Called from:DD_CONTROL_SBR.DOC_TYPE.RowInit Statement:2
A reference to a record.field name was made and the record.field name was not found to exist. Verify that the field exists on the page in which the PeopleCode program is being executed.
Review the program for errors. If necessary, run a PeopleCode trace to determine the program that failed. "
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
The Users are unable to correct the Bank Account Details MICR ID value that has been defaulted, and as such, the Direct Debit transactions cannot be remitted to the Bank without having corrected the needed information.
The system should allow the User to modify the MICR ID value without triggering any Error Message, so that the Customer Bank Account Details can be corrected if need be.
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