In some scenarios when we launch data extraction from BW we may want
to have extractor selection parameters to be defined dynamically.
For
example, for a certain extraction we may want to select a particular
Period and Versions based on data currently available in the source
system. In the post below I will review an example of how to organize
stock planning data load based on Period and Version submitted from the
source system. I will describe a model for loading transactional data to
BW and specify configuration required for automating data loads based
on data availability in the source.
Business Task Description:
Several times per month business users generate stock planning
versions in the source system for certain stock categories. This
information can be gathered via a generic extractor with selection
parameters (Period, Version). Unfortunately, the extractor is working in
a FULL mode only and BW does not know when to extract data and which
version to extract. On the other hand, users maintain a table in the
source system (ZCONTROL) where they specify parameters for new planning
versions that have been generated. Therefore by reading entries in this
table we can identify what needs to be loaded in BW.
Our goal is to build a solution in SAP BW that would automate loads
of Stock Planning Versions and will eliminate manual involvement.
Extract Selection Parameters:
As a first step we want to load Stock version selection parameters to
BW. This is possible to do in a delta mode, as there is a “Modified On”
(AEDAT) field available in the table ZCONTROL.
We have to create a generic extractor ZAG_CONTR (Transaction Code: RSO2)
based on the table ZCONTROL. In the Generic Delta screen we specify
field AEDAT as Delta specific field, and check “Calendar Day” in the
selections:
After the replication of datasources in BW our newly created datasource (ZAG_CONTR) can be connected to a DSO (O_SELP). I suggest having three fields in this DSO:
- Period
