Summary:
Virtual Info Cubes are Info Providers with transaction data. It is not stored in the objects themselves, but is
read directly for analysis and reporting purposes. Virtual Providers using DTP is used for Up-to-date
information from SAP Source system provided very small quantity of data exists.
In this article, we'll deal withsuch a situation as a demo example, wherein data is loaded by using DTP. There are also other ways, likeusing BAPI. In case of VPs based on BAPIs, the transaction data is read from a different source which iscalled BAPI (Business Application Program Interface) and not specifically from an SAP source. Similarly, wehave VPs using FM also, incase data needs to be loaded from non-BI Data Sources in BI without having tocopy the dataset into the BI structures.
Introduction
Virtual info provider with direct access is really slow, and must be threaded wisely. If we have a lot of records
transmitting between the remote function calls. There might be a situation where data for the Info provider
need not be stored physically. One such model is an Virtual Info provider. This acts very similar to an Info
cube, but is not physical data storage, with dimensions, characteristics and key figures like normal Info
cubes. But the actual generation of data for this cube, depends on one's making.
We can choose to create a virtual provider with a 'Direct access' to R/3. This means that upon viewing the
data in this virtual provider, a remote function call is called direct to R/3 to get the values on the fly.
Creating a Virtual Info cube
In SAP BI 7.0, just right click on any info area, and choose create 'virtual provider'. For direct access, you
choose Virtual Provider with 'direct access'. There is one more method by using the old R/3 info source.
Direct Access:
Direct Access is suitable only for data sources with especially small data volume and for a small number of
accesses. Direct Access is relevant for both transactional data and for master data, and is mapped by Virtual
Info Providers, that are defined like regular Cubes & regular IOs. But exist only in the meta data of the BI
system.
3 types of Virtual Providers:
VPs with Staging Connect (Simple DTP)
VPs using BAPI (for transactional data only)
VPs using Function Module
Virtual Providers with Staging Connect
VPs with Staging Connect offer an option to access the data of a source system through Data Sources of the
Source system & use transformation procedure for the supply.
VPs for transactional data are modeled as Info Cubes, but we must choose the type which only selects Meta
data. Virtual Providers for transactional data access the data source in the source system for characteristics
& key figure. However, it always reads master data of characteristics from the existing master data tables in
BI system.
Note: Attributes like IOs can be defined only as display & not as navigational data.
Each Virtual Provider can access a random number of Data Sources. The precondition is the ability of
respective data source to provide data to BI system via direct access. The connection between data sources
& a virtual provider is defined with regular staging by a transformation & DTP.
How many Data sources supply data to a virtual provider depends on the defined transformations & DTP.
With definition of DTP, we must select the option 'Do not extract from PSA but Access Data Source' and the
adapter for synchronous extraction. The data sources which are actually to be read with direct access need
to be redefined explicitly. This is done in the context menu of the respective target structure (master data
attributes or texts or cube) and is activated via 'Activate Direct Access'
Virtual Providers with BAPI:
There are also other ways, like using BAPI. In case of VPs based on BAPIs, the transaction data is read froma different source which is called BAPI (Business Application Program Interface) and not specifically from an SAP source.
Using VPs with BAPI, the systems from the third party suppliers can be used to retrieve data from these
systems. The principle is similar to the virtual provider with staging connect, but the obtained data is not even
processed in a transformation.
Data requirement is not directed to the data sources of the source system, but requires a specifically
prepared 3rd party source system that provides a corresponding BAPI to exchange data.
It needs to be already supplied in the form required for analysis.
The creation of a VP with BAPI is similar to creation of VP with staging connect, where the type based on a
BAPI is selected and the RFC destination to respective 3rd party source system is indicated.
Virtual providers with BAPI are used in special cases if data is to be obtained from a market data supplier.
Up to release of 3.X of BW, BAPI was referred as general Remote Cube.
Virtual Providers using Function Module:
In comparison to other Virtual Providers, this one is more generic. It offers more flexibility, but also requires a
higher implementation effort. The data can be local or remote. We can also use your own logic to change
data before it is passed to OLAP processor.
We use this incase data needs to be loaded from non-BI Data Sources in BI without having to copy the
dataset into the BI structures.
Step-by-Step Guide 
No comments:
Post a Comment