EEX 9.2: Travel Authorization Can Be Submitted In Fluid User Interface Even If It Contains ChartField Combination Editing Errors
Last updated on JUNE 11, 2018
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The Functional Team has detected that while ChartField Combination Editing has been implemented successfully in the Expenses system, Users are able to submit for approval Travel Authorization transaction in Fluid User interface, that contain lines flagged with Combination Editing Errors.
The exact same Travel Authorization transaction created in Online Classic, will not get submitted, as the Combo Error flags will prevent it from being routed through workflow. Expense Report transactions in Fluid UI cannot be submitted as long as a Combo Edit Error has been identified.
1.- At the Expenses Installation Options, select the Combo Edit flag
2.- Create a new ChartField Combination Edit Definition for Account as anchor, and Fund Code as required
3.- Create a new ChartField Combination Edit Rule for the Definition just raised for Account, and Fund Code (Note Tree ACCTROLLUP, with Node EXPENSES, which contains Account 650000)
4.- Create a new ChartField Combination Edit Group for the Rule and Definition for Account, and Fund Code
5.- At the Ledgers For A Unit level for Business Unit US001, on the Ledger Group RECORDING flagged for Journal Generator, define at the Journal Edit Options tab, the ChartField Combination Edit Group for all source transactions
6.- Launch the Combo Data Build process, for the GL Business Unit, and Ledger Group specified previously, so all possible valid combinations are generated
7.- At the Expenses Profile level, for Employee KU0042, define General Ledger Business Unit as US001
8.- At the Expense Type level, for ID SUPPLY, define the Account to be 650000
9.- At the Travel Authorization - Fluid UI mapping set up page, define Expense Type ID SUPPLY, and select the Active flag
10.- Log into the FSCM Online Application as User ID VP1
11.- Go to the Fluid Homepage, and then to Employee Self-Service in Fluid
12.- Click on the Travel Authorizations tile
13.- Proceed to create a new Travel Authorization transaction on behalf of Employee ID KU0042
14.- Notice the Expense Line for Expense Type SUPPLY, and how at the Accounting level, Account value defaults to 650000, and leave the Fund Code ChartField in blank
15.- Notice how the Expense Line is flagged with an Error
16.- Proceed to click on the SUBMIT button for this transaction
17.- The Travel Authorization gets successfully submitted, and routed through workflow, even though it has still a ChartField Combination Edit Error
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.
" Please enter or update the following information:
Combo error for fields ACCOUNT / FUND_CODE in group FUND_REQ. "
The errors on the ChartField Combination values used on the submitted Travel Authorization transactions generate problems through the approvals process, as well as issues when Budget Checking process allocates the encumbrances to incorrect Budgets, or gets errors.
Just like with Expense Report submission in Fluid User Interface, the system should prevent Travel Authorizations from being successfully submitted for approval in Fluid as long as they contain ChartField Combination Editing Errors in their respective Accounting Lines.
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