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: WGDS_PROCESS - Global data synchronisation
Message number: 668
Message text: Catalogue &1/&2 locked and cannot be processed
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.
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.
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:
Check who holds the lock:
Release the lock if appropriate:
Wait for the lock to be released:
Check background jobs or workflows:
System restart or support:
EINK_CATALOG
or similar.If you provide the exact catalogue type and transaction you are using, I can help with more specific guidance.
Get instant SAP help. Sign up for our Free Essentials Plan.
WGDS_PROCESS667
Could not find any order in package &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WGDS_PROCESS666
Could not find package &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WGDS_PROCESS669
Report is already running in daemon mode
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WGDS_PROCESS670
Daemon started as job id "&1", name "&2"
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.