SAP Search: From Transaction Codes to Fiori, HANA & AI-Powered Discovery

“SAP search” is not one engine. It can mean launching an application, retrieving authorised business objects in SAP Fiori, searching text columns in SAP HANA, or finding content in a specific module. A useful implementation begins by naming the object, system, authorisation rule, and action the user expects—then chooses the narrowest search layer that can answer it reliably.

Separate navigation, enterprise search, and in-app search

App search helps a user open an application or transaction. Enterprise Search retrieves business objects such as materials, purchase orders, customers, or projects and can navigate to their object pages. An application may also implement its own field, value-help, or list-report filtering. Combining all three behind one box without labels creates confusing results and makes failures hard to diagnose.

SAP's current Fiori Launchpad documentation states that locating business objects requires Enterprise Search to be integrated and set up; otherwise the scope is limited to applications available through the user's pages and catalog. Results are also constrained by the user's business roles and catalogs. That distinction should be visible in requirements and support runbooks.

Configure search models around business tasks

Search models define which business objects and attributes are searchable and filterable. Start with a small set of high-value tasks: find a purchase order by exact number, a customer by name and city, or an open project by manager and status. Include stable identifiers in the result, provide discriminating attributes, and link to the authorised object page rather than copying transactional actions into the search interface.

SAP's Fiori Search setup guide describes the Enterprise Search on HANA dependency and the role of HANA-enabled search models. Availability and setup differ between S/4HANA editions and releases, so use the documentation for the exact deployed release instead of copying an older activation recipe.

Use HANA text search deliberately

SAP HANA exposes text retrieval through the CONTAINS() predicate. Exact text search, linguistic processing, and fuzzy matching solve different problems. Exact business identifiers should normally remain exact; fuzzy matching is useful for names, descriptions, and genuine misspellings but can produce misleading near matches when applied indiscriminately to codes or amounts.

The official HANA fuzzy text search guide shows that a fuzzy text index is required for indexed fault-tolerant search and that result scores can be ordered with SCORE(). Build a labelled relevance set from real tasks before choosing a fuzzy threshold. A threshold copied from an example does not encode the cost of confusing two customers or materials.

Preserve authorisation from retrieval to navigation

Search must not reveal an object the user cannot otherwise access. Apply authorisation while retrieving results, not only after a user opens one. Titles, snippets, facet counts, recent-search history, suggestions, and exported result lists can all leak protected information. Test with representative roles, revoked access, organisational changes, and objects whose descriptions contain confidential text.

Index updates and permission changes need observable lag. Record the source revision and indexing time, expose failed connectors or models, and make rebuilds resumable. A green search endpoint with a week-old index is not healthy. SAP's product-specific Enterprise Search documentation demonstrates that available models and filters vary by business area.

Evaluate by task and failure mode

Create a test set for exact IDs, names with spelling variation, abbreviations, multilingual terms, statuses, and zero-result cases. Measure first useful result, task completion, no-result rate, and stale-result incidents by object type. Load-test the slowest realistic filters and review query plans. During upgrades, verify model compatibility, reindex duration, rollback, and search behaviour while a rebuild is incomplete. This turns SAP search from a broad product label into an operable business capability.