How To Fix RSAU343 - Inconsistency in the master data table for characteristic &

RSAU343 - Overview

• Message type: E = Error

• Message class: RSAU - Update rules

• Message number: 343

• Message text: Inconsistency in the master data table for characteristic &

What causes this issue?

The master data table of characteristic &V1& was checked for
consistency and error &V2& was discovered.
Missing initial entry in the master data table:
The initial entry in a master data table, whichever one is in version
A/' ', has been manually deleted.
You have to generate this entry again by activating the characteristic
anew.
Double entries in the master data table:
Double entries exist in master data table &V3&. Characteristic values
not only exist in versions 'M'/'I' but also in 'A'/' ' (&WHAT_TO_DO&).
Overlapping time intervals or gaps in the time interval:
&V3& gaps or overlaps exist in the time intervals of individual
characteristic values.
Incomplete coverage of the time interval:
The time interval is not completely covered with &V3& characteristic
values, or to the lower limit. A characteristic value must exist
without any gaps from 01.01.1000 to 31.12.9999.
If this is not the case, an algorithm makes the interval complete when
loading the data. No additional action is required.
Master data records of an invalid version:
The master data table contains records, that appear in the invalid
version '&V3&'/'&V4&'.
Only the versions 'M'/'I', 'A'/' ' and 'A'/'D' are valid.

System Response

The system cannot work with the inconsistent master data table. Before
data can be loaded into the master data table, this must be transferred
into a consistent state.

How to fix this error?

If you delete master data with a 'drop table' or with the aid of SE16,
then you get inconsistencies in the system, that you can only repair by
deleting many different datasets.
If a master data table is linked with very many InfoCubes, then it is
most likely that almost all data is to be deleted from the system.
To be able to delete master data, no transaction data can exist for
this master data, the master data must not be used as an attribute
value, nor may any hierarchies exist for it.
Provided that one of these three conditions is met for master data, an
indicator (*) is placed in the corresponding entry in the SID table.
If, for example, the transaction data, that was responsible for the
entry of the indicator, was deleted, then the indicator in the SID
table remains in position nonetheless.
This means that it is not possible to delete master data, for which one
of the three aforementioned conditions was <ls>ever</> met.
RESET N1
Two indicators exist in the SID table, that give information on this:
DATAFL : Value exists in a dimension or as an attribute
INCFL : Value is installed in all inclusion tables (hierarchies)

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

The master data table is inconsistent.
The following procedure is recommended if the master data table is
inconsistent:
RESET N1
With the function module RSDG_CHKTAB_CONSISTENCY, check the consistency
of the master data table. If you get E_SUBRC <> 0, the table is not
consistent.
Start the report
RSDMD_DEL_METADATA (1.2A) or
RSDMD_DEL_MASTER_DATA_TEXTS (1.2B),
to delete the master data attributes, for which none of the three
aforementioned conditions were ever met.
Call up the function module RSDMD_CLEAN_ATTRIBUTES.
Execute a structure realignment run to activate master data attributes.
Upload the data anew, and activate the master data attributes once
more.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSAU343 - Inconsistency in the master data table for characteristic & ?

  The SAP error message RSAU343 indicates that there is an inconsistency in the master data table for a specific characteristic in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence). This error typically arises when there are discrepancies in the data stored in the master data tables, which can lead to issues in reporting and data analysis.
  
  Cause:
  
  Data Inconsistency: The master data for the characteristic may have been corrupted or not properly updated. This can happen due to incomplete data loads, failed data transfers, or manual data entry errors.
  Missing Data: The characteristic may reference data that does not exist in the master data table.
  Data Model Changes: Changes in the data model, such as modifications to the characteristics or attributes, can lead to inconsistencies if the changes are not properly propagated through the system.
  Transport Issues: If the master data was transported from one system to another, there may have