My Oracle Support Banner

EEX 9.2: Deleting an Expense Report that Has Already Been Budget Checked, the EX_BD_DEL in Step FS_BP_SHDR.uHStat1.uStatus Sets All Existing Expense Reports to Budget Header Status 'I' (Document In Process) (Doc ID 2663240.1)

Last updated on APRIL 24, 2020

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.2 and later
Information in this document applies to any platform.

Symptoms


Having enabled the Commitment Control functionality in the PeopleSoft Enterprise FSCM 9.2 Expenses module, an Expense Report has been created, submitted, and successfully budget checked, (hence present in PS_KK_ACTIVITY_LOG Record). At this stage, the Expense Report can be Sent Back For Revision, or Denied by the Approver User, or Withdrawn from approvals altogether  by the Employee. It is at this stage that the transaction qualifies for online deletion if needed.

If that takes place, and the budget checked Expense Report is deleted online, it is at that moment when the system triggers the Budget Check Request process again. The codeline however picked as eligible not only that single Expense Report being deleted, but all existing Expense Report transactions in the system, even those already paid and fully processed in the past. If the volume of transactions to process becomes too large, the Budget Check AE Program can end up crashing due to tablespace issues (As seen in Error Message listed below).

This abend leaves all of the Expense Report transactions in the system with a Budget Header Status of 'Document In Processing' (PS_EX_SHEET_HDR.BUDGET_HDR_STATUS = 'I').

If at this stage the delivered process is used to unlock them, that would set them back to a status of 'Not Budget Checked', (PS_EX_SHEET_HDR.BUDGET_HDR_STATUS = 'N'), which would mean all Expense Report transactions existing in the system (past and current) would have had to go through Budget Checking again, to get them to be Valid.

REPLICATION STEPS:

  1.- Log into the FSCM Online Application as an Expenses User
  2.- Create and submit for approval a brand new Expense Report
  3.- Launch Budget Checking against the Expense Report transaction submitted
  4.- Before it can get approved, manually withdraw the submitted Expense Report
  5.- Go to the Delete Expense Report page, select the transaction withdrawn, and delete it online
  6.- This triggers a Budget Check run from the back end
  7.- The Budget Check program abends due to tablespace issues

ERROR MESSAGE:

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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