Performance
Tuning for Data loading in process chains
Summary
The objective of the document is to give information on Performance Tuning for process chains
Most of us start our career in a support project. At the initial stages, the information provided below will us in identifying issues with performance of process chains.
Introduction
A process chain is scheduled sequence of processes linked together and executed in a pre-defined order. Process chain is a mechanism that controls extraction, transformation, and loading (ETL) activities execution at a scheduled time in a defined manner.
If you use Process chains, you can
Each step is made up of a Process Type which generally corresponds to BW activity.
Process type is the kind of process that is being executed. Each process has a type of activity associated to it like starting an Info package to load data, activating DSOs. A Process chain can be included in other process chains which is called Meta chain.
Below is a sample process chain which exactly suits the whole ETL process in correct sequence. This sequence can have a significant impact on the load performance.
Commonly faced Issues in process chain (based on runtimes)
There are many challenges which influence the successful execution/completion of the process chains in a support project. Here are the major factors
Proposed Solutions
Most of the above challenges are standard and we may have to face these issues while using process chain. In few cases, we could avoid the issues while designing the process chain itself. There are few steps that can be used to improve the performance of the process chains.
The Info-cube gets full load data from source on a daily basis, but this is the business requirement. Hence we can’t change the same to delta update mode. If
you check the number of transferred records and added records in the below screenshot, there is a huge difference. The load time has also increased day by
day.
The problem was because PSA table has data from day 1 and so the transferred records gradually increased and added records are from the current day. To
overcome this issue, we should add a step to delete the PSA table before info-package picks data from the source.
Once the PSA deletion step has been added, both transferred and records will be almost same and the DTP runtime will be reduced a lot.
Display Variant on Info Package process type. The Maintain Info Package screen will appear.
Click on Scheduler -> Traffic Light Color for Empty Requests as below
The below screen will appear which is by default set to Yellow which means if there is no data in source system, the process will never finish. Hence change the status to Green and save the Info package which will avoid long runtimes and confusions.
Important T-Codes
RSPC – Process Chain Maintenance
RSPCM – Monitor Daily Process Chains
RSPC1 – Display log of one chain at a time
RSM37 – Display Jobs with Program Parameters
ST13 – Runtime Analysis of process chains. (To get the details of process chain/process types,
use BW – Tools and execute)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
36 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 |