How To Fix CMS_SEC072 - Collateral object cannot be set to inactive; active change request exist

SAP Error Message - Details

• Message type: E = Error

• Message class: CMS_SEC - CMS Securities Add-on

• Message number: 072

• Message text: Collateral object cannot be set to inactive; active change request exist

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message CMS_SEC072 - Collateral object cannot be set to inactive; active change request exist ?

  The SAP error message CMS_SEC072 indicates that a collateral object (such as a role, authorization object, or similar) cannot be set to inactive because there is an active change request associated with it. This typically occurs in the context of SAP's Change and Transport System (CTS) when changes to security objects are being managed.
  
  Cause:
  The primary cause of this error is that the collateral object you are trying to deactivate is currently linked to an active change request. In SAP, when changes are made to security objects, they are often captured in a transport request. If that request is still active (i.e., it has not been released or is still in the process of being modified), the system prevents you from deactivating the object to maintain data integrity and consistency.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Active Change Requests:
  
  Go to the transaction code SE01 (Transport Organizer) or SE09 (Workbench