SAP Fiori

Embedded Search & Search Connectors

20 flashcards · answers and review in the app

Which UI services must be activated on the ABAP back end for embedded search?
Which Enterprise Business Functions must be active for embedded search, and how do you check them?
How do search connectors come into existence for a fact sheet app?
Which scheduling options exist for connector indexing?
Which task list creates search connectors and indexes them in one shot?
You selected one search model, but several connectors appeared in the cockpit. Why?
What is the difference between the Keep Index Content and Clear Index Content modes — and what happens if you choose neither?
Which roles does the Fiori admin user need for embedded search administration?
What two factors determine whether connector indexing runs as full or delta indexing in the HANA-based variant?
How do you verify the embedded search installation on a classic Business Suite back end?
Which authorization roles are needed to create search connectors?
A connector creation appears stuck. Where do you watch its progress?
Why does the embedded search initial setup task list run logged into client 000?
Where do you monitor and manage search connectors, and what does a grayed-out model mean there?
Why is embedded search a hard prerequisite for fact sheet apps, and what does its setup span?
After the client-000 run, what does SAP_ESH_INITIAL_SETUP_WRK_CLIENT do, and how should you run it?
In the SAP HANA-based variant of embedded search, which connectors are searchable immediately and which need indexing?
Why should you skip the ESH_SEARCH verification step on an S/4HANA landscape?
What restriction applies to the SAP HANA-enabled search models of software component SAPAPPLH?
What exactly is a search connector?