Last updated on JULY 19, 2017
Applies to:PeopleSoft Enterprise FIN Maintenance Management - Version 9.2 and later
Information in this document applies to any platform.
In the process of replacing SES with Elastic Search in the PT 8.55.13 PUM 22 environment, Elastic Search has been given priority 0 and SES has been given priority 1. When testing the Recommend Labor functionality in Maintenance Management with SES as Priority 0, the system is returning search results. But when Elastic Search is given priority 0, no search results are returned with the same data. The customer has deployed and run the Full Index for EP_WM_SRCH_TECHNICIANS Successfully for Elastic Search.
The customer states that the issue is that the App Package has been hard coded with PTSF_DEFAULT as follows:
RS_MATCHENGINE:RsSearchFilters.MatchAny &rec.PTSF_SRCH_ENG_INS.Value = "PTSF_DEFAULT";
When Elastic Search is priority 0, the Elastic Search should be enabled and the same results of search should be returned as for the same data when the SES Search is priority 0.
This issue can be verified by performing the following steps:
1) Install and enable Elastic Search
2) Set Elastic Search Priority to 0
3) Navigate to Maintenance Management > Work Order; Search on and select a work order in AWSC (Awaiting Schedule) status; Tab to Schedules; Click on the Recommend Labor button.
The customer is unable to get Recommend Labor results with Elastic Search. Using a manual process to search for labor is time consuming.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms