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: WB2B - Trading Contract
Message number: 170
Message text: Either maintain value variance or percentage. Check entry
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.
WB2B170
- Either maintain value variance or percentage. Check entry ?The SAP error message WB2B170 "Either maintain value variance or percentage. Check entry" typically occurs in the context of configuring or processing conditions in pricing or rebate agreements within the SAP system. This error indicates that the system expects either a value variance or a percentage to be defined, but neither has been provided.
Cause:
- Missing Data: The error usually arises when a user is trying to create or modify a pricing condition or rebate agreement, and they have not filled in the required fields for either value variance or percentage.
- Configuration Issues: There may be issues with the configuration of the pricing procedure or the condition types being used, which may not be set up to allow for the required entries.
- Incorrect Condition Type: The condition type being used may not be appropriate for the type of calculation you are trying to perform.
Solution:
- Check Entries: Go back to the transaction where the error occurred and ensure that you have filled in either the value variance or the percentage field. You need to provide at least one of these values.
- Review Condition Type: Verify that the condition type you are using is set up correctly in the system. You can do this by checking the configuration in the SPRO transaction under:
- Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types.
- Consult Documentation: If you are unsure about the required fields for the condition type, refer to the SAP documentation or help files for guidance on the specific condition type you are working with.
- Testing: After making the necessary adjustments, try to save or process the transaction again to see if the error persists.
Related Information:
If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in pricing and conditions in SAP.
Get instant SAP help. Sign up for our Free Essentials Plan.
WB2B169
Reversal not possible. Select all document items
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WB2B168
Deletion not possible as follow-on documents exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WB2B171
Status 'closed' is not defined for contract type &1
What causes this issue? The status "Closed" is not defined in Customizing for this contract type.System Response The system cannot set the...
WB2B172
Contract will be closed (physical deletion no longer possible)
What causes this issue? Physical deletion of the contract is no longer possible because follow-on documents already exist. The contract will be close...
Click on this link to search all SAP messages.