My Oracle Support Banner

EAP: After Applying PUM 39, the Period End Accrual Process Fails with a Unique Constraint - FS_PEACCRL Process Abends at AP_PEACCRL.BA100.STEP01 (SQL) -RC=805" (Doc ID 2819700.1)

Last updated on MAY 01, 2023

Applies to:

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

Symptoms

ISSUE:

After Applying PUM 39, the Period End Accrual Process Fails with a Unique Constraint - FS_PEACCRL Process Abends at AP_PEACCRL.BA100.STEP01 (SQL) -RC=805


PS_RECV_LN_DISTRIB table is joined additionally and the select as well as group by has extra fields which is generating the duplicate rows.
SQL is inserting rows into DIST_RECV_TMP which has some extra non key fields added in PUM 39.-


STEPS:

1. Create PO with quantity 4

Purchasing > Purchase Order > Add/Update Purchase Order
2. Approve PO - click on the Approve button
3. Budget check - click on the Budget Check Icon
4. Dispatch PO - Choose Dispatch from action box.
5. Create 2 Receipts - Purchasing > Receipts > Add/Update Receipts.
6. Purchasing> Receipts > Accrue Receipts > Run Accrual process for both Receipts.
7. Accounts Payable >Vouchers > Regular Voucher - Create Voucher by copying the PO
8. Accounts Payable > Batch Processes > Run Matching process
9. Accounts Payable > Batch Processes > Run Period End Accrual process


Changes

 This issue occurred after applying PUM 39. 

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.