How To Fix CQ071 - Error while inserting into PLMK: & records were not added (DB counter: &)


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 071

  • Message text: Error while inserting into PLMK: & records were not added (DB counter: &)

  • 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 CQ071 - Error while inserting into PLMK: & records were not added (DB counter: &) ?

    The SAP error message CQ071 indicates that there was an issue while trying to insert records into the PLMK (Plant Maintenance: Maintenance Task List) table. The message typically states that a certain number of records were not added, along with a database counter that indicates the number of records that failed to be inserted.

    Causes:

    1. Data Integrity Issues: The data being inserted may violate integrity constraints, such as primary key violations, foreign key constraints, or unique constraints.
    2. Database Locking: The table may be locked by another transaction, preventing the insertion of new records.
    3. Insufficient Authorizations: The user attempting the insertion may not have the necessary authorizations to perform the operation.
    4. Incorrect Data Format: The data being inserted may not conform to the expected format or data type defined in the PLMK table.
    5. System Configuration Issues: There may be configuration issues in the SAP system that affect the ability to write to the database.

    Solutions:

    1. Check Data Integrity: Review the data being inserted to ensure it meets all integrity constraints. Look for duplicate entries or invalid foreign key references.
    2. Release Locks: If the table is locked, identify the transaction that is holding the lock and either wait for it to complete or terminate it if appropriate.
    3. Review Authorizations: Ensure that the user has the necessary authorizations to perform the insertion. This may involve checking roles and permissions in the SAP system.
    4. Validate Data Format: Ensure that the data being inserted matches the expected format and data types for the PLMK table.
    5. Check System Logs: Review system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the failure.
    6. Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on similar issues.

    Related Information:

    • Transaction Codes: You may want to use transaction codes like SE11 (Data Dictionary) to view the structure of the PLMK table and understand its constraints.
    • Debugging: If you have access to debugging tools, you can use transaction SE80 or SE37 to debug the program or function module that is attempting the insertion.
    • SAP Community: Consider searching or posting in the SAP Community forums for additional insights from other users who may have encountered the same issue.

    If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker