How To Fix MN652 - Cond. type &1 of condition class &2 not allowed in settlement schema &3

MN652 - Overview

• Message type: E = Error

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

• Message number: 652

• Message text: Cond. type &1 of condition class &2 not allowed in settlement schema &3

What causes this issue?

Only condition types that belong to <GL:condition_class>condition
class</> C, D or G are permitted in the settlement schema.

System Response

An incorrect settlement schema leads to errors when volume rebate
arrangements are settled.

How to fix this error?

Check your system settings. It is possible that the calculation schema
has been incorrectly assigned as a settlement schema in Customizing.
Otherwise, correct any incorrect entries.
<DS:SIMG.SIMG_CFMENUOLMEKONDT>Set up condition technique</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN652 - Cond. type &1 of condition class &2 not allowed in settlement schema &3 ?

  The SAP error message MN652 indicates that there is an issue with a condition type in the context of a settlement schema. Specifically, it states that the condition type (denoted as &1) of a certain condition class (denoted as &2) is not allowed in the specified settlement schema (denoted as &3). 
  
  Cause:
  This error typically arises due to one of the following reasons:
  
  
  Incorrect Configuration: The condition type you are trying to use is not configured to be part of the specified settlement schema. This could be due to a misconfiguration in the condition type settings or the settlement schema settings.
  
  
  Condition Class Restrictions: The condition class associated with the condition type may have restrictions that prevent it from being used in the specified settlement schema.
  
  
  Settlement Schema Definition: The settlement schema itself may not be set up to accept certain condition types based on business rules or requirements.
  
  
  
  Solution:
  To resolve this error, you can