How To Fix CQ070 - Error while updating PLMK: & records were not changed (DB counter: &)

SAP Error Message - Details

• Message type: E = Error

• Message class: CQ - Messages for buffer table processing (QM in task list)

• Message number: 070

• Message text: Error while updating PLMK: & records were not changed (DB counter: &)

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 CQ070 - Error while updating PLMK: & records were not changed (DB counter: &) ?

  The SAP error message CQ070 indicates that there was an issue while updating the PLMK (Product Lifecycle Management Master Data) records. The message specifically states that a certain number of records were not changed, and it includes a database counter that provides additional context about the operation.
  Cause:
  The error can occur due to several reasons, including:
  
  Concurrency Issues: If multiple users or processes are trying to update the same records simultaneously, it can lead to conflicts, resulting in this error.
  Data Locking: The records you are trying to update may be locked by another transaction or user, preventing your update from being applied.
  Incorrect Data: The data being submitted for the update may not meet the required criteria or constraints, leading to a failure in the update process.
  Database Issues: There may be underlying database issues, such as corruption or connectivity problems, that prevent the update from being executed.
  Authorization Issues: The user may not have the necessary permissions to update the records.
  
  Solution:
  To resolve the CQ070 error, you can take the following steps:
  
  Check for Locks: Use transaction codes like SM12 to check for any locks on the records you are trying to update. If you find locks, you may need to wait for them to be released or contact the user who holds the lock.
  Review Data: Ensure that the data you are trying to update is valid and meets all necessary criteria. Check for any required fields that may be missing or incorrectly formatted.
  Retry the Update: If the error was caused by a temporary issue (like a lock), retry the update after a short period.
  Check Authorizations: Ensure that you have the necessary authorizations to perform the update. You may need to contact your SAP security team if you suspect authorization issues.
  Consult Logs: Check the application logs (transaction SLG1) for more detailed error messages that can provide additional context about the failure.
  Database Health Check: If you suspect database issues, consult your database administrator to check the health of the database and resolve any underlying issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to check locks), SLG1 (to view application logs), and SE11 (to view table definitions).
  SAP Notes: Search for SAP Notes related to the error message CQ070 in the SAP Support Portal. There may be specific patches or updates that address known issues.
  Documentation: Review SAP documentation related to PLMK and the specific transaction or process you are working with to ensure you are following the correct procedures.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.