(2208) SNP OutBoard™ Data Tiering Settings

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.

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.

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.

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.

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.

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.

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.

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.

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.

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. 

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.

Number of automatic repair attempts of the failed offloading/reloading request.