SAP Fiori · Embedded Search & Search Connectors

Verifying embedded search on a classic Business Suite back end, you run ESH_SEARCH and the Web Dynpro search UI appears. Why would copying this exact verification step into an S/4HANA runbook be a mistake?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Embedded Search & Search Connectors

A colleague insists the embedded-search initial-setup task list must run in client 000 because that is the only client allowed to run task lists. Why is that reasoning wrong, and what is the real reason?

What scheduling options can you pick when starting connector indexing?

Embedded search half-works after you activated /sap/es/search. Which other ICF nodes and Web Dynpro services are easy to forget, and why does activating just the search node not suffice?

When re-indexing a connector you can pick Keep Index Content, Clear Index Content, or neither. A teammate assumes leaving both unselected is a safe no-op. What actually happens, and when must you Clear instead?

You selected exactly one search model but the cockpit now shows several connectors. Is this a bug, and what's the mechanism — and what's the wrong move it tempts?

Connector creation in the cockpit looks frozen with no progress shown. What is the actual unit of work doing the creation, and where do you go to see whether it is running, finished, or failed?

Start learning today

Free to start — download the app or use it in your browser.