How To Fix EARC604 - Program started in test run

SAP Error Message - Details

• Message type: E = Error

• Message class: EARC - IS-U: Archiving

• Message number: 604

• Message text: Program started in test run

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message EARC604 - Program started in test run ?

  The SAP error message EARC604, which states "Program started in test run," typically occurs when a program or transaction is executed in a mode that is intended for testing rather than actual execution. This is often seen in batch jobs or when running certain reports or transactions that have a test mode option.
  Cause:
  
  Test Mode Activation: The program was started with a test mode flag, which means it will not make any changes to the database or perform any actions that would affect the system state.
  User Settings: The user may have inadvertently set the program to run in test mode, either through transaction parameters or user profile settings.
  Job Scheduling: If the program is scheduled as a background job, it might have been configured to run in test mode.
  
  Solution:
  
  Check Execution Parameters: Review the parameters used to start the program. If it was started with a test flag (often denoted as "TEST" or similar), remove this flag to allow the program to run in actual mode.
  Modify Job Settings: If the program is scheduled as a background job, check the job settings in transaction SM37 or SM36. Ensure that the job is not set to run in test mode.
  User Profile Settings: Check if there are any user-specific settings that default the execution to test mode. This can be done in transaction SU01 (User Maintenance).
  Consult Documentation: Refer to the documentation for the specific program or transaction to understand how to properly execute it in production mode.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SM37 (to monitor jobs) or SM36 (to schedule jobs) to check the status and settings of the job.
  SAP Notes: Look for relevant SAP Notes that might address this specific error or provide additional context.
  Testing vs. Production: Understand the difference between test and production runs in SAP, as running in test mode is useful for validation but will not affect the actual data.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP Basis or technical team for further investigation.