SAP ECC Systems SP Upgrade and Impact on SAP BI
Applies to:
SAP ECC & SAP BI 7.0
Summary
This document is re-usable for every BW project, where project will be supporting on Maintenance tasks in Support Pack Upgrades.
Author(s): Venkata C Challapalli
Company: Accenture
Created on: 26 February 2012
Author Bio
Venkata currently is working as Associate Manager in SAP BI at Accenture India. He is a SAP-certified BW as well as ABAP professional. He is having around 12 years of experience in IT industry. His experience in SAP is more than 9 years - that includes 8 yrs in BW.
1. Document Objective
The SAP ECC Systems used as source systems for SAP BI and whenever there will be planned SAP ECC SP Upgrade, there will be impact on connected SAP BI system. This document explains about the details of steps considered in SAP BI system while perform SAP ECC SP Upgrade.
This document is re-usable for every SAP BI Project, where project will be supporting on Maintenance tasks in Support Pack Upgrades.
2. Introduction on SP Upgrade & Scenario
Introduction on SP Upgrade
When multiple end users / Clients of SAP reports same bug in the SAP product to SAP Support Team, then SAP recognizes such bug, corrects them and collects all these corrections in one place and adds some enhancements to the earlier version of SAP and then calls this as a SUUPORT PACK. In simple words Collection of SAP NOTES is a SUPPORT PACK.
Scenario
You are planning to upgrade your SAP ECC / SAP CRM systems to the latest Service Pack Level.
- The existing SAP BI system that is in use connected with SAP ECC as source system which is also in use.
- SAP ECC system is a release that is currently in maintenance.
- These SAP ECC releases at time of writing are: SAP ERP 6.0, SAP EHP1 for SAP ERP 6.0, SAP EHP 2 for SAP ERP 6.0, SAP EHP3 for SAP ERP 6.0, SAP EHP 3 for SAP ERP 6.0, SAP EHP4 for SAP ERP 6.0, or SAP EHP5 for SAP ERP 6.0
- Maintenance dates can be viewed on the SAP Service Marketplace (https://websmp205.sapag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000294692004E ) in the release’s respective sub section.
The sample scenario is provided in below.
System |
Current SP Level |
Confirmed SP Level |
SAP ECC 6.0 |
SP Stack 11 |
SP Stack 20 |
SAP ECC 6.0 |
Kernel 145 |
Kernel 185 |
3. Actions to be performed Before SAP ECC SP Upgrade.
Following are the list of tasks to be performed before starting of SAP ECC Upgrade.
S No |
Task |
SAP ECC Side |
SAP BI Side (Yes / No) |
How-To |
1 |
Stop V3 Delta Collection Jobs |
Yes |
No |
Stop Delta Collection Jobs in ECC side after executing them manually till the time they bring ZERO records. We can monitor these jobs log and status in SM37 Transaction in ECC side. |
2 |
Clearing the delta queues before the upgrade and trigger delta loads in BI side manially. |
Yes |
Yes |
After executing these delta collection jobs manually, the records will move from extraction queue to delta queue (RSA7). |
3 |
All extraction queues and open update orders in all clients must be processed. |
Yes |
No |
Call transaction SMQ1 and check whether all queues in all clients (client = '', queue name 'MCEX') have been processed. To process the queues, start the collective run report for each application in the displayed clients. If we no longer need the data in the BW system, deactivate the relevant extraction queues and DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in transaction SMQ1. |
4 |
Check V3 Update – Serialization issue. |
Yes |
No |
If we use the V3 update that is not serialized (usually only for application 03): Start collective run report RMBWV303. Then check the update orders in transaction SM13. If there are incorrect update orders in transaction SM13, correct the orders and then start the collective run report again. If you no longer require the update orders, you can delete them. There may be inconsistencies between tables VBMOD and VBHDR. For further information about this, see Notes 652310 and 67014. |
5 |
The content of the setup tables must be deleted |
Yes |
No |
Before the upgrade, delete the contents of the setup tables. Execute report RMCEX_SETUP_ENTRIES to find out which setup tables still contain entries. |
6 |
Stop all Process Chains |
No |
Yes |
Remove all Process Chains from schedule. |
4. Actions to be executed after SAP ECC SP Upgrade.
Following are the list of tasks to be performed after SAP ECC Upgrade.
S No |
Task |
SAP ECC Side |
SAP BI Side (Yes / No) |
How-To |
1 |
Test the RFC connection between SAP ECC to SAP BI system |
Yes |
Yes |
|
2 |
Replication of extractors / Activation of Transfer Rules. |
No |
Yes |
|
3 |
List down some sample loads – For master data / Transaction data Full and Deltas. |
No |
Yes |
|
4 |
Do a count of the no of records for the loads and reconcile the number with ECC. Run some reports to check data integrity for the above loads. |
Yes |
Yes |
|
5 |
Put V3 Delta Collection Jobs back in to schedule. |
Yes |
No |
|
6 |
Put all Process Chains in to Schedule. |
No |
Yes |
|
5. SAP BI Activities Checklist
Following checklist provides the list of tasks from BI side before & after upgrade.
S.No |
Activity |
Activity Description |
Phase |
||||
---|---|---|---|---|---|---|---|
1 |
Open Transports Clean up. Make sure that all transports in DEV system should be released and imported to all downstream systems QA and PRD systems. |
Check Open Transports in the system and clean up the same. |
PRE Upgrade |
|
|
60 mins |
|
2 |
Check SM13 (Administrate Update Records) |
In this transation we can found the update statistics..means update error,which program/function module..etc used to update the db,user etc...if found any update error found we will find out the cause . More information can be found from below path. |
PRE Upgrade |
|
|
10 mins |
|
3 |
Check SMQ1 / SMQ2 & SM58 on BW side. |
· SMQ1 – qRFC Monitor for the outbound queue You use this transaction to monitor the status of the LUWs in the outbound queue and restart any hanging queues manually. |
PRE Upgrade |
|
|
30 mins |
|
4 |
Check Open Jobs. |
Check SM37 for any scheduled / Active Jobs. |
PRE Upgrade |
|
|
10 mins |
|
5 |
Check for Inconsistent Infoobjects and repair inconsistent Infoobjects as much as possible. |
Check the InfoObjects and repair them if necessary. |
PRE Upgrade |
|
|
30 mins |
|
6 |
Finding and fixing Inconsistent DataSource |
OSS #579022 (Execute RSAR_TRANSTRUCTURE_CHECK) |
PRE Upgrade |
|
|
10 mins |
|
7 |
Check Inactive Infoobjects |
Check for Inactive InfoObjects and activate. |
PRE Upgrade |
|
|
10 mins |
|
8 |
All ODS data loads must be activated |
Activate all ODS Object where the activation queue is not empty. |
PRE Upgrade |
|
|
10 mins |
|
9 |
All Transfer and Update rules should be active |
Check for inactive Update and Transfer Rules |
PRE Upgrade |
|
|
60 mins |
|
10 |
All InfoCubes should be active |
Check for inactive InfoCubes / Multicubes and Aggregates (Aggregates are InfoCubes too!) |
PRE Upgrade |
|
|
30 mins |
|
11 |
Save entries from table EDIFCT |
Any customer specific entries on this tables that needs to be saved. If there are some, then identify by comparing the entries before and after upgrade, since the upgrade will truncate the table during the upgrade and repopulate it with new entries. Possibly, try to export these and import them back after the upgrade. |
PRE Upgrade |
|
|
15 mins |
|
12 |
Check table RSBFILE |
Check the table RSBFILE (Open Hub Destinations: Files) for APPEND ENTRIES (Logical file name & Logical system) |
PRE Upgrade |
|
|
15 mins |
|
13 |
Reschedule process chains. Execute Process Chains |
Execute Process Chains and trouble shoot errors if any. |
POST Upgrade |
|
|
60 mins |
|
14 |
Execute BW Statistics Process chain |
1. Execute BW Statistics process chains. |
POST Upgrade |
|
|
10 mins |
|
15 |
Check Missing Indexes for Cubes (DB02) |
You can also list missing indexes using transaction DB02, pushbutton Missing Indexes. If a lot of indexes are missing, it can be useful to run the ABAP reports SAP_UPDATE_DBDIFF and SAP_INFOCUBE_INDEXES_REPAIR. Refer following link information on Misiing Indexes for InfoCube. |
POST Upgrade |
|
|
20 mins |
|
16 |
Remove All Process Chains from schedule. |
Check Any Process chains are scheduled to run Daily / Weekly / Monthly and remove all from Schedule. |
PRE Upgrade |
|
|
10 mins |
|
17 |
Clean-up Inconsistent PSA directory entries |
Execute this program in TCODE SE38. Program Name: RSAR_PSA_CLEANUP_DIRECTORY. |
PRE Upgrade |
|
|
30 mins |
|
18 |
Check consistency of PSA partitions. |
RSRV - PSA Check. |
PRE Upgrade |
|
|
10 mins |
|
19 |
Check compounding consistency in Multiproviders. |
When MultiProviders are activated, a check is made to establish whether the identification of characteristics and navigation attributes is consistent with respect to compounding. |
PRE Upgrade |
|
|
20 mins |
|
20 |
Time Characteristics Considerations |
Special consideration for modifications to time characteristics 0CURRENCY, 0UNIT, 0DATE, 0DATEFROM, 0DATETO, 0SOURCESYSTEM and 0TIME. |
POST Upgrade |
|
|
15 mins |
|
21 |
Validate BW Objects. |
BW Analyses Tool: RSRV to be run prior to upgrade to check for potential inconsistencies in BW |
PRE Upgrade |
|
|
30 Hrs |
|
22 |
Ensure DB Statistics are uptodate prior to upgrade. |
You can use this BRCONNECT function to update the statistics on the Oracle database for the cost-based optimizer. |
PRE Upgrade |
|
|
20 mins |
|
23 |
Finding and fixing Inconsistent DataSource |
OSS #579022 (Execute RSAR_TRANSTRUCTURE_CHECK) |
POST Upgrade |
|
|
30 mins |
|
24 |
All ODS data loads must be activated |
Activate all ODS Object where the activation queue is not empty. |
POST Upgrade |
|
|
15 mins |
|
25 |
All ODS data loads must be activated |
Activate all inactivated ODS object requests. All ODS 'M' tables must be emptied prior to the upgrade as a new activate process implemented. Inactivated ODS request can be located via the Administrative workbench -> "Monitoring" -> "ODS Status Overview" |
POST Upgrade |
|
|
15 mins |
|
26 |
All Transfer and Update rules should be active |
Check for inactive Update and Transfer Rules |
POST Upgrade |
|
|
15 mins |
|
27 |
All InfoCubes should be active |
Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!) |
POST Upgrade |
|
|
15 mins |
|
28 |
Save entries from table EDIFCT |
Any customer specific entries on this tables that needs to be saved. If there are some, then identify by comparing the entries before and after upgrade, since the upgrade will truncate the table during the upgrade and repopulate it with new entries. Possibly, try to export these and import them back after the upgrade. |
POST Upgrade |
|
|
10 mins |
|
29 |
Check table RSBFILE |
Check the table RSBFILE (Open Hub Destinations: Files) for APPEND ENTRIES (Logical file name & Logical system) |
POST Upgrade |
|
|
10 mins |
|
30 |
Check for possible inconsistencies with RSZ* tables in BW system |
Check any inconsistency in the system with RSZ* tables. |
PRE Upgrade |
|
|
10 mins |
|
31 |
Check 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. |
PRE Upgrade |
|
|
15 mins |
|
32 |
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. |
PRE Upgrade |
|
|
10 mins |
|
33 |
Activate the Myself source system and replicate all datasources. |
Reactivate the BI source system. Also replicate all the source system data sources. |
POST Upgrade |
|
|
30 mins |
|
34 |
Activate all Transfer structures and Update rules. |
Execute report RS_TRANSTRU_ACTIVATE_ALL for myself system and the source systems. |
POST Upgrade |
|
|
60 mins |
|
35 |
Migration for BEx history, variables personalization, Web Report Personalization |
Execute report RS_PERS_ACTIVATE |
POST Upgrade |
|
|
20 mins |
|
36 |
Rename the duplicate queries and then delete. Also correct the other errors. |
Execute program ANALYZE_RSZ_TABLES and rename the duplicate queries and then delete |
PRE Upgrade |
|
|
120 mins |
|
1. Related Content
http://forums.sdn.sap.com/thread.jspa?threadID=845002
http://www.sap-basis-abap.com/bc/difference-between-sap-notes-and-support-package.htm
2 Comments
Coskun Istanbulluoglu
Very good documentation. Thanks.
Former Member
Also useful the following link:
http://scn.sap.com/thread/1917754 : Impact on BI after ECC 6.0 Upgrade from EHP 3 to EHP 4