Show TOC

InfoProvider PropertiesLocate this document in the navigation structure

Concept

In the transaction for modeling InfoProviders, you can make the following settings by choosing Start of the navigation path Extras Next navigation step InfoProvider Properties Next navigation step Change End of the navigation path in the main menu:

Query/Cache tab page:

Here, you can make various settings that you can call via the Query Monitor. Here, you only make the settings per InfoProvider and not per query like in Query Monitor.

More information: Query Properties

Roll up tab page:

You only see this tab page when working with InfoCubes. You can make settings for the aggregates here.

Load register page:

You only see this tab page when working with DataStore objects. You can make settings here that you can also make in the Settings filer in the DataStore object maintenance transaction.

DB Performance tab page:

You only see this tab page when working with InfoCubes. You can make the following settings here:

  • Delete index before each data load and rebuild again afterwards:

    This deletes the index before each data load and rebuilds it again afterwards:

  • Delete index before each delta load and rebuild again afterwards:

    This also deletes the index before each delta load (smaller amounts of data, that is) and rebuilds it again afterwards. With smaller amounts of data, it is often not worth rebuilding, as the effort involved is greater than the gain. However, for delta loads with a large quantity of data (more than a million records), it does actually make sense to delete the indexes and rebuild them completely after loading.

  • Recalculate DB statistics after each load:

    By recalculating the statistics after each load, you can ensure better performance with data analysis.

  • Recalculate statistics after delta upload too:

    This also recalculates the statistics after each delta load (smaller amounts of data, that is). With smaller amounts of data, it is often not worth recalculating, as the effort involved is greater than the gain.

  • Percentage of IC data for rebuilding the statistics:

    Here, you can define the percentage of data in the InfoCube to use when rebuilding the statistics. Rebuilding the statistics then takes less time than if all data is taken.

  • Zero elimination in the summarization module:

    Here, entries in the fact table where all key figures are identical with the initial value are deleted when the fact table is compressed. Whether or not zero elimination makes sense depends on your scenario. If you want to see characteristic combiations with key figures that are zero in reporting and analysis, you should not carry out zero elimination. During compression, elimination of zero values makes runtime longer.

  • No update of the non-cumulative marker:

    This stipulates that the marker is not updated when changes to non-cumulatives are posted to an InfoCube with non-cumulative key figures. You can use this option to load non-cumulative changes from the past to an InfoCube after initialization with the current non-cumulative has already occurred. You then need to perform a compression with this option before using this data in the analysis.

  • Delete index during rollup:

    Normally, the index of the F table for the aggregate is deleted and rebuilt during rollup. If you have deactivated this automatic setting, you can reactivate it here for this specific InfoProvider.