SAP ECC Systems SP Upgrade and Impact on SAP BI 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. PACK. In simple words C o l l ec CK.. ec t i o n o f S A P N O T E S i s a S U P P O R T P A CK
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 (Yes / No)
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). In RSA7 make sure all the delta Data Sources should remains empty by repetitive triggering of corresponding Delta Data Loads in BI side. In BI side, Data Loads Monitor is showing below:
3
All extraction queues and open update orders in all clients must be
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
processed.
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.
You can use transaction LBWG to delete the contents of the setup tables for all clients. Unfortunately the check that the system carries out during the upgrade or when you import a Support Package does not display all affected applications. Therefore, Note 1083709 provides a check report that you can use to determine all affected applications and tables or queues.
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 (Yes / No)
SAP BI Side (Yes / No)
1
Test the RFC connection between SAP ECC to SAP BI system
Yes
Yes
How-To
Check Source system
connection in RSA1 à Source Systems. 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
Phas e
1
Open Transport s Clean up. Make sure that all transports in DEV system should be released and imported to all downstrea m systems QA and PRD systems.
Check Open Transports in the system and clean up the same. o Go to SE10 and check the open transports in the system.
PRE Upgr ade
60 mi ns
2
Check
In this transation we can found the update statistics..means update
PRE
10
SM13 (Administ rate Update Records)
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. [http://help.sap.com/saphelp_nw04/helpdata/en/e5/de870535cd11d 3acb00000e83539c3/frameset.htm ]
Upgr ade
mi ns
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. · SMQ2 – qRFC Monitor for the inbound queue. You use this transaction to monitor the status of the LUWs in the outbound queue. . SM58 - Check the tRFC Status.
PRE Upgr ade
30 mi ns
4
Check Open Jobs.
Check SM37 for any scheduled / Active Jobs.
PRE Upgr ade
10 mi ns
5
Check for Inconsiste nt Infoobject s and repair inconsiste nt Infoobject s as much as possible.
Check the InfoObjects and repair them if necessary. o Transaction RSD1 (Edit InfoObjects), o Extras > Rapir InfoObjects o Execute Repair o Expert Mode > Select Objects
PRE Upgr ade
30 mi ns
o Select following checkboxes: • Check Generated Objects • Activate Inconsistent InfoObjects • Delete DDIC Ob jects • Display Log o Execute Program. o Check Log and prepare excel with inconsistent object details. Capture details like - Object Tech name - Description, What is the inconsistency, Any resolution given by SAP in Log. o If we found any inconsistent InfoObject that exists in the system, execute the report RSDG_IOBJ_ACTIVATE and activate a single InfoObject.
6
Finding and fixing Inconsiste nt DataSour ce
OSS #579022 (Execute RSAR_TRANSTRUCTURE_CHECK)
PRE Upgr ade
10 mi ns
7
Check Inactive Infoobject
Check for Inactive InfoObjects and activate.
PRE Upgr ade
10 mi ns
s 8
All ODS data loads must be activated
Activate all ODS Object where the activation queue is not empty. Refer to OSS: #905029 & #861890 RSDG_ODSO_ACTIVATE program There must be no data load request in the ODS objects with a yellow status. If any such entry is found, delete the request.
PRE Upgr ade
10 mi ns
9
All Transfer and Update rules should be active
Check for inactive Update and Transfer Rules o All update rules and transfer rules should be active. Execute ABAP RSUPGRCHECK to locate any inactive Update and Transfer Rules See SAP note 555717 and 449160.
PRE Upgr ade
60 mi ns
10
All InfoCube s should be active
Check for inactive InfoCubes / Multicubes and Aggregates (Aggregates are InfoCubes too!) o All InfoCubes should be activated o Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes See SAP note 555717 and 449160.
PRE Upgr ade
30 mi ns
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 Upgr ade
15 mi ns
12
Check table RSBFILE
Check the table RSBFILE (Open Hub Destinations: Files) for APPEND ENTRIES (Logical file name & Logical system)
PRE Upgr ade
15 mi ns
13
Reschedu le process chains. Execute Process Chains
Execute Process Chains and trouble shoot errors if any.
POS T Upgr ade
60 mi ns
14
Execute BW Statistics Process chain
1. Execute BW Statistics process chains. 2. Execute sample Standard statistics report to see Query statistics and capture results.
POS T Upgr ade
10 mi ns
15
Check Missing Indexes for Cubes
You can also list missing indexes using transaction DB02, pushbutton Missing Indexes. If a lot of indexes are missing, i t can be useful to run the ABAP reports SAP_UPDATE_DBDIFF and SAP_INFOCUBE_INDEXES_REPAIR. Refer following link
POS T Upgr ade
20 mi ns
(DB02)
information on Misiing Indexes for InfoCube. http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a6473e072 11d2acb80000e829fbfe/frameset.htm
16
Remove All Process Chains from schedule.
Check Any Process chains are scheduled to run Daily / Weekly / Monthly and remove all from Schedule. No process chains should be in schedule mode. Go to RSPC & click on schedule tab & remove the chains from schedule.
PRE Upgr ade
10 mi ns
17
Clean-up Inconsiste nt PSA directory entries
Execute this program in TCODE SE38. Program Name: RSAR_PSA_CLEANUP_DIRECTORY. With this function we delete requests from the PSA. This reduces the volume of data in the PSA. It is a good idea to delete incorrect requests or deltas for a data target, to which you do not want to load any more delta.
PRE Upgr ade
30 mi ns
18
Check consisten cy of PSA partitions.
RSRV - PSA Check.
PRE Upgr ade
10 mi ns
19
Check compoun ding consisten cy in Multiprov iders.
When MultiProviders are activated, a check is made to establish whether the identification of characteristics and navigation attributes is consistent with respect to compounding. Report RSCOMPCONS helps you to identify inconsistent MultiProviders. When you execute the report, it lists MultiProviders that are inconsistent with respect to compounding
PRE Upgr ade
20 mi ns
20
Time Character istics Considera tions
Special consideration for modifications to time characteristics 0CURRENCY, 0UNIT, 0DATE, 0DATEFROM, 0DATETO, 0SOURCESYSTEM and 0TIME.
POS T Upgr ade
15 mi ns
21
Validate BW Objects.
BW Analyses Tool: RSRV to be run prior to upgrade to check for potential inconsistencies in BW
PRE Upgr ade
30 Hr s
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. BRCONNECT supports update statistics for the following:
PRE Upgr ade
20 mi ns
· Partitioned tables, except where partitioned tables are explicitly excluded by setting the active flag in the DBSTATCtable to I. For more information, see SAP Note 424243.
· InfoCube tables for the SAP Business Information Warehouse (SAP BW) 23
Finding and fixing Inconsiste nt DataSour ce
OSS #579022 (Execute RSAR_TRANSTRUCTURE_CHECK)
POS T Upgr ade
30 mi ns
24
All ODS data loads must be activated
Activate all ODS Object where the activation queue is not empty. Refer to OSS: #905029 & #861890 RSDG_ODSO_ACTIVATE program
POS T Upgr ade
15 mi ns
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"
POS T Upgr ade
15 mi ns
26
All Transfer and Update rules should be active
Check for inactive Update and Transfer Rules o All update rules and transfer rules should be active or deleted. Execute ABAP RSUPGRCHECK to locate any inactive Update and Transfer Rules See SAP note 555717 and 449160.
POS T Upgr ade
15 mi ns
27
All InfoCube s should be active
Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!) o All InfoCubes should be activated or deleted. o Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes See SAP note 555717 and 449160.
POS T Upgr ade
15 mi ns
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.
POS T Upgr ade
10 mi ns
29
Check table RSBFILE
Check the table RSBFILE (Open Hub Destinations: Files) for APPEND ENTRIES (Logical file name & Logical system)
POS T Upgr ade
10 mi ns
30
Check for possible inconsiste
Check any inconsistency in the system with RSZ* tables. Execute the report ANALYZE_RSZ_TABLES. Correct any such inconsistency.
PRE Upgr ade
10 mi ns
ncies with RSZ* tables in BW system
Also refer SAP Note 792779
31
Check Master Data Consisten cy
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 Upgr ade
15 mi ns
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 Upgr ade
10 mi ns
33
Activate the Myself source system and replicate all datasourc es.
Reactivate the BI source system. Also replicate all the source system data sources.
POS T Upgr ade
30 mi ns
34
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.
POS T Upgr ade
60 mi ns
35
Migration for BEx history, variables personaliz ation, Web Report Personali zation
Execute report RS_PERS_ACTIVATE
POS T Upgr ade
20 mi ns
36
Rename the
Execute program ANALYZE_RSZ_TABLES and rename the duplicate queries and then delete
PRE Upgr
12 0
duplicate queries and then delete. Al so correct the other errors.
ade
mi ns
