Content
Restrictions, limitations and prerequisite
A general overview on Embedded Search / Enterprise Search can be found here.
When using HANA as DB, the landscape can be simplified as shown in the diagram "system landscape variants".
This HowTo guide focuses on the landscape variant using HANA as DB.
Use cases with embedded search
The following uses cases shall be addressed with this HowTo guide.
As an user I want to:
- ... find my objects in a simple way. I want to search google like with one input field. The search shall also provide a very quick feedback, even while typing.
- ... find objects via key attributes: I want to search for the most important fields / attributes of objects I'm looking for. This includes fields like number, description in all languages.
- ... find objects via classification: I want to search across the classification fields (characteristics) of the objects I'm looking for. This includes name and values in all languages across all assigned classes and characteristics.
- ... find via related objects (e.g. find document via a characteristic in a linked material): I want to search objects that are linked with other objects, that are found via my search term. E.g. I'm searching for a document, which is linked to a material, which has the material number XYZ.
- ... find fuzzy: as an user I want to still get a result, even when I have small typos, like searching for "confidential" even when I enter "confidetail"
- ... find content in files attached to documents (CAD files are not indexed)
ECTR UI configuration with new Quick Search
This is available with SAP ECTR 5.2.3 / ECTR for S4 1.1.3. There will be new FuBas which can then be configured.
The search can be enabled with
<ectr configuration root>\customize\config\default.txt
plm.search.provider.types = DOC;MAT;ECN;ESH <<<<<<<<<<<< add the entry ESH plm.search.provider.DOC = ... plm.search.provider.DOC = ... plm.search.provider.ECN = ... plm.search.provider.ESH = SEARCH_PROVIDER(/DSCSAG/SMS_ESH_BY_TEXT); <<<<<<<<<<<< add this line
Be aware, that function module /DSCSAG/SMS_ESH_BY_TEXT is only available with S4ECTR 110 SP03 (ECTR for S/4HANA 1.1.3).
<ectr configuration root>\customize\config\menu.guidef
+ om.file.menu = fnc.advanced.options
...
= fnc.cdesk.srv.search
= fnc.start.quick.search <<<<<<<<<<<< add this
...
Define keyboard shortcuts
...
fnc.start.quick.search.keystroke = control Q
...
Introduction to embedded search on HANA
With HANA you have implicit the embedded search capabilities. There is no need to create an index on a separate Indexing Server, but you can directly use the database table for searching.
There are three main steps required to get the embedded search up and running (for ECC on HANA or S/4HANA):
- configure your search model(s)
- create a connector help.sap.com
- start indexing (regular job) help.sap.com
There are default search models (templates) delivered with S/4HANA (see SAP Note 2513466) and ECC. You can find them with transaction ESH_MODELER (a browser will open to display the Webdynpro application). Either search or navigate through the hierarchy to the object models:
- Material Master: PLMWUIH->EAAPPLH->SAPAPPLH->[LO-MD]->MATERIAL_H
- Document Info Record: PLMWUIH->EAAPPLH->SAPAPPLH->[CA-DMS]->DOCUMENT_MODEL_H
- Change Number: PLMWUIH->EAAPPLH->SAPAPPLH->[LO-ECH]->CHANGE_NUMBER_H
- Engineering Record: PLMWUIH->EAAPPLH->SAPAPPLH->[PLM-WUI-OBJ-ECR]->ENGIN_CHANGE_REC_H
- Change Record: PLMWUIH->EAAPPLH->SAPAPPLH->[PLM-CR]->CHANGE_RECORD_H
Extend the existing search models
Prerequisite: Here's an introduction on how to create your own software component to extend search models.
The modeler can be launch with transaction ESH_MODELER.
Extend model with long texts of document info record
Step 1:
Step 2:
Include classification of document info record
Step 1:
Step 2:
Search document info record via related material master
