To BW consultants/Developers who are planning for upgrade BW system from 3.5 version to BI 7.0 version.
Following are the brief overview on the issues that will be faced by us during and after the BW upgrade.
5. Issues faced
The general activities involved during the planning phase:
1. Work out a plan for the system downtime required
2. Communicate the downtime of the system and get an approval on the same
3. Provide exact details of the upgrade
4. Send service announcement to all end users
5. Send first draft of cut-over plan to all involved parties to check and confirm for completeness, timing and dependencies
6. Confirm the upgrade schedule by communicating to all parties
To ensure that the business is not adversely affected by the upgrade, the development system should be upgraded first and BW team has to perform extensive tests. Based on the test results, the issues faced and the learnings were recorded as lessons learned document/issues document with suitable solutions. Then, once BW team is confident of performing the upgrade team should go for performing the upgrade task in quality system. Based on the learning documented/issues faced these will help to ensure that such issues did not crop up on the live system.
Note: A joint co-ordination of synergy is required b/w Basis team and SAP BW consultants/teams to perform the successful BW upgrade task which will helps us to go extra mile to use features/functions that are available in BI 7.0 Version from BW 3.5.
2. Pre-upgrade tasks
1. Check for possible inconsistencies with RSZ* tables in BW system
Check any inconsistency in the system with RSZ* tables.
Execute the report ANALYZE_RSZ_TABLES.
Correct any such inconsistency.
Also refer SAP Note 792779.The Following mentioned tables should show as No errors found in the BW system. They are
2. How to Activate inconsistent InfoObjects in BW
If we found any inconsistent InfoObject that exists in the system, execute the report RSDG_IOBJ_ACTIVATE and activate a single InfoObject.
3. Check SPDD/SPAU for old entries
Using this transaction, find any old entries that are present in BW system.
Check Note 510138 and 676395.
4. All Update and Transfer rules should be active
All the transfer and update rules must be active. Find for inactive transfer and update rules by executing report RSUPGRCHECK. If any entry is found, activate the rule or delete the same.
5. All InfoCubes should be active
All the InfoCubes must be active. Find for inactive InfoCubes by executing report RSUPGRCHECK. If any entry is found, activate or delete the same.
6.Master data consistency
Check the consistency of master data objects by executing the report RSDMD_CHECKPRG_ALL. If there is any inconsistency, run the same report with the Repair option.
7.Repair inconsistent InfoObjects
1. Go to transaction RSD1
2. Go to Extras > Repair InfoObjects
3. Go to Execute > Repair
4. Go to Expert Mode > Select Objects
5. Select the following checkboxes:
Check Generated Objects
Activate Inconsistent Objects
Delete DDIC Objects
8.Use transaction RSRV & test all the SAP BW Objects; ensure their correctness prior to the upgrade.
9.All ODS objects should be active
All the ODS objects must be active in the system. Find for any inactive ODS objects by executing report RSUPGRCHECK. If any entry is found, activate or delete the same.
10.Ensure all ODS data load requests have been activated.
There must be no data load request in the ODS objects with a yellow status. If any such entry is found, delete the request.
11. Transport requests
Release all the existing transport requests to the target systems. There should not be any transport request lying idle or in repair mode.
12. Process chains
No process chains should be in schedule mode. Go to RSPC & click on schedule tab & remove the chains from schedule.
13. Check compounding consistency in MultiProviders
Check the SAPNote 920416.
14. Check for invalid temp tables
Check for invalid temp tables from transaction SE14->Extras->Invalid Temp Tables. If an entry exists, delete them from this screen.
Note: Follow SAP Relevant notes on upgrades and documentation for any additional instructions other than listed in this document. Also, make sure the know issues & dependencies that exist b/w Import packages before going for upgrade.
The actual upgrade of the BW system is done by the BASIS team in coordination with BW team.
B. Post-upgrade tasks are as follows;
1. Activate the Myself source system and replicate all datasources
Reactivate the BI source system. Also replicate all the source system data sources.
2. Activate all Transfer structures and Update rules
Execute report RS_TRANSTRU_ACTIVATE_ALL for myself system and the source systems.
Execute the report RSAU_UPDR_REACTIVATE_ALL to activate the update rules.
3. Recreate views for Cubes. It can also be executed before the upgrade. For us this is must because we are using Infospokes also.
Execute report SAP_FACTVIEWS_RECREATE from SE38
4.Migration for BEx history, variables personalization, Web Report Personalization
Execute report RS_PERS_ACTIVATE
5.Run the reports RSSTATMAN_CHECK_CONVERT_DTA and RSSTATMAN_CHECK_CONVERT_PSA (also using sufficient parallel processing).refer Note 914536.
6.Reschedule process chains
7.Check InfoObjects status
Check the InfoObjects status after the upgrade. All InfoObjects should be in active state or saved (not active).
Use Transaction RSD1 and follow the path as described in point A-7.
8.Run report RSUPGRCHECK to locate any inactive objects
Below are the typical issues BW team will be faced post upgrade. This is only indicative & not an exhaustive list
1.Data load to cube failed
Detail: The data load to cube was failing, giving error 7 in the update.
Solution: Executed program RSDD_RSTMPLWIDTP_GEN_ALL.
2. BI content activation failed
Detail: The InfoObject 0TCTUSERNM was locked for conversion.
Solution: Go to RSA1->InfoObject->Extras->Remove conversion lock.
3. Error in data activation in DSO
Detail: The data loaded to DSO was not getting activated. Error -Insufficient privileges on Oracle side.
4. Job RSSM_HASH_ENTRIES_CREATE resulted in dump
Detail: When scheduled in background, the job was getting cancelled.
Solution: Refer Note 962365.
What is SPAU (Support package updates) in SAP?
SPAU is for modifying the repository objects in SAP.
During an upgrade of a Support Packages, the existing objects of the SAP standard will be overwritten. In order to help the customer to retain the objects that are modified, SAP provides all modified objects which are redelivered (in an upgrade or Support Package) in the upgrade adjustment of using the transactions SPAU. SPAU transactions allow customers to enter their modifications into the corresponding new objects being delivered at upgrade. The Modification Assistant in SPAU supports the process of adopting customer modification versions