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

Close

How To Fix WGDS_PROCESS668 - Catalogue &1/&2 locked and cannot be processed


SAP Error Message - Details

  • Message type: E = Error

  • Message class: WGDS_PROCESS - Global data synchronisation

  • Message number: 668

  • Message text: Catalogue &1/&2 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_PROCESS668 - Catalogue &1/&2 locked and cannot be processed ?

    The SAP error message:

    WGDS_PROCESS668: Catalogue &1/&2 locked and cannot be processed


    Meaning / Cause:

    This error occurs when you try to process a catalogue (e.g., a purchasing catalogue or service catalogue) that is currently locked in the system. The lock prevents simultaneous changes or processing by multiple users or processes to maintain data consistency and integrity.

    The placeholders &1 and &2 represent the catalogue type and catalogue number or version, respectively.

    Typical causes:

    • The catalogue is currently being edited or processed by another user or background job.
    • A previous process did not release the lock properly due to an error or system crash.
    • The catalogue is locked for change due to a workflow or approval process.

    Solution:

    1. Check who holds the lock:

      • Use transaction SM12 (Lock Entries) to find and analyze the lock entries related to the catalogue.
      • Search for lock objects related to the catalogue number or type.
      • Identify the user or process holding the lock.
    2. Release the lock if appropriate:

      • If the lock is held by a user who is no longer working on it or a stuck process, you can delete the lock entry in SM12.
      • Be cautious when deleting locks to avoid data inconsistencies.
    3. Wait for the lock to be released:

      • If the lock is held by an active user or process, coordinate with them to finish their work and release the lock.
    4. Check background jobs or workflows:

      • Sometimes background jobs or workflows lock catalogues during processing.
      • Verify if any jobs are running or stuck and handle accordingly.
    5. System restart or support:

      • If locks persist due to system issues, a system restart or SAP support intervention may be required.

    Related Information:

    • Lock Objects: SAP uses lock objects to synchronize access to master data and transactional data. For catalogues, the lock object might be something like EINK_CATALOG or similar.
    • Transaction SM12: Used to monitor and manage lock entries.
    • Catalogue Processing Transactions: Depending on the catalogue type, transactions like ME31K (Create Contract), ME32K (Change Contract), or specific service catalogue transactions might be involved.
    • SAP Notes: Check SAP Notes for any known bugs or patches related to catalogue locking issues.
    • User Authorization: Ensure users have proper authorization to process or unlock catalogues.

    Summary:

    • Cause: Catalogue is locked by another user/process.
    • Solution: Identify and release the lock via SM12 or wait for the lock to be released.
    • Precaution: Avoid deleting locks without understanding the impact.

    If you provide the exact catalogue type and transaction you are using, I can help with more specific guidance.

    • 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