General Features

To enable the integration of different objects and systems, the objects in SAP QIM were decoupled from a specific data model.

For this, object types were defined in SAP QIM. For all object types, abstract definitions were stored in the business object layer (BOL) via the geNIL Model Editor (transaction GENIL_MODEL_EDITOR).

The following genIL components are relevant for SAP QIM:

Worklists

Reference objects (examples)

In SAP QIM, the object types are subdivided into object categories. Access to the specific objects in the source systems is technically executed by category-dependent implementations of Business Add-Ins (BAdIs):

The system accesses the business object layer (BOL) via the object category. The BOL calls the genIL component, which in turn calls the category-dependent BAdI implementation. Depending on the object category, the system accesses an object with a specific data model. This object may be located in another source system, such as an SAP ERP system, or it may be located in the same system.

Setting Options

You make the settings for the object types and object categories in Customizing for QIM, depending on whether the settings are for worklists or reference objects:

The technical implementation is the same in both areas. You specify for an object category which system is to be used to display the data, for example. For more information about the setting options, see the documentation for the respective Customizing activities.

Mapping

The assignment of the different data models is done via structure mapping. This is stored in Customizing for the object category. For more information, see the example relating to worklists under Structure Mapping.

For nonharmonized systems, you can also store an ID mapping (key or value mapping). For more information, see ID Mapping.