VirtualProvider with BAPI 

Definition

VirtualProviders whose transaction data is read for analysis and reporting from an external system using a BAPI.

Use

Using a VirtualProvider, you can carry out analyses on data in external systems without having to physically store transaction data in the BI system. You can, for example, use a VirtualProvider to include an external system from a market data provider.

When you start a query with a VirtualProvider, you trigger a data request with characteristic selections. The source structure is dynamic and is determined by the selections. The non-SAP system transfers the requested data to the OLAP processor using the BAPI.

This VirtualProvider allows you to connect non-SAP systems, in particular structures that are not relational (hierarchical databases). You can use any read tool that supports the interface for a non-SAP system.

Since the transaction data is not managed in the BI system, you have very little administrative effort on the BI side and can save memory space.

Structure

When you use a VirtualProvider to analyze data, the data manager calls the VirtualProvider BAPI, instead of an InfoProvider filled with data, and transfers the parameters.

●     Selection

●     Characteristics

●     Key figures

The external system transfers the requested data to the OLAP processor.

Integration

To use a VirtualProvider with BAPI for analysis and reporting purposes, you have to perform the following steps:

...

       1.      In the BI system, create a source system for the external system that you want to use.

       2.      Define the required InfoObjects.

       3.      Load the master data.

       4.      Define the VirtualProvider.

       5.      Define the queries based on the VirtualProvider.