Versions Compared

Version Old Version 1 New Version Current
Changes made by

SNP

Marian Vidra

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 notification 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

...

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

ColumnDescription
ObjectContains a technical name of an InfoProvider
TypeDisplays a type of an InfoProvider (InfoCube, DSO, aDSO, WODS)
DescriptionLong description of an InfoProvider
Off. interface

Recommended offloading interface

InfoDetailed 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
RowsNumber 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 the this case, the InfoProvider is empty. This event occurs when a query uses a MultiProvider which includes this InfoProvider
Trend - Number of queriesVisualization 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 countHow 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. countNumber 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 (see for more details)

  • Subset of requests relevant for straggler analysis, which contain at least one straggler record
DTP stragg. rowsNumber 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

...

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:

...

Example: How to set an additional filter

Choose the column which you want to filter

...

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 email and for Actions queue. Default offloading variant variants cannot be changed, but you can create your own.

...

  • 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).