BW Daily Monitoring - 11

Mile Stone of Presentation 1. Need for monitoring 2. Prior to monitoring 3.
Monitoring/Transaction
i) ii) RSMO RSPC
iii) SM37 iv) RSA1(Event Collector) v) ST22
Page 1
SISL / Mumbai / SAP-C
Mile Stone of Presentation

VI. VII. DB02(YOXM) SM58
VIII. SM50
4. 5. 6. 7. 8.
Scheduling/Unscheduling of Jobs How to correct failure, if any? PSA Deletion Special monitoring Communication
Page 2
1. Need for monitoring
Monitoring jobs and tasks are performed on a regular basis to ensure system performance and stability of BW system Monitoring for BW is to carry out system checks and thereby ensure smooth running of different applications and take corrective actions wherever necessary. With the Monitor you can check the data loading process and data processing in BW and analyze errors.
Page 3 SISL / Mumbai / SAP-C
2. Prior to monitoring
Before starting actual monitoring, we need to know
1. Data flow diagram of various application of system. 2. Few basic terminologies of SAP Business Warehouse Info Provider Info Package Data Source Source System PSA Info Source Transfer Structure & Transfer rule Update Rule
Page 4
3. Monitoring/Transaction
Monitoring (Transaction)
Page 5
3.1 RSMO
You can use the RSMO Monitor to check data loading. Here, in addition to the header information for a request, information about the technical and full status of the request is displayed, as well as detailed information about the status for individual processing steps in the data request is displayed. You can customize your view.
Page 6
3.1 RSMO
Page 7
3.1 RSMO
Page 8
3.1 RSMO
Page 9
3.1 RSMO
Page 10
3.2 RSPC
In and operative BW system, in addition to the loading process, there are a number of processes that occur regularly, for example loading processes such as the execution of an InfoPackage, processes for data target administration such as filling aggregates or reporting agent processes such as precalculating Web templates. With the background processing system,
Page 11
BW processes or jobs can be scheduled for certain times, for certain dates, according to certain predecessor jobs or according to event. Beyond that, SAP BW supports graphic modeling of the BW process using process chains. Process chains allow you to control several interconnected processes. A process chain is a sequence of processes that wait in the background for an event. Some of these processes trigger a separate event that starts other processes in turn.
RSPC transaction is used for process chain monitoring. We can check status of process chains from here.
Page 12
3.2 RSPC
Page 13
3.2 RSPC
Page 14
3.3 SM37 Check for jobs which are active, cancelled, ready & finished. The BI jobs have special names: BIREQU_* relates to a loading job. BI_ODSA* means activating an ODS BI_SAGR* means filling aggregates BI_AGGR* means rolling up BI_IDX means refreshing index on a cube BIPROCESS means jobs from a process chain To find out of a loading job where it loads the data you have to go into the job log. Press on the icon for job log on your BIREQU* jobs. Then you can see which datasource, which data targets and what it is doing,
Page 15
3.3 SM37
Page 16
3.3 SM37
Page 17
3.4 RSA1 including Event Collector
The Administrator Workbench is the tool for controlling, monitoring, and maintaining all of the processes connected with data staging and processing in the Business Information Warehouse. Event Collector An event collector is a quantity of several events that have been successfully completed independently of each other, to which background processing should respond. The event collector corresponds to the AND process and the process chain maintenance. If an application process is scheduled via an event collector, it starts when all events for the preceding process were successfully triggered.
Page 18
Page 19
Page 20
3.5 ST22
We can use the System Errors analysis to obtain information about the most important error messages of our system.
Page 21
3.5 ST22
Page 22
3.6 DB02(YOXM) To check the table space
Page 23
Page 24
3.7 SM58 Check for queue status
Page 25
3.7 SM58 Check for queue status
Page 26
3.8 SM50
The process overview is intended primarily for information-gathering. Form this list of we have to check for the processes running for longer time Find out which data load is running for is these process
Page 27
3.8 SM50
Page 28
4. Scheduling/Unscheduling of Jobs
1. InfoPackage 2. Process Chain 3. InfoPackage Group 4. Job Overview
Page 29
Page 30
5. How to correct failure, if any?
We can check failure from 1. 2. 3. 4. Monitor Screen Process Chain Job Overview SM50 Depending upon error message relevant corrective actions have to be taken.
Page 31
6. PSA Deletion
Performance related checks include the daily run of the specific programs as well regular checks on the PSA deletion jobs. But unnecessary use of PSA can degrade performance of overall system. So periodic deletion of PSA is necessary for system performance. By doing this we can utilize system resources properly.
Page 32
Page 33
7.Special monitoring
Special monitoring have to be carried out other than normal day

to day monitoring. e.g. Refreshment of quality server, when inconsistency in records, etc. Month End monitoring Weekly monitoring
Page 34
8. Communication
You can use short messages to send important information to the users of an SAP system. Depending on the Monitoring status we need to communicate with customer. It is in both the cases of success in dataload or errors in dataloads.
Page 35
Page 36
Thank You
Page 37

BW Daily Monitoring - 11

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

BW Daily Monitoring - 11

Încărcat de

Drepturi de autor:

Formate disponibile

Mile Stone of Presentation 1. Need for monitoring 2. Prior to monitoring 3.

iii) SM37 iv) RSA1(Event Collector) v) ST22

SISL / Mumbai / SAP-C

Mile Stone of Presentation

SISL / Mumbai / SAP-C

1. Need for monitoring

Before starting actual monitoring, we need to know

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

3.4 RSA1 including Event Collector

SISL / Mumbai / SAP-C

3.4 RSA1 including Event Collector

SISL / Mumbai / SAP-C

3.4 RSA1 including Event Collector

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

3.6 DB02(YOXM) To check the table space

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

3.7 SM58 Check for queue status

SISL / Mumbai / SAP-C

3.7 SM58 Check for queue status

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

1. InfoPackage 2. Process Chain 3. InfoPackage Group 4. Job Overview

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

5. How to correct failure, if any?

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

Special monitoring have to be carried out other than normal day

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

SISL / Mumbai / SAP-C

S-ar putea să vă placă și