Diagnosis
The master data table of characteristic &V1& was checked forconsistency 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 versionA/' ', has been manually deleted.
You have to generate this entry again by activating the characteristicanew.
Double entries in the master data table:
Double entries exist in master data table &V3&. Characteristic valuesnot 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 individualcharacteristic values.
Incomplete coverage of the time interval:
The time interval is not completely covered with &V3& characteristicvalues, or to the lower limit. A characteristic value must existwithout any gaps from 01.01.1000 to 31.12.9999.
If this is not the case, an algorithm makes the interval complete whenloading the data. No additional action is required.
Master data records of an invalid version:
The master data table contains records, that appear in the invalidversion '&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. Beforedata can be loaded into the master data table, this must be transferredinto a consistent state.

Procedure
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 bydeleting many different datasets.
If a master data table is linked with very many InfoCubes, then it ismost likely that almost all data is to be deleted from the system.
To be able to delete master data, no transaction data can exist forthis master data, the master data must not be used as an attributevalue, nor may any hierarchies exist for it.
Provided that one of these three conditions is met for master data, anindicator (*) is placed in the corresponding entry in the SID table.If, for example, the transaction data, that was responsible for theentry of the indicator, was deleted, then the indicator in the SIDtable remains in position nonetheless.
This means that it is not possible to delete master data, for which oneof the three aforementioned conditions was 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 master data table is inconsistent.
The following procedure is recommended if the master data table isinconsistent:
RESET N1
With the function module RSDG_CHKTAB_CONSISTENCY, check the consistencyof the master data table. If you get E_SUBRC <> 0, the table is notconsistent.
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 threeaforementioned 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 oncemore.