EEX 9.2: Expense Report With Multiple Transaction Lines Gets Header And Line Statuses Out Of Sync When Using Fluid Approvals (Doc ID 2135832.1)

Last updated on NOVEMBER 01, 2017

Applies to:

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

Symptoms

ISSUE:

Having activated Expenses Fluid Approvals, it has been noticed that when an HR Supervisor approves a multi-line Expense Report, only the Expense Report Header Status (Record Field PS_EX_SHEET_HDR.SHEET_STATUS), and the very last Expense Report Line (Record Field PS_EX_SHEET_LINE.EX_LINE_STATUS) get updated to a status of 'PAR' (Approvals In Process), should additional levels of approval be needed. All the remaining Expense Report Lines, except the last one, get stuck into a value of 'SUB' (Submitted For Approval).

Expense Report Header, and Line Statuses become out of sync, and the transaction gets corrupted. This does not get resolved even if all remaining approval levels act on the submitted Expense Report transaction. This is only happening in Fluid Approvals, when the Expense Reports have multiple Lines to be handled.

REPLICATION STEPS:

     - Log into the FSCM Online Application as User ID VP1
     - Set up all the needed configuration to enable Fluid Approvals in the FSCM environment for testing
     - Navigate to: Set Up Financials/Supply Chain > Install > Installation Options > Expenses
     - Make sure to select the below options:
          - Workflow Enabled = Y
          - HR Manager – Supervisor = Y
          - Approval List Routing = Y
     - Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Management > Approval Setup > Transaction Definition
     - Open the configuration for Expense Reports, and make sure to activate the below approval levels:
          - HR Supervisor = Y
          - Pre Pay Auditor = Y
     - Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Management > Approval Setup > Approver Assignment
     - For Business Unit US001, and Approver Profile Pre Pay Auditor, ensure User IDs EXS1 and EXS2 are defined as the Pre Pay Auditor for the whole range of Department IDs
     - Log into the FSCM Online Application as User ID VP1
     - Navigate to: Employee Self-Service > Travel and Expense Center > Expense Report > Create/Modify
     - Define Employee ID KU0042, and click on ADD button
     - Create a new Expense Report, with at least 2 Lines
     - Submit the new Expense Report, and confirm that once refreshing the page, the workflow has routed the transaction to: HR Supervisor, and Pre Pay Auditor
     - Log into the FSCM Online Application as User ID MGR1
     - Navigate to: Fluid Homepage > Approvals
     - Find the submitted multiple-line Expense Report, and open it
     - After careful review, click on the APPROVE button
     - Click SUBMIT button to register the action taken
     - Query PS_EX_SHEET_HDR Record, and confirm that the Field SHEET_STATUS has been properly set to 'PAR' (Approvals In Process)
     - Query PS_EX_SHEET_LINE Record, and confirm that only the last ER Line has a Field value of EX_LINE_STATUS = 'PAR', while the remaining Lines have a value of 'SUB' (Submitted For Approval)

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.

ACTUAL RESULT:

As not all the Expense Report Lines get a correct PS_EX_SHEET_LINE.EX_LINE_STATUS = 'PAR' (Approvals In Process), but stuck in 'SUB' status (Submitted For Approval), the transaction cannot further get routed from HR Supervisor to the Pre Pay Auditor. As such, approvals of Expense Reports are being delayed, and so are their respective reimbursements. Bringing the Expense Report Header and Line status fields out of sync, cause the transaction to be corrupted. Even if Approvals get completed by all levels required, the Statuses do not get corrected, and the transaction is stuck unable to be processed further.

EXPECTED BEHAVIOR:

If the HR Supervisor Approver actually approves the submitted Expense Report transaction, all Lines, and Header level statuses should get into 'PAR' status, (or whatever proper value needed), and workflow should route the transaction to the next level of approvals: Pre Pay Auditor.

 

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