Show TOC

InfoProviderLocate this document in the navigation structure

Use

The data source Read Data from InfoProvider allows you to use data from a BW InfoProvider as a data source in the analysis process. InfoProviders are InfoCubes, DataStore objects, InfoObjects, MultiProviders, InfoSets and queries.

More information: Creating InfoProviders

The data is provided as a basic table. The selection of characteristics and key figures determines which columns the table contains. If fields are omitted during selection of the characteristics, key figures are aggregated using the unselected characteristics. Aggregation is performed using the standard aggregation behavior for the selected key figure. If available, aggregates for InfoCubes are used.

Features

Reading data from an InfoProvider is comparable to direct selection of data according to the schema:

SELECT <selected characteristics and key figures>

FROM <InfoProvider>

GROUP BY <selected characteristics>

Some basic functions of the query are not supported and need to be mapped using downstream transformations.

Active Data

The system only reads data that is available for analysis and reporting from the data source InfoProviders. For InfoCubes, the data is available immediately, assuming that the requests loaded successfully. You can see this by checking the Request is Available for Reporting icon in InfoCube administration. For master data, the attribute change run must have finished. For DataStore objects, the data must have been activated. With DataStore objects of type Direct Update, the data can be seen immediately.

Compound Characteristics

All characteristics are considered independent fields. If characteristic Fiscal Year / Periods (0FISCPER) is selected for example, and compound characteristic Fiscal Year Variant (0FISCVARNT) is not selected, the data is aggregated using all fiscal year variants.

Units/Currencies

Units of key figures are considered independent fields. No currency translation takes place. If you aggregate using the Revenue key figure (0REVENUE) for example, the currency is ignored during aggregation. If necessary, include the relevant currency or unit field in the list of selected characteristics.

InfoObjects defined as "attribute only"

InfoObjects that are defined as Attributes Only are not offered as fields for selection if they are used in InfoProviders, especially with DataStore objects and master data tables.

Exception Aggregation

Key figures are only aggregated according to their standard aggregation. If the selected key figures include a key figure with exception aggregation, the associated reference characteristic for the exception aggregation must also be selected as a characteristic. This is intended to prevent a Number of Employees key figure with exception aggregation LAST from being totaled using periods, as this would be illogical.

The exception aggregation can be mapped using a downstream grouping step:

  • If the exception aggregation type is SUM, MIN, MAX, AVG, AV0 or NOP, you can use the Aggregate Data transformation. See Aggregating Data.

  • If the aggregation type is different to those listed above, you have to use the ABAP Routine transformation and program the aggregation yourself. See ABAP Routines.

Non-Cumulative Key Figures

Non-cumulatives can be modeled in the BW system using a non-cumulative key figure with the corresponding fields for changing the non-cumulative or the corresponding fields for receipts or issues. The current non-cumulative is then saved on a marker.

If a non-cumulative key figure is selected, the period end non-cumulative is provided for each period in the selected timeframe. This value is determined when data is read from the marker and the changes to non-cumulatives. If the selected period is outside the validity period, no non-cumulatives are returned.

More information: Modeling Non-Cumulatives with Non-Cumulative Values.

Features of non-cumulative key figures:

  • The reference characteristic for time-based aggregation (time-reference characteristic) must always be selected as a characteristic. If additional validity-determining characteristics were selected in the maintenance for non-cumulative parameters, these must also be added to the selected characteristics.

  • Since non-cumulatives are returned for all periods in the selected timeframe, a restriction for the time-reference characteristic must be defined in a downstream filter. Only one interval or a list of single values is supported here. Other restrictions for the time-reference characteristic cause errors during execution.

Query

If you want to use a query as an InfoProvider, you have to make the corresponding setting in the Query Monitor. See Query Properties. Note that the F4 help for InfoProviders only lists objects from the BW Repository. You therefore have to enter the name of InfoProviders of type Query manually. The name of the InfoProvider comprises the prefix @Q and the name of the query.

Example

For a query called QUERY, the associated InfoProvider would then be called @QQUERY.

Activities

  1. On the Data Source tab page, select an InfoProvider.

  2. On the Field Selection tab page, select the individual fields for the system to read data from during the analysis process.

    On the right of the dialog box, all the fields for the InfoProvider are listed, separated according to characteristics (top list) and key figures (bottom list). You must select at least one key figure and one characteristic from the list.

Example

You have selected the following characteristics and key figures from DataStore object RFM Response Rates (0CRM_OFCV):

  • RFM Response rate model (0CRM_RFMFCV)

  • RFM Segmentation model (0CRM_RFMSGV)

  • RFM R Segment (0CRM_RFM_R)

  • RFM F Segment (0CRM_RFM_F)

  • RFM Number of responses (0CRM_RFM_RE)

InfoProvider characteristic RFM M Segment (0CRM_RFM_M) is not selected.

When the data is read, the data passed on to the subsequent nodes (the next step of the analysis process) is grouped together with the standard aggregation behavior of the key figure on the level of the selected characteristics. The aggregation for the key figure is SUM, meaning that the system totals all records with the same combination of characteristics.

Example data:

  • RFM Response rate model (0CRM_RFMFCV) = test

  • RFM Segmentation model (0CRM_RFMSGV) = test

    R Segment

    F Segment

    M Segment

    Number of Responses

    1

    1

    1

    17

    1

    2

    2

    16

    2

    1

    1

    15

    2

    1

    2

    14

    2

    1

    3

    13

    3

    1

    1

    12

    In this example, the data on the node is as follows:

    R Segment

    F Segment

    Number of Responses

    1

    1

    17

    1

    2

    16

    2

    1

    42

    3

    1

    12