How To Fix CMT072 - Controlled object has not been transferred

SAP Error Message - Details

• Message type: E = Error

• Message class: CMT - CM: Message Class in CM Environment

• Message number: 072

• Message text: Controlled object has not been transferred

What causes this issue?

You want to create a successor folder or a Baseline. The controlled
object of the configuration folder is a serialized object that means a
serial number or equipment.
It is not possible to copy serial numbers or equipment into a successor
folder.

System Response

The system creates a successor folder without a controlled object.

How to fix this error?

You can enter another controlled object in the successor folder.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CMT072 - Controlled object has not been transferred ?

  The SAP error message CMT072 ("Controlled object has not been transferred") typically occurs in the context of controlling (CO) and project systems (PS) when there is an issue with the transfer of controlled objects, such as cost centers, internal orders, or projects, to the controlling area or when trying to execute a transaction that requires these objects to be properly set up.
  Causes:
  
  Missing Configuration: The controlled object (e.g., cost center, internal order) may not be properly configured or may not exist in the system.
  Transfer Issues: The controlled object has not been transferred to the relevant controlling area or is not assigned correctly.
  Authorization Issues: The user may not have the necessary authorizations to access or transfer the controlled object.
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data related to the controlled object.
  Incorrect Settings: The settings in the controlling area or the object itself may not be aligned with the requirements for the transaction being executed.
  
  Solutions:
  
  Check Object Configuration: Verify that the controlled object is correctly configured in the system. Ensure that it exists and is active in the relevant controlling area.
  Transfer the Object: If the object has not been transferred, you may need to perform the necessary steps to transfer it to the controlling area. This can often be done through transaction codes like OKEQ (for cost centers) or KO01 (for internal orders).
  Review Authorizations: Ensure that the user has the necessary authorizations to access and manage the controlled object. This may involve checking user roles and profiles.
  Data Consistency Check: Run consistency checks on the master data and transaction data to identify and resolve any inconsistencies.
  Consult Documentation: Review SAP documentation or help resources for specific guidance related to the controlled object in question.
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OKEQ (Cost Center) and KO01 (Internal Order) for managing controlled objects.
  SAP Notes: Check SAP Notes for any known issues or patches related to the CMT072 error message.
  System Logs: Review system logs for additional error messages or warnings that may provide more context about the issue.
  Training and Documentation: Ensure that users are trained on the proper procedures for managing controlled objects in SAP.
  
  By following these steps, you should be able to identify the cause of the CMT072 error and implement a solution to resolve it.