How To Fix QT220 - Confirmation is expected via process message

SAP Error Message - Details

• Message type: E = Error

• Message class: QT - QM: Inspection during production (with inspection points)

• Message number: 220

• Message text: Confirmation is expected via process message

What causes this issue?

The material that was inspected was created using a process order. This
means that:
confirmation is expected to take place via a process message or by
calling up a function from the PI sheet.
the operation quantities that have been processed must be confirmed.
This may not be the same as the product quantity that was created,
which is recorded in the inspection point.

System Response

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

How to fix this error?

RESET N1
You should check whether
a confirmation from process control is planned in the process order
the operation quantity and the inspection point quantity are different
You should then only trigger the confirmation from QM, if neither of
these possibilities apply.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message QT220 - Confirmation is expected via process message ?

  The SAP error message QT220 ("Confirmation is expected via process message") typically occurs in the context of production planning and execution, particularly when dealing with process orders or production orders in SAP. This message indicates that the system is expecting a confirmation for a process message that has not yet been received.
  Cause:
  
  Missing Confirmation: The most common cause is that a confirmation for a process message (like a production order or process order) has not been entered in the system.
  Process Message Not Triggered: The process message that should trigger the confirmation might not have been generated or sent correctly.
  System Configuration: There may be issues with the configuration of the process messages in the system, leading to the expectation of a confirmation that is not being fulfilled.
  User Error: The user may have forgotten to enter the confirmation or may have entered it incorrectly.
  
  Solution:
  
  Enter Confirmation: Check if the confirmation for the process message has been entered. If not, enter the confirmation using the appropriate transaction (e.g., CO11N for production orders).
  Check Process Messages: Review the process messages related to the order in question. You can do this through transaction codes like COHV (for mass processing of production orders) or CO02 (to change production orders).
  Review Configuration: If the issue persists, review the configuration settings for process messages in the system. Ensure that the settings are correct and that the system is set up to handle confirmations as expected.
  Check for Errors: Look for any errors in the logs that might indicate why the confirmation was not processed. This can be done through transaction codes like SLG1 (Application Log).
  Consult Documentation: Refer to SAP documentation or help resources for specific details on handling process messages and confirmations.
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CO11N (Enter Production Order Confirmation), CO02 (Change Production Order), and COHV (Mass Processing of Production Orders).
  Process Messages: Understand the role of process messages in production planning and how they interact with confirmations.
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific fixes or patches that address known issues.
  User Training: Ensure that users are trained on the correct procedures for entering confirmations and handling process messages to minimize the occurrence of this error.
  
  By following these steps, you should be able to identify the cause of the QT220 error and implement a solution to resolve it.