Page Comparison

...

• AUTHORIZATION – this parameter determines if OutBoard Authorization is switched ON (value X) / OFF (value ' ')
  Default value: OFF
• BG_JOB_DIRECT_START – this parameter determines if Background jobs in OutBoard are started "With converting to Time – Based Jobs" (value 'X')/ "Without converting to Time – Based Jobs" (no value). When job is started "Without converting to time based jobs", this job is scheduled and started normally, when any background job is free. When selecting "With converting to Time – Based Jobs", the job will be started immediately if any background job is free, if there are no free background jobs it will try to execute the job every ten seconds for 30 minutes.
  Default value: OFF.
• CURRENCY – the currency in which money saved is calculated.
  Possible values: Any currency available in SAP.
  Default value: EUR
• DATA_CLASS – determines the Data Class for storage table and its indexes. It can be changed only when no data is archived. For Oracle database the tablespace for particular storage table can be selected. It is determined by DATA_CLASS. The link between a tablespace and Data Class can be found in table TAORA.Possible values: Any Data Class available in SAP system.
  Default value: APPL1
• DISPLAY_COMP_RATIO_TYPE – this – This parameter determines the way of computing the saved storage by archiving. Two There are two possible settings are possible:

  1. LOCAL_ONLY

  : when the saved storage is calculated,

  - In case the archiving is performed in external database, the ratio for calculating of the saved storage in

  external storages

  primary database is set to 100%

  , for data archived in the online database the compression ratio was determined during archiving. When the saved storage is calculated, the compression ratio used for calculation is taken and was determined during archiving. In case the parameter is changed

  .

  2. EMPTY - In case the archiving is performed in primary database (e.g., Cluster), the compression ratio is calculated based on the size between all data and archived date. 

  If the parameter is changed from LOCAL ONLY to EMPTY, the statistics need to be recalculated with the report /dvd/nls_upd_clu_ratio_size.

• FILTERING_TYPE – determines the way, how is the archived data filtered when accessed. Can be based on RANGE or SETS.
  Possible values: RANGE, SETS
  Default Value: RANGE
• HNA_UNLOAD_PRIO – determines the Unload Priority of Outboard tables for SAP BW running on SAP HANA. It can be 0 ~ 9, where 0 means not-unloadable and 9 means earliest unload.
  Default value: 9
• LOAD_MAX_GRAN – determines the maximum number of packages that can be processed at once in the loading via a Data Transfer Process (DTP).
  Possible values:  integer > 0 e.g. 10, 20, 50
  Default value:  5

• LOAD_USE_ADD_SORTING – when enabled, data loaded from archived WODS is sorted in same order in which it was loaded. This applies when setting has value ‘X’, L mode is used, source WODS is archived. Setting may be switched ON (value X) / OFF (value ‘ ’)

  Default value: ‘ ‘
• LOAD_PAR_RET – maximum number of finished processes during parallel DTP load.
  Possible values:  integer > 0 e.g. 10, 20, 50
  Default value:  2
• LOAD_PAR_WP – determines how many parallel jobs will be used for reading from the archive when loading from the archive via DTP. 
  Possible values:  integer >= 0 e.g. 0, 4, 15
  Default value: 2 (parallelization using 2 jobs)
• NAV_ATTR_BUFFER – size of buffering table when Navigation attribute support is switched on.
  Possible values:  integer > 0 e.g. 10, 20, 50
  Default value: 3000000
• NAV_ATTR_FILTER_POS – defines the filtering order/ priority when Navigation attribute support is switched on. Value 0 means that filtering on Navigation attribute is done at first then the filtering on other attributes is done. Value 1 represents the opposite scenario.
  Default value: 0
• NAV_ATTR_SELECTION – parameter to turn the navigation attribute support functionality: on (1) or off (" "). This setting can be edited on InfoProvider level. It is recommended to turn off this parameter for SybaseIQ archiving storage, because needed filtering is done on the database level and there is no need to use the standard Outboard navigational functionality in this case.
  Default value: 1
• NLS_STATISTICS – this parameter determines if OutBoard Statistics is switched ON (value X) / OFF (value ' ')
  Default value: ON
• REBUILD_AGGREGATE – this parameter defines if OutBoard aggregates are rebuilt automatically (value X) during the archiving process, or deactivated instead (value ' '). If the automatic rebuild is switched off, the OutBoard aggregates can be activated and filled again using the report /DVD/NLS_FILL_AGGREGATE_IN_BG.
  Default value: ON (X)
• REP_PAR_WP – this value determines how many work processes are used for reading when data from OutBoard is requested for reporting. For more information see [#Reporting Reporting on archived data].
  Possible values:  integer > 0 e.g. 10, 20, 50
  Default value:  2 (parallelization using 2 jobs)
  Note: For an IQ transparent storage, the parameter for REP_PAR_WP cannot be set to higher than 1.
• SIZE_DIFF_TRESHOLD – if using a size dependent OutBoard license, after reaching this value of free space, the user will get a warning message by each archiving process or creation of DAP.
  Default value: 60 GB
• SIZE_TO_MONEY_COEFF – determines how much money costs one GB. Money saved is computed by multiplying SIZE_TO_MONEY_COEFF by storage saved.
  Possible values: integer > 0 e.g. 10, 20, 50
  Default value: 10
• SIZE_UNIT – the value used as a base unit of measurement for all volumes shown in GUI. If changed, data is recalculated accordingly.
  Possible values:  KB, MB, GB    
  Default value:  GB

• UPDATE_SIZE_STATISTICS – this parameter determines if object size statistics are updated when archiving or reloading data. In case of substantial archiving requests, recalculation has a noticeable performance impact. Setting may be switched ON (value X) / OFF (value ‘ ’)
  Default value: ON

• USE_DATA_CLASS_BADI - determines if BAdI will be used to define DATA_CLASS. If the value is 'X' the parameter DATA_CLASS cannot be edited in Settings for a given InfoProvider. (The default value can still be changed.) If the BAdI is used, the implementation for BAdI /DVD/NLS_DETERMINE_DATACLASS has to be created. Parameters of BAdI: iv_dapname – Technical Name of InfoProvider ev_data_class – Data class in technical settings. The output format of the BAdI implementing class method GET_DATA_CLASS should be of type TABART.
  

...

• NLS within the database tables of the particular BW system. This solution is not supported, if the primary system is running on SAP HANA database.

...