Do you have any question about this error?
Message type: E = Error
Message class: RSAU - Update rules
Message number: 343
Message text: Inkonsistenz in der Stammdatentabelle des Merkmals &
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.
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.
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)
Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.
The master data table is inconsistent.Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE
RSAU343
- Inkonsistenz in der Stammdatentabelle des Merkmals & ?Get instant SAP help. Start your 7-day free trial now.
RSAU342
Keine Stammdaten-Operationen während eines Änderungslaufes möglich
Was verursacht dieses Problem? There are operations to be carried out on master data tables. This applies to loading master data (attributes), for ...
RSAU341
Stammdaten: Fehler beim Verbuchen von Attributen
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
RSAU344
Die Sperre der Stammdaten-/Texttabelle des Merkmals & wurde gelöscht
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
RSAU345
Fortschreibung: Start der benutzerdefinierten Datenanreicherung
Selbsterklärende Nachricht Da SAP der Meinung ist, dass diese spezielle Fehlermeldung 'selbsterklärend' ist, wurden keine weiteren Informationen geg...
Klicken Sie auf diesen Link, um alle SAP-Meldungen durchsuchen.