You can use the SAP Fiori Search to find apps and central business objects. To enable the SAP Fiori search in the SAP Fiori launchpad, perform the steps described below.
The search for business objects is enabled through corresponding search models. You can find an up-to-date list of the search models delivered for SAP Business Suite in SAP Note 1999463.
SAP Fiori fact sheets are based on search models, and the results list of SAP Fiori search is the main entry point to fact sheets.
Note
The setup of SAP Fiori search is a prerequisite for the use of fact sheets.
SAP Fiori fact sheets for business objects provide information on top of what is displayed in the search results. Furthermore, they enable you to navigate to fact sheets of related business objects and to transactional apps, or to access back-end transactions, and you can drill down into a business object's details.
Note
From SAP NetWeaver 7.4 Support Package 6, you can perform setup tasks for SAP Fiori by using task lists that SAP delivers. A task list groups configuration tasks logically and guides you through the necessary tasks.
For an overview of all task lists and tasks for SAP Fiori, see Configuration Using Task Lists.
The following task lists apply for this step:
SAP_ESH_INITIAL_SETUP_000_CLIENT
SAP_ESH_INITIAL_SETUP_WRK_CLIENT
You must have set up the communication between SAP Web Dispatcher and the ABAP servers. For more information, see:
You must have set up the Embedded Search
technology. The setup process consists of the following main steps:
Implement SAP Notes
Implement the SAP Notes listed in the Release Information Notes (RINs) for SAP NetWeaver Enterprise Search and for SAP Fiori Fact Sheets:
Activate business functions
Activate the following business functions in Customizing for your SAP Business Suite back-end system under Activate Business Functions
:
To enable SAP Fiori search and fact sheets: SAP HANA-Based Search for SAP Business Suite (BSESH_HANA_SEARCH
)
For more information, see SAP Library for SAP Enhancement Package 7 for SAP ERP 6.0 on SAP Help Portal at http://help.sap.com/erp607 under .
To enable fact sheets: SAP HANA-Based Navigation for SAP Business Suite (BSCBN_HANA_NAV
)
For more information, see SAP Library for SAP Enhancement Package 7 for SAP ERP 6.0 on SAP Help Portal at http://help.sap.com/erp607 under .
Furthermore, the activities under
are relevant in Customizing for your SAP Business Suite application.Set secondary database connection for search to SAP HANA database
Make this setting in Customizing for your back-end system under
.Alternatively, you can use report ESH_ADM_SET_TREX_DESTINATION
to set the database connection.
Prerequisites:
You have created a second database connection in transaction DBCO
.
A database user not equal to SAP<SID> is available. Database users must have the following authorizations:
Object authorizations TREXVIADBSL
and TREXVIADBSLWITHPARAMETERS
Scheme authorization SELECT
for the _SYS_REPO
scheme.
Scheme authorizations SELECT
, ALTER
, and INDEX
for the SAP<SID>
scheme.
For more information, see SAP Help Portal at http://help.sap.com/nw_platform under .
Activate connector-based authorization checks
To restrict the search results to the business object instances a user is authorized to see, embedded search supports authorizations based on business object instances. In addition, authorization checks based on search connectors are supported – mainly for performance reasons. For more information, see SAP Help Portal at http://help.sap.com/nw_platform under .
Activate the connector-based authorization checks in Customizing for your back-end system under Model Authorization
, select Check
from the dropdown menu.
Activate UI services
Activate the following services for the Embedded Search in transaction Activate Service
(SICF
) in your back-end system.:
Create connectors
Prerequisite: You need the following authorizations:
SAP_ESH_SEARCH
SAP_ESH_LOCAL_ADMIN
Create connectors in the Connector Administration Cockpit
(transaction ESH_COCKPIT
).
The connectors required for each fact sheet and the relevant search software components are documented in the implementation documentation for the single fact sheets.
Note
Note the following system behavior:
Search software components build a stack: On top of the basis component, different layers can be installed.
Search models can be available in different components: In their original component, but also in higher layer components (extension components).
Once you create a search connector in an extension component, all search models from the original component are transferred into the extension component. You will therefore no longer find the search models in the original component.
Example:
You have created a connector for a search model originating in search component SAPAPPLH
. You have created the connector via component EAAPPLH
, not via its original component SAPAPPLH
.
From that moment on, all search models originating in component SAPAPPLH
can only be found under the EAAPPLH
node in transaction ESH_COCKPIT
.
For more information about connector creation, see SAP Help Portal at http://help.sap.com/nw_platform under .
Note
When search models are transported, for example in the event of a system upgrade, manual steps can be required. For more information, see SAP Help Portal at http://help.sap.com/nw_platform under .
Start indexing of Connectors
For more information, see SAP Help Portal at http://help.sap.com/nw_platform under .