BW Operations

Customer: NXP Semiconductors

By: Laurens Vestjens

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

BW Operations

http://www.ciber.nl/

Revision HistoryVersion Issue Date Modified By: Summary of ChangesDraft V1 Jul. 2007 Laurens Vestjens First draft with structureFinal Jul. 2007 Laurens Vestjens

Content

1 SUMMARY...............................................................................................................................................................4

2 ACTIVITIES.............................................................................................................................................................4

2.1 MONITORING......................................................................................................................................................42.2 SYSTEM HEALTH................................................................................................................................................42.3 PERFORMANCE...................................................................................................................................................52.4 FREE SPACE........................................................................................................................................................52.5 CHANGES............................................................................................................................................................5

3 MONITORING.........................................................................................................................................................6

3.1 BATCH JOBS........................................................................................................................................................63.2 DATA LOADS......................................................................................................................................................63.3 REPORT ABILITY OF DATA..................................................................................................................................63.4 MISSING INDEXES...............................................................................................................................................73.5 FREE SPACE........................................................................................................................................................83.6 ABAP DUMPS.....................................................................................................................................................93.7 SYSTEM LOGS...................................................................................................................................................103.8 INTERNET GRAPHIC SERVER (IGS)..................................................................................................................103.9 AGGREGATES...................................................................................................................................................113.10 QUERY PERFORMANCE.....................................................................................................................................113.11 DATABASE BACKUPS........................................................................................................................................113.12 BW STATISTICS................................................................................................................................................11

4 SYSTEM HEALTH................................................................................................................................................12

4.1 INACTIVE BW OBJECTS....................................................................................................................................124.2 QUERY CONSISTENCY.......................................................................................................................................124.3 SOURCE SYSTEM CONNECTIONS.......................................................................................................................124.4 REORGANIZE UNSED WORKBOOKS AND FAVOURITES......................................................................................134.5 TRFC ENTRIES..................................................................................................................................................134.6 UNREFERENCED OBJECTS.................................................................................................................................144.7 INFOOBJECTS....................................................................................................................................................144.8 DATASOURCE REPLICATION AND TRANSFER RULES ACTIVATION....................................................................154.9 USER ID’S........................................................................................................................................................154.10 UNUSED QUERIES.............................................................................................................................................154.11 SYSTEM RESTART.............................................................................................................................................164.12 EARLY WATCH REPORT....................................................................................................................................16

5 PERFORMANCE...................................................................................................................................................16

5.1 DATABASE AND SAP STATISTICS.....................................................................................................................165.2 UNUSED DIMENSION TABLE ENTRIES...............................................................................................................175.3 BW STATISTICS................................................................................................................................................175.4 INFOCUBE INDEXES..........................................................................................................................................175.5 READ MODE OF QUERIES AND INFOCUBES.......................................................................................................18

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

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

Page 2 of 27 april 27, 2023 Version: 1.0

6.2 TEMPORARY TABLES........................................................................................................................................196.3 LOG-FILES........................................................................................................................................................206.4 ARCHIVING.......................................................................................................................................................206.5 PSA TABLES CLEAN-UP....................................................................................................................................206.6 COMPRESSION..................................................................................................................................................216.7 BW STATISTICS................................................................................................................................................21

7 CHANGES..............................................................................................................................................................22

7.1 SAP NOTES / SERVICE PACKS / ADD-ONS.........................................................................................................227.2 BW UPGRADES.................................................................................................................................................227.3 TRANSPORT......................................................................................................................................................227.4 CLIENT COPY ACTIVITIES.................................................................................................................................227.5 DATABASE AND KERNEL SETTINGS..................................................................................................................22

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

Appendix B: One-time actions.......................................................................................................................................22


1 SummaryThe 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 ActivitiesAbbreviations:

o BW: BW operations teamo SB: SAP BASIS teamo MO: System management / Managed Operations

2.1 MonitoringDescription Freq. WhoBatch jobs daily BW / SBData loads: InfoPackages, InfoPackage groups and process chains daily BWReport ability of data loads in InfoCubes and ODS objects daily BWMissing indexes in the database daily BWDatabase free space daily BW / SBABAP dumps daily BW / SBSystem logging daily BW / SBInternet Graphic Server (IGS) daily BWAggregates: status / usage monthly BWQuery performance, perform corrective actions monthly BWMonitor if database backups have been made daily BW /

SB / MOMonitor if the server has been restarted on a weekly basis weekly BW /

SB / MOCheck if all InfoProviders are still BW statistics relevant, so the OLAP time etc. will be updated in the BW statistics InfoCubes

weekly BW

For a list of tools to perform correct monitoring, see chapter 3.

2.2 System healthDescription Freq. Who


Make sure all BW objects are active in production like transfer rules and update rules, but also MultiProviders, InfoObjects, InfoObject catalogs, etc.

daily BW

Make sure all queries are consistent and can be executed. Make also sure there are no queries with duplicate names

weekly BW

Check all source system connections if they still work weekly BWReorganize unused workbooks and favorites weekly BWReorganize / delete unprocessed tRFC entries weekly BWClean-up unreferenced objects like PSA tables, transfer rules, etc. weekly BWMake sure InfoObjects are consistent, definitions as well as the data monthly BWReplicate datasources / regenerate transfer rules weekly BWLock /cleanup user ID’s that don’t use the system / didn’t logon recently monthly SBDelete old / unused queries monthly BWProcess SAP Early Watch report - BW / SBFor a list of tools for system health checking, see chapter 4.

2.3 PerformanceDescription Freq. WhoOptimize database and SAP statistics for better performance weekly BW / SBDelete unused dimension table entries of InfoCubes weekly BWEvaluate BW statistics for query and load performance monthly BWDrop / recreate indexes on InfoCubes quarterly BWRead mode of queries and InfoCubes monthly BWFor a list of tools for performance checking, see chapter 5.

2.4 Free spaceDescription Freq. WhoDelete unused partitions in F-tables of InfoCube weekly BWRemove unused temporary query / analytics / realignment run tables in table space PSAPTEMP

daily BW

Delete log-files: database / application / error logs weekly BWArchive IDoc’s weekly BWClean-up PSA table content weekly BWCompress InfoCubes weekly BWDelete old BW statistics monthly BWFor a list of tools for achieving free space, see chapter 6.

2.5 ChangesDescription Freq. WhoApply SAP notes / SAP service packs / add-on’s - SBBW upgrades - SB / MOTransports - BW / SBClient copy activities - BW / SB /

MOCheck database and SAP kernel parameters - SB / MOFor a list of tools for handling changes, see chapter 7.


3 Monitoring

3.1 Batch jobsTool: 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 loadsTools: tx RSMO, tx RSMON, tx RSPC, tx RSPCM, tx ZDAILY

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

Example of the load monitor:

3.3 Report ability of dataTools: tx RSA1 (maintenance of InfoCubes / ODS objects), tx ZDAILY.


o Check if the data in all active InfoCubes is reportable. Data could be loaded, but aggregates are not rolled up yet.

o Check also if data in all active ODS objects is activated and booked into it’s data targets.

Example of unreportable data loads:

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

3.4 Missing indexesTools: tx DB02, tx ZDAILY, tx SE14

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

Example:


In previous screenprint 3 indexes and 4 tables are missing.

o 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:


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

3.5 Free spaceTools: tx DB02

o Make sure that there’s 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 there’s not enough free space, it’s 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 dumpsTools: tx ST22, tx ZDAILY

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


Example:

3.7 System logsTools: 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:


3.9 AggregatesTool: 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 it’s 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 performanceTool: 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 backupsTool: tx DB14 and others

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


3.12 Restart serverTool: tx OS06 and others

o Make sure the BW server is restarted periodically.

3.13 BW statisticsTool: 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 objectsTool: tx ZDAILY, ABAP ‘RS_TRANSTRU_ACTIVATE_ALL’, transports

o Make sure the following BW objects are always active:o Transfer ruleso Update ruleso InfoObjectso InfoCubeso ODS objectso MultiProviderso And all others

In a BW some object can become inactive due to some reasen. If update rules become inactive it’s 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 consistencyTool: 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.


o Make sure the metadata tables of queries are consistent. Run ‘ABAP ANALYZE_RSZ_TABLE’ to check and repair this.

o Run ‘RSR_GEN_DIRECT_ALL_QUERIES’ on a weekly basis for all queries, so ZDAILY will show all queries that don’t compile. Compiled queries are also faster when running them.

o Make sure all queries compile (and are therefore consistent). If they don’t 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 won’t 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 doesn’t compile, fix it in BW-D.

Example of an inactive query:

4.3 Source system connectionsTool: 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 favouritesTool: 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:


4.5 tRFC entriesTool: tx SM58, tx ZWEEKLY option 03

o Clean up transactional RFC’s from cancelled loads in all BW- and connected systems.

When a data loads cancels, some residu’s are left behind in the system(s). One of those residue’s are tRFC’s. SM58 shows those tRFC’s and offers a reorganize (delete) option.

Example of error tRFC’s:

4.6 Unreferenced objectsTool: 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 Check transfer rules consistency by running ABAP ‘RSAR_TRANSTRUCTURE_CHECK’. See note 577022 for more details.

o 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.


o Clean up unreferenced PSA metadata objects by using ABAP ‘RSAR_PSA_CLEANUP_DEFINITION’. See note 739407 for further details.

o Clean-up unused / inconsistency PSA tables by running ABAP ‘RSAR_PSA_CLEANUP_DIRECTORY’. See note 773371 for further details.

o Activate inactive communication structures by running ABAP ‘RS_COMSTRU_ACTIVATE_ALL’. See note 542872 for further details.

o Correct duplicate transfer structures in table RSISOSMAP by running ABAP ‘RSAR_RSISOSMAP_REPAIR’. See note 613449 for further details.

o Correct source system consistency (table ROOSGEN) by running ABAP ‘RS_SRCSYSTEM_TS_CHECK’.

o Check the consistency of DDIC names for transfer rules and InfoSources by running ABAP ‘RSAR_DDIC_NAME_CONFLICT’. See also note 542872.

o Correction for the technical name of transfer structures and communication structures by running ABAP ‘RSAR_STRUCTURE_NAMES_CHECK’.

o Clean obsolete entries in table DBDIFF, by running ABAP ‘SAP_UPDATE_DBDIFF’.

4.7 InfoObjectsTool: 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.


o 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 activationTool: tx ZUTIL3 option 13, ABAP ‘ZSS_REPLICATE’, ABAP ‘RS_TRANSTRU_ACTIVATE_ALL’

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

4.9 User ID’sTool: tx SU01

o Lock all users that haven’t logged on to the system in the last 3 monthso Delete all users from the system that haven’t logged on for the last 6 months.

4.10 Unused queriesTool: BW statistics queries

o Determine unused queries and delete them

4.11 Early watch reportTool: tx SDCC

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


5 PerformanceTool: tx OS06, tx SM04, tx AL08, tx SM50, tx SM51, tx SM66, tx ST03, tx ST04

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

5.1 Database and SAP statisticsTool: 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:


o 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 entriesTool: 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 statisticsTool: BW statistics queries


o Evaluate the system performance using BW statistics queries.

5.4 InfoCube indexesTool: 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 InfoCubesTool: 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.


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 partitionsTool: 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 tablesTool: 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


o Run frequently or schedule ABAP report ‘RSAN_RTT_CLEAR_TEMP_TABLES’.

Example of the output:

o Run frequently function module ‘RSDDS_CHANGERUN_TMPTABLS_DEL’ or tx ZUTIL, option 15. See note 650780 for further details.

6.3 Log-filesTool: tx ZWEEKLY options 061, 062 and 063, ABAP ‘SBAL_DELETE’, ABAP ‘RSTBPDEL’, ABAP ‘RSSM_ERRORLOG_CLEANUP’

Remove old application logs from the database

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

6.4 ArchivingTool: tx SARA, tx ZWEEKLY option 11, ABAP ‘RSEXARCA’

o Archive and remove processed IDoc’s from the database

Archive the BW related IDoc’s with transaction SARA or ABAP report ‘RSEXARCA’.

6.5 PSA tables clean-upTool: tx ZWEEKLY option 20, tx RSA15, ABAP ‘ZCHECK_PSA_TABLE_SIZES’


o 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 CompressionTool: tx ZWEEKLY option 21, tx RSA11

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

6.7 BW statisticsTool: tx RSA1, Tools, BW Statistics for InfoProviders, F7

o Delete old BW statistics on a regular basis

Example:


7 Changes

7.1 SAP notes / service packs / add-onsTool: tx SNOTE, tx SAINT, tx SPAM

o Implement a SAP note on demando 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.

o Implement BW add-ons on demand.

7.2 BW upgradeso Upgrade the BW system on demand.

7.3 TransportTool: tx STMS

o Import transports into the system on demand

7.4 Client copy activitiesTool: tx RSA13, Restore Source System

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

7.5 Database and kernel settingsTool: tx RZ10, and others

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


Appendix A: SAP kernel and database settingsBy implementing following notes, the overall system performance will be improved. Note Description129252 Oracle DB Statistics for BW Tables180605 Oracle parameters for BW184905 Profile parameters for BW192658 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 applications428212 Update of statistics of InfoCubes with BRCONNECT.565075 Recommendations for BW systems with Oracle 8.1.x567745 Composite note BW 3.x performance: DB-specific settingsRZ10 Change parameter rdisp/max_wprun_time to at least 3600 in all BW systems.

Appendix B: One-time actionsDescription

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 IDoc’s with status 64 (status halt).

Schedule ABAP RBDAPP01 to reprocess these status 64 IDoc’s every 15 minutes.


https://service.sap.com/sap/support/notes/417307

Process waiting E-mails and other communication methods

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


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.



Date post:	13-Apr-2016
Category:	Documents
Upload:	abirami-manikandan
View:	43 times
Download:	7 times

BW Operations

Documents