Another
property of a DTP packages among those like Version, Indicator (Saved/Not
Saved) and Object status
is Processing Mode. It describes the order in which processing steps such as
extraction, transformation and transfer to target are processed at runtime of the
DTP request. The processing mode also determines when parallel processes are to
be separated.
The
processing mode of a request is based on whether the request is processed
asynchronously, synchronously or in real-time data acquisition mode (RDA), and
on the type of the source object.
It
also takes the number of parallel processes defined in the Background Manager
into consideration. If only one process is defined there, no additional
processes are separated while the DTP request is being processed.
- Asynchronous
Processing - A
request is processed asynchronously in a background process when a DTP is
started in a process chain or a RDA request is updated. The processing mode is
based on the source type.
- Synchronous Processing
- A request is
processed synchronously in a dialog process when it is started in debug mode
from DTP maintenance. RDA requests cannot be started in debug mode.
- RDA
Processing - A request is processed in RDA mode when it is started using a
real-time demon.
Technically
the DTP processing mode is stored in table RSBKDTP
and column PROCESSMODE. Following
are types of processing identified by tech ID and name and description.
- " 0 (serial) " Serially in the Background Process
Requests are processed
one by one on background.
- " 3 (par_all) " Parallel Extraction and Processing
The
data packages are extracted and processed in parallel processes, meaning that a
parallel process is derived from the main process for each data package. This
parallel process extracts and processes the data. Maximum number of background
processes that can be used for each DTP can be defined. Execution is performed
in parallel background processing.
- " 4 (sync_debug) " Serially in the Dialog Process (for Debugging)
Processing
of the DTP is executed in debugging mode. The request is processed
synchronously in a dialog process and the update of the data is simulated.
- " 8 (sync) " Serially in Dialog Process
Requests
are processed one by one in dialog (foreground) mode.
- " 9 (no_data) " No Data Transfer; Delta Status in Source:
Fetched
With
this processing mode a delta request is created without transferring data. This
is analogous to simulating the delta initialization with the InfoPackage. The DTP
is executed directly in the dialog. No data is transferred in BW, but the delta
pointer is established with the initializing status. When next delta loads is
triggered it fetches only those new records which are created after the delta
pointer was set.
- " S (par_source) " Parallel Extraction and Processing (Flexible
Preparation)
With
this processing type, data transfer processes are executed that directly
transfer data without a PSA from a DataSource (in the operational data
provisioning (ODP) source system) to an InfoProvider. The processing mode is
used if error handling is activated and the transformation does not require any
semantic grouping.
The
difference between this processing mode and V1 is that this processing mode has
no explicit preparation phase in the program flow (see the Execute tab). During
the preparation phase with ODP source systems, the system cannot find out how
many data record and packages are delivered by the source. The main process
does not ask whether a data package exists until after a parallel process has
been spilt off.
- " I (no_data_no_i) " No Data Transfer; Delta Status in Source:
Not Fetched
B)
Processing the Data Transfer Process in SAP HANA
- " D (script) " Serial SAP HANA Execution
If
certain prerequisites are met, you can use this processing mode for a data
transfer process that can be transformed in SAP HANA.
- " E (script_par) " Parallel SAP HANA Execution
Execution is
performed in parallel background processing.
- " F (mix_ser_all) " Serial Processing with partial SAP HANA
Execution
In
case Transformation run in HANA mode but contains ABAP End Routine. Mixed
scenario.
- " H (mix_par) " Parallel Processing with partial SAP HANA
Execution
In
case Transformation run in HANA mode but contains ABAP End Routine and execution
is performed in parallel background processing. Mixed scenario.
- " J (script_sync)" Serial SAP HANA Execution in Dialog Process (new in BW/4HANA)
- " K (mix_sync) " Serial Partial SAP HANA Execution in Dialog
Process (new in BW/4HANA)
C)
Obsolete processes:
- " 1 (par_immediate) " Serial Extraction, Immediate Parallel
Processing (Obsolete)
The data
packages are extracted sequentially in a process. The packages are processed in
parallel processes, meaning that the main process extracts the data packages
sequentially and derives a process that processes the data for each data
package.
Note You can
define the maximum number of background processes that can be used for each
DTP.
- " 2 (par_later) " Serial Extraction, Then Parallel Processing
(Obsolete)
- " 5 (realtime) " Processing Mode for Real-Time Data Package
(Obsolete)
With this
processing mode, you execute data transfer processes for real-time data
acquisition.
- " 6 (remote) " Processing Mode for Direct Access
(Obsolete)
With this
processing mode, you execute data transfer processes for direct access.
- " 7 (ser_package) " Serial Extraction and Processing of Source
Packages (Obsolete)
The data
packages are extracted and processed sequentially in a process, the main
process.
- " A (par_non_init)" Parallel Extraction and Processing Except Delta
Except Delta init / (Obsolete)
Using this
processing mode, you can achieve extensive parallelization for delta DTPs that
extract data from a standard DataStore object who delta initialization is not
read from the change log.
When the
request is created for this kind of DTP, the processing mode is set dynamically
as follows: During delta initialization, the data is extracted in serial form
(from the active table with or without archive), and the data packages are
processed in parallel processes. The delta requests are then extracted and processed
in parallel.
- " G (mix_ser_x) " Serial SAP
HANA Transformation, Immediate Paral. ABAP Update (Obsolete)
Mixed
scenario.