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

Close

How To Fix WGDS_PROCESS663 - Trade item &1 is locked and cannot be processed


SAP Error Message - Details

  • Message type: E = Error

  • Message class: WGDS_PROCESS - Global data synchronisation

  • Message number: 663

  • Message text: Trade item &1 is locked and cannot be processed

  • 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 WGDS_PROCESS663 - Trade item &1 is locked and cannot be processed ?

    Certainly! Here's a detailed explanation regarding the SAP error message:


    SAP Error Message:

    WGDS_PROCESS663: Trade item &1 is locked and cannot be processed


    Cause:

    This error occurs when a trade item (such as a product or material master record in the SAP Global Trade Services (GTS) or SAP EWM system) is currently locked by another user or process. The lock prevents simultaneous changes or processing to ensure data consistency and avoid conflicts.

    Typical reasons for the lock include:

    • Another user is editing or processing the same trade item.
    • A background job or batch process is currently working on the trade item.
    • A previous process did not release the lock properly due to an error or system crash.

    Solution:

    1. Identify the Lock Owner:

      • Use transaction SM12 (Lock Entries) to check which user or process holds the lock on the trade item.
      • Search for the lock object related to the trade item (usually by material number or trade item ID).
    2. Wait or Communicate:

      • If the lock is held by another user, coordinate with them to finish their work and release the lock.
    3. Manually Remove the Lock (if appropriate):

      • If the lock is stale (e.g., due to a crashed session), and you have authorization, you can delete the lock entry in SM12.
      • Be cautious when deleting locks to avoid data inconsistencies.
    4. Check Background Jobs:

      • Verify if any batch jobs or processes are running that might be locking the trade item.
      • Wait for the job to complete or investigate if it is stuck.
    5. System Restart (last resort):

      • If locks persist and cannot be cleared, a system restart might be necessary, but this is rarely required and should be done with caution.

    Related Information:

    • Lock Objects:
      The lock is managed by SAP lock objects related to trade items, such as EWM_TRADE_ITEM or similar, depending on the module.

    • Transactions to Use:

      • SM12: Display and delete lock entries.
      • SM21: System log to check for errors related to locking.
      • SM37: Check background jobs that might be locking the item.
    • Modules Involved:

      • SAP Global Trade Services (GTS)
      • SAP Extended Warehouse Management (EWM)
      • SAP ERP Material Management (MM) in some cases
    • Preventive Measures:

      • Ensure proper session management and user training to avoid leaving transactions open unnecessarily.
      • Monitor batch jobs and system performance to prevent long-running locks.

    If you provide the exact module or context (e.g., GTS, EWM), I can tailor the solution further.

    • 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
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant