Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix TT349 - The start action was canceled in number & of & runs


SAP Error Message - Details

  • 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

  • Show details Hide details
  • What causes this issue?

    When the log was formatted, a running transaction in a CATT procedure
    has probably terminated.

    System Response

    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.

    How to fix this error?

    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.


Smart SAP Assistant

  • What is the cause and solution for SAP error message 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:

    1. Job Cancellation: The job may have been manually canceled by a user or an administrator.
    2. Resource Issues: There may be insufficient resources (e.g., memory, CPU) available to start the job.
    3. Configuration Issues: Incorrect configuration settings for the job or the system may prevent it from starting.
    4. Dependencies: The job may depend on other jobs or processes that have not completed successfully.
    5. Authorization Issues: The user or process attempting to start the job may lack the necessary authorizations.
    6. System Errors: There may be underlying system errors or issues that are preventing the job from starting.

    Solutions:

    1. 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.
    2. 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.
    3. Resource Monitoring: Monitor system resources to ensure that there are enough resources available for the job to run.
    4. Configuration Review: Verify the job configuration settings to ensure they are correct and that all dependencies are met.
    5. Authorization Check: Ensure that the user or process has the necessary authorizations to execute the job.
    6. Retry the Job: If the issue was temporary, you may try to restart the job manually.
    7. Consult Documentation: Refer to SAP documentation or support notes for any specific guidance related to the error message TT349.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM36 (Job Scheduling), and SM21 (System Log) for troubleshooting.
    • SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
    • System Performance: Regularly monitor system performance and job scheduling to prevent resource-related issues.
    • User Training: Ensure that users involved in job scheduling and monitoring are adequately trained to handle job cancellations and errors.

    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.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
The AI Support Assistant is great. It provides comprehensive assistance even on the most difficult issues. I highly recommend this service.
Rate 1
John Jordan
SAP Consultant & Author