EEX 9.1+: Mobile Applications Expense Location Search Feature Uses Logic On Location Code Instead Of Description
(Doc ID 1948146.1)
Last updated on APRIL 09, 2019
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.
With the fix delivered for <Bug 17016046> (EX: Expense Location Field on Mobile Expenses Application Should Have Search Field Logic), contained within FSCM 9.1 ESA Bundle #27, search logic functionality in Mobile Expenses was configured for the Expense Location field, instead of using the drop down list. This was due to the fact that there can be thousands upon thousands of potential valid values on Locations worldwide, and a drop down list is not efficient. However, this search logic was built around the Expense Location Code field (TXN_LOCATION) which enables only 5 character long combinations, instead of the Expense Location Description field (DESCR). This limits the potential logic Location Code convention, and sometimes a Location Code may have no resemblance whatsoever with the Location Description.
It is impossible to expect Expenses Employees to remember by heart all the Expense Location Code values possible when trying to add new Expense Lines via the Mobile Applications.
In the PIA FSCM Online Application mode for Expense Report Entry, unlike the Mobile Applications Version, the Location on Expense Report Header and Lines base their partial data fill search logic feature on the Expense Location Description, (DESCR Feld, with 30 character length). There is an out of sync problem on data entry functionality between Mobile Applications and PIA. This should be corrected.
- Log into the FSCM Online Application as User ID VP1
- Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Location > Expenses Location
- Add a new value with the below settings:
- Set ID = SHARE
- Expense Location = ABCDE
- Effective Date = 01/01/1900
- Status = Active
- Description = GCS Location
- Short Description = GCS Loc
- Location Group = NEREG
- Country = USA
- State = NY
- Navigate to: Employee Self-Service > Travel and Expense Center > Expense Report > Create
- Define Employee ID KU0042, and click on ADD Button
- At the Expense Report Header level, in the Default Location field, enter the value of GCS, and see how the system displays 'GCS Location' with Search logic
- At the Expense Report Line level, in the Expense Location field, enter the value of GCS, and see how the system displays 'GCS Location' with Search logic
- Navigate to: Employee Self-Service > Mobile Applications
- Click on the Expenses icon
- Click on the 'Create Expense Report' icon
- Enter the below listed values:
- Description = EX Mobile GCS Test Location
- Business Purpose = Consulting Services
- Click on SAVE Button
- Continue in adding the below values:
- Expense Type = Groceries
- Date = 08/08/2014
- Payment Type = Cash
- Expense Billing Code = Internal
- Transaction Amount = 100.00
- Currency = USD
- Description = GCS Test.
- At the Expense Location field, enter the value of GCS, and see how the system states that 'No matching values were found'
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.
With thousands upon thousands of valid Expense Location values, the Expense Location Code field (TXN_LOCATION) is only enabling 5 character long combinations. This means that at some point in time, the potential combinations of defining a Location run out, and other values need to be found. Due to this, Expenses Employees are unable to know all potential combinations of Location Code by heart, and are unable to find the Expense Location they need. This is not user friendly.
The Expense Location Description field (DESCR) has instead 30 character length, and can be used as the field search logic is built around to find Expense Location values. This is what the FSCM Online Application is already using when creating Expense Reports via PIA functionality. The Mobile Applications should also use the same logic.
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