The SAP Fiori launchpad offers an enterprise search function that searches across all apps and business objects, such as materials, customers, and maintenance plans. The search icon is displayed in the shell bar of the launchpad and is always readily available at the top of the screen.

When pressing the search icon in the shell bar, the search field and the type selector appear.

After entering a search term, users can trigger the search by pressing ENTER, by clicking the magnifier icon, or by selecting one of the suggestions. A search for All can be achieved by pressing ENTER in an empty search field or by using the * query.

If the search field is left empty, clicking the search icon closes the search field.

The search can be restricted to objects of a particular type.

This can be done before the search is triggered, either by using the type selector or by typing the object type into the search field and selecting the respective suggestion.

To filter a result list by object type, users can select the type tabs or the respective section in the filter panel.

When the user starts typing in the search field, suggestions appear. There are 3 main suggestion types:

• Type suggestions switch the type selector (for example, Search In: Sales Orders).
• App suggestions launch the app (for example, App Create Leave Request).
• Term suggestions execute a search with the respective terms (for example, SAP Walldorf)

In addition to the the one-click filters, the user can set more filters by choosing Show More or Show All Filters. This opens a filter dialog with a list of all the available filters on the left. The details for the selected filter show on the right.

The available options depend on the data type of the filter (text-based, numeric, date) and the configuration. For most filters, a list of filter conditions is shown, similar to the filter panel. For texts, this list can be filtered and sorted. For numbers and dates, the user can add custom ranges. There is also an option to enter variable conditions: Instead of picking items from a list, the user can specify advanced conditions like begins with.

Users can switch the personalized search on or off, depending on the configuration.

Development teams can fine-tune the search for the business objects they are responsible for.

The display and behavior of the enterprise search is based on search models. Apply the following rules when creating search models.

• Implement the title of a search result as a link to the object page or an equivalent full screen representation of that particular business object.
• Align the title, subtitle, and object type with the corresponding object page. Displaying objects consistently makes them easier to scan.
• To help users recognize objects quickly, use images whenever they are available. However, don’t display indistinctive images or placeholder images.
• Include relevant attributes in the object preview. They can help users to distinguish between objects and answer common questions up front (such as a contact phone number).
  • Do not show unimportant attributes or attributes that aren’t shown on the corresponding object page.
    Hint: When choosing attributes, focus on attributes that are important during productive use. These can differ from attributes that seem most important during development. For example, master data attributes like “Created On” and “Created By” would not normally be relevant for the preview.
  • Use consistent attribute labels that are either identical or aligned (for example, “Team Type” vs. “Type” in the “Team” section of the object page).
  • Align the attribute content, especially the display order of “text (ID)” attributes.
• Make visible fields searchable (note that this may not be possible for all fields due to technical constraints).
• Include facets only if they are meaningful as filter criteria. Otherwise, avoid them.
  For example, a facet for an ID would not make sense – each ID would return a single result, rather than a set of results.