It is possible to transfer already offloaded data from a DataProvider to an InfoProvider through the standard DTP. In this kind of DTP load, offloaded data is read from a DataProvider, appended to other data, and stored in the target InfoProvider.
The following requirements must be fulfilled for a DTP load that includes offloaded data:
-
SAP HANA Execution must be disabled in the DTP definition
You must deselect the SAP HANA Execution checkbox. If you execute the DTP with a selected checkbox, the HANA database handles all data processing without the application server. As a result, the function for reading offloaded data is not used at all.
See the figure DTP definition requirements below for the correct settings.
-
Parallel Extraction must be disabled in the DTP definition
For most types of objects, the Parallel Extraction checkbox is automatically deselected after you deselect the SAP HANA Execution checkbox. You only need to deselect this checkbox manually for write-optimized DataStore objects (WODS) and the ADSO data acquisition layer.
If the Parallel Extraction checkbox remains selected, offloaded data will be not processed.
DTP definition requirements
-
Extraction Mode is set to Full
Delta loads are not supported. If you select delta load as the extraction mode, only data from the active data table will be loaded.
See the figure DTP definition requirements above for the correct settings.
-
Some data of the DataProvider is successfully offloaded
This requirement means that at least one offloading request is successfully offloaded. If no request is offloaded, the DTP will run as usual, but it will not include any offloaded data.
Offloaded DataProvider
-
The DataProvider setting READ_OFF_DATA is enabled
If you enable this setting with an X, the offloaded data is extracted together with the data of a DataProvider during a DTP load.
The setting is disabled by default, you can check or edit its value in the Settings tab under DP Settings.
DataProvider setting for reading offloaded data during a DTP load
-
A data archiving process (DAP) must not be created for a DataProvider in NLS
A DAP must not be created for a DataProvider because it could cause data inconsistencies. You can access a DAP via transaction RSA1 by selecting the corresponding InfoProvider from the context menu.
-
Each request of a DataProvider is completed successfully
This means that the reloading and offloading requests of a DataProvider have a successful status.
A successful status in the offloading and reloading phases for a DataProvider
The transfer cannot be completed if the request phases are Offload Copy/Verify/Delete or Reload Copy/Verify/Delete, or if any phase has a failed status.
Unsupported request state – Running
Unsupported request state – Failed
After the execution of a DTP load, the DTP monitor shows you which offloaded data of a DataProvider was transferred.
Proceed as follows to display the offloaded data:
1. Start transaction RSA1.
2. Right-click the specific InfoProvider and select Manage.
3. Click the DTP Monitor icon.
The offloaded data is displayed.
DTP monitor after load from offloaded DataProvider
