Online Tutorials & Training Materials |
Register Login

Inconsistency between Master data table and SID table

Jyoti Pandey || 06 Jun 2016 1:30 pm || 1

Master data table Vs. SID table

How should I resolve the inconsistency between SID table and master data table?


  • 06 Jun 2016 1:35 pm Best Answer

    This is for the BW systems only that functions on the SAP HANA database.

    The master data ID (SID) table that exists in the master data table may find several entries are missing in rare cases. When the system issues message BRAIN 290 "Error while writing master record "..." of characteristic ...", this inconsistency is noticed.

    An error in the database that has been fixed with revision 30 can be the reason for this problem. 

    Implement the attached corrections to your ABAP server to ensure that the inconsistency is discovered as early as possible. The potential inconsistencies are discovered early by this. 

    The test should be activated if database is not up to revision 30. SAP recommends the test to be activated if revision 30 has been implemented. With a BW support package, the test will be deinstalled again. 

    The test is automatically active when the attached corrections are implements and if BW runs on an SAP HANA database.

    Note that the runtime of loading processes is increased by the additional test. Using an RSADMIN parameter, the test must be deactivated if performance tests are being carried out. If the column VALUE = space for the line OBJECT = HDB_SIDCHECK in the table RSADMIN, the test is deactivated. When this line is deleted from the table RSADMIN or when the entry to VALUE = X is set, the test can be activated again.

    To create and to change the entry, the program SAP_RSADMIN_MAINTAIN (transaction SE38) can be used. 

    The loading process terminates with the short dump MESSAGE_TYPE_X BRAIN 299 in SAPRRSI and FORM NEW_VALDSID_SAVE-HDB1A-, NEW_VALDSID_SAVE-HDB1B-, NEW_VALDSID_SAVE-HDB2-, or NEW_VALDSID_SAVE-HDB3-, if the test discovers a problem. SAP should be contacted directly in this case.
    SAP NetWeaver BW 7.30 

    For SAP NetWeaver BW 7.30 (SAPKW73008) into the BW system, import Support Package 8. When SAP 1680997 "SAPBWNews NW BW 7.30 BW ABAP SP8", which explains this Support Package in more detail, is released for customers, the Support Package is available. 

    SAP NetWeaver BW 7.31 (SAP NW BW 7.0 Enhancement Package 3)

    For SAP NetWeaver BW 7.31 (SAPKW73105) into the BW system, import Support Package 5. When 1708177 "SAPBWNews NW BW 7.31/7.03 ABAP SP5", which explains this Support Package in more detail, is released for customers, the Support Package is available.

    The correction instructions as an advance correction can be implemented in urgent cases.

    SAP 875986 must be read first as it provides information about transaction SNOTE.

    Before the Support Package is released, the SAP Notes mentioned above may already be available to provide information in advance. The words "Preliminary version" are contained in the short text of the SAP Note in this case.