EGL: Fix from Bug 11557549 Changes How Commitment Control Option 'Value Required' Works When Budget Checking. (Doc ID 873262.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

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

Symptoms

ISSUE
=======
After applying Maintenance 9.0 for release 9.0, the 'Required Value' checkbox on the Key and Translation page in the Budget Definition does not work.  If Value Required option is checked for one Budget Definition but not another, all budget check transaction that do not have that required field populated will fail with budget check exception 'Required Key CF is blank'.

BUSINESS IMPACT
==============
Due to the change in the way the "Value Required" checkbox work, all budget checked transactions are subject are required to have every field marked "Value Required" on the budget definition keys. This means all transactions in the GL BU are being required to meet conditions of budget definitions that do not apply to them.

EXPECTED BEHAVIOR
===============
Without Bundle 19/MP 9 applied,  within a commitment control budget definition and if the budget definition is set to control, any fields marked as "Value Required" on the keys and translations page.  It will be required on every transaction within that ruleset.  Therefore, Project_ID marked "value required" on parent KK Budget Definition, every transaction selected for that ruleset will require a Project ID when only that ruleset within that budget definition is required to have ProjectID.

ACTUAL BEHAVIOR
==============
With Bundle 19/MP 9 applied :  For any commitment control budget definition,  if the budget definition is set to Control ( this also occurs at other control levels) - all fields marked as "Value Required" on the keys and translations page will be required on every transaction within that GL Business Unit.  For example, if Project_ID is marked "Value Required" on the Grants parent KK Budget Definition, every transaction will require a Project ID, even if it's just a departmental transfer and not using a project.  If Project ID is blank on a transaction, a budget check failure results, saying a key chartfield is blank. The solution is to uncheck "Value Required" for Project ID and PC Business Unit. This results in a new problem, because unchecking "value required" means that one can enter transactions with a sponsored fund and blank PCBU/Project ID. This will pass budget checking, bypassing the ledger groups where Project_ID is a key with "Value Required" turned off, allowing one to spend restricted funds willingly.

SPECIFIC ERROR MESSAGE
===========================
Budget exception occurs if "Value Required" check box is checked, " Required Key CF is blank".


STEPS (Sequence of Events)
===================
By following these steps the issue can be reproduced:
1. Setup multiple budget definition to a particular business unit.
2. In the Keys and Translation one of the Budget Definition set all the chartfields to 'Value Required'.
3.In the other Budget Definition, have a chartfield in the key and transaction set to use a chartfield value that is not part of the first budget definition. For, example Project_id.
4. Create a transaction that will budget check against the budget, such as General Ledger Actuals Journal. Leave the Project chartfield blank.
5.Budget check the transaction to receive Budget Exception "Required Key CF is blank"

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