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?

In the Connector Administration cockpit (ESH_COCKPIT) one search model is grayed out. A new admin reads this as 'this model is unavailable.' What does grayed-out actually mean, and what wrong move does it tempt?

Embedded search returns nothing and you have already created connectors. Before redoing connector work, which Enterprise Business Functions must be active, where do you check, and what does an inactive one look like?

Is a search connector the same thing as a search model? If you transport a search model to another system, are its connectors transported too?

You want connectors created AND indexed in one pass instead of creating them in the cockpit and scheduling indexing afterward. Which task list does that, and when would you NOT want it?

A fact sheet app deploys cleanly but shows no business data. Connectors aside, which step in the app's implementation information was likely skipped, and why is it a hard prerequisite?

After the client-000 initial-setup run, what does SAP_ESH_INITIAL_SETUP_WRK_CLIENT do, which client do you run it in, and what execution detail trips people up?

Why won't fact sheet apps work without embedded search, and why is back-end ESH config alone not enough to make them work?

In the SAP HANA-based embedded search variant, a new admin schedules indexing for ALL connectors. Which connectors did NOT need that, and what property decides immediate vs index-required?

Which roles does the Fiori admin user need for embedded search administration, and how are they assigned?

Which authorization roles are needed to create search connectors, as opposed to general ESH administration?

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?

Can you reuse the SAP HANA-enabled search models of software component SAPAPPLH in your own custom search consumer, or only in Fiori search?