(1902) Data Transfer Process (DTP) Including Offloaded Data

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 which includes offloaded data:

• SAP HANA Execution must be switched off in the DTP definition

The SAP HANA Execution checkbox must be cleared. If you execute the DTP with a selected checkbox, the HANA database handles all data processing without the application server. As a result, the functionality for reading offloaded data, isn't used at all. 
See the figure DTP definition requirements for the correct settings.

• Parallel Extraction must be switched off in the DTP definition

By most types of objects, the Parallel Extraction checkbox is automatically switched off after the SAP HANA Execution is cleared. Only by the Write Optimized DataStore object (WODS) and ADSO - Data acquisition layer you must clear this checkbox manually.

If the Parallel Extraction checkbox stays checked, offloaded data will be not processed. 

 DTP definition requirements

• The Extraction Mode is set to "Full"

Delta Load isn't supported. In the case Delta Load is selected as the extraction mode, only data from the Active data table will be loaded.

See the figure DTP definition requirements.

• 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, DTP will run as usual, but won't include any offloaded data.

                       Offloaded DataProvider

• The DataProvider setting READ_OFF_DATA is turned on

By marking this setting with an X, the offloaded data is extracted together with data of a DataProvider during a DTP load.

By default, the setting is turned on, but you can check or edit its value under DP settings.

DataProvider setting for reading offloaded data during a DTP load

• Data Archiving Process (DAP) mustn't be created for a DataProvider in NLS
  

A Data Archiving Process (DAP) can't be created for a DataProvider, as it could cause data inconsistency. DAP can be accessed through the transaction RSA1 with a right-click on the corresponding InfoProvider.

• Each request of a DataProvider is completed successfully

This means, that the reload and offload requests of a DataProvider have a successful status. 

  A successful state of the offload and reload phase for an DataProvider

The transfer can't be completed, when the request phases is: 'Offload Copy/Verify/Delete' or 'Reload Copy/Verify/Delete' or any phase which has a failed status.

Unsupported request state - Running

Unsupported request state - Failed

Log display

After the execution of a DTP load, the DTP Monitor displays which offloaded data of a DataProvider was transferred:

To display the offloaded data go to the RSA1, select the specific InfoProvider, right-click Manage and click on the DTP Monitor icon.

                                                  DTP monitor after load from offloaded DataProvider