Post-Migration Steps – SAP BW Specific

 Once the Basis related activities are done after migration, you must carry out SAP  BW specific post migration activities.

Step 1: Restore Myself system and SAP BW source systems

The users are automatically locked out of SAP BW on HANA system. You should unlock the technical system users after migration. Do not release the end users still. In the source system tab in RSA1, check whether you can see the SAP BW myself system. Right click and select 'Restore'.  Then also check and restore the other connected source systems. Here you may need to enter the passwords for the relevant background users. Check with the administrator of the respective systems.

Step 2: Adapt BI Lock Server

For BW-IP, you may need to adapt the configuration for the lock server using the transaction for the BI lock server. E.g. The name of the SAP BW application server has changed, you must correct it here. In the tcode RSPLSE, go to the LOCK TABLE tab, select the LOCK SERVER option. (More details in the SAP note 1594606)

Identifying and Remedying Inconsistencies

The following describes on how to identify possible issues in the SAP BW system and remedy them before the SAP BW system is released.

Step 3: Check PSA

In SE38, run the report RSAR_PSA_NEWDS_MAPPING_CHECK report. This is a check for all datasources, whether the respective PSA is obsolete or inactive.

Execute the report without checking the 'Repair' option. If there are inconsistencies found, execute the report again with the 'Repair' option.

img2.PNG

Please note that you should restore the source system connections and release the defined technical users before executing the report.

Step 4: Check the SAP BW system for Inactive Objects

Run the report RSUPGRCHECK to ensure that all the InfoObjects, DSOs and Cubes are activated correctly after the SAP BW on HANA migration. Check the option 'DISPLAY LOG' while executing the report.

img1.PNG

This report has a long runtime and possibly aborts in the DIALOG mode. If this happens, run the report in the background mode.

Check the logs to see the list of Inactive Objects. It is not always possible to activate them in RSA1. In such cases, run the below programs to activate them-

InfoObject: RSDG_IOBJ_ACTIVATE

DSO: RSDG_ODSO_ACTIVATE

InfoCube: RSDG_CUBE_ACTIVATE

Multiprovider: RSDG_MPRO_ACTIVATE

Transformation: RSDG_TRFN_ACTIVATE

Datasource: RSDS_DATASOURCE_ACTIVATE_ALL

DTP: RSBKDTPREPAIR

Update rule: RSAU_UPDR_REACTIVATE_ALL

Transfer Structure: RS_TRANSTRU_ACTIVATE_ALL

Step 5: Correct Inconsistencies of Tables

Correct table inconsistencies in SAP BW on HANA systems using the program RSDU_TABLE_CONSISTENCY. The first run identifies the inconsistencies. In se38 tcode, execute the report and set the option STORE ISSUES, then set all the check marks.

img3.PNG

Once you see the inconsistencies in the check results, go BACK and select the REPAIR option and click SHOW. The system displays a list of error categories. Double click the red ones and the objects are now displayed. Select those objects that are marked with REPAIRABLE status and click SAVE. Click BACK, double click on next object and follow the same steps.  After you have selected all the repairable objects, execute the report again with REPAIR option.

Step 6: Remedy SAP BW Inconsistencies

There may be some SAP BW BEx queries specific inconsistencies which must be resolved after migration. For many years, SAP has provided the report ANALYZE_RSZ_TABLES to identify the issues in query definitions. You can run this report to analyse errors at any time without any risks. However, the REPAIR mode has caused problems sometimes.

img4.PNG

It was seen that the report unintentionally deleted query elements (variables and references) due to a bug even though these elements were still used actively in the SAP BW system. The bug in the report has been fixed by SAP in the meantime.

Considering this, it is better to check this report in the test systems. Moreover, it is recommended to use the report in versions SAP BW 7.3/7.31 with SPS 11, and 7.4 with SPS 06 only (see also SAP note 1930178)

Step 7: Resolve DDIC Inconsistencies

Run the report RUTMSJOB to correct the inconsistencies in the Data Dictionary (DDIC). After you have executed the report, select all check options and execute them as background 'Immediate' option. After all jobs are completed successfully, you can view the results by clicking the RESULTS button. The system automatically runs the clean up activities for some checks.

 

Step 8: Check Multiproviders

You can delete or rebuild the metadata runtime by means of the RSR_MULTIPROV_CHECK report. Start the report in tcode SE38 and select 'All Multiproviders'. This resets the shared memory buffer of all Multiproviders. (SAP note 1626753).

img6.PNG

Step 9: Execute Consistency Checks Using the DBA Cockpit

In the tcode DBACOCKPIT, on the left side, select DIAGNOSTICS for your SAP BW system and double click MISSING TABLES AND INDEXES. Then, click REFRESH. The system displays the results of the consistency checks. For example, error of 'Missing primary index' in the database is displayed. You can correct these inconsistencies by clicking icon1.PNG icon in the ACTION column. If you receive general errors while running the DBA cockpit, please refer to SAP note 1640741.

Comments

Post a Comment

Popular posts from this blog

Sample ABAP program for Updating notepad file data to Internal table and Sending it to Application server

 *--Structure type TYPES: BEGIN OF TY_STD, RONO TYPE C LENGTH 4, NAME1 TYPE C LENGTH 20, GEN TYPE C LENGTH 6, FEES TYPE C LENGTH 10. END OF TY_STD. *--Header line and internal table DATA WKA TYPE TY_STD. DATA INT_TAB TYPE TABLE OF TY_STD. *--Application server files are known as "Datasets" *--here "fname" is the Dataset DATA FNAME TYPE C LENGTH 40 VALUE "StudentsInfo.txt". *--Convert notepad file data into internal table CALL FUNCTION 'GUI_UPLOAD' EXPORTING FILENAME = 'C:Documents and SettingsAdministratorDesktopstudents.txt' HAS FIELD_SEPARATOR = 'X' TABLES DATA_TAB = INT_TAB. *--Sending data to Application Server OPEN DATASET FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT. LOOP AT INT_TAB INTO WKA. TRANSFER WKA TO FNAME. ENDLOOP. CLOSE DATASET FNAME.
Read more

OPEN SQL EXAMPLES IN ABAP – PART 2

 ******************************************* **displaying Raw Materials and Finished products **only from MARA table. DATA WA TYPE MARA. * **--WHERE clause is for filtering the records SELECT * FROM MARA INTO WA WHERE MTART = 'ROH' OR MTART = 'FERT'. WRITE: / WA-MATNR, WA-MBRSH, WA-MTART, WA-MEINS. ENDSELECT. * **************************************************
Read more

Domains and Data Elements

  Domains A domain provided Technical attributes (type, length and possible values) for a field. The definition of domain in ABAP is same as that in Mathematics. In the world of Mathematics, a domain is defined as the set of input values that are valid for a given function. The same holds true for domains in ABAP. To understand this, let us first see what is the role of domains in ABAP data dictionary. Domains -> Data Elements -> (Structures, DB tables, program references etc.)
Read more