Show TOC

Decision Tree for InfoProvidersLocate this document in the navigation structure

This decision help is aimed at users who are just getting to know SAP Business Warehouse (but who are familiar with Data Warehouses) and users who are not familiar with the current release and the latest InfoProviders.

Decision help:The number of InfoProviders is very high. Therefore you need a decision help that enables you to find the InfoProviders that are suited to your needs. Therefore the aim is to build a small, initial (test) scenario and not to build an entire Data Warehouse. You need to be able to quickly find an InfoProvider, so that you have a suitable "container" for your data.

Learning aid: You need to have an overview of the different InfoProviders and you need to be able to check whether you have selected the correct InfoProvider for your requirements. The arrangement of InfoProviders is based on the layered scalable architecture (LSA).

Call the decision tree:

To call the right decision tree, you first need to answer the following basic question: What is the main purpose of the new InfoProvider?

Restrictions

The decision tree cannot display all possibilities/properties as this would make it too complex and less user-friendly (if only transaction data is used for example, the planning is only covered briefly). The decision tree cannot replace a project in which the entire Data Warehouse is defined.

To improve performance when loading InfoCubes, we recommend using either a BW Accelerator (BWA) or a SAP HANA database. You can then

  • store the InfoCube data in the BW Accelerator (BWA index). However, this InfoCube has several restrictions, such as selective and request-based deletion, compression and data archiving. If these restrictions are not relevant for you, you should follow the above recommendation. If these restrictions are relevant, use a standard InfoCube.

    More information: Restrictions for the InfoCube with Data Persistence in the BWA

  • if using a SAP HANA database, create SAP HANA-optimized InfoCubes.