How To Fix ATP_SOT_VDM714 - Do not use absolute and relative conditions for attribute &1 together.

ATP_SOT_VDM714 - Overview

• Message type: E = Error

• Message class: ATP_SOT_VDM - Message class for SOT VDM Logic

• Message number: 714

• Message text: Do not use absolute and relative conditions for attribute &1 together.

What causes this issue?

You tried to use an absolute and a relative representation for an
attribute.

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

Examples:
An absolute representation is for example: Order Creation Date is 1.
June 2019.
A relative representation is for example: Order Creation Date is in the
last 3 days (with respect to today).

System Response

The system forbids this with an error message.
The reason is that the selection you define in this App can be used in
two different scenarios.
1. It is run once at a certain date, for which the absolute
representation should be used.
2. It is scheduled to be run on a regular basis, for which the relative
representation should be used.

How to fix this error?

By forbidding the combination of the two representations the user is
forced to pre-think in which scenario the selection should be used.
Reformulate all conditions of the attribute in such a way that either
the absolute or the relative representation is used.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

ATP_SOT_VDM714 - Details

• The SAP error message ATP_SOT_VDM714 indicates that there is a conflict in the way conditions are defined for an attribute in the context of Advanced Planning and Optimization (APO) or similar modules. Specifically, it suggests that both absolute and relative conditions are being used simultaneously for the same attribute, which is not allowed.
  
  Cause:
  The error arises when:
  
  An attribute is defined with both absolute conditions (fixed values) and relative conditions (values that depend on other variables or conditions) at the same time.
  This can happen during the configuration of planning scenarios, where the system expects a clear definition of how conditions should be applied.
  
  
  Solution:
  To resolve this error, you should:
  
  Review the Configuration: Check the configuration settings for the attribute in question. Look for any definitions that mix absolute and relative conditions.
  Modify Conditions: Decide whether you want to use absolute conditions or relative conditions for the attribute. Remove one type of condition to ensure that