My Oracle Support Banner

EAR 9.2: When a User Tries To Open a Direct Journal Payment Deposit, “No Matching Buffer Found for Level” Error Occurs. (Doc ID 2791561.1)

Last updated on NOVEMBER 09, 2022

Applies to:

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


Issue 1: When a user tries to open a direct journal payment deposit,  "No matching buffer found for level" error occurs.

No matching buffer found for level. (15,26)

Replication Steps:
1. Create an online deposit ( Receivable - Payments - Online Deposit) with two payments as a direct journal.
2. Save the deposit.
3. Query PAYMENT_ID_ITEM for this deposit id, it has two rows.
4: Delete the second payment adjust the total count and deposit sum. Save.
5: Goto some other page and come back to find the same deposit id under online payments then click on the deposit id, the error will pop up.
6: Query again PAYMENT_ID_ITEM, it still has two rows.

The issue is PAYMENT_ID_ITEM table should not be populated for direct journal payment.

Issue 2: The same error occurs when a payment within a deposit is changed from payment of an Item to Direct Journal payment without removing the Item Reference on the payment.
A row is left in the PAYMENT_ID_ITEM table for that payment sequence.
If a user deselects the Direct journal box again and adds an Item Reference for the payment sequence, on Save, a second row is inserted for that same payment sequence in PAYMENT_ID_ITEM.
If the payment sequence is then deleted, only one of the rows for the payment in PAYMENT_ID_ITEM is deleted, leaving an orphaned row that causes a No matching buffer error for the deposit.



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

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