EEX 9.2: Elastic Search on Expense Report Transactions Not Immediately Displaying the Line Number Details When Opening Search Hit (Doc ID 2914476.1)

Last updated on DECEMBER 08, 2022

Applies to:

Symptoms

Having implemented Elastic Search feature, and performed some search by keyword on the Global Search functionality, the system has retrieved a detailed list of hits, showing the Expense Report ID value, as well as the Line Number, and the keyword being searched on (Expense Type). However, upon clicking on one of the listed hits, the displayed information is not the expected one:

    a) The system first displays the Fluid Expense Report Header page, which is inconsistent, as the link already listed Line Number data
    b) Upon clicking on the 'View Details' button, the system displays the Fluid Expense Entry page, but from the wrong Line Number, and there is no possibility to navigate among the multiple Lines of the transaction
    c) User needs to perform un-necessary steps to re-load the Fluid Expense Entry page, which finally displays the multiple transaction lines on the left hand-side panel, and has to manually select the Line Number identified from the Global Search

REPLICATION STEPS:

    1.- Ensure that the Elastic Search feature is properly implemented in the affected environment
    2.- Log into the FSCM Online Application as a System Administrator User
    3.- Navigate to: PeopleTools > Search Framework > Administration > Define Search Instances
    4.- Configure all needed settings at the Search Instance properties level for the well functioning of Elastic Search
    5.- Navigate to: PeopleTools > Search Framework > Administration > Configure Monitoring Server
    6.- Define all set up for the Server to use
    7.- Navigate to: PeopleTools > Search Framework > Designer > Define Search Definitions
    8.- Confirm that Search Definition EP_EX_REPORT exists, and is properly set up, and linked to delivered Source Connected Query EX_SRCH_HDR_LINE_CQ
    9.- Navigate to: PeopleTools > Search Framework > Administration > Deploy Search Objects
    10.- At the 'Deploy Search Definition' tab, make sure that Search Definitions EP_EX_REPORT, PSFT_RECENTMENU, and PTPORTALREGISTRY are successfully deployed
    11.- Log into the FSCM Online Application as an Expenses User
    12.- Navigate to: Set Up Financials/Supply Chain > Product Related > Expenses > Purchase > Create Expense Type Codes
    13.- Create a new Expense Type named OSSTEST, with a Description of 'OSS Expense Costs'
    14.- Go to the Employee Self Service Fluid Homepage, and click on the Expenses Tile
    15.- Click on the Create Expense Report Tile
    16.- Proceed to create a brand new Expense Report, with all Header field populated, and at least 3 or more lines, but making sure that Expense Report Line Number 2 is using the Expense Type OSSTEST recently defined
    17.- Save the transaction at this point, but not yet submit it for approval
    18.- Log into the FSCM Online Application as a System Administrator User
    19.- Navigate to: PeopleTools > Search Framework > Administration > Schedule Search Indexes
    20.- Create a new Run Control ID, with the below settings:
              a) Search Instance = PTSF_DEFAULT
              b) Search Definition = EP_EX_REPORT
              c) Indexing Type = Full
              d) Language Option = Base Language
    21.- Click on Run button
    22.- Select the PTSF_GENFEED AE Program, and click OK button
    23.- Navigate to: PeopleTools > Process Scheduler > Process Monitor
    24.- Find the Process Instance at hand for the PTSF_GENFEED AE Program, and confirm it completed in Success
    25.- Repeat steps 19 to 23, but this time with Search Index Definition PTPORTALREGISTRY
    26.- Navigate back to the Employee Self Service Fluid Homepage
    27.- On the Global Search console, select the Expenses option from the drop down menu
    28.- Fill in the keyword OSSTEST, and search
    29.- Confirm that the system is now returning one hit in the list, with the Expense Report ID previously created, and Line Number 2, with the Description of 'OSS Expense Costs' all displayed
    30.- Click on the search result hit to open it
    31.- ISSUE #1: The system directly displays the Fluid Expense Report Header page for transaction clicked upon, which has no information related to the OSSTEST keyword being searched on
    32.- As such, the User is forced to click on the available 'View Details' button
    33.- ISSUE #2: The system is not automatically displaying the Expense Report Line Number 2, which contains the OSSTEST keyword being search on, instead, it displayed the first/last Line Number of the transaction
    34.- ISSUE #3: In the very same page, the left hand-side panel offering the option to navigate through the multiple existing Expense Report Lines is missing, so User cannot select Line Number 2 at this stage
    35.- As such, the User is forced to click on the 'View Summary' button
    36.- Once at the Fluid Expense Summary page, the User must proceed to click on the 'View Details' button once again
    37.- At this stage, the User is brought into the Fluid Expense Entry page, and this time, the left hand-side panel is present, displaying the complete list of Expense Report Lines available in the transaction
    38.- The User has to try to identify Line Number 2 (the one Global Search pointed as the one containing Keyword OSSTEST), and click on it to display its information. If the Expense Report has many lines, this becomes far from ideal

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.

The Global Search functionality for Expense Reports is properly identifying all Expense Report transactions containing the Keyword value being searched on, however, the Users need to go through cumbersome number of steps to be able to display the line that got identified by Elastic Search, making unnecessary clicks, and having to eventually manually try to identify the Line Number they were looking for. This makes the whole Elastic Search feature not very user friendly, and difficult to roll out due to its poor display capabilities.

As the Global Search has identified not only the Expense Report ID transaction, but also its Line Number containing the Keyword being searched on, once the User clicks on the hit list row, the system should automatically bring the User to the Fluid Expense Entry page, displaying the already identified Line Number information details. In other words, do not automatically display the Expense Report Header, which is not relevant for this Keyword Search, and do not force the User to have to search for the Line Number via many unnecessary steps. The left hand-side panel showing all existing Expense Report Line transactions should also be displayed automatically.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.