Prerequisites for Modeling Operational Data Providers

System Configuration:

You have configured the system for operational data provisioning.

More information: Configuring Operational Data Provisioning

Data Sources Supported for Search and Analysis Models

DataSources in particular are supported as data sources for analysis, but other data sources from the applications, such as DDIC tables, can also be used for operational data provisioning.

Prerequisites for DataSources

To be used for modeling ODPs, a DataSource must meet the following prerequisites:

• The DataSource supports direct access.

  Note

  If the DataSource does not support direct access, operational data provisioning is only possible if the data in the database or SAP BW Accelerator is indexed.

• The ODP-relevant DataSource fields has field descriptions.

  Note

  If the DataSource does not contain any field descriptions, the descriptions in the search and analysis node at node attribute level have to be maintained.

• The DataSource key fields have been propertly defined.

  Check the DataSource's key fields and change them if necessary. Proceed as follows:

  1. The DataSource inherits its key fields from the extract structure. You should therefore consider checking the extract structure's key fields in the ABAP Dictionary. To view the key fields in the ABAP Dictionary, choose  Extras  DB Properties  Keys On/Off .

  2. We only recommend maintaining key fields at node level in the search and analysis model if the key fields can be changed in the ABAP Dictionary.

     Example

     • If the extract structure is made up of includes, the includes provide key fields too, but these might not be suitable as DataSource key fields.

     • If the extract structure is a view, the ABAP Dictionary assigns the key fields to the view. If the ABAP Dictionary does not know how to assign the key fields to the view, all fields are defined as key fields.

• If you want to replicate large data sets, or data sets that change very rapidly (mainly transaction data), the DataSource should ideally support deltas.

• If a delta DataSource is real-time compatible, the corresponding field is flagged in the settings for the generic delta in DataSource maintenance (transaction RSO2).

  Note

  For BW replication (with real-time data acquisition) and data replication to external consumers (ETL), this means that the data is loaded at a frequency of up to once a minute.

  This means real-time indexing can be used in the database or in the SAP BW Accelerator. More information: Managing Real-Time Indexing

• The DataSource has uniquel defined selection properties that are supported by the extractor.

• Not supported for customer-defined modeling: DataSources for hierarchies and DataSources that build non-cumulative values.

• DataSources for data reconciliation are not relevant for operational data provisioning.