To access the settings of a specific DataProvider, you can choose the Settings button.
To access the global settings of DataProviders, click on the Settings tab.

Under DP Settings you can either change the general setting for all DataProviders by clicking on Display or you can change the settings for one DataProvider by entering its name.

It is possible to transport the definition of the DataProvider and its' settings to another system directly from SNP OutBoard™ Data Tiering. More information can be found in the chapter (2302) Transport of DataProviders and Settings to Other Systems.

SETTINGS

Parameters	Description
Group ID	Name of the default Group ID for mass processing of DataProviders. For better processing, Group ID should contain DataProviders that have a common characteristic. The group ID is a global setting and may be changed only for all DataProviders.
On-the-fly replication	When reading offloaded data through a query with the navigation attributes, this feature creates a master data table replica of these navigation attributes (if it is not created yet) and performs a join with this table on the external storage.
Source storage	Name of the default storage from which data is offloaded. Source storage is a global setting and may be changed only for all DataProviders.
Target Storage	Name of the default storage to which data is offloaded. Target storage is a global setting and may be changed only for all DataProviders.
Selectivity field for DP	Name of the field for partitioning. If the value of this setting is filled, the partitioning will be based on the entered field name. If the value stays empty, the request won't be divided into partitions. We recommend using a field name that has many distinct values (has a higher granularity), for example, a document number.
Max BG jobs for parallel offload	A maximum number of background jobs for parallel offloading of one request. Please note that by parallel processing, the system creates first a job for offloading, and after that, it creates other jobs for the subrequests.
Max BG jobs for parallel reload	Maximum number of background jobs for parallel reloading of one request. Please note that by parallel processing, the system creates first a job for reloading, and after that, it creates other jobs for the reload of the subrequests.
Fetch package size	A maximum number of records in one package is fetched from the source storage. This setting is used when reading data from source storage. The recommended minimum value is 100 000 rows.
Package volume for the subrequest	Maximum size of a subrequest. Relevant only when parallel offloading is enabled. Maximum size of a GLUE subrequest (in MB) This parameter should be high enough to not have small files on HDFS but also not to fail on SAP memory. The recommended value is between 500-1000 MB.
Minimum offloaded rows	A minimum number of offloaded rows for the offloading process. If the parameter isn't high enough, it may influence the storage performance (too many partitions are created). Also, the offloading condition should be defined as lower or equal to this parameter. In the case number of offloaded rows is less than the parameter Minimum offloaded rows a confirmation message appears. The recommended value is 100 000 rows.
Use index	Indexes are used only by Writer 3, which supports DSO and ADSO-like DSO objects. Indexes for other types of objects are not needed anymore and can be disabled for existing DataProviders. To delete the unused indexes execute report /DVD/OFF_INDEX_DELETE, which also automatically disables this setting. For more info check the settings and report's info button.
Enable data synchronization	Allows the data synchronization of the source table.
Table for data synchronization	Name of the table used for data synchronization. Create a table based on the source table, then create an extractor and execute the data extraction.
BAdI Provider - BAdI Implementation	To use BAdI Providers, you need to create an Enhancement implementation of RSO_BADI_PROVIDER Enhancement Spot and BAdI implementation with Implementing class /DVD/OFF_BW4HANA_CL_BADI_PROV. You can create both implementations using transaction SE19. If the setting is empty functionality try to find BAdI implementation with implementing class /DVD/OFF_BW4HANA_CL_BADI_PROV, if there is only one such implementation it will use it otherwise the creation of BAdI Provider end up with an error.
BAdI Provider - Enhancement Implementation	To use BAdI providers you first need to create your enhancement implementation of enhancement spot RSO_BADI_PROVIDER. To create enhancement use transaction SE19. This parameter should contain the name of the created enhancement implementation. If the setting is empty functionality try to find BAdI implementation with implementing class /DVD/OFF_BW4HANA_CL_BADI_PROV, if there is only one such implementation it will use it otherwise the creation of BAdI Provider end up with an error.
Reload via DTP	This functionality enables a way of inserting data back into the original InfoProvider, which meets SAP standards. To use this functionality, you need to create a Data Transfer Process between a composite provider and the original InfoProvider. The composite provider must contain the original InfoProvider and a generated Virtual/BAdI provider. This DTP has to be set as this parameter. If the parameter is not filled, data will be written or deleted directly from the database table of the original InfoProvider.
Manual import of a transport	In case you have any issues with the creation/activation of DataProvider using the XPRA report, here you can set that import of the transport will not be executed by XPRA functionality. You will then be able to manually execute it by using transaction /DVD/OFF_IMPORT. Functionality is disabled by default as it is easier to import the transport and XPRA will do the creation/activation of objects automatically.
Automatic ratio calculation	This setting enables/disables automatic calculation of the offloading ratio after a DataProvider is created. To enable automatic ratio calculation, enter 'X' or enter ' ' to disable it.
Automatic repair – repeat	Number of automatic repair attempts of the failed offloading/reloading request.
Data verification	Enables hash verification during the offload copy phase.
Days for Straggler Analysis	Number of days to be searched for stragglers. 30 days means that Straggler Analysis will be executed for 30 days back

Browser not supported