EEX 9.1+: Expense Report Send Back For Revision Status/Comments Not Displayed, And Action History Is Misplaced If Original Comments Get Overridden (Doc ID 2104132.1)

Last updated on FEBRUARY 05, 2016

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

ISSUE:

Having applied the solution from original <Bug 21117026> (EX: Send Back For Revision Pre Pay Auditor Comments At Expense Report Level Not Displayed If Action User Differs From Comments User), a sub-scenario has been identified still as faulty. This would be when the Expense Report gets re-submitted once again for approvals, and the new Pre Pay Auditor deletes the original Comments, and adds new ones, just before Send Back For Revision is performed again. In such case, the transactions gets reset by Workflow again to Pending status, and the below problems are faced:

     - Issue #1: Send Back For Revision status is not displayed
     - Issue #2: Send Back For Revision Comments are nowhere to be displayed
     - Issue #3: Send Back For Revision action, while contains proper Date and Time, it is misplaced within Action History section in improper order

As such, the original problem is not completely resolved when the above mentioned scenario is met.

REPLICATION STEPS:

     - Activate Expense Report approvals for HR Supervisor, and Pre Pay Auditor
     - At the Approver Assignment set up page, define a pool of Users that will be acting as Pre Pay Auditors (such as User IDs EXS2, and EXS3)
     - Log into the FSCM Online Application as an Expenses User, such as User ID EXA1
     - Create, and submit, and brand new Expense Report transaction
     - Confirm that the Expense Report has been routed to the HR Supervisor, and have it approved at that level
     - Log into the FSCM Online Application as User ID EXS2 (one of the Pre Pay Auditors), open the routed Expense Report, add some value in the Comments section, and Save the Changes
     - Log into the FSCM Online Application as User ID EXS3 (the other Pre Pay Auditor), open the affected Expense Report, confirm that the comments entered by the previous User are present, and click on Send Back For Revision
     - Proceed to log into the FSCM Online Application as the Expenses User owner of the affected Expense Report
     - Navigate via the online application, and open the Expense Report whether in View or Modify mode
     - Confirm that the Expense Report status is Pending, and that the Send Back For Revision status, and its related comments are properly displayed as they should
     - Have the User re-submit for approval the Expense Report
     - Confirm that the Expense Report has been routed to the HR Supervisor, and have it approved at that level
     - Log into the FSCM Online Application as User ID EXS2 (one of the Pre Pay Auditors), open the routed Expense Report, delete the existing Comments, add new ones, and Send Back For Revision the transaction
     - Proceed to log into the FSCM Online Application as the Expenses User owner of the affected Expense Report
     - Navigate via the online application, and open the Expense Report whether in View or Modify mode
     - Confirm that the Expense Report is not displaying the header of Sent Back For Revision, and that its related comments are not displayed as they should

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

BUSINESS IMPACT:

There is no way for the Expense Report owner to see why the transaction is in Pending status, as the Send Back For Revision action is not being reflected at the top of the screen as it should be, nor the comments justifying the action. As such, the Employee is confused as to what is the reason why the transaction has not passed the approvals required, and what may need to be changed/updated/modified, before re-submitting the transaction once again. This can potentially delay the approvals process, and subsequently, the reimbursement payments. On top of that, the latest Send Back For Revision action taken by the original Pre Pay Auditor is being misplaced in the Approval Action history section, even though the Date and Time values are correct.

EXPECTED BEHAVIOR:

Regardless of who has entered or even later deleted and updated the Comments section at the time of Approvals, these need to always be properly displayed and be viewable for the Employee. If the User that has entered the Comments is also the person who took the Approval action of Send Back For Revision, the data gets properly displayed online. This should also be the case in the eventual scenario that the User adding the Comments does not correspond with the User taking the approval action (Approve, Deny, Send Back For Revision, etc...).

 

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