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

MN880 - Overview

• 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