My Oracle Support Banner

EEX 9.2: Currency Code Field Gets Displayed at Fluid My Wallet Entry Page Even After Hiding It Through Page and Field Configurator (Doc ID 2793659.1)

Last updated on JULY 22, 2021

Applies to:

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

Symptoms

It has been detected that the Hide settings defined at the Page and Field Configurator level for Component EX_MY_WALLET_FL, on Currency Code Field from the Fluid Wallet Entry page (EX_TRANS_LN_FL), are only working when first loading the page online. However, when the User defines/enters a value into the Expense Type field, the system refreshes the page, and then displays once again the Currency Code field look-up.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a System Administrator
    2.- Navigate to: Enterprise Components > Page and Field Configuration > Page and Field Configurator
    3.- Add a new value for Component Name EX_MY_WALLET_FL, under Market Global, and Configuration Type Standard
    4.- On the Page Configuration tab, define Sequence Number 1, and click on the SELECT FIELDS button
    5.- From the Primary Page drop down, select the value '04 - Wallet Entry' and click on SEARCH button
    6.- From the list of Fields displayed, select the following ones:
              a) Currency (Record EX_TRANS, Field CURRENCY_CD)
              b) Transaction Currency (Record EX_TRANS, Field TXN_CURRENCY_CD)
              c) Currency (Record EX_TRANS_BD_VW, Field CURRENCY_CD)
              d) Transaction Currency (Record EX_TRANS_BD_VW, Field TXN_CURRENCY_CD)
    7.- Click on the OK button
    8.- In the 4 new rows that have been added into the 'Configure Field Properties' section, select the check-box for 'Hide Field'
    9.- Save the changes
    10.- Click on the VALIDATE CONFIGURATION button
    11.- Confirm that the system pops up Message (18111,25019) confirming the validation was correct without any errors detected
    12.- Go to the User List tab, and define the below set up:
              a) Level = Header Level
              b) Applies To = All With Excluded Roles/Users
    13.- Go to the 'Map to Portal Registry' tab, select the 2 EMPLOYEE rows displayed, and click on the APPLY CONFIGURATION button
    14.- Confirm that the system pops up Message (18111,25043) confirming the mapping of the configuration to the Component Events
    15.- Log into the FSCM Online Application as an Expenses User
    16.- Navigate to the Employee Self-Service Fluid Homepage, and click on the Expenses Tile
    17.- Click on the Add Quick Expense Tile
    18.- Once at the Fluid Wallet Entry page (EX_TRANS_LN_FL), confirm that the Currency Code field/look-up is hidden next to the Amount field, this is working fine
    19.- Proceed to use the look-up feature to select an Expense Type value from the view
    20.- ISSUE: Once back at the Fluid Wallet Entry page, confirm that the Currency Code field/look-up is now being displayed next to the Amount field

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 issue.

As the Currency Code field and its look-up gets displayed once the Expense Type field is filled in, then the User can intentionally or by mistake select a different value for Currency than the original default, creating foreign currency transactions, which should not be created in the company.

The settings defined for Currency Code field at the Page and Field Configurator level for the Component EX_MY_WALLET_FL, and Fluid Wallet Entry page (EX_TRANS_LN_FL), should be properly followed throughout the complete process of creating My Wallet transactions online via Fluid User Interface.

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.