Defining Model Properties 
In this first step of the roadmap, you define the purpose of the search object connnector model.
Procedure
In the model overview in the administration cockpit, choose the new search object connector model and choose Edit.
A roadmap appears.
Choose Select Icon if you want to select an icon that is to appear in the search results alongside the actual search results from connectors created using this search object connector model.
NoteThe use of the icon depends on the application.
End of the note.To deselect an icon, choose Select Icon again and then choose the empty icon at the top of the list.
Specify whether this model is to be used as an application model, a technical model, or an authorization model, or if it is to be a virtual model.
NoteAn application model is a normal model that is used for searching. It is used as template for the search object connector and represents an object that can be searched directly, for example material, activity, or customer.
A technical model is an object that cannot be searched 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 codes.
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.
End of the note.Only if you choose the virtual model: Select a node below the available models that is to be used as a reference for the virtual model and choose Select.
Optional: You can assign a package on the Properties tab page. If you are not using a package assignment, enter the value $TMP in the Package field.
If a package has been assigned, the system displays the application component and the system software component. In the modeler, the package is used as a further hierarchy level in the model list.
Optional: On the Keywords tab, you can add alternative keywords that can be used during searches as aliases for this search object connector. The system uses the keywords to identify this connector is a search query. Keywords are language-specific.
ExampleIf you create a search object connector 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 search object 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.
End of the example.Optional: On the Categories tab, you can assign this search object connector model to categories and create more categories.
More information: Managing Search Categories
Optional: On the Extraction Schedule tab page, you enter either a default frequency for indexing or define whether or not indexing is to take place in real time.
NoteThe back-end system must support real-time indexing.
End of the note.If you enter a default frequency, this is adopted in the administration cockpit as the default value for indexing of all connectors based on this model. You can change the values at any time there.
We recommend entering the highest possible frequency that does not negatively impact system performance as the default frequency.
ExampleYou specify a default frequency of one hour for business objects.
End of the example.More information: Scheduling Indexing
To move to the next step in the roadmap, choose Continue.
More information: Defining Model Nodes