Deleting CBTA configuration for a given System Under Test in SAP SOLMAN 7.2


Introduction:

Generally we are more excited about configuring any new functionality in SAP Solution Manager and in this process we configure few things which are no more required by business. So ideally, that configuration should be removed or deleted so that we can save some space.

So in continuation of my previous blog about CBTA Configuration in SAP SOLMAN https://blogs.sap.com/2022/05/15/cbta-configuration-in-solution-manager-7.2/ , this blog will explain the way to de-configure/delete CBTA for a given SUT in SAP Solution Manager.

How to Start:

In the process of CBTA configuration for a SUT, you might have performed the below two steps, which you have to undo:

  1. Client Setting for the SUT- Go to SCC4, change the settings of CATT and ECATT. Change it to “Not Allowed”.
  2. Enable scripting in client-  Go to RZ11, give parameter sapgui/user_scripting and change the current value from “TRUE” to “False”.

Next Steps:

After you perform the above two steps, please go and delete the logical component group created for the SUT. This activity will delete the SDC as well in SUT Management.

After you delete the LCG, just go to the SUT Management and resynchronize the solution. Your SDC will be deleted.

Once you delete the LCG, please go and delete RFCs. READ, TMW and LOGIN RFCs created while performing managed system configuration of the SUT.

Note: After performing all the above mentioned steps, you need to go to table ECSD_SYS in solman system and mention the solution where you had your LCG.

In this table you need to delete the SDC of the SUT. This will be the final step to de-configure the CBTA for the SUT.

Summary:

Let me summarize the steps to de-configure/delete the CBTA for a SUT in SAP Solution Manager 7.2:

  1. Change the client settings in SCC4
  2. Change parameter value for parameter sapgui/user_scripting
  3. Delete the LCG for the SUT
  4. Resynchronize the the solution in SUT management for deleting SDC
  5. Delete the RFCs created(if not required)
  6. Delete the entry in SCATT table.

Conclusion:

Its always good to delete CBTA configuration for a SUT, for which CBTA is not required. It will surely some space and will eliminate the risk of scripting for a system.

Keep learning and keep sharing.

Cheers!!!