Show TOC

Defining Model PropertiesLocate this document in the navigation structure

Context

In this first step of the roadmap, you define the purpose of the search object connnector model.

Procedure

  1. In the model overview in the administration cockpit, choose the new search object connector model and choose Edit .

    A roadmap appears.

  2. 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.
    Note

    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.

  3. Choose whether this model is to be used as a model for business objects, for technical objects, or for authorization objects, or whether it is to be a virtual model.
    Note

    An 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. 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 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 .

  4. 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 .
  5. Only if you choose the model for application models: 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.
    Example

    If 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.

  6. Only if you choose the model for application models: On the Categories tab, you can assign this search object connector model to categories and create more categories.
  7. Only if you choose the model for application models: On the Extraction Scheduling tab, you can define default values for regular extraction or alternatively, activate real-time indexing, if the back-end system supports this. The values entered here appear as default values for the search object connectors derived from this model in the administration cockpit at Start of the navigation path Action Next navigation step Scheduling Indexing End of the navigation path.
  8. Choose Next .

    This takes you to the next step in the roadmap: Define Nodes .

    More information: Defining Model Nodes