How To Fix ECATT348 - The test script has been active for &

ECATT348 - Overview

• Message type: E = Error

• Message class: ECATT - eCATT Messages (Middleware and GUI)

• Message number: 348

• Message text: The test script has been active for &

What causes this issue?

When the system prepared the log, the transaction that was started in
eCATT had not been terminated.

System Response

After starting eCATT you can display the log simultaneously in a
different session, even if a transaction is still active.
This message appears only when the time between the start of the
transaction and the log preparation is less than 20 minutes. After 20
minutes the system assumes that the transaction was terminated and
shows the corresponding message.

How to fix this error?

You can repeat the log preparation by selecting "Back" (F3) and
renewing the selection. In this case the system updates the transaction
time or eCATT functions complete the log.

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message ECATT348 - The test script has been active for & ?

  The SAP error message ECATT348 indicates that a test script in the eCATT (extended Computer Aided Test Tool) framework has been active for a certain period of time, which is specified by the placeholder "&". This message typically arises when a test script is running longer than expected, which can be due to various reasons.
  Causes:
  
  Long Execution Time: The test script may be executing a large number of transactions or complex operations that take longer than usual.
  System Performance Issues: The SAP system may be experiencing performance issues, such as high load or resource contention, causing the script to run slowly.
  Infinite Loops: There may be a logical error in the script, such as an infinite loop or a condition that is never met, causing the script to hang.
  External Dependencies: The script may be waiting for responses from external systems or services that are slow or unresponsive.
  
  Solutions:
  
  Review the Script: Check the logic of