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

Close

How To Fix QM668 - Affected object list with key &1 and &2 not found


SAP Error Message - Details

  • Message type: E = Error

  • Message class: QM - Messages for quality notifications

  • Message number: 668

  • Message text: Affected object list with key &1 and &2 not found

  • 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 QM668 - Affected object list with key &1 and &2 not found ?

    The SAP error message QM668, which states "Affected object list with key &1 and &2 not found," typically occurs in the Quality Management (QM) module when the system is unable to find a specific object or record that is expected to exist based on the provided keys. This can happen in various scenarios, such as during the processing of quality notifications, inspection lots, or other QM-related transactions.

    Causes:

    1. Missing Data: The object you are trying to access may not exist in the database. This could be due to data not being created or deleted.
    2. Incorrect Keys: The keys provided in the transaction may be incorrect or not match any existing records.
    3. Authorization Issues: The user may not have the necessary authorizations to view the object.
    4. Data Consistency Issues: There may be inconsistencies in the database, such as missing links between related objects.
    5. System Configuration: The system may not be configured correctly to handle the specific type of object you are trying to access.

    Solutions:

    1. Verify Object Existence: Check if the object with the specified keys actually exists in the system. You can do this by using transaction codes relevant to the object type (e.g., QA32 for inspection lots, QM01 for quality notifications).
    2. Check Input Keys: Ensure that the keys you are entering are correct. Double-check for typos or incorrect values.
    3. Review Authorizations: Make sure that the user has the necessary authorizations to access the object. You may need to consult with your SAP security team.
    4. Data Consistency Check: Run consistency checks or reports to identify any issues with the data. This may involve checking for orphaned records or missing links.
    5. Consult Documentation: Review SAP documentation or notes related to the specific transaction or object type for any known issues or additional troubleshooting steps.
    6. Contact Support: If the issue persists, consider reaching out to SAP support for further assistance, especially if it appears to be a system bug or configuration issue.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes in the QM module, such as QA01 (Create Quality Notification), QA02 (Change Quality Notification), QA03 (Display Quality Notification), QA32 (Display Inspection Lot), etc.
    • SAP Notes: Check SAP Notes for any known issues or patches related to the error message QM668.
    • User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.

    By following these steps, you should be able to diagnose and resolve the issue related to the QM668 error message.

    • 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
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant