SAP BW Upgrade From 3.5 To 7.3

Introduction

SAP BW is integrated tool for data warehousing, business intelligence and other tools which enables a business to analysis and interpret their business data. With the new releases of SAP BW, it tries to transfer customer scenario created in previous release into the new release, but some manual effort are necessary to perform to ensure that existing scenario can be used after the upgrade.

When we have to upgrade SAP BW, there are different activities defined for Basis, Security and BW team to perform. This document will provide you short descriptions of the pre and post- upgrade activities need to perform by BW team only. The key responsibility of BW team is to ensure that all the existing objects can be used after upgrade and to handle incompatibility if any. You can also refer upgrade guide provided by SAP for complete reference for Upgrade activities. The main purpose of this document is to give details of some critical issues we faced after upgrade.

Pre-Upgrade Activities

1.  Checking Inconsistent InfoObjects

A.  Execute RSD1

B.  Choose Extras > Repair InfoObjects (F8) > Choose Execute Repair > execute (for all InfoObjects) or Choose Expert Mode>Select Objects.

C.  On the following screen, activate the following checkboxes:

a)  Check Generated Objects

b)  Activate Inconsistent InfoObjects

c)  Delete DDIC Objects

d)  Display Log

D.  Execute the program.

E.  Check the log and manually correct any remaining inconsistencies.

2.  Checking for Incompatibilities with Source Release SAP BW 3.5

SAP Note: 955990 to be checked & implemented as necessary

3.  Preparing the Migration of Workload Statistics Data

SAP has created a completely new workload statistics collector to meet the requirements of large systems. To migrate workload statics data to ensure that we can read data from old release after upgrade, the following steps are must to perform.

A.  Create Custom Table (SE11) - ZWNCMOMIGR manually, which store the converted workload statics data.

B.  Create and execute the Program (SE38) - RSMIGR12, which will convert the data and save in the custom table ZWNCMOMIGR.

C.  The above two step need to perform before upgrade. Once upgrade is done use Program (SE38) - SWNCMIGRATION1 to convert the data of table ZWNCMOMIGR to NetWeaver2004s format and save it to new standard tables.

Please refer to SAP Note: 1005238 for more details on fields and settings of table- ZWNCMOMIGR and for source code of program- RSMIGR12.

4.  Run program RSUPGRCHECK to find inconsistent Info cubes, ODS, Info objects, Multiproviders, Update and Transfer Rules

Activate the relevant objects

5.  Release all CTS.

Release all transport requests if present before you start the actual upgrade

6.  All extractions and loads should be completed.

There should be no extraction and data load while actual upgrade is going on. So make sure that all loads are done before upgrade.

7.  If possible, ensure that the data queues are empty in the source systems

Recommendation: Temporarily stop all V3 collection processes

8.  Run program RSDMD_CHECKPRG_ALL for consistency test of all Master Data.

Execute the program (SE38) - RSDMD_CHECKPRG_ALL to test all Master Data consistency, all inconsistencies here will be carried forward in the upgrade.

9.  Activate all Transfer Structures.

Run program RS_TRANSTRU_ACTIVATE_ALL in SE38 to activate all Transfer Structures. Check the log and manually activate Transfer structure which is still inactive in any.

10.   Activate all Multiproviders.

Run program RSDG_MPRO_ACTIVATE to activate all Multiproviders.

Upgrade process

Actual upgrade of BW system was performed by BASIS team.

Post-Upgrade Activities

1.  TADIR entries for factviews

Execute program (SE38) - SAP_FACTVIEWS_RECREATE, please refer SAP Note: 563201 for more details.

2.  Set the SAP BI Menu

Execute Tcode - SSM2 and set the value of SAP BI Menu, refer SAP Note: 725184.

Collects the above changed in TR while doing this in development system and move it to next systems when they get upgraded because in Production and quality system this feature is disabled.

3.  Ensure BI Object consistency

Execute Tcode – RSRV and perform “Database Indices of an InfoCube and Its Aggregates” and “Database Statistics for an InfoCube and Its Aggregates” for InfoCubes. Please refer SAP Note: 555717 for more details.

4.  Activate the source systems again

Execute Tcode – RSA1 and activate all the source systems. Please refer SAP Note: 538052 for more details.

5.  Repair InfoObjects

Execute Tcode – RSD1 and repair all InfoObjects.

6.  Activate transfer structures

Execute Program (SE38) - RS_TRANSTRU_ACTIVATE_ALL to activate all transfer structures refer SAP Note: 1027827 for more details.

7.  Reactivation of all active update rules

Execute Program (SE38) - RSAU_UPDR_REACTIVATE_ALL to activate all active update rules, refer SAP Note: 631601 for more details.

8.  Activation of MultiProviders

Execute Program (SE38) - RSDG_MPRO_ACTIVATE to activate all MultiProviders, refer SAP Note: 897735 for more details.

9.  Create dropped factviews again

Execute program (SE38) - SAP_FACTVIEWS_RECREATE, please refer SAP Note: 563201 for more details.

10.   Activate BEx history

Execute Tcode - RS_PERS_ACTIVATE, refer SAP Note: 744009 for more details.

11.   Problem with a hierarchy with remaining nodes

Execute program (SE38) RRINCLTAB_REBUILD for all hierarchies. If there are lots of hierarchies, it is recommended to run this program in background, refer SAP Note: 922467 for more details.

12.   Convert the data sources and the PSA to the new DTP process

Execute program (SE38) - RSSM_CREATE_REQDONE_FROM_SEL, please refer SAP Note: 906789 for more details.

13.   Execute report RSSM_HASH_ENTRIES_CREATE

Execute program (SE38) - RSSM_HASH_ENTRIES_CREATE, please refer SAP Note: 906789 for more details.

14.   Execute report RSSTATMAN_CHECK_CONVERT_DTA

Execute program (SE38) - RSSTATMAN_CHECK_CONVERT_DTA, please refer SAP Note: 906789 for more details.

15.   Convert the PSA to the new DTP process

Execute program (SE38) - RSSTATMAN_CHECK_CONVERT_PSA, please refer SAP Note: 906789 for more details.

16.   Run Report RSR_VARIANT_XPRA for the Query Variants

Execute program (SE38) - RSR_VARIANT_XPRA, please refer SAP Note: 953346 for more details.

17.   Migration of variants

Execute program (SE38) - RSR_MIGRATE_VARIANTS, please refer SAP Note: 1003481 for more details.

18.   Check RSZ* Tables

Execute program (SE38) - ANALYZE_RSZ_TABLES, please refer SAP Note: 792779 for more details.

19.   Repair errors in RSZ* tables

Execute program (SE38) - ANALYZE_MISSING_ELEMENTS, please refer SAP Note: 792779 for more details.

20.   Check for problem with Input help for tech characteristic

Execute program (SE38) - RSDG_XPRA_IOBJ_TO_NW05, please refer SAP Note: 939484 for more details.

21.   Migrate Chart settings to BW 3.5

Execute program (SE38) - RSZW_CHART_MIGRATION_35, please refer SAP Note: 818240 for more details.

22.   Migration of Web Items/Templates to BW 7.0

Execute program (SE38) - RSZW_ITEM_MIGRATION_3X_TO_70, please refer SAP Note: 832712 for more details.

23.   Configure runtime parameters for DataStore objects

Execute Tcode - RSODSO_SETTINGS to configure runtime parameters for DSOs.

24.   Customizing: Check notes 647002 and 653469

Execute Tcode - RSCUSTV8 to configure runtime parameters for DSOs.

25.   OLAP Cache Parameters

Execute Tcode - RSRCACHE to configure runtime parameters for DSOs, please refer SAP Note: 791065 for more details.

26.   Maintain OLAP Cache parameters

Execute Tcode - RSCUSTV14 to configure runtime parameters for DSOs, please refer SAP Note: 683194 for more details.

27.   Customizing SAP Web Application Server protocol

Execute Tcode - RSCUSTV15 to configure runtime parameters for DSOs, please refer SAP Note: 512337 for more details.

28.   Maintain Authorization settings

Execute Tcode - RSCUSTV16 to configure runtime parameters for DSOs, please refer SAP Note: 520588 for more details.

Issues faced After Upgrade

1.  Identification issues of Characteristics and KFs of MultiProvider

This was a very critical issue we faced after upgrade. We were getting incorrect data in Report output due to this issue. For some MultiProviders, mapping of some characteristics and KeyFigures got changed (removed or selected), see below.

After Upgrade:

Before Upgrade (Copy of 3.5 system- Not Upgraded)

Solution:  Use Table – RSDICMULTIIOBJ (Tcode-SE16) for each MultiProvider in Upgraded system and Copy System (not upgraded) and compare the entries. If you find any mismatch, correct it in upgraded development system and move to next upgraded system.

After Upgrade:

Before Upgrade (Copy of 3.5 system- Not Upgraded)

2.  Data load issues due to Database inconsistency

We faced following data load issues due to database inconsistency after upgrade.

a.  Upon activation of data request of DSO, the activation job got canceled. Checked the job log and found an ABAP dump with following exception:

“CX_SDB_ORA_PROGRAM_ERROR"                            

The cause of the exception was:

ORA-20000: Insufficient privileges,

Solution: Implemented the SAP note: 963760 by basis team.

b.  Getting below dump while deleting the old data load request for cube/DSO.

Solution: Implemented SAP Note: 3807 - Error messages regarding rollback and undo segments by basis team.

c.   Data load request took long time and ended with following ABAP dump. Upon checking in Tcode- ST22, got below details-

Solution: Implemented SAP Note 3155 - Termination due to tablespace overflow by basis team.

3.  Other data load issue

a)  Faced one other issue while loading data to InfoCube through InfoPackage,

The InfoPackage failed with following error message

'Error occurred in write_ic for data target' and

'Error occurred in UPDATE_INFOPACKAGE for data target'.

Solution:

1. Executed the report (SE38) RSDD_RSTMPLWIDTP_GEN_ALL

2. Executed the program (SE38) RSDG_CUBE_ACTIVATE.

3. Executed the report (SE38) RSAU_UPDR_REACTIVATE_ALL to activate update rule.

4. Executed InfoPackage again, Data loaded successfully.

b)  InfoPackage failed to load data to one DSO by giving below error message:

“Faulty Status found in DataStore”.

Upon checking the DSO, there was a red request. We were unable to delete this request as it was partially activated. It might have happened because of server went down while activation of DSO request was in progress.

Solution: We need to delete the request from control tables - RSMONICDP, RSICCONT, RSODSACTREQ and RSODSACTUPDTYPE. Please refer SAP Note: 947481 for more details.

4.  Issue with report broadcasting

After Upgrade, broadcasting feature worked fine except for excel file format. When we broadcasted any report to excel file format, report output is coming three times in single excel file as below-

But it should appear only one time as below-

Solution: The above issue was due to BI JAVA. Basis team installed SAP BI JAVA 7.3 SPS0. Some Patches were missing in this service pack, while available in further service packs, see below-

(Refer SCN DOC - http://scn.sap.com/docs/DOC-25489 for more details)

So Basis team had manually downloaded and installed all the missing java patches (See SAP note: 1601504 and SCN thread - http://scn.sap.com/thread/3160230 for more details) after that the issue got resolved.

Some Important Points

1. First step is to upgrade the development system and make sure everything is working fine. If you find any issue, you can always take the reference of production system. If need to correct any object after upgrade, collects those objects in transport request. Move these TRs to next systems (e.g. - Quality, Production) after they are upgraded in order to fix those issues.

2. In order to make SAP 3.5 query executable from Bex 7.3, you need to open each query in Query Designer 7.3 and save it again. You cannot open these queries in query designer 3.5 after this.