EGL: PO Entry Events - Double Liquidation Occurs After Running Entry Event Then Changing The Chartfield String And Running The Entry Event Process A Second Time

(Doc ID 1681970.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.1 and later
PeopleSoft Enterprise SCM Purchasing - Version 9.1 and later
Information in this document applies to any platform.


On : 9.1 version, Commitment Control
MP11 bundle 23

When a user creates a PO with a given chartfield string and then budget checks and runs the PO through Event Generation, and then subsequently changes that chartfield string again, a double liquidation occurs against the original chartfield string once Event Generation runs again.

If User runs same transaction through entry event after making a change, the liquidation should not be doubled.

The issue can be reproduced at will with the following steps:
1. Create Purchase Order(PO) with a given chartfield string
2. Approve Budget Check PO
3. Run Entry Event for the PO
4. Change DEPTID
5. Approve Budget Check PO
6. Run Entry Event for the PO


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