How To Fix MQ670 - Conversion started as test run -> No changes to database

SAP Error Message - Details

• Message type: E = Error

• Message class: MQ - Messages for Euro Changeover Package

• Message number: 670

• Message text: Conversion started as test run -> No changes to database

What causes this issue?

The conversion program was started as a test run.
This means that the fields are converted normally as in an update run
but that the changed data is not updated in the database.
The conversion results contain the values for the records read and
converted as they would have been in the update run.

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?

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 MQ670 - Conversion started as test run -> No changes to database ?

  The SAP error message MQ670, which states "Conversion started as test run -> No changes to database," typically occurs during a data conversion or migration process in SAP. This message indicates that the conversion process was initiated in test mode, meaning that no actual changes will be made to the database. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Test Run Mode: The conversion process was executed in test mode (often indicated by a specific parameter or flag), which is designed to simulate the conversion without making any changes to the database. This is useful for validating the process and identifying potential issues before performing the actual conversion.
  
  Solution:
  
  
  Check Execution Parameters: Review the parameters used to start the conversion process. If you intended to perform a real conversion, ensure that the test mode flag is not set. This may involve changing a parameter in the transaction or program you are using.
  
  
  Run in Production Mode: If you are ready to proceed with the actual conversion, execute the conversion program again, ensuring that it is set to run in production mode (i.e., without the test run flag).
  
  
  Review Logs and Messages: Check the logs generated during the test run for any warnings or errors that may need to be addressed before running the actual conversion.
  
  
  Consult Documentation: Refer to the SAP documentation or notes related to the specific conversion program you are using. There may be specific instructions or prerequisites that need to be followed.
  
  
  Backup Data: Before running any conversion in production mode, ensure that you have a complete backup of your database to prevent data loss in case of issues during the conversion.
  
  
  Related Information:
  
  Transaction Codes: Depending on the context of the conversion, you may be using specific transaction codes (e.g., SGEN for generating objects, or others related to data migration).
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to the conversion process you are undertaking.
  Testing Procedures: It is a best practice to always perform a test run before executing any data conversion in a production environment to identify potential issues.
  
  If you continue to encounter issues or if the conversion process is complex, consider reaching out to your SAP Basis team or SAP support for further assistance.