My Oracle Support Banner

EEX 9.2: Transaction Line Amount Not Populated When Mileage Transaction Exported Directly From My Wallet Into Fluid Expense Report, if Transportation Type Feature Is Not Used (Doc ID 3063041.1)

Last updated on DECEMBER 10, 2024

Applies to:

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

Symptoms

A problem has been detected in Fluid User Interface functionality, where the system is no longer automatically calculating the Expense Amount of a Mileage related Expense Type transaction if exported from My Wallet (from Add Quick Expense feature), into an Expense Report. Instead, the Amount field remains 0.00, with the Transaction Line being flagged in Error.

This was working fine, but stopped after a systems' upgrade. Seems that this is taking place if the Transportation Type check-box is not selected at the Expense Type Code set up level.

At the same time, if the Transaction Line is manually created in Fluid Expense Report component, or imported directly from My Wallet if the Employee already is in the Fluid Expense Report component, the Amount field is correctly calculated, and no Error Message is being triggered.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a System Administrator User ID VP1.
    2.- Navigate to: Set Up Financials/Supply Chain > Install > Installation Options > Overall
    3.- Make sure to select the 'Use Oracle Maps Services' check-box.
    4.- Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Purchase > Create Expense Type Codes
    5.- Open the existing Expense Type MILEAGE, and make sure to configure the below settings:
           a) Transportation Type = N
           b) Expense Type Edit = Automobile
    6.- Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Management > Distance Rate
    7.- Define a new Distance Rate as below:
           - Set ID = SHARE
           - Expense Type = MILEAGE
           - Country = USA
           - Distance Type = Miles
           - Distance Rate Type = Standard
           - Standard Distance Rate = 0.6700
           - Currency Code = USD
    8.- Navigate to: Travel and Expenses > Manage Employee Information > Update Employee Detail
    9.- Open existing Employee ID KU0021.
    10.- Go to the Organizational Data tab.
    11.- Ensure the GL Unit is pointing to US001, (Business Unit in USA).
    12.- Go to the User Defaults tab, and define the Business Purpose, and Report Description fields.
    13.- Save the changes.
    14.- Navigate to: Travel and Expenses > Manage Expenses Security > Authorize Expense Users
    15.- Authorize User ID EXA1 to edit and submit expense transactions on behalf of Employee ID KU0021
    16.- Log into the FSCM Online Application as Expenses User ID EXA1
    17.- Go to the Employee Self Service Fluid Homepage.
    18.- Click on the Expenses Tile.
    19.- Click on the Add Quick Expense Tile.
    20.- Create a new Expense Transaction with Expense Type MILEAGE, and defining a Starting Point, and Ending Point for the trip.
    21.- Click on the 'Calculate GPS Distance' button.
    22.- Confirm that the Miles Calculated and Miles fields are automatically populated.
    23.- Save the transaction.
    24.- Click on the MORE button.
    25.- Select the mileage transaction, and click on the REPORT button.
    26.- PROBLEM: The Fluid Expense Entry page is loaded, with the mileage Transaction Line defaulted, but also flagged in Error due to the Expense Amount field being 0.00.

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

ERROR MESSAGE:

    " Correct the following errors prior to submission:

         - Amount Spent cannot be 0.

         - Accounting Detail -- The sum of distribution amounts must equal the Expense Amount. Accounting Ln 1. "


Employees are forced to edit the imported Wallet Transaction, and re-save, in order for the validation formulas to kick in, populate the Amount field, and resolve the Error Message. This is unnecessary steps to be taken by Users, when before the upgrade all was working fine, while at the same time, the miles edited may no longer be entirely accurate.

When a My Wallet mileage related transaction is exported into the Fluid Expense Report component, the system should calculate the Expense Amount field by multiplying the Miles entered, by the Distance Rate.

NOTE: In the images/screenshots/examples mentioned and/or 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.