The purpose of the offloading analysis is to identify a list of InfoProviders suitable for offloading. The analysis is collecting and evaluating multiple statistics about each InfoProvider in order to reduce your database in an easy way. You set up the analysis once and just wait for an email notification with the results or suggestions.

Table of Contents:

Setup

Initial setup consists of two parts. Initial setup of the system and BW Analysis setup.

Go to transaction /DVD/HS_OFF_SETUP
Initial system setup
- Install license if needed
- Fill customer information
  - Insights customer ID
    - If you don't have your customer ID you can e.g. number 123
  - Customer name
- Fill administrator information
  - Email address will be used for receiving notifications or results
- Leave selected 'Only central' deployment scenario
- Fill central customizing
  - User name for execution of background jobs
  - Sender's e-mail address for notifications or results
- Confirm setup with the Complete button
- See setup logs and click Exit
BW Analysis setup
- Confirm that system will be added to the system landscape
- Confirm that you want to continue with the BW Analysis setup
- See setup logs

The analysis is executed immediately after finishing the setup. Once the analysis is done and the results are ready, an e-mail notification is sent to you. Please be aware the analysis can take multiple hours, depending on your database size and system performance.

Notification email

Once the results of the analysis are ready, you will receive a notification email with the following information:

Size of the database that you could save
List of InfoProviders that fulfill offloading rules
Step list to offload proposed InfoProviders
Criteria used for InfoProvider list creation
2 attachments
- Shortcut file to see the result in the SAP system
- JSON file with the necessary information for offloading

Offloading analysis viewer

Results are available using transaction /DVD/HS_OFFD directly on the analyzed system.

InfoProviders that fulfill offloading rules are displayed in the results. The following table shows the meaning of particular columns in a result table.

Column	Description
Object	Contains a technical name of an InfoProvider
Type	Displays a type of an InfoProvider (InfoCube, DSO, aDSO, WODS)
Description	Long description of an InfoProvider
Off. interface	Recommended offloading interface
Info	Detailed information about available offloading interfaces and special functions recommended for an InfoProvider
Size [MB]	Total object size in MB InfoCube: F table + E table + dimension tables DSO / WODS / ADSO: new table + active table Table size calculation differs by various database types HANA database: main memory + delta memory + index Other databases: table size (without index)
Off. pot. size [MB]	Offloading potential size in MB Sum of data partitions that fits offloading rules
Off. %	Offloading potential size in percentage relative to the object size
Rows	Number of rows in InfoProvider data tables (same tables are used as in the size calculation)
Number of queries	The total number of queries that read data in an InfoProvider This column can contain a value > 0, also in this case, the InfoProvider is empty. This event occurs when a query uses a MultiProvider which includes this InfoProvider
Trend - Number of queries	Visualization displaying the usage of data areas - values are rounded to natural numbers
Trend - Size [MB]	Visualization displaying the size of data areas - values are rounded to natural numbers
Split characteristic	Describes applied time characteristic If the characteristic is empty, then the Data distribution analysis doesn't identify a suitable characteristic, and the distribution of size and number of queries isn't successful
Condition	Recommended offloading condition Condition includes all data partitions that fit offloading rules
Archived size [MB]	Size of unpacked archived data in MB Size of data in an online database that would be occupied, if all archived data would be reloaded
DTP source count	How many times an InfoProvider is used as a source in DTP load requests
Last DTP exec.	Timestamp of the last DTP load request execution
DTP dest. count	Number of DTP requests loaded into an InfoProvider (including reloaded requests from an archive)
DTP dest. relv.	Number of requests (DTPs for InfoCubes, activation requests for DSOs) relevant for straggler analysis by a DSO object - request is relevant when a Changelog contains records of this request by an InfoCube object - request is relevant when request records are not compressed by a WODS object - requests aren't relevant, as WODS can be archived only based on a request creation date by an ADSO object - based on the type of the object, the ADSO behaves the same as the equivalent object type (DSO, WODS, InfoCube) as ADSO object can have various settings. In general, the analysis collects requests for the following object types: Data warehouse - the data mart Information is gathered from the inbound table Corporate memory – reporting capabilities Information is gathered from the inbound table Data warehouse – delta calculation Information is gathered from the Changelog table
DTP stragglers	Number of requests with straggler records Subset of requests relevant for straggler analysis, which contain at least one straggler record
DTP stragglers rows	Number of rows that represent straggler records
Number of lookups	Number of lookups that are present in a system for an InfoProvider Number of lookups in the source code

Due to the readability of a result table, not all columns are displayed by default. To show or hide columns, you can choose from predefined ALV layouts or create your own.

Notification settings

The email address that was set during setup will be receiving notifications about potential offloading candidates. You are able to change delivery parameters as follows:

Find menu Notifications and choose Advanced settings.

List of notification parameters

Tech. name	Description	Details
ENABLED	Notifications enabled	If the value is set to X notification is enabled, if the value is empty notifications are disabled
LAST_MAIL_TIMESTAMP	Timestamp of the last email	Timestamp of the last sent email to the notification email address in format YYYYMMDDHHmmss, if the value is empty no email was sent yet
EMAIL	Recipient e-mail	Email address used for notifications
NEXT_MAIL_DAYS	Send next email after (days)	Time period in days when an email could be sent to the recipient e.g. If the value is 14, an email will be sent each 14 days If the value is 0, each time analysis collects data email will be sent
OFFLOADING_VARIANT	Offloading variant used	Offloading variant used for calculation of suitable candidates for offloading
SAP_USER	SAP GUI User	Name of SAP user that will be pre-filled in a shortcut attached to an email

Offloading rules

InfoProvider is displayed in results only in case it fits the rules. The product installation provides default rule values. However, you can adjust rule values according to your archiving strategy. Here you can find available rules:

Rule description	Default value	Details
Size of InfoProvider is greater than X MB	0.1 % of database size	The rule will avoid offloading for too small objects by setting the size threshold for InfoProvider
Data partition usage is less than X query executions	60	The rule will avoid offloading often used data partitions. The smallest data partition that can be identified is one month. Therefore, value 60 means that data from a particular month cannot be used more than 60 times in the analysis time range. If so, it will not be included in the offloading condition
Size of the data partition is bigger than X MB	1	The rule will avoid offloading for too small data partitions by setting the size threshold
Do not offload data newer than X months	12	The rule is setting a retention period for online data. For default value data that are newer than 12 months are excluded from the offloading condition
Analysis time range: last X months	3	The viewer is using data only for the last 3 months by default. If you are collecting data for multiple months, you can change these parameters to a bigger value. If you start with data collection within the last 3 months it will not give you more information

Rule values can be changed by clicking on the Rules button.

You can define additional "rules" by setting filters to the ALV table. When you then hit the Save button, all rules are saved together in offloading variant.

Example: How to set an additional filter

Choose the column which you want to filter

Set select option e.g. all object starts to Z

Confirm and save offloading variant

Offloading variants

Offloading variant contains rule values as well as ALV filters. You can create multiple variants in order to compare different offloading strategies. One offloading variant can be set as default for the calculation of notification emails and for Actions queue. The default offloading variant cannot be changed, but you can create your own.

Set offloading variant for notifications

The initial installation contains the default offloading variant that is used for notifications. If you want to get notifications based on your own offloading variant, proceed as follows.

Notifications > Set current variant

Offloading interface availability

Offloading analysis can recommend two offloading interfaces for objects:

Offloading interface	Description
DTO	SAP BW/4HANA SNP OutBoard™ Data Tiering Optimization
SDA+	SNP OutBoard™ Data Tiering with SDA+

Interface is recommended by multiple criteria. Here you can find the main criteria:

System prerequisites required by interface implementation
InfoProvider type support
InfoProvider requirements to interface
- special functions e.g. WRITER

Export configuration

If you choose InfoProviders that should be offloaded, you can select them and export their offloading-related configuration into the file. This file can be then imported to the development system in order to create offloading DataProviders. There are two ways to get the configuration:

Notification email contains a configuration file
Download the configuration file from the result viewer
- Choose the object that you want to export (if nothing is selected everything is exported)
- Click on the button Export configuration

Information on how to add DataProviders using a configuration JSON file can be found here: SNP OutBoard™ Data Tiering Main Screen (find Define DP from file).

Browser not supported