2010187 - How to archive/lock of IBase components and related IObjects for deleted systems in LMDB

You are working with job REFRESH_ADMIN_DATA_FROM_SUPPORT, transaction IB_GEN or with IBases in general. You delete a system in LMDB and you need to ensure that the related IBase component (text/object) and the related IObject (for object components) are not going to be used further in new incidents.

Solution Manager uses the IBase to represent the customer’s system landscape in a way the individual systems and their clients can be identified and referenced in business documents.

Before Solution Manager 7.1 SP5 the source of that information was the SMSY. With Solution Manager 7.1 SP05 the LMDB was introduced as the new database reflecting the system landscape of a customer environment.

With 7.1 SP5 the IBase components are provided as object components (only text components were provided in the earlier releases). With the use of object components, also called individual object or IObjects, objects can be used to reference LMDB as well as CMDB, database and host objects in ITSM scenarios.

The linkage between IObject/IBase text component and LMDB is the ULA GUID value.

SAP Solution Manager 7.1

ibase, iobject, text, object, duplicated, LMDB, ULA GUID,  REFRESH_ADMIN_DATA_FROM_SUPPORT, ib_gen, ib52, SAP_GUID, Master Data, sm_Crm, AI_CRM_DEL_NOT_USED_IBASE_COMP, AI_CRM_PRODUCT_DELETE, archive, locked, to be archive   , KBA , SV-SMG-SUP , Service Desk / Incident Management , Problem