Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TT - Extended Computer Aided Test Tool (eCATT) messages
Message number: 349
Message text: The start action was canceled in number & of & runs
When the log was formatted, a running transaction in a CATT procedure
has probably terminated.
It is fundamentally impossible to tell from the CATT log, when a
transaction is terminated, because that terminates the complete CATT
session. The log can then not be completed and closed. It is always
possible that the transaction is still active.
The only indication is the elapsed time. The log assumes that a
transaction has terminated if it started more than 20 minutes
previously.
If less than 20 minutes have elapsed, the message TT 148: 'The
procedure has been active
for & minutes' is entered in the log.
As the function refresh is no longer available after more than 20
minutes of transaction time, the log can be refreshed via F3 'Back' and
re-selection. It is possible that the CATT procedure may have
progressed in the meantime, if it contains long-running transactions.
As this becomes ever less likely as time passes, you should look for
the cause of termination in the system log.
Error message extract from SAP system. Copyright SAP SE.
TT349
- The start action was canceled in number & of & runs ?The SAP error message TT349, which states "The start action was canceled in number & of & runs," typically occurs in the context of SAP's background processing or job scheduling. This error indicates that a scheduled job or action was not able to start as expected, and it provides information about the number of runs affected.
Causes:
- Job Cancellation: The job may have been manually canceled by a user or an administrator.
- Resource Issues: There may be insufficient resources (e.g., memory, CPU) available to start the job.
- Configuration Issues: Incorrect configuration settings for the job or the system may prevent it from starting.
- Dependencies: The job may depend on other jobs or processes that have not completed successfully.
- Authorization Issues: The user or process attempting to start the job may lack the necessary authorizations.
- System Errors: There may be underlying system errors or issues that are preventing the job from starting.
Solutions:
- Check Job Status: Use transaction codes like
SM37
to check the status of the job and see if it was canceled or if there are any error messages associated with it.- Review Logs: Look at the job logs for any additional error messages or warnings that could provide more context about why the job was canceled.
- Resource Monitoring: Monitor system resources to ensure that there are enough resources available for the job to run.
- Configuration Review: Verify the job configuration settings to ensure they are correct and that all dependencies are met.
- Authorization Check: Ensure that the user or process has the necessary authorizations to execute the job.
- Retry the Job: If the issue was temporary, you may try to restart the job manually.
- Consult Documentation: Refer to SAP documentation or support notes for any specific guidance related to the error message TT349.
Related Information:
SM37
(Job Monitoring), SM36
(Job Scheduling), and SM21
(System Log) for troubleshooting.If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.
Get instant SAP help. Sign up for our Free Essentials Plan.
TT348
The test case has been active for & minutes
What causes this issue? The transaction being executed in the CATT procedure has not yet finished at the time of formatting the log.System Response ...
TT347
Referencing test case can only be called from Test Workbench
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TT350
Error & in application transaction &
What causes this issue? The transaction reported an error.System Response The message issued was not expected by the CATT procedure and was not flag...
TT351
Transaction & canceled by the user
What causes this issue? The transaction was terminated by the user.System Response User interaction takes place in foreground processing of a transa...
Click on this link to search all SAP messages.