My Oracle Support Banner

EGL9.2: Upward/Downward Adjustments To Prior Year Adjustment Chartfields - Unexpried Checked or Unchecked - in Commitment Control (Doc ID 2724576.1)

Last updated on OCTOBER 30, 2020

Applies to:

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


While testing upward/downward adjustments to prior year adjustment chartfields in Commitment Control - using Fund Code as the prior year chartfield for these adjustments - we noticed the need to have to always do an override of a budget exception when dealing with Expired funds (not so with Unexpired funds).

In the Budget Definition under the tab “Prior Year Adj Chartfield” there is an “Unexpired” flag on each row. When this Unexpired flag is checked (meaning the fund code is NOT expired) and we process a transaction using that fund code in the appropriate period, no budget exception is encountered so nothing to override. However, when this Unexpired flag is not checked (meaning the fund code IS expired), when we process a transaction using that fund code, the budget check always goes to error stating that the funding has expired and (always) requires us to do an override of this budget exception.

Is there a way to bypass having to do this override of an expired funding budget exception, via a configuration of some kind?


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.