How To Fix KQ701 - Unexpected table inconsistencies occurred

KQ701 - Overview

• Message type: E = Error

• Message class: KQ - Error Messages for Customizing Product Costing

• Message number: 701

• Message text: Unexpected table inconsistencies occurred

What causes this issue?

A consistency check found inconsistencies in the Customizing tables for
variance calculation in version &v1&.

System Response

The tables cannot be converted.

How to fix this error?

Since the inconsistency only affects the functions "Variance
calculation for orders" and "Variance calculation for cost object
hierarchies" in product cost accounting, production operation of your
system can still be started immediately.
If you do not use the above variance calculation functions, you can
ignore this error.
Variance calculation for orders and cost object hierarchies will not
function until the inconsistency is removed. If version 000, which is
relevant for settlement, is affected by the inconsistency, you also
cannot settle variances for orders and cost object hierarchies until
the inconsistency is removed.
To correct this error, proceed as follows:
Run report RKTKV30A and print out the list that is generated.
Run report RKTKVIN1 and print out the list that is generated.
Send these printouts to SAP together with a problem message.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KQ701 - Unexpected table inconsistencies occurred ?

  The SAP error message KQ701, which indicates "Unexpected table inconsistencies occurred," typically arises in the context of the Controlling (CO) module, particularly when dealing with cost center accounting, internal orders, or other related areas. This error suggests that there are inconsistencies in the database tables that SAP uses to store data related to controlling.
  Causes:
  
  Data Corruption: This can occur due to issues during data entry, system crashes, or improper data migration.
  Inconsistent Data: If there are inconsistencies between related tables (e.g., master data and transaction data), this error may be triggered.
  Custom Developments: Custom programs or enhancements that manipulate CO data may inadvertently lead to inconsistencies.
  System Upgrades or Patches: Sometimes, inconsistencies can arise after an upgrade or patch if the data structures have changed and the data has not been properly migrated.
  
  Solutions:
  
  Consistency Check: Use transaction codes like KAH3 (for cost centers) or KAH2 (for internal orders) to perform consistency checks on the relevant