My Oracle Support Banner

EAR 9.2: Error "No matching buffer found for level. (15,26)" Occurred in Regular Deposit When Selecting Journal Directly W/O Removing Item Reference (Doc ID 2937779.1)

Last updated on APRIL 13, 2023

Applies to:

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

Symptoms

When a payment within a deposit is changed from payment of an Item to Journal Directly 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 Journal Directly 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.

 


Step:
1. Verify selecting below in Installation Options:
    Products > Commitment Control enabled for Receivables
    Receivables > Track Direct Journal Customer
2. Create a deposit with 2 payment sequences; Seq 1 select an Item, Seq 2 select journal directly and Save.
    Navigation: Accounts Receivable > Payments > Online Payments > Regular Deposit
3. Checking tables (PS_PAYMENT, PS_PAYMENT_ID_CUST and PS_PAYMENT_ID_ITEM)
    2 records are created in PS_PAYMENT and PS_PAYMENT_ID_CUST. 1 record is created in PS_PAYMENT_ID_ITEM
4. For Sequence 1, without removing the Item Reference, select Journal Directly and save.
5. Checking tables again. Row is still in PAYMENT_ID_ITEM for sequence 1, even though the payment sequence is now Journal Directly.
6. For Sequence 1, deselect Journal Directly, note that Item Reference is automatically removed from the Reference Information grid and the field is open again. Select an Item and save.
7. Checking tables again. There are now 2 rows in PAYMENT_ID_ITEM for Sequence 1
8. Without making any changes to Sequence 1, delete Sequence 1 and save.
9. Checking tables again.Sequence 1 still has a row in PAYMENT_ID_ITEM.
10. Try to reopen a deposit.
11. No matching buffer error message is received.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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