Virtual InfoProvider on SAP

HANA Model View

Introduction
The main role of Virtual InfoProvider is to give the needed information without any time lag
and without storing the data physically on the BW server.
So, Virtual Providers are just like structures with no persistent storage.
Virtual providers are often used for reconciliation purposes of the data loaded in SAP BW
with a normal staging data flow and the source system.
Direct Access is relevant for both transactional data and for master data, and is mapped by
Virtual Info Providers,

Important Factors to be considered:

Virtual Providers are only suitable for cases when:

The need of precisely up-to-date information is very strong.
A small amount of data is accessed from the source
The information will be requested only by a few users simultaneously


Types of Virtual Providers:
Virtual Provider based on Data Transfer Process (DTP) - SAP Remote Cube
Virtual Provider based on BAPIs. - Remote Cube
Virtual Provider based on function module. - Virtual Infocube with Services
Virtual Provider based on HANA Model.
Types of Virtual Providers:
Virtual Provider on HANA
Introduction to Direct Access
Datasource:
In order to support a virtual infoprovider, a datasource must be of direct access enabled.
Generally all Generic Datasource supports Direct Access.
But the Business Content Datasource needs to be activated for direct access.
The most important use this Direct Access Datasource can be seen in data reconciliation
Business Scenarios.
If a Datasource is supporting Direct Access, then directly the source system data can be
accessed with the help of that Datasource, thus it can be used in a Virtual Infocube.
Each Virtual Provider can access a random number of Data Sources.
The connection between data sources & a virtual provider is defined with regular staging by a
transformation & DTP.

There are two categories of this type of Datasources:
1. Preaggregation Supporting Datasource.
2. Preaggregation Not Supporting Datasource.
Preaggregation Supporting Datasource:
Such types of datasources are capable of extracting aggregated data (key figures) when data
is extracted from the fields of corresponding tables.
So this Datasource can be used in a DSO with Overwrite mode also.

Preaggregation Not Supporting Datasource:
Such types of datasources are not capable of aggregating data, when data is extracted from
the fields of corresponding tables.
So a DSO in overwrite mode cannot be used for this Datasource.


Note:
Since our Datasource is Direct Access Enabled, so there is no need for creating Infopackage
for this Datasource. It will access the data directly from the source system tables.
Types of Virtual Providers
Virtual Provider based on BAPIs:

The transaction data is read from a different source which is called BAPI (Business Application
Program Interface) and not specifically from an SAP source.

Virtual Provider based on function module:

A user-defined function module is used as the Datasource.
In comparison to other Virtual Providers, this one is more generic.
It offers more flexibility, but also requires a higher implementation effort.
It allows not only to select the needed data from the source, but freely make complex data
calculations or changes before pushing it to the OLAP engine.
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.




Virtual Provider on HANA Analytic view
Key Features:
It offers a very flexible way of integrating data not stored in BW Objects into the consistent
BW world.
We can turn on Navigational Attributes for the Virtual Provider as usual. Then we can map
the Navigational Attribute also to a field in the HANA model in the Provider specific
properties if you do not map it, the data comes from the Master data tables in BW.
Virtual Provider can be transported as usual, it can be used in a Multi Provider and BEx
Queries can be built on top, just like for any other Virtual Provider.


Virtual Provider on HANA Analytic view

Prerequisites:

SAP HANA database.
Have created a SAP HANA model in SAP HANA Studio.
If we also want virtual master data for the Virtual Provider, then you need to start by creating
virtual master data.
We can create a Virtual Provider based on a SAP HANA model if you want to use this model in
the BW system.
Analytic views and calculation views are available as SAP HANA models.
Unlike the Transient Provider based on a SAP HANA model, the Virtual Provider based on a
SAP HANA model is suitable for stable, long-term scenarios.
Virtual Provider can be used in a MultiProvider.
In addition, navigation attributes can be used. To use navigation attributes, we can select
InfoObjects with master data access Standard or SAP HANA Attribute View.


Virtual Master Data:

If you want to use virtual navigation attributes and texts in a Virtual Provider based on an SAP
HANA model, we need to create virtual master data.

Steps For creating Virtual Provider on HANA
Analytic view
Steps For creating Virtual Provider on HANA
Analytic view
Next click the Assign HANA Model Attributes button in upper right corner in order assign the
attributes to Info Objects.
Select propose mapping checkbox and click continue

Steps For creating Virtual Provider on HANA
Analytic view
Select the required attributes and If not found then Click continue.

Steps For creating Virtual Provider on HANA
Analytic view
For Manual mapping, right click the dimension/Key Figures and click provider specific-Info
Objects properties.

Steps For creating Virtual Provider on HANA
Analytic view
Similarly do the same for Key Dimensions.
Note: Make sure measure attributes like COST, NETPRICE,NETVALUE have same data type
with predefined Info Objects .








Finally Virtual provider is created and we now check the data
We also create a B ex Query on Virtual provider and report it using RSRT.