Data Transfer Process and Error handling process

Introduction about Data Transfer Process

In SAP BI-BW
1. You use the data transfer process (DTP) to transfer data within BI from a
persistent object to another object in accordance with certain transformations
and filters. In this respect, it replaces the data mart interface and the Info
Package. As of SAP Net Weaver 2004s, the Info Package only loads data to the
entry layer of BI (PSA).
2. The data transfer process makes the transfer processes in the data warehousing
layer more transparent. Optimized parallel processing improves the performance
of the transfer process .You can use the data transfer process to separate delta
processes for different targets and you can use filter options between the
persistent objects on various levels. For example, you can use filters between a
Data Store object and an Info Cube.
3. Data transfer processes are used for standard data transfer, for real-time data
acquisition and for accessing data directly.

Interesting Benefits of New Data Transfer Process

1. Loading data from one layer to others except Info sources.
2. Separation of delta mechanism for different data targets.
3. Enhanced filtering in dataflow.
4. Improved transparency of staging processes across data warehouse layers.
5. Improved performance : optimized parallelization
6. Enhanced error handling in the form of error stack
7. Enables real-time data acquisition.
Most important advantage in Data Transfer Process
1. Delta logic can be separately handled for separate data targets
2. Example for separation for delta logic
3. Delta logic is a part of DTP
4. One Source PSA
5. Two targets : One DSO keeping daily data and other one keeping weekly data
Five process for handling errors in DTP
Process#1 Enhanced Filtering, Debugging and error handling options

Process # 2 -Handling Data Records With Errors

1. Using the error handling settings on the Update tab page in the data transfer
process, when data is transferred from a DTP source to a DTP target, you can
specify how the system is to react if errors occur in the data records.
2. These settings were previously made in the Info Package. When using data
transfer processes, Info Packages write to the PSA only. Error handling settings are
therefore no longer made in the Info Package, but in the data transfer process
Process # 3 -Error Handling Features
1. Possibility to choose in the scheduler to
2. Abort process when errors occur
3. Process the correct records but do not allow reporting on them
4. Process the correct records and allow reporting on them
5. Number of wrong records which lead to a wrong request
6. Invalid records can be written into an error stack
7. Keys should be defined for error stack to enable the error handling of data store
object
8. Temporary data storage can be switched on/off for each sub step of the loading
process
9. Invalid records can be updated into data records after their correction

Process # 4 - Error Stack

1. Stores erroneous records
2. Keeps the right sequence of records à for consistent data store handling.
3. Key of error stack defines which data should be detained from the update after
the erroneous data record.
4. After Correction, Error-DTP updates data from error stack to data target.
Note: Once the request in the source object is deleted, the related data records in error
stack area automatically deleted.
1. Key of Error Stack = Semantic Groups.
2. Subset of the key of the target object.
1. Max. 16 fields
2. Defines which data should be detained from the update of erroneous
data record (for data store object)
3. The bigger the key, the fewer records will be written to the error
stack
 Process # 5 - Temporary Data Storage
2. In order to analyze the data at various stages you can activate the temporary
storage in the DTP
3. This allows you to determine the reasons of error

Subscribe
A Replacement for RSPCM - Process Chain monitoring Print
from ST13 (/SSA/BWT program) Permalink
Balaji Venugopal Share
Business Card
Company: Cognizant
 Posted on Feb. 11, 2010 08:10 AM in Business Intelligence
(BI)

Before Starting this blog, let us first look at the benefits of monitoring the process chains from
ST13 (or /SSA/BWT program) compared to RSPCM transaction.

Process Chain Monitoring from RSPCM Process Chain Monitoring from /SSA/BWT

Need to add every Process chain MANUALLY to Whenever a Process chain is created it is
be monitored in RSPCM automatically included on the chain's first run.

Only the LATEST INSTANCE of the process chain

All the instances will be displayed in the given time
will be displayed even if it had run multiple times in
interval.
a day.
Details like whether the Process chain is a Main
chain or a Sub chain, End Date/Time, Number of
sub-chains, Number of steps in each chain, Number All these details can be viewed here.
of Failed/In-Progress steps, Total number of errors
in the chain will NOT be displayed.
The Refresh time will be VERY SLOW if the
The time taken for Refresh is very much faster
number of process chains included in RSPCM
compared to RSPCM.
increases.

The number of Added/Transferred records will be

Added/Transferred number records will NOT be
displayed against each LOADING/DTP_LOAD step
displayed in the detail view
in the first detail view.

The Runtime CANNOT be compared for each step The Runtime for each step in the process chain can
in the process chain. be compared.

In many systems, ST13 authorization will not be given. But don’t worry, follow the below steps.

1) In SE38 (or SA38) transaction, enter the Program “/SSA/BWT” and execute (F8)
2) Select “Process Chain Analysis” Radio button and execute (F8)

3) Select “Process Chains” button

4) Enter “*” in Chain ID field (or leave it blank). Enter Start Date and End Date.
5) The “Process chain Run time Analysis” screen will be displayed. The Log REFRESH is much
faster compared to RSPCM. A one stop shop for all the monitoring activities.

The “STATUS” shows the overall status of the process chain.

The “STEPS” shows the status of the process steps (Sub-chains, data load step, activation step,
Rollup, etc.).

For example, a Process chain has failed in a data load step and then it was repeated and the issue got
fixed. The process chain got completed successfully. Then the “STEPS” would be in RED as the
data load had failed and the “STATUS” will be in GREEN showing that the overall chain got
completed successfully.
By this we can easily track all the chains that got failed and we can know if a chain needs to be
corrected or not.
If both “STATUS” and “STEPS” are in RED then the Process chain needs to be corrected.
If “STATUS” is in “YELLOW” and “STEPS” is in RED then still there are chances that there might
be some failure in the Process chain and that needs to be looked into.
6) Click the individual process chain under “CHAIN” column. It will take you to the below screen.

7)Now it will show at which step the chain had failed. Click the chain again. It will take you to the
Process chain Log, from where the failure can be corrected.

Also, we can get additional information like,

•Start Date / Time
•End Date / Time
•Run time (in Seconds & Minutes)
•Whether the Process chain is a Main Chain or Sub chain
•Number of Sub-chains within the Main chain
• Number of Process steps within each chain
•Number of “Failed” steps (Red)
•Number of “In-progress” steps (Yellow)
•Total Number of errors in each chain
Additional Parameters:
We can even compare the Runtime of each process types in a process chain. To do this, select a
process chain and click on "Compare Runtimes" button.

The Runtime for each step in the process chain will be displayed as shown below.

Hope this helps BW Consultants to monitor the chains in an efficient manner.