Business applications store operative data in the form of business documents and master data.
In SAP BW, DataSources and their extractors make it possible to access this data.
DataSources provide a flat analytical view of the data in business documents, such as sales orders or purchase orders.
They contain the business logic that derives an analytical view of the data from the transactional view.
There are various types of DataSource: DataSources for transaction data, master data attributes, master data texts and master data hierarchies.
Until now, DataSources have been used to replicate mass data from the operative system to SAP NetWeaver’s Data Warehouse, SAP NetWeaver BW.
OLAP analyses in BW are not based directly on DataSources however, they are based on InfoProviders.
InfoProviders provide a view of a dataset from various, semantically related DataSources (purchase order data, customer data, or product data for example).
With Operational Data Provisioning, SAP NetWeaver provides a metadata concept that allows analytic query access for OLAP analysis.
This occurs in an operative system with replication scenarios (including an ETL service with a delta mechanism).
ODP is implemented in a modeling environment, used together with the search, and provides a metadata view in which a DataSource can be given analytical properties to define an Operational Data Provider (ODP).
An Operational Data Provider can be used to access the data for the replication in various consumers (SAP BusinessObjects Data Services for example) and for the purpose of operational analytics.
DataSources are not suitable for Operational Analytics, as they are too basic. A transaction data DataSource does not recognize the associated master data attributes, and the DataSource for master data attributes does not recognize the associated texts.
Operational Data Provisioning uses ODPs here to allow semantically related DataSources to act as InfoProviders, so that the data is available to the Analytic Engine in an Operational Analytics scenario without the need for replication to SAP NetWeaver BW.
With Operational Data Provisioning, the delta queue is located highly compressed in the source system.
The delta can be directly loaded to the BW InfoProvider using the Data Transfer Process.
A delta queue is a data store in the source system. Data records are either written automatically to the delta queue using an update process in the source system (for example, standard datasources), or retrieved using the extractor interface (for example, generic datasources).
The role of a provider is to provide one or more delta queues of a specific type. The BW DataSource is an example of a provider. In this case, the delta queue name matches the DataSource name (for example, ZDS_VBAK).
The target application of the delta queue is referred to as the Subscriber (of a specific data services system, for example).
A specific subscriber orders data changes from one or more queues and continues processing the transferred data. Subscribers are categorized by their subscriber type (for example, SAP BusinessObjects Data Services).
A subscription occurs when the subscriber requests data. Every subscription has a unique transaction number (for example, 2010-10-22 08:03:52 000001 CET).
A subscriber can have more than one subscription. A queue can also be in multiple subscriptions for the same subscriber.
The data is stored in a compressed state in the delta queue. A delta request transfers data records from the queue to the subscriber. The data changes to a queue can also be requested by more than one subscriber.
A subscriber can also request data from a queue as a one-off request (Full). In this case, the request is not a subscription. The data is retained in the delta queue for a specified time for recovery purposes – in other words in case the subscriber wishes to retrieve the data records.
The Delta Queue Monitor (transaction ODQMON) helps you to monitor delta queues in the following views:
● Queues Here you see all the queues available in the system with the status of each queue, the number of associated subscriptions and the number of associated requests.
● Subscriptions This view displays the detailed information for the subscription level.
● Requests This view displays the detailed information for the request level.
● Units This view displays units in which the data from a request can be transferred jointly
Create ODP source system and datasource.
Refer to post for more details on how to create source system and datasource of type ODP:
Create transformation and DTP. Execute the DTP. Once load is finished, check the data in the inbound table. Go in runtime information to see the number of entries and memory consumption.