How To Fix WRF_UPGRADE_MSG035 - Cannot migrate all plants

SAP Error Message - Details

• Message type: E = Error

• Message class: WRF_UPGRADE_MSG -

• Message number: 035

• Message text: Cannot migrate all plants

What causes this issue?

Not all sites/plants can be converted because the system detected
errors.

System Response

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

How to fix this error?

Execute report UPGBA_DISPLAY_REPORT_LOG with LOGID LOGID
MIGRATION_CV_BP. This report displays all messages that were written
during the migration process.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WRF_UPGRADE_MSG035 - Cannot migrate all plants ?

  The SAP error message WRF_UPGRADE_MSG035 indicates that there is an issue during the migration process of plants in the SAP system. This error typically arises during system upgrades or migrations, particularly when moving from one version of SAP to another or when consolidating data from multiple systems.
  Causes:
  
  Data Inconsistencies: There may be inconsistencies in the data related to the plants that are being migrated. This could include missing or incorrect entries in the relevant tables.
  Configuration Issues: The configuration settings for the plants may not be compatible with the new system or version.
  Dependencies: There may be dependencies on other objects or configurations that are not being met during the migration process.
  Authorization Issues: The user performing the migration may not have the necessary authorizations to access or modify the plant data.
  Technical Errors: There could be technical issues such as database locks, system performance problems, or other errors that prevent the migration from completing successfully.
  
  Solutions:
  
  Check Data Consistency: Review the data for the plants that are failing to migrate. Ensure that all required fields are populated and that there are no inconsistencies.
  Review Configuration: Verify that the configuration settings for the plants are correct and compatible with the new system. This may involve checking settings in the SPRO transaction.
  Analyze Dependencies: Identify any dependencies that may be causing the migration to fail. Ensure that all related objects are also migrated or configured correctly.
  User Authorizations: Ensure that the user performing the migration has the necessary authorizations to access and modify plant data.
  Check Logs: Review the migration logs for any additional error messages or warnings that may provide more context about the failure.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide guidance on migration issues.
  Testing: If possible, perform the migration in a test environment first to identify and resolve any issues before attempting it in the production environment.
  
  Related Information:
  
  SAP Notes: Look for specific SAP Notes related to the migration process and the error message. These notes often contain patches, workarounds, or additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Review the official SAP documentation regarding the migration process for your specific version and module to ensure compliance with best practices.
  
  If the issue persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.