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

Close

How To Fix WSTI_CALC021 - Parallel after &1 unsuccessful attempts


SAP Error Message - Details

  • Message type: E = Error

  • Message class: WSTI_CALC - Physical Inventory Messages: Book Inv. Calc. at Count Time

  • Message number: 021

  • Message text: Parallel after &1 unsuccessful attempts

  • Show details Hide details


  • 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 WSTI_CALC021 - Parallel after &1 unsuccessful attempts ?

    The SAP error message:

    WSTI_CALC021: Parallel after &1 unsuccessful attempts


    Meaning / Cause

    This error occurs in the SAP Workflow system, specifically related to the parallel processing of workflow tasks. The message indicates that the system tried to execute a parallel step (e.g., a parallel activity or parallel branch) after &1 unsuccessful attempts, but it failed to do so.

    In other words:

    • The workflow engine attempted to start or continue a parallel step.
    • It retried the operation multiple times (the number &1 is the number of attempts).
    • All attempts failed, so the system raises this error.

    This usually happens due to:

    • Locking issues: The workflow step or related objects are locked by other processes.
    • Database contention: Deadlocks or resource contention in the database.
    • System performance issues: High load causing timeouts or delays.
    • Incorrect workflow design: Parallel branches that conflict or cause synchronization problems.
    • Authorization or runtime errors: The user or system process lacks necessary permissions or encounters runtime exceptions.

    Where does it occur?

    • During workflow execution, especially when the workflow engine tries to process parallel steps.
    • In transaction SWI1 (Work Item Selection) or SWI2_FREQ (Work Item Analysis) you might see related work items stuck or in error status.
    • In workflow logs (transaction SWI2_DIAG or SWI6) you can find more details.

    Solution / Troubleshooting Steps

    1. Check Workflow Logs:

      • Use transaction SWI2_DIAG or SWI6 to analyze the workflow logs.
      • Identify which step or task is causing the problem.
      • Look for related error messages or dumps.
    2. Check for Locks:

      • Use transaction SM12 to check for locked entries related to the workflow objects.
      • If locks are stale or blocking, consider releasing them carefully.
    3. Check System Performance:

      • Review system load and database performance.
      • Check for deadlocks or long-running transactions in SM50, SM66, or database monitoring tools.
    4. Review Workflow Design:

      • Analyze the workflow model in SWDD.
      • Ensure parallel branches are designed correctly and do not cause conflicts.
      • Avoid unnecessary parallelism if it causes issues.
    5. Check Authorizations:

      • Verify that the user or system process executing the workflow has the necessary authorizations.
    6. Restart Workflow:

      • Sometimes, restarting the workflow or the affected work items can help.
      • Use SWI1 or SWI2_FREQ to find and restart or delete problematic work items.
    7. Apply SAP Notes:

      • Search for SAP Notes related to WSTI_CALC021.
      • There might be patches or corrections available.

    Additional Information

    • The message class WSTI_CALC relates to workflow step calculation.
    • The parameter &1 indicates the number of unsuccessful attempts.
    • The workflow engine tries multiple times to process steps to handle transient issues.
    • Persistent failure indicates a deeper problem that needs investigation.

    Summary

    Aspect Details
    Error WSTI_CALC021: Parallel after &1 unsuccessful attempts
    Cause Workflow engine failed to process parallel step after multiple retries (locking, DB, design)
    Solution Check workflow logs, locks, system performance, workflow design, authorizations, restart workflow, apply SAP Notes
    Transactions SWI1, SWI2_FREQ, SWI2_DIAG, SWI6, SM12, SM50, SM66

    If you provide more context (workflow ID, step, system version), I can help you with more specific guidance or SAP Notes references.

    • 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