How To Fix WV716 - Price activatn on price list level and adoptn of ref. plants incompatible

WV716 - Overview

• Message type: E = Error

• Message class: WV - Messages about Sales Price Calculation

• Message number: 716

• Message text: Price activatn on price list level and adoptn of ref. plants incompatible

What causes this issue?

In the selection screen, <DS:DE.W_WKKALEB>price activation</> at price
list level has been defined for the new market-basket price
calculation.
At the same time, reference plant relationships are to be adopted from
<DS:DE.W_WKKNRA>reference market-basket price calculation</> &V1&.
This is contradictory, as the use of reference plants is linked to
price activation at plant level. This contradiction makes it unclear
how the market-basket price calculation is to be carried out.

System Response

The market-basket price calculation could not be started.

How to fix this error?

If you want to activate sales prices at price list level, remove the
setting for adopting reference plant relationships from reference
market-basket price calculation &V1&.
If you want to adopt reference plant relationships from the reference
market-basket price calculation entered, reset the indicator for price
activation to "plant level".

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

WV716 - Details

• The SAP error message WV716 indicates that there is an issue with the price activation on the price list level and the adoption of reference plants being incompatible. This error typically arises in the context of pricing and condition records in SAP, particularly when dealing with multiple plants or reference plants in the pricing procedure.
  
  Cause:
  
  
  Incompatible Reference Plants: The error often occurs when the reference plant used for pricing does not match the plant for which the price list is being activated. This can happen if the pricing conditions are set up for a specific plant, but the system is trying to apply them to a different plant.
  
  
  Missing or Incorrect Condition Records: If the condition records for the pricing are not correctly maintained for the relevant plants, it can lead to this error.
  
  
  
  Configuration Issues: There may be configuration issues in the pricing procedure or the way the plants are set up