EEX 9.2: Expense Report Budget Header Status Is Incorrectly Set to Valid While Saving the Transaction, Bypassing Commitment Control Budget Checking (Doc ID 3076854.1)

Last updated on MARCH 14, 2025

Applies to:

Symptoms

A problem has been detected at the time of creating, and saving, an Expense Report transaction in Fluid User Interface. If Commitment Control functionality is being actively used on the Business Unit the Expense Report is being created/updated, the system will be properly setting the Budget Header and Line Statuses as 'N' (Not Budget Checked). However, if the Employee navigates from the Expense Line Entry page to the Expense Report Header page, then back to the Expense Line Entry page, and a change is done at the Transaction Line fields level, upon saving, the system maintains the Budget Line Status as 'N', but automatically changes the Budget Header Status to 'V' (Valid).

This effectively will ensure the Expense Report transaction is bypassing Budget Checking further down the line.

REPLICATION STEPS:

     1.- Log into the FSCM 9.2 Online Application as a System Administrator.
     2.- Navigate to: Set Up Financials/Supply Chain > Install > Installation Options > Products
     3.- Ensure that Commitment Control is enabled for both Expenses and General Ledger modules.
     4.- Navigate to: Set Up Financials/Supply Chain > Business Unit Related > General Ledger > Ledger For A Unit
     5.- Open the GL Business Unit at hand, find the Ledger Group set as default for Journal Generator, go to the Commitment Control tab, and define the Commitment Control Ledger Group.
     6.- Log into the FSCM 9.2 Online Application as an Expenses User.
     7.- Go to the Employee Self Service Fluid Homepage.
     8.- Click on the Expenses tile.
     9.- Click on the Create Expense Report tile.
     10.- Define the various Expense Report Header field details.
     11.- Select the option of 'Add Expense Lines' from the Expense Report Action drop-down list.
     12.- At the Expense Report Line level, define the Expense Date, Expense Type, Description, Amount, Billing Type, Payment Method, and alike values.
     13.- Save the changes performed so far.
     14.- Query Record PS_EX_SHEET_HDR for the Expense Report at hand, and confirm Field BUDGET_HDR_STATUS is set to 'N' (Not Budget Checked).
     15.- On the Expense Entry page, click on the pencil icon to go back to the Expense Report Header page.
     16.- At the Expense Report Header page, click on the Update Details button.
     17.- Once again at the Expense Entry page, edit the Description field to a new value.
     18.- Save the changes.
     19.- PROBLEM: Query Record PS_EX_SHEET_HDR for the Expense Report at hand, and confirm Field BUDGET_HDR_STATUS has been now set to 'V' (Valid).

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the problem.

This problem is causing that while the company has set as required any Budget Checking prior to approvals, the affected Expense Reports are being set automatically as Valid, allowing the transactions to be approved, staged, paid, and posted without ever having to go through a Budget Check Request, bypassing the Budget Amount for the period, and missing all Commitment Control tables.

While the Employees are creating/updating the Expense Report, the Budget Header Status, (Record Field PS_EX_SHEET_HDR.BUDGET_HDR_STATUS), should always be kept in 'N' (Not Budget Check), as long as Commitment Control is required at the Business Unit level, so that Budget Checking Request will be required before the transaction can be approved, reflecting the amount in the Budget for the period at hand.

Cause

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