How To Fix CQ072 - Error while deleting from PLMK: & records were not deleted (DB counter:&)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 072

• Message text: Error while deleting from PLMK: & records were not deleted (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 CQ072 - Error while deleting from PLMK: & records were not deleted (DB counter:&) ?

  The SAP error message CQ072 indicates that there was an issue while attempting to delete records from the PLMK (Planning Data for Material) table. The message specifies that a certain number of records were not deleted, and it also provides a database counter that indicates how many records were affected.
  Cause:
  The error can occur due to several reasons, including:
  
  
  Foreign Key Constraints: There may be foreign key constraints in the database that prevent the deletion of records. If other tables reference the records in PLMK, the deletion will fail.
  
  
  Locking Issues: The records you are trying to delete may be locked by another transaction or user, preventing the deletion.
  
  
  Authorization Issues: The user executing the deletion may not have the necessary authorizations to delete the records.
  
  
  Data Integrity Issues: There may be data integrity issues that prevent the deletion of certain records.
  
  
  System Errors: There could be temporary system errors or inconsistencies in the database.
  
  
  Solution:
  To resolve the CQ072 error, you can take the following steps:
  
  
  Check Foreign Key Constraints: Review the database schema to identify any foreign key constraints that may be preventing the deletion. You may need to delete or update related records in other tables first.
  
  
  Check for Locks: Use transaction codes like SM12 (to check for locks) to see if the records are locked by another user or process. If they are, you may need to wait for the lock to be released or contact the user who holds the lock.
  
  
  Review Authorizations: Ensure that the user has the necessary authorizations to delete records from the PLMK table. You may need to consult with your SAP security team.
  
  
  Check for Data Integrity Issues: Investigate if there are any data integrity issues that need to be resolved before deletion. This may involve checking for orphaned records or inconsistencies.
  
  
  Use Transaction Codes: If you are using a specific transaction to delete records, ensure that you are following the correct procedure. You may also want to try using transaction codes like SE14 (Database Utility) to perform the deletion.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  
  Log Analysis: Review the application logs (transaction SLG1) for more detailed error messages that may provide additional context for the failure.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE14 (Database Utility), and SM12 (Lock Entries).
  SAP Documentation: Refer to SAP Help documentation for more information on PLMK and related tables.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical team for further investigation.