How To Fix CNVMBT137 - Call Extended Process Monitor to view subactivity status details

CNVMBT137 - Overview

• Message type: E = Error

• Message class: CNVMBT - Messages for MBT/API/PCL

• Message number: 137

• Message text: Call Extended Process Monitor to view subactivity status details

What causes this issue?

The given activity execution was not performed by a single process - but
by a set of subactivity processes . The final status of the given
execution is a cumulated status of all assigned subactivites (Tasks) .
Complete information of each subactivity status and related logs is
available in Extended Process Monitor .

System Response

How to fix this error?

Call Extended Process Monitor by executing the respective function in
Process Tree / Monitor Task bar .
Alternatively - execute TASK Icon directly placed in the line of
activity execution to directly navigate to subactivity overview .

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.

CNVMBT137 - Details

• The SAP error message CNVMBT137 indicates that there is an issue related to the data migration process, specifically in the context of the SAP Landscape Transformation (SLT) or the SAP Data Migration process. This message suggests that you should check the Extended Process Monitor to get more details about the subactivity status.
  
  Cause:
  The error typically arises when there is a problem during the execution of a migration activity. This could be due to various reasons, such as:
  
  Data inconsistencies or errors in the source data.
  Configuration issues in the migration settings.
  Network issues or timeouts during data transfer.
  Missing authorizations or roles for the user executing the migration.
  System performance issues leading to delays or failures in processing.
  
  
  Solution:
  To resolve the CNVMBT137 error, follow these steps:
  
  
  Check the Extended Process Monitor:
  
  Go to the transaction code SCC3 or SCC4 (depending on your SAP version) to access the Extended Process Monitor.
  Look for the specific migration job that triggered the error