Start of Content Area

Function documentation Search Engine Service  Locate the document in its SAP Library structure

Use

The search engine service (SES) allows you to use the TREX search engine technology to index and search for SAP ERP business objects.

More than 50 business object types have implemented the SES methods. You can perform a full-text search on these object types in the possible entries help (F4) on the SAP GUI.

SES is used by SAP ERP as of version 2005 and is supported until the end of maintenance of ERP 2005. New business content for the object search is delivered predominantly based on the new Embedded Search.

The SES options are restricted to indexing and searching within a single SAP system (one system ID (SID)). To extend the range of your search, use SAP NetWeaver Enterprise Search (more information: http://help.sap.com/nwes70).

Integration

SES as Part of the SAP NetWeaver Search Technologies

SES is part of the SAP NetWeaver Application Server ABAP. SES is connected to a TREX system and can be integrated in SAP NetWeaver Enterprise Search.

This graphic is explained in the accompanying text

SES Architecture

SES replicates the business objects from the database into the TREX system. When a user enters a search query, the TREX system responds to it, not the database.

The following figure shows the SES architecture and its use for both end users and administrators. As administrator, you complete the initial configuration of the search engine service (SES) and monitor it during production operations.

This graphic is explained in the accompanying text

Features

SES has the following benefits:

●      You do not require knowledge of the technical implementation of the business objects to perform searches.

●      You can also search for known attribute characteristic values (field contents) even if you do not know the attribute schema of the business object being searched.

The main features of SES are:

●      Quick search using attributes and full-text

●      Extended search (attribute search)

●      Exact search, linguistic search (for example, house/houses), error-tolerant search

●      Search for multilingual objects

The main components are:

●      Interfaces for searching for direct integration in ABAP

●      Interfaces for updating the indexes

●      Indexing service and administration

●      Customizing

 

 

End of Content Area