BW Operations

Customer: NXP Semiconductors

By: Laurens Vestjens

CIBER Netherlands
Telephone: +31-40-2329090
Fax:
+31-40-2329091
Web:
www.ciber.nl

Revision History
Version Issue Date Modified By:
Draft V1 Jul. 2007
Laurens Vestjens
Final
Jul. 2007
Laurens Vestjens

Summary of Changes
First draft with structure

Content
1

SUMMARY...............................................................................................................................................................4

ACTIVITIES.............................................................................................................................................................4
2.1
2.2
2.3
2.4
2.5

MONITORING.........................................................................................................................................................6
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12

INACTIVE BW OBJECTS....................................................................................................................................12
QUERY CONSISTENCY.......................................................................................................................................12
SOURCE SYSTEM CONNECTIONS.......................................................................................................................12
REORGANIZE UNSED WORKBOOKS AND FAVOURITES.......................................................................................13
TRFC ENTRIES..................................................................................................................................................13
UNREFERENCED OBJECTS.................................................................................................................................14
INFOOBJECTS....................................................................................................................................................14
DATASOURCE REPLICATION AND TRANSFER RULES ACTIVATION......................................................................15
USER IDS........................................................................................................................................................15
UNUSED QUERIES.............................................................................................................................................15
SYSTEM RESTART..............................................................................................................................................16
EARLY WATCH REPORT.....................................................................................................................................16

PERFORMANCE...................................................................................................................................................16
5.1
5.2
5.3
5.4
5.5

BATCH JOBS........................................................................................................................................................6
DATA LOADS.......................................................................................................................................................6
REPORT ABILITY OF DATA...................................................................................................................................6
MISSING INDEXES...............................................................................................................................................7
FREE SPACE........................................................................................................................................................8
ABAP DUMPS.....................................................................................................................................................9
SYSTEM LOGS...................................................................................................................................................10
INTERNET GRAPHIC SERVER (IGS)...................................................................................................................10
AGGREGATES....................................................................................................................................................11
QUERY PERFORMANCE.....................................................................................................................................11
DATABASE BACKUPS.........................................................................................................................................11
BW STATISTICS.................................................................................................................................................11

SYSTEM HEALTH................................................................................................................................................12
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12

MONITORING......................................................................................................................................................4
SYSTEM HEALTH.................................................................................................................................................4
PERFORMANCE...................................................................................................................................................5
FREE SPACE........................................................................................................................................................5
CHANGES............................................................................................................................................................5

DATABASE AND SAP STATISTICS......................................................................................................................16

UNUSED DIMENSION TABLE ENTRIES................................................................................................................17
BW STATISTICS.................................................................................................................................................17
INFOCUBE INDEXES..........................................................................................................................................17
READ MODE OF QUERIES AND INFOCUBES.......................................................................................................18

FREE SPACE..........................................................................................................................................................18

Page 2 of 27

februari 21, 2016

Version: 1.0

6.1
6.2
6.3
6.4
6.5
6.6
6.7
7

UNSED DATABASE PARTITIONS.........................................................................................................................18

TEMPORARY TABLES........................................................................................................................................19
LOG-FILES........................................................................................................................................................20
ARCHIVING.......................................................................................................................................................20
PSA TABLES CLEAN-UP....................................................................................................................................20
COMPRESSION..................................................................................................................................................21
BW STATISTICS.................................................................................................................................................21

CHANGES..............................................................................................................................................................22
7.1
7.2
7.3
7.4
7.5

SAP NOTES / SERVICE PACKS / ADD-ONS..........................................................................................................22

BW UPGRADES.................................................................................................................................................22
TRANSPORT......................................................................................................................................................22
CLIENT COPY ACTIVITIES.................................................................................................................................22
DATABASE AND KERNEL SETTINGS...................................................................................................................22

APPENDIX A: SAP KERNEL AND DATABASE SETTINGS...................................................................................22

APPENDIX B: ONE-TIME ACTIONS.........................................................................................................................22

Page 3 of 27

februari 21, 2016

Version: 1.0

1 Summary
The following chapters describe the actions that BW operation needs to perform to keep a BW landscape
well performing and in the best possible condition. These actions improve speed (loading as well as
reporting), as well as a small(er) database. They also improve the stability of the landscape: lesser failed
uploads, stable source system connections, consistent master data and lesser problem reports by the user.
Chapter 2 describes the activities that BW operations needs to take care of.
Chapter 3 describes in more detail all monitoring activities of BW operations
Chapter 4 describes in more detail all system health improving activities
Chapter 5 describes in more detail all performance improving activities
Chapter 6 describes in more detail all activities to free up database space
Chapter 7 describes in more detail all activities related to changes to the BW landscape
Appendix A: SAP kernel and database settings that need to be taken into account for good performance.
Appendix B: one-time actions to be taken to assure the correct working and proper performance.

2 Activities
Abbreviations:
o BW:
BW operations team
o SB:
SAP BASIS team
o MO:
System management / Managed Operations

2.1

Monitoring

Description
Batch jobs
Data loads: InfoPackages, InfoPackage groups and process chains
Report ability of data loads in InfoCubes and ODS objects
Missing indexes in the database
Database free space
ABAP dumps
System logging
Internet Graphic Server (IGS)
Aggregates: status / usage
Query performance, perform corrective actions
Monitor if database backups have been made

Freq.
daily
daily
daily
daily
daily
daily
daily
daily
monthly
monthly
daily

Monitor if the server has been restarted on a weekly basis

weekly

Check if all InfoProviders are still BW statistics relevant, so the OLAP time etc. will
be updated in the BW statistics InfoCubes
For a list of tools to perform correct monitoring, see chapter 3.

weekly

Who
BW / SB
BW
BW
BW
BW / SB
BW / SB
BW / SB
BW
BW
BW
BW /
SB / MO
BW /
SB / MO
BW

Freq.

Who

2.2

System health

Description
Page 4 of 27

februari 21, 2016

Version: 1.0

Make sure all BW objects are active in production like transfer rules and update
rules, but also MultiProviders, InfoObjects, InfoObject catalogs, etc.
Make sure all queries are consistent and can be executed. Make also sure there are
no queries with duplicate names
Check all source system connections if they still work
Reorganize unused workbooks and favorites
Reorganize / delete unprocessed tRFC entries
Clean-up unreferenced objects like PSA tables, transfer rules, etc.
Make sure InfoObjects are consistent, definitions as well as the data
Replicate datasources / regenerate transfer rules
Lock /cleanup user IDs that dont use the system / didnt logon recently
Delete old / unused queries
Process SAP Early Watch report
For a list of tools for system health checking, see chapter 4.

daily

BW

weekly

BW

weekly
weekly
weekly
weekly
monthly
weekly
monthly
monthly
-

BW
BW
BW
BW
BW
BW
SB
BW
BW / SB

Freq.
weekly
weekly
monthly
quarterly
monthly

Who
BW / SB
BW
BW
BW
BW

Freq.
weekly
daily

Who
BW
BW

weekly
weekly
weekly
weekly
monthly

BW
BW
BW
BW
BW

Description
Apply SAP notes / SAP service packs / add-ons
BW upgrades
Transports
Client copy activities

Freq.
-

Check database and SAP kernel parameters

For a list of tools for handling changes, see chapter 7.

Who
SB
SB / MO
BW / SB
BW / SB /
MO
SB / MO

2.3

Performance

Description
Optimize database and SAP statistics for better performance
Delete unused dimension table entries of InfoCubes
Evaluate BW statistics for query and load performance
Drop / recreate indexes on InfoCubes
Read mode of queries and InfoCubes
For a list of tools for performance checking, see chapter 5.

2.4

Free space

Description
Delete unused partitions in F-tables of InfoCube
Remove unused temporary query / analytics / realignment run tables in table space
PSAPTEMP
Delete log-files: database / application / error logs
Archive IDocs
Clean-up PSA table content
Compress InfoCubes
Delete old BW statistics
For a list of tools for achieving free space, see chapter 6.

2.5

Changes

Page 5 of 27

februari 21, 2016

Version: 1.0

3 Monitoring
3.1

Batch jobs

Tool: tx SM37, tx ZDAILY

Check with tx SM37 all batch jobs that have status Canceled. Try to solve the issue, perhaps by rerunning
the batch job.
Example of canceled batch jobs:

3.2

Data loads

Tools: tx RSMO, tx RSMON, tx RSPC, tx RSPCM, tx ZDAILY

o
o
o
o
o

Make sure all InfoPackages (groups) finished successfully with tx RSMO.

Make sure all process chains have finished successfully. Rerun them if necessary.
Make also sure the InfoPackages loaded via the PSA are also booked from PSA into their data targets.
Verify if transaction data loads with 0 records are valid.
Analyze PSA error requests that occur. Determine if the error records are valid.

Example of the load monitor:

3.3

Report ability of data

Tools: tx RSA1 (maintenance of InfoCubes / ODS objects), tx ZDAILY.

Page 6 of 27

februari 21, 2016

Version: 1.0

o
o

Check if the data in all active InfoCubes is reportable. Data could be loaded, but aggregates are not
rolled up yet.
Check also if data in all active ODS objects is activated and booked into its data targets.

Example of unreportable data loads:

In ODS SAPP_O01 2 data request are not booked to their data targets.

3.4

Missing indexes

Tools: tx DB02, tx ZDAILY, tx SE14

o

Run tx DB02 to find out if there are missing indexes.

Example:

Page 7 of 27

februari 21, 2016

Version: 1.0

In previous screenprint 3 indexes and 4 tables are missing.

Make sure there are no database indexes missing other than the ones that are dropped to speed up
data loads into an InfoCube. Perform this test multiple times a day. If InfoCube indexes stay missing,
create them via the maintenance screen of InfoCubes, Performance tab.

Example:

Page 8 of 27

februari 21, 2016

Version: 1.0

If the indexes dont belong to an InfoCube, like in the example, create them by using tx SE14

3.5

Free space

Tools: tx DB02
o

Make sure that theres enough database space free for the system. How much needs to be free,
depends on the system. The table space that contains the BW related data should have at least 30GB,
depending on how much data is added on a daily basis. If theres not enough free space, its a good
idea to start deleting unused PSA packages. If that is not possible, start the process of adding more disk
space to the application.

Example:

In this example there are no Space-critical objects and the Total free/kb is about 33% of the database size.

In this example the main table space PSAPBWP is free for 33%. No problem here.

3.6

ABAP dumps

Tools: tx ST22, tx ZDAILY

o

Try to solve recurring ABAP dumps. Apply SAP notes if needed.

Page 9 of 27

februari 21, 2016

Version: 1.0

Example:

3.7

System logs

Tools: tx SM21, tx ZDAILY

o

Try to solve recurring problems in the system log. Apply SAP notes if needed.

Example of some problems in the system log:

3.8

Internet Graphic server (IGS)

Tools: tx ZDAILY, ABAP BW_IGS_CHART_TEST

o

Check if the IGS is still operational using ABAP BW_IGS_CHART_TEST. If not fix it.

An example of a correct working IGS server:

Page 10 of 27

februari 21, 2016

Version: 1.0

3.9

Aggregates

Tool: tx RSA1, tx RSMON

Aggregates should boost query performance on an InfoCube, but also cost time to activate master data and
load performance to fill them. An aggregate should not be created lightly: there has to be a good reason for
its existence.
o

Check the usage of aggregates. Determine that the aggrgate is actually used or useful for filling other
aggregates. If not, delete the aggregate. If an aggregate is activated, but not filled, remove it.

Example of 2 bad aggregates, that are never used since creation:

Example of a non-filled aggregate:

3.10 Query performance

Tool: tx RSRT, queries on the BW statistics InfoCubes
o

Run a BW statistics report to show the top 25 of worst performing queries. Improve their performance.

3.11 Database backups

Tool: tx DB14 and others
o

Make sure there is a daily backup made of the complete BW system

Page 11 of 27

februari 21, 2016

Version: 1.0

3.12 Restart server

Tool: tx OS06 and others
o

Make sure the BW server is restarted periodically.

3.13 BW statistics
Tool: tx RSA1, Tools, BW statistics for InfoProviders, tx ZWEEKLY option 22
o

Make sure all InfoProviders are switched on for BW statistics collection, the OLAP as well as the
warehouse management part. If the collection is switched on performance valuations can be made.

Example:

4 System health
4.1

Inactive BW objects

Tool: tx ZDAILY, ABAP RS_TRANSTRU_ACTIVATE_ALL, transports

o

Make sure the following BW objects are always active:

o Transfer rules
o Update rules
o InfoObjects
o InfoCubes
o ODS objects
o MultiProviders
o And all others

In a BW some object can become inactive due to some reasen. If update rules become inactive its
impossible to load data via them anymore.
If transfer rules are inactive, they can be activated without transport via ABAP
RS_TRANSTRU_ACTIVATE_ALL. All other inactive objects should be repaired by transport rather than
activating them in the system itself (via opening it).

4.2

Query consistency

Tool: tx ZDAILY, tx ZWEEKLY option 08, tx RSRT, ABAP RSR_GEN_DIRECT_ALL_QUERIES, ABAP

RENAME_DUPLICATE_ELEMENTS, ABAP ANALYZE_RSZ_TABLES
o

Make sure there are no queries with duplicate names. Run ABAP
RENAME_DUPLICATE_ELEMENTS to correct any inconsistencies. See not 541024 for further
details.

Page 12 of 27

februari 21, 2016

Version: 1.0

o
o
o

Make sure the metadata tables of queries are consistent. Run ABAP ANALYZE_RSZ_TABLE to
check and repair this.
Run RSR_GEN_DIRECT_ALL_QUERIES on a weekly basis for all queries, so ZDAILY will show all
queries that dont compile. Compiled queries are also faster when running them.
Make sure all queries compile (and are therefore consistent). If they dont compile repair them of delete
them.

Queries become inactive (and inconsistent) if something changes to their InfoProvider. Sometimes a
characteric is deleted from the InfoCube, but a certain query is not changed. Result: de query wont run
naymore.ZDAILY will show all those inactive queries. Queries can be compiled via RSRT or via ABAP
RSR_GEN_DIRECT_ALL_QUERIES. If a query doesnt compile, fix it in BW-D.
Example of an inactive query:

4.3

Source system connections

Tool: tx RSA13, tx ZDAILY, tx ZWEEKLY option 12, ABAP RS_LOGSYS_ACTIVATE

o

Make sure all source system connections are consistent and active. If not, repair the connection or
remove it.

Inconsistent source system connections make it impossible to load data. Example of inconsistent
connections (in this case connection INFORDEV):

4.4

Reorganize unsed workbooks and favourites

Tool: tx ZWEEKLY option 02, ABAP RSWB_ROLES_REORG

o

Run ABAP report RSWB_ROLES_REORG to delete workbooks not assigned to any role or favorites.

When users or authorization roles are deleted, workbooks linked to roles of favourites get unreferenced and
cannot be called anymore. The mentioned ABAP will remove via a selection screen all relations.
Example of the selection screen:

Page 13 of 27

februari 21, 2016

Version: 1.0

4.5

tRFC entries

Tool: tx SM58, tx ZWEEKLY option 03

o

Clean up transactional RFCs from cancelled loads in all BW- and connected systems.

When a data loads cancels, some residus are left behind in the system(s). One of those residues are
tRFCs. SM58 shows those tRFCs and offers a reorganize (delete) option.
Example of error tRFCs:

4.6

Unreferenced objects

Tool: tx ZWEEKLY option 09, tx ZMONTHLY option 14 till 22

Cleanup unreferenced / inconsistent objects in the database in the most broadest sense of the word.
o
o

Check transfer rules consistency by running ABAP RSAR_TRANSTRUCTURE_CHECK. See note

577022 for more details.
Correct PSA tables (Oracle) that have partition number 0 by running ABAP
SAP_PSA_ZEROCORRECT. These are inconsistent and need to be fixed. See SAP note 856097 for
further details.

Run ABAP SAP_PSA_ZEROCORRECT to correct PSA table with partition number 0. Sometimes a
correction can be made, so the data is still available. If this correction cannot be made, the content is
deleted.

Page 14 of 27

februari 21, 2016

Version: 1.0

o
o
o
o
o
o
o
o

4.7

Clean up unreferenced PSA metadata objects by using ABAP RSAR_PSA_CLEANUP_DEFINITION.

See note 739407 for further details.
Clean-up unused / inconsistency PSA tables by running ABAP RSAR_PSA_CLEANUP_DIRECTORY.
See note 773371 for further details.
Activate inactive communication structures by running ABAP RS_COMSTRU_ACTIVATE_ALL. See
note 542872 for further details.
Correct duplicate transfer structures in table RSISOSMAP by running ABAP
RSAR_RSISOSMAP_REPAIR. See note 613449 for further details.
Correct source system consistency (table ROOSGEN) by running ABAP
RS_SRCSYSTEM_TS_CHECK.
Check the consistency of DDIC names for transfer rules and InfoSources by running ABAP
RSAR_DDIC_NAME_CONFLICT. See also note 542872.
Correction for the technical name of transfer structures and communication structures by running ABAP
RSAR_STRUCTURE_NAMES_CHECK.
Clean obsolete entries in table DBDIFF, by running ABAP SAP_UPDATE_DBDIFF.

InfoObjects

Tool: tx RSD1 F8, tx ZWEEKLY option 10, ABAP RSDMD_CHECKPRG_ALL, ABAP

RSDG_IOBJ_REORG
o

Check the consistency of the content of the master data and text tables of InfoObjects and repair any
inconsistencies.

Run frequently ABAP RSDMD_CHECKPRG_ALL to check the consistency of all InfoObjects and repair
inconsistencies. See note 447341 for further details.

Page 15 of 27

februari 21, 2016

Version: 1.0

Check the consistency of the meta data of InfoObjects.

Run ABAP RSDG_IOBJ_REORG to check the consistency of all InfoObjects and repair any
inconsistencies to the definitions.

4.8

Datasource replication and transfer rules activation

Tool: tx ZUTIL3 option 13, ABAP ZSS_REPLICATE, ABAP RS_TRANSTRU_ACTIVATE_ALL

o

4.9

To avoid problems in uploads, replicate all datasources of all connected source systems, and afterwards
regenerate all transfer rules of all source systems.

User IDs

Tool: tx SU01
o
o

Lock all users that havent logged on to the system in the last 3 months
Delete all users from the system that havent logged on for the last 6 months.

4.10 Unused queries

Tool: BW statistics queries
o

Determine unused queries and delete them

4.11 Early watch report

Tool: tx SDCC
o

Run tx SDCC for an unedited version of the SAP Early Watch report. Try to solve the recommendations.

Page 16 of 27

februari 21, 2016

Version: 1.0

5 Performance
Tool: tx OS06, tx SM04, tx AL08, tx SM50, tx SM51, tx SM66, tx ST03, tx ST04
o
o
o
o
o

5.1

Check CPU load with transaction OS06.

Check the number of users logged on to the system with SM04 or AL08.
Check the workload of the system with transaction ST03.
Check the workload of all processes with SM50, SM51 or SM66.
Check the database performance with ST04.

Database and SAP statistics

Tool: tx ZWEEKLY option 04, tx DB14, ABAP SAP_ANALYZE_ALL_INFOCUBES, ABAP

ZCHECK_IC_DB_STATISTICS
o

Calculate good database statistics

For Oracle databases, run the BRCONNECT script to calculate good database statistics. Use tx DB14 to
view the result of the batch job. If the job aborts or runs too long like in the next example, double click on the
line to review the joblog.
Example of a wrong Update optimizer statitstics:

The detailed log:

Page 17 of 27

februari 21, 2016

Version: 1.0

Recalculate good BW statistics for InfoCubes

Job on basis of SAP_ANALYZE_ALL_INFOCUBES (note 129252): run once a week to collect good SAP
statistics on InfoCubes.

Run periodically function RSDDCVER_DB_STATISTICS (or ABAP ZCHECK_IC_DB_STATISTICS) to

calculate database statistics for an InfoCube.

Use transaction RSRV (and RSRVALT) on a regular basis to check InfoCubes. Most importantly tag
Database, options DB statistics of an InfoCube and its aggregates to check the health of an InfoCube

5.2

Unused dimension table entries

Tool: tx RSRVALT, ABAP UNUSED_ENTRIES_IN_DIM_TABLES

o

Remove unused dimension table entries of an InfoCube.

Run function module RSDRD_DIM_REMOVE_UNUSED to delete unused dimension table entries of an

InfoCube. You can also do this by running RSRVALT, tag InfoCube data, option Unused entries in the
dimensions of an InfoCube. Or by running ABAP Z_UNUSED_ENTRIES_IN_DIM_TABLES.

5.3

BW statistics

Tool: BW statistics queries

Page 18 of 27

februari 21, 2016

Version: 1.0

5.4

Evaluate the system performance using BW statistics queries.

InfoCube indexes

Tool: tx RSA11, Manage (of InfoCubes), Performance tab

o

Drop indexes on all InfoCubes, and recreate them. Suggestion: change the first and next extent sizes of
the InfoCube F-, E- and dimension tables (with SE14).

Use transaction RSRV (and RSRVALT) on a regular basis to check InfoCubes. Most importantly tag
Database, option Indices of an InfoCube and its aggregate to check the health of an InfoCube.
Example of RSRVALT on InfoCube SFP_C04:

And the result:

5.5

Read mode of queries and InfoCubes

Tool: tx ZWEEKLY option 22, tx RDMD, tx RSRT

o

Switch the read mode of InfoCubes and queries to type H (tx RSRT and RDMD). Also check regularly if
the read mode stays H for new InfoCube / query developments. See notes 422527.

Page 19 of 27

februari 21, 2016

Version: 1.0

One can find the InfoCubes with the wrong read mode by looking in table RSDCUBE, column READMODE,
and for queries table RSRREPDIR column READMODE.

6 Free space
6.1

Unsed database partitions

Tool: tx ZWEEKLY option 01, ABAP SAP_DROP_EMPTY_FPARTITIONS, ABAP ZBW0005

o

Remove unused and empty partitions in the F-table of InfoCubes.

Run frequently ABAP SAP_DROP_EMPTY_FPARTITIONS. See note 430486 for further details.

Or run ABAP ZBW0005 to check all InfoCubes in one run. Corrections still needs to be carried out with
ABAP SAP_DROP_EMPTY_FPARTITIONS.

6.2

Temporary tables

Tool: tx ZWEEKLY option 051 and 052, tx ZUTIL option 15, ABAP SAP_DROP_TMPTABLES, ABAP
RSAN_RTT_CLEAR_TEMP_TABLES
o

Run frequently or schedule ABAP report SAP_DROP_TMPTABLES. See notes 308533, 449841 for
further details

Page 20 of 27

februari 21, 2016

Version: 1.0

Run frequently or schedule ABAP report RSAN_RTT_CLEAR_TEMP_TABLES.

Example of the output:

6.3

Run frequently function module RSDDS_CHANGERUN_TMPTABLS_DEL or tx ZUTIL, option 15. See

note 650780 for further details.

Log-files

Tool: tx ZWEEKLY options 061, 062 and 063, ABAP SBAL_DELETE, ABAP RSTBPDEL, ABAP
RSSM_ERRORLOG_CLEANUP
Remove old application logs from the database
o
o
o

6.4

Run periodically ABAP RSSM_ERRORLOG_CLEANUP to remove old error logs (note 456150).
Run periodically ABAP RSTBPDEL to remove old database table logs (note 706478).
Run periodically ABAP SBAL_DELETE to remove old application logs (note 456150).

Archiving

Tool: tx SARA, tx ZWEEKLY option 11, ABAP RSEXARCA

o

Archive and remove processed IDocs from the database

Archive the BW related IDocs with transaction SARA or ABAP report RSEXARCA.

6.5

PSA tables clean-up

Tool: tx ZWEEKLY option 20, tx RSA15, ABAP ZCHECK_PSA_TABLE_SIZES

Page 21 of 27

februari 21, 2016

Version: 1.0

Remove unnecessary PSA packages from the database. Schedule periodic jobs to remove them, or do
it by hand.

Example of the output of ZWEEKLY option 20:

6.6

Compression

Tool: tx ZWEEKLY option 21, tx RSA11

o

6.7

Compress as much and soon as possible. See notes 375132, 407260, 590370 for further details

BW statistics

Tool: tx RSA1, Tools, BW Statistics for InfoProviders, F7

o

Delete old BW statistics on a regular basis

Example:

Page 22 of 27

februari 21, 2016

Version: 1.0

7 Changes
7.1

SAP notes / service packs / add-ons

Tool: tx SNOTE, tx SAINT, tx SPAM

o
o
o

7.2
o

7.3

Implement a SAP note on demand

Implement SAP service packs on demand. Typically this would happen twice a year. More frequent if the
BW version is rather new and the service packs come out more frequent, lesser when the BW version is
at the end of its life cycle.
Implement BW add-ons on demand.

BW upgrades
Upgrade the BW system on demand.

Transport

Tool: tx STMS
o

7.4

Import transports into the system on demand

Client copy activities

Tool: tx RSA13, Restore Source System

o

7.5

After a client copy of an connected source system, the connection needs to be restored

Database and kernel settings

Tool: tx RZ10, and others

o

Revaluate the SAP kernel and database settings on a yearly basis.

Page 23 of 27

februari 21, 2016

Version: 1.0

Appendix A: SAP kernel and database settings

By implementing following notes, the overall system performance will be improved.
Note
Description
129252
Oracle DB Statistics for BW Tables
180605
Oracle parameters for BW
184905
Profile parameters for BW
192658
Setting basis parameters for BW systems.
351163
Better Oracle statistics by implementing.
359835
Design of the temporary table space in the BW System, solution part 4. SAP recommends more
like 10GB for size.
417307
Extractor package size: Collective note for applications
428212
Update of statistics of InfoCubes with BRCONNECT.
565075
Recommendations for BW systems with Oracle 8.1.x
567745
Composite note BW 3.x performance: DB-specific settings
RZ10
Change parameter rdisp/max_wprun_time to at least 3600 in all BW systems.

Appendix B: One-time actions

Description
Switch on the correct Oracle statistics calculation table RSADMIN, parameter ORA_DMBS_STATS value 3
(see note 351163)
Create a daily backup of the database. Schedule the job on a daily basis.
Restart the BW server. Schedule the job on a weekly basis.
Switch on other RSADMIN parameters like ORA_PARALLEL_DEGREE, USE_FACTVIEW,
RSDM_F4_NO_XYTAB_JOIN and SPLIT_SX_TABL_THRES
Switch MultiProvider reporting to parallel in table RSADMIN (parameter MP_IMPL_MAP, note 907246)
Process IDocs with status 64 (status halt).
Schedule ABAP RBDAPP01 to reprocess these status 64 IDocs every 15 minutes.

Page 24 of 27

februari 21, 2016

Version: 1.0

Process waiting E-mails and other communication methods

Schedule ABAP RSCONN01 every 15 minutes to process waiting E-mails

Page 25 of 27

februari 21, 2016

Version: 1.0

Import exchange rates from R/3

Schedule ABAP RSIMPCURR on a daily basis to get the latest exchange rates

Import currency and unit of measurement definitions from R/3

Schedule ABAP RSIMPCUST to run weekly in order to get the latest currency and unit of measurement
definitions.

Import factory calendars from R/3

Schedule ABAP RSIMPCUST to run weekly in order to get the latest factory calendars.

Page 26 of 27

februari 21, 2016

Version: 1.0

Page 27 of 27

februari 21, 2016

Version: 1.0