How To Fix MN880 - Condition type &1 was removed from calc. schema &2 (no updating)

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 880

• Message text: Condition type &1 was removed from calc. schema &2 (no updating)

What causes this issue?

Condition type &V1& no longer exists in calculation schema &V2& of the
document.

System Response

Therefore, no business volume is updated in the documet during
recompilation.

How to fix this error?

Please look into this matter. You may have to enter the condition type
in the schema again.
The recompiliation for arrangement &V3& must then be repeated to ensure
that business volume data is correct.
As the business volume data for the document is to be recompiled, the
only possible reason for this problem is that condition type &V1& has
been deleted from calculation schema &V2&.

<ds:SIMG.SIMG_CFMENUOLMEOMER5>Maintain calculation schema</>
ENDIF

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 MN880 - Condition type &1 was removed from calc. schema &2 (no updating) ?

  The SAP error message MN880 indicates that a specific condition type (denoted as &1) has been removed from the calculation schema (denoted as &2) and that there is no updating taking place for that condition type. This error typically occurs in the context of pricing or condition records in SAP, particularly in the Sales and Distribution (SD) module or the Materials Management (MM) module.
  Cause:
  
  Condition Type Removal: The condition type specified in the error message has been removed from the pricing procedure or calculation schema. This could happen due to changes in configuration or updates to the pricing procedure.
  Incorrect Configuration: The pricing procedure may not be correctly configured to include the condition type, or the condition type may not be relevant for the current transaction.
  Condition Records: There may be no valid condition records for the specified condition type, leading to its exclusion from the calculation.
  Transaction Type: The transaction type being processed may not support the condition type in question.
  
  Solution:
  
  
  Check Pricing Procedure: Review the pricing procedure assigned to the relevant sales document or purchasing document. Ensure that the condition type is included in the pricing procedure.
  
  Go to transaction code V/08 (for SD) or M/08 (for MM) to check and modify the pricing procedure.
  
  
  
  Review Condition Type Configuration: Verify the configuration of the condition type in transaction code V/06 (for SD) or M/06 (for MM). Ensure that it is set up correctly and is active.
  
  
  Check Condition Records: Ensure that there are valid condition records for the condition type. You can check this using transaction code VK11 (for SD) or MK11 (for MM) to create or display condition records.
  
  
  Transaction Type Compatibility: Ensure that the transaction type being processed is compatible with the condition type. If necessary, adjust the configuration to allow for the condition type in the relevant transaction.
  
  
  Consult Documentation: If the issue persists, consult SAP documentation or reach out to your SAP support team for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as V/08, V/06, VK11, M/08, and M/06 for managing pricing procedures and condition types.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on this error message.
  Testing: After making changes, perform tests to ensure that the condition type is now being processed correctly in the calculation schema.
  
  By following these steps, you should be able to resolve the MN880 error and ensure that the condition type is properly included in the calculation schema.