Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: WB2R - Messages Rebates
Message number: 374
Message text: Contract determination relevance not allowed for type &1.
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
WB2R374
- Contract determination relevance not allowed for type &1. ?The SAP error message WB2R374, which states "Contract determination relevance not allowed for type &1," typically occurs in the context of contract management and pricing in SAP. This error indicates that the system is trying to determine a contract for a specific document type that is not allowed for contract determination.
Cause:
- Document Type Configuration: The document type specified (represented by &1 in the error message) is not configured to allow contract determination. This could be due to settings in the configuration of the pricing procedure or the document type itself.
- Contract Type Restrictions: Certain contract types may have restrictions on which document types can reference them for pricing or determination.
- Missing Configuration: The necessary configuration for contract determination may not have been set up correctly in the system.
Solution:
Check Document Type Configuration:
- Go to the configuration settings for the document type in question (transaction code SPRO).
- Navigate to the relevant area for Sales and Distribution (SD) or Material Management (MM) depending on the context.
- Ensure that the document type is allowed for contract determination.
Review Contract Types:
- Check the contract types that are set up in the system.
- Ensure that the contract type you are trying to use is compatible with the document type you are working with.
Adjust Pricing Procedure:
- Review the pricing procedure associated with the document type.
- Ensure that the pricing procedure allows for contract determination and that the necessary conditions are set up.
Consult Documentation:
- Refer to SAP documentation or help resources for specific details on contract determination and the configuration of document types.
Testing:
- After making changes, test the scenario again to see if the error persists.
Related Information:
If the issue persists after checking the above points, it may be beneficial to consult with an SAP functional consultant who specializes in the relevant module (SD or MM) for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
WB2R373
Semantic settlement cal. key cannot be changed. Date &1 and date type &2.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WB2R372
Deletion of settlement calendar entry via CID not supported.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WB2R375
Contract determination relevance not allowed for type &1, variant &2.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WB2R376
Multiple use of External GUID &1 (Settlement Calendar of Contract &2)
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.