EGL: After Changing Entry Event On A Requisition Or Purchase Order Distribution And Budget Checking, When Reviewing The Entry Event Table (EE_REQ_ACCTG_LN or EE_PO_ACCTG_LN) We See An Extra Set Of Reversal Entries (Doc ID 1667810.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

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

Symptoms

CUSTOMER ENVIRONMENT
======================
Application Release 9

ISSUE
=====
Incorrect Entry Event entries after changing the Entry Event Code on Requisition or Purchase Order

1) Create a Requisition or Purchase Order using Entry Event Code PO_COMB on the distribution.
2) Run Budget Check and Entry Event
3) Review Entry Event table (EE_REQ_ACCTG_LN or EE_PO_ACCTG_LN)
4) Change Entry Event Code on the Requisition or Purchase Order distribution
5) Run Budget Check and Entry Event
6) Review Entry Event table (EE_REQ_ACCTG_LN or EE_PO_ACCTG_LN) and see that there is an extra set of reversal entries for PO_COMB


EXPECTED RESULTS
==================
Review Entry Event table (EE_REQ_ACCTG_LN or EE_PO_ACCTG_LN) should not show an extra set of reversal entries for PO_COMB

ACTUAL RESULTS
================
After changing entry event code on a requisition or purchase order distribution and budget checking when doing a review of Entry Event table (EE_REQ_ACCTG_LN or EE_PO_ACCTG_LN) we see that there is an extra set of reversal entries for PO_COMB

BUSINESS IMPACT
================
Incorrect EE accounting reversal entry

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