|
|
BC-EIM-ESH |
|
Embedded Search allows searches in enterprise data and information (business objects). Therefore, it is particularly suitable for applications in SAP Business Suite 7.
User Interface
As of this release, Embedded Search provides a simple and intuitive search UI specifically for SAP Business Suite applications. Users can use this UI to submit basic and advanced search requests. The system returns the search results in the form of a list, which you can further refine.
The user can navigate in the results using new functions and perform additional functions, such as starting a related search or launching an editing UI.
In addition, special functions are available, such as saving search requests, displaying the history, subscribing to search requests as a news feed, and extended personalization options.
More information: Getting Started – Using the Search
Definition of Navigation Targets
In order to jump directly from a search result to the corresponding back-end system using a link, navigation targets are required. In earlier releases, these navigation targets contained links with fixed server information. As of this release, you can use variables for the server information. You maintain the server information outside the template modeler on the configuration screen for the UI technologies.
If a back-end system provides more than one UI technology to display a function, you can group together the associated navigation targets semantically. The grouping is done by function and using an operation ID.
More information: Defining Optional Settings and Maintaining UI Technologies
Actions in Connection with UI Technologies
Before you can use the navigation targets defined in the template modeler, you must work through the following activities for the connected back-end system:
Activate supported UI technologies
WebClient UI
SAP GUI for HTML
SAP GUI
Web Dynpro
Define the sequence and thus the priority of the UI technologies
Specify the associated server connections
More information: Maintaining UI Technologies
New Features in the Administration Cockpit
The administration cockpit contains the following new features:
The overview table contains a new column called Searchable. You can use this column to identify whether or not the search object connector can be used for the search.
You can now choose more than one search object connector and perform an action that affects the entire selection, for example, you can simultaneously schedule indexing for more than one search object connector.
There is a new pushbutton called System Settings. When you choose this pubshbutton, you can access the Maintain UI Technologies and Control Real-Time Indexing functions. For more information about these functions, see the corresponding sections of this release note.
The pushbutton Switch to Modeler has been replaced by the link Template Modeler.
More information: Administration Cockpit
Managing Real-Time Indexing
Embedded Search allows you to index data that exists in back-end systems with a minimal time delay. From the administration cockpit, you launch an administration UI that you can use to control and monitor real-time indexing.
More information: Managing Real-Time Indexing
Resolving Naming Conflicts
No object types (templates, data types) within a hierarchy of software components may have identical names, therefore the system automatically performs a check for identical names during actions involving search object connector types.
However, in the case of an import, the automatic check and renaming does not take place during the import, but is done later. Therefore, we recommend checking the imported objects for naming conflicts as soon as possible after an import and resolving any conflicts manually.
More information: Resolving Naming Conflicts
New Features in the Template Modeller
The template modeller contains the following new features:
You can use the new Create Classification Template action to generate the templates that TREX requires for a classification search.
NoteThis function is available for SAP Business Suite applications to allow them to implement the classification search.
The new Switched indicator specifies whether or not a template with the switch assignment function has been activated using the SAP Switch Framework.
The new Display Switch Assignments action is also available to application developers as part of the SAP Switch Frameworks.
New Features in the Define Template Properties Roadmap Step
On the Extraction Schedule tab, you can define default values for regular extraction or alternatively, activate real-time indexing, if the back-end system supports this.
New Features in the Define Nodes Roadmap Step
Support for attribute groups (see entry below)
New Features in the Define Search Requests Roadmap Step
If there is no search request, you can use the Generate Default Request function to automatically generate the default search request with all response attributes.
Support for attribute groups (see entry below)
Specification of the relevance of attributes (see entry below)
More information: Using the Template Modeler
Support for Attribute Groups
In the Define Nodes and Define Search Requests roadmap steps, you can create attribute groups and use these to bundle attributes. Attribute groups modeled in the Define Nodes step earlier in the roadmap allow reuse of attributes and simplify the management of them.
More information: Defining Nodes and Defining Search Requests
Specification of the Relevance of Attributes
To influence the location of items in the search results list, you can vary the weighting of the attribute for this search request in the Relevance column. You can assign a higher or lower weighting to the attribute. The higher the weighting of the attribute, the more influence it has in the calculation of the relevance of an item. Items with a higher relevance are located higher up the search results list.
NoteNote that other factors play a role in the calculation of the relevance, such as the frequency and order of the attributes in the structure.
More information: Defining Search Requests
Virtual Templates
Virtual templates introduce an abstraction layer in the template modeler. They allow you to cover the following requirements:
You assign meaningful names that people can read easily instead of cryptic technical names.
The system can search through data using different virtual templates that each provide a different perspective on a template.
A normal template has one response structure. If you require a different response for the reasons listed above, you can use a virtual template to implement this requirement.
Virtual templates provide additional entry points to a search object connector template. This allows extraction models to be closely connected with the business object model.
Virtual templates allow you to refine the generic object types. This makes sense if you want to address an instance of a generic object type that is distributed among more than one subobject type.
More information: Creating Virtual Templates
Model Compression
While Embedded Search is running, the system compresses the models that you have created with the template modeler in the background by default, if there are 1:1 relationships between nodes within a template. Fewer TREX indexes are generated when using model compression, which reduces memory usage on the TREX server and improves search performance.
Model compression is activated by default.
More information: Model Compression
Reference documentation for Embedded Search