Entry Events Incorrect POCLOSE And Unbalanced Lines (Doc ID 1964981.1)

Last updated on JANUARY 13, 2017

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9 to 9 [Release 9]
PeopleSoft Enterprise SCM Purchasing - Version 9 to 9 [Release 9]
Information in this document applies to any platform.

Symptoms

Entry Events Incorrect POCLOSE and unbalanced lines when voucher exists against PO line but has not been budget checked and then new PO line is added.

1.  Enter a PO for $10 with current year funding (FY14), accounting date 9/1, budget check, entry event and dispatch.  This creates the POPOST entry event.
2.  Enter a Voucher based on the PO and click the finalized checkbox, save, but do not budget check -- simulating a match error.
3.  Enter a second line on the PO from step 1 for $20, accounting date 10/1 with current year funding (FY15), budget check and entry event.  For line 1, entry events creates a POCLOSE.  For line 2, entry events creates a POPOST.
4.  Change the accounting date to 10/2 on the PO, budget check and entry event.  For line 1, entry events creates a reversal and restatement of the POCLOSE, but the lines are not balanced which eventually causes a posting error.  For line 2, entry events correctly reverses and restates the POPOST.


Cause

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