In the first step in the roadmap, you define the use and other properties of the search and analysis model.
A roadmap appears.
The use of the icon depends on the application.
To deselect an icon, choose Select Icon again and then choose the empty icon at the top of the list.
An application model is a normal model that is used for search and operational analytics. It is used as template for the connector and represents an object that can be searched directly, for example material, activity, or customer. In addition to the object attributes, you can use the content of attached binary files (for example, documents) for the search.
A technical model is an object that cannot be searched or analyzed directly. Its content is used by business objects. Typically, this type of model is used by more than one business object. One example is the language-specific descriptions of the country code or order status.
An authorization model is an object that cannot be searched directly. Its content is used during authorization checks on business objects. One example is the models delivered by SAP for the ABAP authorization check.
A virtual model is an object that references a node of another available model and can have completely different response attributes and search queries to the referenced model. Virtual models do not have their own persistence because they access the TREX indexes for the referenced models. For more information, see Creating Virtual Models.
If you use the search and analysis model for operational data provisioning, choose Application Model or Technical Model as the model usage.
The system reads the application component hierarchy for this package. It uses the subcomponent assigned to this package as a structuring criterion below the software component when displaying the model in the search and analysis modeler.
Subcomponents are a display function and do not have any impact on the relations between model nodes; this means that a model node can be associated with another model node in the same software component, even if the models are located in difference application components.
If you create a model for a customer order BO and enter here the keywords PO, order, and sales, the search request PO Name Miller searches through the back-end systems that are connected to the connectors created using this model and returns all customer orders for the customer Miller, even if the keywords sales order were not part of the search request.
More information: Defining Model Nodes