Beruflich Dokumente
Kultur Dokumente
Contents
Introduction ..................................................................................................................................... 2
Housekeeping in Business Intelligence for BPMon Alerts ............................................................... 2
Identify the Data Volume of the Info Cube ..................................................................................... 3
Deletion of Info Cube Data .............................................................................................................. 5
Deletion of Data Store Objects (DSO) ............................................................................................. 7
Deletion of Data Packages from the Persistent Staging Area (PSA) ................................................ 8
Housekeeping in the SAP Solution Manager ................................................................................. 10
Reorganization of BPMon Alerts ................................................................................................... 10
Reorganization of the transfer table (DSWP_BPM_BI_EXTN)....................................................... 12
Summary........................................................................................................................................ 13
2011-11-01
Introduction
When using Business Process Monitoring (BPMon) alerts are created. These are written
to BPMon specific data base tables. If you want to do Alert Reporting on BPMon
Alerts, you have option Keep Data for BI (Find more details how to setup BPMon
Alert Reporting in the Service Marketplace alias /BPM Media Library Technical
Information Setup Guide - BPMon Trend Analysis). In this case the alerts data are
copied and transferred from SAP Solution Manager to cube 0SM_BPM of SAP Business
Intelligence (BI).
The following sections will explain how to avoid unnecessary amounts of data. This
might help you to set up a housekeeping process according to your individual needs.
Page 2
With the help of a defined housekeeping process, the average access time to the data
serving BPMon Alert Reporting as source can be optimized and the growth of data
storage for the Info Cube in the SAP Solution Manager can be managed.
Depending on the amount of data loaded to the cube for BPMon Alert Reporting Info
Cube 0SM_BPM the data shall be deleted or archived. This needs to be triggered
manually by deleting old requests which are not needed any more from the Info Cube via
the BW Administration Workbench.
Page 3
On the right hand side open tab Contents and click on button Fact Table.
On the new screen (which can be reached via transaction SE16 for table
/BI0/FSM_BPM as well) click on button Number of Entries.
Page 4
The displayed number is the number of data records (= Alerts) in the fact table of
the Info Cube 0SM_BPM. The performance of a query depends on many factors.
One of these factors is the amount of data in the fact table. Therefore you might
consider to delete data from the cube, if there are not needed anymore.
Page 5
If you decide to delete data, be aware that you shall delete a range of specified requests
and not the complete Info Cube contents. The deletion is done as follows:
-
On the right hand side of the screen open tab Requests and display the select a
time frame. Within this list, you have an overview of all available requests in the
Info Cube which contain data for BPMon alert reporting and of course its
creation date. The time range of this requests can be adjusted due to your needs,
just enter another time interval below the list and press the Refresh button once.
In order to delete a request, just mark it in the list and press the Delete button to
start a background job taking care of the data deletion. In a first step, the status of
Page 6
the selected request is changed from green to red until the deletion ended and
the request is finally removed from the list. Note: You will not be able to delete
any request, if older requests still exist.
Of course you can select more than one request to be deleted at one point in time,
but be aware that with each additional request a higher amount of workload is
generated for the background processing executing this deleting task. So we
strongly recommend to test at first the runtime for the deletion of one single
request to estimate the possibility to select multiple requests for deletion in
parallel.
The execution of the background job can be observed via transaction SM37 and SM50.
The number of entries deleted from the Info Cube can be evaluated directly from the
request list, because for each request stored in the Info Cube the number of entries
included is mentioned.
The size of the Info Cube can always be checked via its fact table /BI0/F0SM_BPM
accessible in transaction SE16 using the Number of entries-function ( Identify the
Data Volume of the Info Cube).
Page 7
Page 8
In the next screen you can see the Number of Requests in PSA DB Table and
you can schedule a frequent job in order to delete processed requests, e.g. older
than a particular time frame.
Page 9
The job chain of the InfoCube picks up the data from the transfer table
By using the check boxes Delete you do not only avoid that data are loaded
redundantly to the Info Cube, but also keeping small the transfer tables to get good
response times.
Consider that the BPMon alerts shall be only deleted from the transfer tables after they
have been caught by the BW process chain and have been stored successfully to the Info
Cube.
IMPORTANT: We strongly recommend using the Delete Delta in Extraction flag
in the extraction job to delete extracted data written to the transfer table to reduce the
amount of data in the system.
Page 12
Summary
If you use BPMon with or without Alert Reporting, i.e. without the option Keep Data
for BI, the data growth caused by the alert data shall be controlled by defining
reorganization times in the BPMon Setup Environment and by running the report
DSWP_BPM_REORGANISATION.
If you use Alert Reporting you should additionally, delete frequently
- Data Store Objects (DSO)
- Data packages of the Persistent Staging Area (PSA) that have been processed
successfully
- Info Cube requests, which might not be needed anymore for analysis.
The performance of BI queries on the Info Cube is influenced by the selected and the
total amount of data from the Cube. Anyway be aware that those requests remain in the
cube being essential for a useful analysis according to your business needs.
Page 13