Professional Documents
Culture Documents
Delta Queue BI Extr CVPM BA 6 PDF
Delta Queue BI Extr CVPM BA 6 PDF
Introduction ................................................................................................................................2
2.1
2.2
3.2
3.3
3.4
Test execution.............................................................................................................................9
4.1
4.2
4.3
4.4
References ................................................................................................................................13
1 Introduction
Situation
Bank Analyzer 6.0 does not support BI Extraction using Delta Queues.
Note 1007325 Generic Bank Analyzer DataSources with Delta Queue describes how to
apply a Delta-Queue-Extraction logic with the DPF (= Data Processing Framework) of the
Bank Analyzer.
Bank Analyzer 6.0 is featured with the CVPM (= Calculation and Valuation Process Manager)
which is functionally superior to the DPF, e.g. it supports a process step Close SDL (SDL =
Source Data Layer).
You would like to apply a BI Extraction using Delta Queues with usage of CVPM in the Bank
Analyzer 6.0.
Problem:
There is no standard solution for a BI Extraction using Delta Queues with usage of CVPM in
the Bank Analyzer 6.0.
Solution:
This How to-guide describes how an implementation of a BI Extraction using Delta Queues
with usage of CVPM in Bank Analyzer 6.0 might be attempted. The following descriptions are
suggestions, they may not be complete, and they may not be correct in all situations. Please
make modifications to your system cautiously.
Pre-requisites:
These suggestions are for Bank Analyzer 6.0 only.
You are familiar with the Generic BI extraction of the Bank Analyzer.
You are familiar with the Delta Queue extraction concept.
You are familiar with the CVPM of the Bank Analyzer.
Comments:
For Bank Analyzer 7.0 a standard solution for BI Extraction using Delta Queues with usage of
CVPM exists. It is very similar to the solution as described here.
The descriptions in this How To-document do not replace any existing documentation
regarding the used functions.
Example:
These steps as described before are uncritical, they are a standard procedure for creating Generic BI
DataSources in the Bank Analyzer.
z_change_deltamode.
PARAMETERS:
p_datas TYPE roosource-oltpsource,
p_deltap TYPE roosource-delta default 'AIM',
p_flag
TYPE xflag DEFAULT 'X'.
"DataSource
"Process for DataSource
"remove mandatory selection fields
TABLES:
roosource.
DATA:
ls_roosource TYPE roosource.
SELECT SINGLE * FROM roosource INTO ls_roosource
WHERE oltpsource = p_datas AND objvers = 'A'.
IF sy-subrc EQ 0.
ls_roosource-delta = p_deltap.
UPDATE roosource FROM ls_roosource.
MESSAGE 'The DataSource has been updated successfully.' TYPE 'I'.
ELSE.
MESSAGE 'The DataSource entered is not valid, try again.' TYPE 'E'.
ENDIF.
* remove mandatory selection fields, in particular for CALDAY
DATA: ls_roosfield TYPE roosfield.
IF p_flag = 'X'.
SELECT SINGLE * FROM roosfield INTO ls_roosfield
WHERE oltpsource = p_datas AND selection = 'M'.
IF sy-subrc EQ 0.
ls_roosfield-selection = 'X'.
UPDATE roosfield FROM ls_roosfield.
ENDIF.
ENDIF.
Run this report with the DataSource that you have created previously and change the Delta mode
accordingly, e.g. to AIM, and change mandatory selection fields from value M to X.
Check tables roosource and roosfield via transaction se11 that your changes were done
successfully.
Attention: the process parameter /BA1/C61POSTXT is the place holder for a proper info object that
points to BI DataSources. You must create such an info object in the customer namespace first. For
test purposes you may use the characteristic /BA1/C61POSTXT, but this is just a work around here.
Now open the view Data Reading Groups:
In case of using the SDL close as leading process do not use Data Reading Groups 001 and 003 on the
selection screen, because their usage would overwrite the SDL-close based timestamps for these
groups.
If you do not want to use the SDL close then create another CVPM process without leading process
and flag DRG IDs 001, 002 and 003 for being used on the selection screen.
Create a first step in the sequence and apply type parameter enrichment:
You should use here the same PDS work list as you have assigned to the DPF-Selection ID that was
used for generating the Generic BI DataSource.
You can add now additional steps, according to the DPF-selection-ID, e.g.
module editor or
aggregation
Finally you have to add a step type data enrichment for which you can use class
/BA1/CL_AL_R7_GEN_BI_CVPM_ST (see SAP note FS-BA-IF-ERS 1396125):
You may copy now this step sequence to EXTRACT_DY and add a last step ALV display with
callback class /BA1/CL_AL_FW_DISPLAY:
Delete step 30 (write to Delta Queue). This second sequence is more or less the same as before, but
you can run it in test mode and display the selected data.
4 Test execution
4.1 Initialisation in the BI system
Replicate the metadata of the DataSource to the BI system via transaction RSA1 - Modeling - DW
Workbench, activate the DataSource and create an InfoPackage:
Then start the InfoPackage. The result should show a green traffic light with 1 (dummy) record.
10
11
Then we run the step sequence EXTRACT that writes data to the Delta Queue (comment: the Delta
Queue is here cluster table in the OLTP system):
12
Start Data Load immediately and check the Monitor for results:
If you check now RSA7 in the OLTP system you still find all data packages in the Delta Queue. This
ensures restartability:
After you have started another InfoPackage right now (that will find 0 records because we did not
run the CVPM again)
13
5 References
[1] SAP note FS-BA-IF-ERS 1396778 Generic Delta Queue BI Extraction with CVPM.
[2] SAP note FS-BA-IF-ERS 1396125 Example implementation for BI Delta Queue with CVPM.
[3] SAP note FS-BA-IF-ERS 1007325 Generic Bank Analyzer DataSources with Delta Queue.
[4] How-to Guide SAP NetWeaver 2004s How ToCreate Generic DataSources which use the Delta
Queue. This document is attached to SAP note FS-BA-IF-ERS 1007325.