EGL 9:Incorrect accounting is generated from Entry Events when there is a chart field change and amount change for expired funding. (Doc ID 1920165.1)

Last updated on AUGUST 13, 2015

Applies to:

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

Symptoms


ISSUE
---------------
Incorrect accounting is generated from Entry Events when there is a chart field change and amount change for expired funding. Entry Events is reversing and restating POPOST rather than creating a PODN entry when the Amount Change and the Chartfield Change are done in one step.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Scenario 1 produces the correct results on EE_PO_ACCTG_LN.
1. Enter a PO with FY13 funding -accounting and budget date are 9/1/2013 (current year funding).
2. Run budget check and entry events
3. Change a chartfield in FY14-accounting and budget dates are 5/9/2014 (expired funding)
4. Run budget check and entry events
5. Reduce the amount of the PO from $26 to $16- accounting and budget dates are 5/9/2014 (expired funding)
6. Run budget check and entry events

In this scenario, Entry Events first reverses and restates the POPOST entries for the chart field change, and then creates a PODN for the amount change.

Scenario 2 produces incorrect results on EE_PO_ACCTG_LN
1. Enter a PO with FY13 funding-accounting and budget date are 9/1/2013 (current year funding).
2. Run budget check and entry events
3. Change a chartfield and amount in FY14 -accounting and budget date are 5/9/2014 (expired funding)
4. Run budget check and entry events


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