Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 260
Message text: Condition class & of condition record not allowed
A program or function module within the subsequent settlement
functionality has been called up with a condition record that does not
belong to condition class 'C'. This is not allowed.
The arrangement involved has the number &V3&; the condition record has
the (internal) number &V4&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
&WHAT_TO_DO& (system administrator)Error message extract from SAP system. Copyright SAP SE.
MN260
- Condition class & of condition record not allowed ?The SAP error message MN260, which states "Condition class & of condition record not allowed," typically occurs in the context of pricing and condition records in SAP. This error indicates that there is an issue with the condition class associated with a pricing condition record that you are trying to use in a transaction.
Cause: Invalid Condition Class: The condition class of the condition record you are trying to use is not valid for the operation you are performing. This could be due to the condition type being incorrectly configured or not allowed in the current context.
Configuration Issues: The condition type may not be properly configured in the pricing procedure, or it may not be assigned to the relevant pricing procedure for the transaction. Missing Condition Records: The condition record you are trying to access may not exist for the specified condition type or may not be valid for the specific combination of
Get instant SAP help. Sign up for our Free Essentials Plan.
MN259
Settlement indicator not set for item &1 of document &2
What causes this issue? The indicator "Settlement" exists for each item in a document. This indicates whether the item is relevant for subs...
MN258
No condition table defined for number &, usage &
What causes this issue? A condition table number &V1& for usage &V2& has not been defined.How to fix this error? Contact your system...
MN261
Category & of purchasing document & not allowed
What causes this issue? The updating of supplier business volumes within the framework of <DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent ...
MN262
Overflow in statistics update, subsequent settlement, Purchasing
What causes this issue? What causes this issue? An overflow has occurred during the process of updating the business volume subject to rebate settlem...
Click on this link to search all SAP messages.