Show TOC

Editing Runtime Parameters of DataStore ObjectsLocate this document in the navigation structure


To improve performance when processing data in the DataStore object, you can make a number of settings for each DataStore object in the runtime parameters or edit general default settings for DataStore objects.


  1. You can access the maintenance transaction for runtime parameters in Customizing under Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver Next navigation step Business Warehouse Next navigation step Performance Settings Next navigation step Maintain Runtime Parameters of DataStore Objects End of the navigation path. Alternatively, you can access this transaction in the Administration section in the Data Warehousing Workbench, under Start of the navigation path Current Settings Next navigation step DataStore Objects End of the navigation path.
  2. The left area of the screen shows all the DataStore objects. You can search, filter and sort this list. Choose Specific Settings to only display the DataStore objects with settings that do not match the default settings. Choose Delete Filter to display the entire list again.
  3. Choose Edit System Setting to display or change the system-wide default settings.
  4. Generic Settings:

    You can define the following:

    • Activation Package Size: minimum number of data records for each data package when data is activated in the DataStore object.

    • Activation Waiting Time: The maximum wait time in seconds when data in the DataStore object is activated. This is the time that the main process (batch process) waits for the split process before it determines that it has failed.

    • Package Size for SID Generation: Minimum number of data records for each data package when SIDs are generated in the DataStore object.

    • Waiting Time for SID Generation: Maximum wait time in seconds when SIDs are generated in the DataStore object.

    • Rollback Waiting Time: Maximum wait time in seconds for rollback in the DataStore object.

  5. Process Settings:

    You can make the following settings for activation, rollback and SID generation:

    • Parallelization: Type of processing: serial, parallel (batch), parallel (dialog)

    • Number of processes: Maximum number of parallel processes

    • Server Group: Server group to be used for parallel processing of data in DataStore objects. You need to create the server groups beforehand using: Start of the navigation path SAP Easy Access Next navigation step Tools Next navigation step Administration  Next navigation step  Network  Next navigation step  RFC Destination, RFC  Next navigation step  RFC Groups End of the navigation path. Unless you specify otherwise, processing runs on the server where the batch activation process was started. If a server in the server group is not active, processing is terminated.

  6. Expert settings:

    You can expand and collapse the expert settings by choosing Show/Hide Expert Settings. Usually it is not necessary to change these settings from their default values.

    You can define the following:

    • MPP:

      • Classic activation: MPP activation can be disabled here.

      • Log SQL: By logging the generated native database statements, you can display them in transaction RSODSO_SQLTRACE.

      • Access for SID handling: Here you can specify which database access strategy is used.

    • SAP HANA:

      • Package Size for Data Restriction: the package size used for the SAP HANA-optimized and memory-optimized (MCR, "memory consumption reduced") activation of requests.

      • Number of Packages: the number of packages that are processed in parallel during SAP HANA-optimized request activation.

      • Access for SID handling: In the context of SAP HANA-optimized DataStore object activation, SID generation supports various access methods for reading characteristic values for further processing from the active data/activation queue. Refer to the system F1 help for the options.

      • Compress Change Log: Only select this option if you want to write change log entries for activated records, and the activation of these records has actually changed the status of the active data.