How To Fix QG173 - Status records were recovered


SAP Error Message - Details

  • Message type: E = Error

  • Message class: QG - QM: Evaluation of inspection results

  • Message number: 173

  • Message text: Status records were recovered

  • Show details Hide details
  • What causes this issue?

    When the system accessed the archive, it couldn't locate status records
    for one or more inspection lots.

    System Response

    In order to display the inspection lot, the system recovered several
    (but not all) of the status records. To identify the inspection lot,
    the status "Locked" (I0043) was set. This status normally does not
    exist for archived inspection lots.

    How to fix this error?

    Note that the status information was not taken from the original
    archived
    inspection lot, and that this information therefore may not correspond
    to the actual status before archiving. The problem of the missing
    status records was solved in note 519977. The original data, however,
    cannot be recreated. If you want to determine which inspection lots
    were affected, you can do so by selecting using a suitable selection
    profile, which queries the status "Locked".

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message QG173 - Status records were recovered ?

    The SAP error message QG173, which states "Status records were recovered," typically occurs in the context of Quality Management (QM) within SAP. This message indicates that the system has encountered an issue with the status records of a quality inspection lot or a related object, and it has taken corrective action to recover the status records.

    Cause:

    The error can be caused by several factors, including:

    1. Data Inconsistencies: There may be inconsistencies in the status records due to incomplete transactions or system errors.
    2. Database Issues: Problems with the database, such as corruption or locking issues, can lead to status records not being properly updated or retrieved.
    3. User Actions: Manual interventions or incorrect processing of quality inspection lots can lead to status discrepancies.
    4. System Configuration: Incorrect configuration settings in the QM module may lead to unexpected behavior.

    Solution:

    To resolve the issue indicated by the QG173 message, you can take the following steps:

    1. Check Logs: Review the application logs (transaction SLG1) for more detailed information about the error and the context in which it occurred.
    2. Inspect the Inspection Lot: Use transaction code QA03 to display the inspection lot and check its status. Ensure that all required steps have been completed.
    3. Reprocess the Lot: If the inspection lot is in an inconsistent state, you may need to reprocess it. This could involve redoing certain quality checks or resetting the status.
    4. Database Consistency Check: Perform a consistency check on the database to identify and resolve any underlying issues. This may require the assistance of your SAP Basis team.
    5. Review Configuration: Ensure that the QM module is correctly configured. Check for any recent changes that may have affected the status handling.
    6. Consult SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide guidance on similar issues.
    7. Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for further assistance.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as QA01 (Create Inspection Lot), QA02 (Change Inspection Lot), and QA03 (Display Inspection Lot).
    • Quality Management Documentation: Review SAP documentation related to Quality Management for best practices and troubleshooting tips.
    • 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 address the QG173 error and ensure that your quality management processes are functioning smoothly.

    • 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 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