Name: Activating Enterprise Search for SAP Fiori - SAP S/4 User Experience
Uploaded: 2021-12-9
Duration: 653 s
Description: This microlearning explains how to activate enterprise search using the task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT in SAP S/4HANA User Experience.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Learn more

About SAP Learning Hub

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>This microlearning explains how to activate enterprise search using the task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT in SAP S/4HANA User Experience. </div></div>

Activating Enterprise Search for SAP Fiori - SAP S/4 User Experience

Hello and welcome to this learning unit on activating Enterprise Search for SAP Fiori. My name is Gabrielle Young. I'm a Senior Technical Consultant. First part is how to activate Enterprise Search. In this section, we will first reset Enterprise Search using task list, SAP underscore ESH underscore reset. Then activate enterprise search using task list SAP underscore ESH underscore initial underscore setup underscore WRK underscore client. In the second part, we will learn how to deactivate search connectors such as duplicate searches or searches not required business. In the last part, we will learn Managing Search Models with SAP Fiori, SAP Fiori App F3036, Manage Search Models. The prerequisite for this learning, your SAP Fiori Launchpad, must be active. You need to refer to SAP Notes 262-6107, How to Execute task list using SAP underscore esh underscore initial underscore setup underscore wrk underscore client. In addition, you must be authorized to create transport requests. Access SAP Transaction STC01, STC02, and ESH cockpit ability to launch SAP Fiori Launchpad from your web browser. Lastly, access SAP Fiori app F3036. Manage search models. You must be assigned SAP Business role administrator, technical ID SAP underscore BR underscore administrator. In addition SAP S4 HANA release 1909 or higher. Now let's begin with the demo. We will execute SAP transaction STC01 and tasklist SAP underscore ESH underscore reset. Now let's click generate tasklist run. We need to populate field parameter. Prior executing the job in background, click field parameter. In here, we can see KIPP customer specific data has been selected. Leave it so the custom work remains. Nevertheless, select Reset Confirm for this client. Click Save and back arrow. Now, since this job will take a couple of hours, schedule the job in background. Click F9, start resume task list run in background. Now let's execute SAP Transaction STC02, and using task list SAP underscore ESH underscore reset to view the jobs update. Click execute, select the line, and click detail for task list run. As you can see, enterprise search was reset to initial state. Now, how do we activate enterprise search? Using SAP transaction STC01 and task list SAP underscore esh-initial-setup-wrk-client. Now click Generate Task List Run. In here, there are two parameters, which require to be set prior scheduling the job in background. First parameter, set tracks destinations of SAP HANA database connections. Click Fill Parameters. Select Use SAP HANA Primary Database Connection Default. Click Save and back arrow. The second field parameter is Select Models to Create Connectors. Click Field Parameters. In the software component, type in SAP APP LH. This is the standard model for all search connector SAP S4 HANA. Select All Models. Before we proceed, if you can't find SAP APPLH, you can click Tick if software component is missing in dropdown. Otherwise, click Save and back arrow. To view the progress of the job, use SAP transaction STC02 using task list SAP underscore ESH underscore initial underscore setup underscore wrk underscore client. In STC02, status is green, and hence you have successfully activated Enterprise Search. Select the line and see detail. Nevertheless, how does it look like in SAP Fiori? Let's execute the Launchpad. This is SAP Fiori Launchpad. Let's see the result from activating Enterprise Search. In the Search toggle, you can see there are duplicate searches or searches like allergens, which only required for a pharmaceutical company. Now, how do you remove these searches? How about removing duplicate searches? Let's run SAP Transaction ESH underscore cockpit, which is the connector administrator. This is ESH cockpit, the connector administration cockpit. You can see the status, consent, all active and inactive. Let's reduce them to display active only. Now let's deactivate allergens. In the find table, we type in allergens, find, find connector. The allergen connector selected. Click actions, deactivate. Let's go back to Launchpad to confirm the result. Remember to refresh web browser. It has been deactivated. We will now deactivate duplicate searches like supplier. We will also use similar steps. There's one with S4H and the other one with CD-DOLAROR. Now, let's go back to ESH cockpit and do the activations. In find in table, we enter supplier, then click find connector. Supplier duplicate search has two connector ID. One is the classic search. Classic search is named after system ID and client. Hence, in this case, it's S4H100. The other is CDS view search, which is the CD dollar. As a rule, we deactivate the classic search. Please notice number of entries equals 91. Let's look at the other duplicate. Find connector. Again, number of entries also 91. Hence, we will deactivate the classic search. To deactivate, select supplier, click actions, deactivate. Now let's go back to the launchpad. Now, please remember to refresh the web browser. We have successfully deactivated duplicate search. Now our last demo will be on managed search models with SAP Fiori. Now, what is managed search models with SAP Fiori? In our last demo, we can see to manage the searches, it requires many steps. Why do we need to do that? is to deactivate the connector to clean up the list. As we all can see, the connector cockpit is quite complicated. Hence, we are shifting to CDS search. We are moving from the older classic search to the new CDS-based search. In the search drop-down, we select Apps. We type in Manage Search Models, Enterprise Search. Now you can see all the CDS view-based search. In the status column, you can see the active and inactive. To deactivate the search, you can do it here, which makes it less complicated and more user-friendly. Notice, the allegiance is in it active. How about supplier? Notice, supplier is active. You can see the enable, yes, and therefore the status is active. In the fields tab, you can view all the fields. In the technical details, you can even see all the roles. We are certainly working towards greater capability and easier way to manage and fine-tune search models. There is a variety of search in the app, configured, personalized search, fine-tuning, defined search behavior, hence we need to move this over time. So, what have we learned? From this learning, now you can reset Enterprise Search using tasklist.sap.esh.reset. You can activate Enterprise Search using tasklist.sap.esh.initial.setup.wrk... You should run these tasks in background as they are long-running tasks. individual search connectors are created using CDS view. Classic search connectors may be superseded by CDS view. You can deactivate individual search connectors using SAP transaction ESH underscore cockpit. Lastly, CDS view search can views and manage using SAP Fiori app F3036, search models. To do further learning, you can follow the micro learning or open SAP courses listed below. Thank you and hope the learning is informative.