Show TOC

Function documentationInstalled Base


With installed bases, you manage the objects that are installed in the customer's system landscape. The installed base or IBase is a multilevel structure that contains installed base components. SAP Customer Relationship Management provides IBases to handle master data.

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 the relevant data.

LMDB replicates data to the IBase as IBase object components (IObjects). By default, SAP Solution Manager uses an IBase with the external ID SOL_MAN_DATA_REP to store the IObjects. The LMDB is connected to the IObject using the ULA GUID, a unique identifier used by the LMDB.

Users use IBase object components, 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. For example, an IBase component represents the device for which an incident is reported.



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

  • USERS_OWN (individual level) provides 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 users business partner master

  • USERS_ORG (organizational level) provides 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 take into account:

    • Business partner relations: Organizations where 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 to in the organization structure.

  • ALL provides full access to all objects. The user can use all available configuration items.


  • You have performed the following activities in SAP Solution Manager Configuration:

    • Start of the navigation path Basic Configuration Next navigation step Maintain Systems in IBase End of the navigation path

    • In Start of the navigation path Basic Configuration Next navigation step Configure Automatically Next navigation step Schedule Solution Mgr Background Job End of the navigation path, 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.

  • You have implemented SAP Note 1741109Information published on SAP site ITSM 7.1 - Generation of IBase Components is not working.

  • You have implemented SAP Note 1935934Information published on SAP site Various problems when creating IBase components and objects.

  • In table DNO_CUST04, parameter IB_GEN_AUTO is empty (that means that the automatic IBase generation is active), so that the system creates the IBase components automatically for the systems that are created in the LMDB. For more information, see SAP Note 1483276Information published on SAP site Use of Customizing Parameters in DNO_CUST04, AGS_WORK_CUSTOM, and ICT_CUSTOM.


Creating IBase Components

Initially, you create IBase components in SAP Solution Manager Configuration, in the Basic Configuration scenario, Maintain Systems in IBase step.

Subsequently, you create IBase components as follows:

  • For LMDB objects: use transaction Create and install I-Objects for LMDB (IB_GEN).

    You can start the transaction from SAP Solution Manager Configuration in the Basic Configuration scenario, Maintain Systems in IBase step, Create IBase Components for LMDB Systems activity.

    You can also use this transaction to a manually load specific systems.

  • For CMDB objects: use the AI_CRM_IBASE_CMDB_GENERATE_71 report to initially and manually load data from the CMDB.

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 2012029Information published on SAP site Duplicate IBases - how to clean up.

Deleting Duplicate IBase Components

If you have detected that duplicate IBases were created for the same system client, you need to 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 shown in the SAP_GUID in the LMDB, then the IBase component is a candidate to be deleted.

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

Archiving IBase Components

When entities are deleted from the LMDB, they must be locked and archived in the IBase so that they can no longer be used in messages and change transactions.

For more information about how to archive IBase components, see SAP Note 2010187Information published on SAP site How to archive/lock of IBase components and related IObjects for deleted systems in LMDB.

More Information

Installed Base Management in the SAP Library for SAP Customer Relationship Management at Start of the navigation path published on SAP site Next navigation step <current release> Next navigation step Application Help Next navigation step <language> Next navigation step Master Data End of the navigation path

Reference Objects