How To Fix CNV_MBT_CWB019 - Active execution package &1 is controlled by another control system

CNV_MBT_CWB019 - Overview

• Message type: E = Error

• Message class: CNV_MBT_CWB - Messages for CWB-PCL-Interface

• Message number: 019

• Message text: Active execution package &1 is controlled by another control system

What causes this issue?

You want to create a new package. In the execution system another
package is active which is controlled by another control system. That
means it is not assigned to a project existing on this control system
and therefore can't be deactivated.

How to fix this error?

Before creating your package you need to deactivate the current active
package in the execution system. If you have access to the other control
system and the authorization to the assigned procject you can deactivate
the package from this control system.
If you do not have access to the control system or the control system
does not exist anymore in your landscape and you are sure that this
package is not needed anymore you can also deactivate it as described
below:
Enter transaction SE37 in your control system.
Start function module CNV_MBT_CWB_ACTIVE_PACK_CHANGE
Enter the following parameters:
I_PCL_PACK,,,,,,keep empty
I_ACTION,,,,,,,,R
I_DESTINATION,,,,,,enter RFC destination ID to the execution system
I_SUPPRESS_POPUP,,,,keep empty
I_PROJECT,,,,,,,,keep empty
A popup will appear with the information of the current active package.
You need to confirm that this package can be deactivated.

Error message extract from SAP system. Copyright SAP SE.

CNV_MBT_CWB019 - Details

• The SAP error message CNV_MBT_CWB019 indicates that an active execution package is being controlled by another control system. This typically occurs in the context of data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools.
  
  Cause:
  
  Concurrent Execution: The error usually arises when there is an attempt to execute a migration package that is already being processed or controlled by another session or user.
  Locking Mechanism: SAP uses a locking mechanism to prevent multiple users from modifying the same execution package simultaneously, which can lead to data inconsistencies.
  Session Management: If a previous session was not properly closed or terminated, it may still hold control over the execution package.
  
  
  Solution:
  
  Check Active Sessions: Verify if there are any active sessions or users currently working on the same execution package. You can do this by checking the transaction codes like SM50 (Process Overview) or SM66 (Global Process Overview) to see if