How To Fix QG173 - Status records were recovered

QG173 - Overview

• Message type: E = Error

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

• Message number: 173

• Message text: Status records were recovered

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:
  
  Data Inconsistencies: There may be inconsistencies in the status records due to incomplete transactions or system errors.
  Database Issues: Problems with the database, such as corruption or locking issues, can lead to status records not being properly updated or retrieved.
  User Actions: Manual interventions or incorrect processing of quality inspection lots can lead to status discrepancies.
  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:
  
  Check Logs: Review the application logs (transaction