How To Fix ABADR070 - Inconsistency: rule is not time-dependent but contains time-dep. entries

ABADR070 - Overview

• Message type: E = Error

• Message class: ABADR - Message Class for Characteristic Derivation

• Message number: 070

• Message text: Inconsistency: rule is not time-dependent but contains time-dep. entries

What causes this issue?

The entries in the table for this derivation rule have different "From"
dates, but in Customizing you specified that the entries should not be
defined with validity dates.
This state is inconsistent and should not occur. One reason for its
occurrence might be that entries were made directly in the table using
a user-created program and this program does not function correctly.

System Response

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

How to fix this error?

In Customizing, allow entries with validity dates for this derivation
rule.
If the entries were made directly in the table by a program, correct
that program.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ABADR070 - Inconsistency: rule is not time-dependent but contains time-dep. entries ?

  The SAP error message ABADR070 indicates that there is an inconsistency in a rule where it is defined as not being time-dependent, yet it contains entries that are time-dependent. This typically occurs in the context of SAP's application areas that deal with rules, such as pricing, condition records, or other configuration settings.
  
  Cause:
  
  Rule Configuration: The rule in question has been configured to be non-time-dependent, but it has entries that specify time-dependent conditions or values.
  Data Entry Error: During the creation or modification of the rule, time-dependent entries may have been inadvertently added.
  System Migration or Upgrade: If the system has been migrated or upgraded, inconsistencies can arise due to changes in how time dependencies are handled.
  
  
  Solution:
  
  
  Review Rule Configuration:
  
  Go to the configuration settings for the rule in question.
  Check if the rule is indeed set to be non-time-dependent. If it is, you need to either remove the time-dependent entries or change the rule to be