How to use CLB2_CUST - Transaction to fill SMI customzings

SAP Transaction Code - Details

• Transaction Code: CLB2_CUST

  Description: Transaction to fill SMI customzings

  Release: S/4HANA and ECC 6

• • Program: RCLB2_FILL_CUSTOMIZING

    Screen: 1000

    Authorization Object:

  • Development Package: AR_FND_SM_JAM_CUST

    Package Description: SAP Jam specific Customizing

    Parent Package: AR_FND_SM_JAM_MAIN

  • Module/Component: CA-UI2-AR-SM

    Description: SAP UI Integration - Social Media Collaboration Enablement

Smart SAP Assistant

• SAP Tcode: CLB2_CUST - Transaction to fill SMI customzings

  
  Overview: 
  CLB2_CUST is a transaction code used in SAP to fill customizing settings for the System Monitoring Infrastructure (SMI). It is used to configure the SMI settings for the system, such as setting up the monitoring of certain objects and activities. 
  
  Functionality: 
  The CLB2_CUST transaction code allows users to configure the SMI settings for their system. This includes setting up the monitoring of certain objects and activities, as well as configuring the alerting and reporting functions. The transaction code also allows users to view and edit existing SMI customizing settings. 
  
  Step-by-step How to Use: 
  1. Log into your SAP system and enter the CLB2_CUST transaction code. 
  2. Select the “Customizing” tab. 
  3. Select the “SMI Settings” option from the drop-down menu. 
  4. Select the “Monitoring” tab and select the objects and activities you want to monitor. 
  5. Select the “Alerting” tab and configure your alerting settings. 
  6. Select the “Reporting” tab and configure your reporting settings. 
  7. Save your changes by selecting “Save” from the toolbar at the top of the screen. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with SMI customizing settings before using this transaction code, as it can be difficult to understand all of the options available without prior knowledge of SMI customizing settings. Additionally, it is important to ensure that all changes made are saved correctly in order to avoid any potential issues with SMI monitoring or alerting functions in the future.