Do you have any question about this error?
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
Only condition types that belong to <GL:condition_class>condition
class</> C, D or G are permitted in the settlement schema.
An incorrect settlement schema leads to errors when volume rebate
arrangements are settled.
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.
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 take the following steps:
Check Condition Type Configuration:
- Go to the configuration settings for the condition type in SAP (Transaction code:
V/06
).- Verify that the condition type is correctly defined and that it is allowed in the settlement schema you are using.
Review Settlement Schema:
- Check the configuration of the settlement schema (Transaction code:
OKO7
).- Ensure that the condition type is included in the schema and that it is compatible with the condition class.
Adjust Condition Class:
- If necessary, review the condition class settings (Transaction code:
V/07
) to ensure that the condition type can be used in the context of the settlement schema.Consult Documentation:
- Review SAP documentation or help resources related to condition types and settlement schemas to understand any specific restrictions or requirements.
Testing:
- After making any changes, test the settlement process again to ensure that the error is resolved.
Related Information:
Transaction Codes:
V/06
: Condition TypesOKO7
: Settlement SchemaV/07
: Condition ClassesSAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
User Roles: Ensure that you have the necessary authorizations to make changes to condition types and settlement schemas.
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in pricing and settlement processes.
Get instant SAP help. Start your 7-day free trial now.
MN651
Acct. key for provision missing for cond. type &1, settlement schema &2
What causes this issue? The account key for account determination for income and provisions is not entered in settlement schema &V2&.System R...
MN650
Calculation schema &1 used in purchase order and supplier billing doc.
What causes this issue? Calculation schema &V1& (application &V2&, usage &V3&) is used in both price determination and the su...
MN653
Subtotal &1 occurs several times in calculation schema &2
What causes this issue? Subtotal &V1& occurs several times in calculation schema &V2&.System Response In the case of condition types...
MN654
Subtotal &1 missing in payment schema &2 (see long text)
What causes this issue? In payment schema &V2&, subtotal &V1& does not occur first, i.e. it is entered underneath the first condition...
Click on this link to search all SAP messages.