How To Fix O3329 - QCI check results are inconsistent

O3329 - Overview

• Message type: E = Error

• Message class: O3 - IS-Oil: HPM messages (goods movements, QCI, deliveries)

• Message number: 329

• Message text: QCI check results are inconsistent

What causes this issue?

Once a default set has been created, it has to be activated before it is
used for quantity conversion calculations. During activation, the
Quantity Conversion Interface (QCI) checks the set for consistency. A
trial quantity conversion is carried out. If a set is not consistent, in
other words would lead to an error message within the QCI, it cannot be
activated. The parameters have to be changed so that the trial
conversion does not fail. Once a set has been activated, it can no
longer be deleted.
In this case, the QCI has carried out the quantity conversion, but the
resulting quantity differs from the transaction quantity, although the
units of measure are identical.

System Response

The default set cannot be activated.

How to fix this error?

Check the QCI conversion using the desktop calculator function
(Transaction O3QCITEST).

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message O3329 - QCI check results are inconsistent ?

  The SAP error message O3329, which states "QCI check results are inconsistent," typically relates to Quality Inspection (QI) processes in SAP. This error can occur during the Quality Management (QM) module operations, particularly when there are inconsistencies in the quality inspection results or data.
  Causes:
  
  Inconsistent Data: The error often arises when there are discrepancies between the inspection lot data and the results recorded in the system. This could be due to manual entry errors or data corruption.
  Incomplete Inspection Results: If the inspection results have not been fully recorded or if there are missing entries, the system may flag this inconsistency.
  
  Configuration Issues: Incorrect configuration settings in the Quality Management module can lead to inconsistencies in how data is processed and checked.
  Batch Management Issues: If batch management is enabled, inconsistencies in batch data can also trigger this error.
  User Authorizations: Sometimes, insufficient user authorizations can prevent proper data entry or updates, leading to inconsistencies.
  
  Solutions:
  
  Check