Installed Base

The installed base or IBase is a multi-level structure that contains installed base components. With installed bases, you manage the objects in the customer's system landscape. SAP Customer Relationship Management provides IBase.

In SAP Solution Manager, the landscape management database (LMDB) represents the system landscape. The LMDB is created from the system landscape directory (SLD). In the IT service provider scenario, the REFRESH_ADMIN_DATA_FROM_SUPPORT job provides the LMDB with data.

LMDB replicates data to the IBase as IBase object components (IObjects). IBase object components contain IObjects (configuration items). By default, SAP Solution Manager uses an IBase with the external ID SOL_MAN_DATA_REP to store the IObjects. The LMDB entity is connected to the IObject by the ULA GUID, a unique identifier used by the LMDB. Databases and host IObjects are not installed in IBase components because they do not follow a hierarchical structure of systems and clients.

Configuration management databases (CMDB) also replicate data to SAP Solution Manager. If location replication is active, an IBase is created for each CMDB object location. A CMDB object is replicated as an IObject.

Users use IObjects, called reference objects or configuration items, to reference system landscape entities in messages and change transactions they create. This allows users to report incidents and request services for specific entities, so, for example, an IObject (configuration item) represents the device in which an incident is detected.

Integration

Authorizations

You authorize users to use IObjects (configuration items) in authorization object SM_SDK_IBA. These authorizations are applied at the following levels:

USERS_OWN (individual level) grants access to objects that are assigned directly to the user as follows:
- Configuration items that are assigned to the business partner of the reporter when the reporter is the employee responsible
- Configuration items that are identified by the external identification number assigned in the user's business partner master
USERS_ORG (organizational level) grants access to objects assigned to organizations to which the user is directly assigned, using the organization model and business partner relations such as sold-to party, employee responsible, and external identifications.
To determine the user’s organizations, the following sources are taken into account:
- Business partner relations: Organizations to which the user’s business partner is related as a contact person (organization using business partner relation is contact person for)
- Organization structure: Organization units to which the user’s business partner is directly assigned in the organization structure.
ALL grants full access to all objects. The user can use all configuration items.

Prerequisites

You have performed the following activities in SAP Solution Manager Configuration:
- For LMDB replication:
  Mandatory Configuration Infrastructure Preparation Configure CRM Basics
- For CMDB replication:
  In Basic Configuration Schedule Jobs , you have scheduled job AI_CRM_AIDIAGNOTIF_CREATE. This job should be scheduled daily. It copies changes from the LMDB or the CMDB to the IBase.

Activities

Creating IBase Components

Initially, you create IBase object components and IObjects for LMDB objects in SAP Solution Manager Configuration, in the Infrastructure Preparation scenario, Configure CRM Basics step.

Note Note

To disable the LMDB to IBase replication, you can deactivate the AI_CRM_LMDB_NOTIF_CONS_IMPL BAdI implementation for the BADI_LMDB_NOTIFICATION BAdI.

To disable the CMDB to IBase replication, you can deactivate the BADI_DIAG_NOTIF_LISTENER_CMDB BAdI implementation for the BADI_DIAG_NOTIFICATION BAdI.

End of the note.

Subsequently, you create IBase object components and IObjects as follows:

For LMDB objects: use transaction Create and install I-Objects for LMDB (IB_GEN).
You can also use this transaction to load specified systems manually.
For CMDB objects: use the AI_CRM_IBASE_CMDB_GENERATE_71 report to initially load data from the CMDB, manually.

Checking IBase Components

You can check whether the LMDB and the IObjects are linked correctly in the LMDB, Change Installed Base (transaction IB52), and in the IT Service Management master data.

For more information about checking IBase components, see knowledge base article 2012029 Duplicate IBases - how to clean up.

Deleting Duplicate IBase Components

If you have detected that duplicate IBases are created for the same system or client, identify which duplicates should be deleted. When you detect an IBase component with an empty ULA_GUID or with an ULA_GUID value that differs from the one in the SAP_GUID in the LMDB, then the IBase component is a candidate for deletion.

For more information about deleting duplicate IBase components, see knowledge base article 2012029 Duplicate IBases - how to clean up.

Archiving IBase Components

Deletions from LMDB are replicated as follows:

The system locks the related object.
The system moves the corresponding IBase component to an archive IBase.

Locked objects behave as follows:

When a user selects a locked object from the Details assignment block, an error message is displayed.
If configured, users can find locked objects when searching for change transactions and messages, to search for change transactions and messages to which a locked object is assigned.

As an administrator, you configure the system so that users can find locked objects if the objects are locked or archived as follows:

For the required user and client, in table AIC_OBJECT_CONF, set the SEARCH_LOC property to X.

More Information

Installed Base Management in the SAP Library for SAP Customer Relationship Management at Start of the navigation path http://help.sap.com/crm Next navigation step <current release> Application Help <language> Master Data End of the navigation path

Reference Objects