Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 706
Message text: Cond. class & assigned to cond. type & does not allow cond. maintenance
Condition type &V2& has the condition class &V1& and cannot therefore
be used in condition maintenance.
The system will not allow further processing.
Please change the condition class &V1& of condition type &V2& or remove
the condition type from condition type group &V3&.
Error message extract from SAP system. Copyright SAP SE.
MN706
- Cond. class & assigned to cond. type & does not allow cond. maintenance ?The SAP error message MN706 indicates that a condition class is assigned to a condition type that does not allow condition maintenance. This typically occurs in the context of pricing or conditions in SAP, where certain condition types are configured to be non-maintainable.
Cause:
- Condition Class Configuration: The condition type is linked to a condition class that is set to "non-maintainable." This means that the system does not allow manual maintenance of conditions for that specific type.
- Custom Configuration: In some cases, custom configurations or settings in the pricing procedure may restrict the maintenance of certain condition types.
- Incorrect Assignment: The condition type may have been incorrectly assigned to a condition class that does not support maintenance.
Solution:
Check Condition Type Configuration:
- Go to the transaction code
V/06
(for pricing condition types).- Look for the condition type that is causing the error and check its configuration.
- Ensure that the condition class assigned to the condition type allows for maintenance.
Modify Condition Class:
- If you need to maintain conditions for this type, you may need to change the condition class to one that allows maintenance. This can be done in the configuration settings.
- Use transaction code
V/07
to check and modify the condition classes.Review Pricing Procedure:
- Check the pricing procedure assigned to the relevant sales document type or purchasing document type.
- Ensure that the condition type is correctly included in the pricing procedure and that it is set up to allow maintenance.
Consult Documentation:
- Review SAP documentation or consult with your SAP functional consultant to understand the implications of changing condition classes or types.
Testing:
- After making changes, test the configuration by trying to maintain the condition again to ensure that the error is resolved.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with an SAP expert or support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MN705
Condition type group & does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN704
No condition types exist for condition type group &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN707
Invalid call of function module & (parameter missing) (internal error)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN708
Promotion & does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.