My Oracle Support Banner

EEX: Error Message In Fluid Approvals When Denying A Valid Budget Checked Expense Report Copied From A Travel Authorization (Doc ID 2618960.1)

Last updated on SEPTEMBER 21, 2021

Applies to:

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

Symptoms


The Expenses Approver Users have detected the system to throw an Error Message when an already budget checked Expense Report, created from a Travel Authorization, gets denied using Fluid Approvals.

REPLICATION STEPS:

    1.- Enable Commitment Control in the Expenses module
    2.- At the Expenses Options level, ensure to flag the options to require Budget Check on submitted Travel Authorizations and Expense Reports prior to their approval
    3.- Create a new Travel Authorization, and submit it for approval
    4.- Budget Check the Travel Authorization
    5.- Approve the Travel Authorization
    6.- Through Fluid User interface, select the approved Travel Authorization, and choose the related action of 'Copy To Expense Report'
    7.- Complete any further missing data from the Fluid Expense Report, and submit it for approval
    8.- Launch Budget Check Request in Expenses module for the Expense Report through the batch process
    9.- Access the Fluid Approvals functionality, open the Expense Report, and deny it
    10.- The system throws an Error Message

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.

ERROR MESSAGE:

    " Invalid application package:method registered for this action.  App Package:method EX_APPROVAL_FL:Expenses:actionControlApp:submitAction.
      Contact your system administrator. "


The Expenses Approver Users receive such Error Message when completing the Fluid Approvals denial, and such message is confusing to the User, as it states that they should contact their System Administrator. The system should not trigger such Error Message.

NOTE: In the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

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.