Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-EI-APD (Application Component) Analysis Process Designer⤷
RSAN_WB (Package) APD - Tool - User Interface
Basic Data
| Data Element | RSAN_WB_DS_INFOPROV |
| Short Description | Source "InfoProvider" |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | STRG | Character String of Variable Length |
| Length | 0 | |
| Decimal Places | 0 | |
| Output Length | 0 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Text |
| Medium | 20 | Description |
| Long | 40 | Description |
| Heading | 60 | Description |
Documentation
Use
Data source InfoProvider allows you to use data from BW InfoProviders as data sources in analysis processes. Examples of InfoProviders are InfoCubes, DataStore objects or InfoObjects.
The data is provided as a basic table. The selection of characteristics and key figures defines 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 found, aggregates for InfoCubes are used.
To improve performance, you have the option of deactivating theEnsure Complete Aggregation" flag.
To access data stored in a near-line storage, set the "Read Near-Line Storage As Well" flag.
Details
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
Only data available for reporting is read from the data source InfoProviders. For InfoCubes, the data is available immediately, assuming that the requests loaded successfully. For master data, the attribute change run must have finished. For DataStore objects, the data must have been activated. For DataStore objects for direct update, the data is visible immediately.
Compound Characteristics
All characteristics are considered independent fields. If for example characteristic Fiscal Year / Period is selected, 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 that Are "Attributes Only"
InfoObjects that are defined as attribute only are not offered as fields for selection if they are used in InfoProviders, especially if used in 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.
- If the aggregation type is different to those listed above, you have to use the ABAP Routine transformation and program the aggregation yourself.
Non-Cumulative Key Figures
Non-cumulatives are modeled in BW using a non-cumulative value and its fields for changing the non-cumulative or for receipts or issues. The current non-cumulative is 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 set when data is read from the marker, and the non-cumulative value changes (see SAP Library -> SAP NetWeaver -> NetWeaver by Key Capability -> Information Integration -> Business Intelligence -> BI Platform -> OLAP -> Performance Optimization -> Non-Cumulatives). If the selected period is outside the area of validity, no non-cumulatives are returned.
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 can cause errors during execution.
Example
You have selected the following characteristics and key figures from the 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.
During the read process, the data passed on to the subsequent nodes is grouped together with the standard aggregation behavior of the key figure at 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
Activities
- On the Data Source tab page, select an InfoProvider.
- 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.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 30B |
