Transient and Virtual Provider for HANA model

[Former Member]

Hi experts ,

i would know the differences between Transient Provider and Virtual Provider to consume in SAP BW a HANA Model.

Thank you very much.

Best Regards.

Andrea

[vivekbhoj · Accepted solution]

Hi Andrea,

In Transient Provider:

All the columns of HANA Model are mandatory and will be included in the Transient Provider

InfoObjects are optional

No support for Navigational Attributes

Uses BW authorizations for assigned InfoObjects

Can combine HANA data with BW Data in a Composite Provider

It is not visible in BW Workbench using RSA1 transaction

Check: http://help.sap.com/saphelp_nw73/helpdata/en/11/69442974eb49aaa08ee5c225766858/frameset.htm

In Virtual Provider:

Can select the columns from HANA Model that you need for your Virtual Provider

InfoObjects are mandatory

Supports Navigational Attributes

Uses All BW Authorizations

Can combine HANA data with BW Data in a Multi Provider / Composite Provider

Check: http://help.sap.com/saphelp_nw73/helpdata/en/e4/e39762e1854b24a7230849c9ff589e/content.htm?frameset=...

[Former Member · Accepted solution]

Seems that same..

Could you suggest me some examples ? 

Thank you very much.

Andrea

[Former Member]

Hello,

For a virtual provider you can manual add the fields i.e. info objects.  Virtual provider can get data from any BW table using generic data source.

For a Transient provider you can not specify fields explicitly as they are created on HANA views. System automatically generate fields for them.

[Former Member]

Hi Andrea,

A Transient InfoProvider is like a Virtual InfoProvider, simply the meta data is transient rather than stale. That means that, yes, from a READ perspective it behaves like any InfoProvider. But from a WRITE perspective there is no information, i.e. it cannot be a data target. So you cannot write data into the transient InfoProvider; you can only write data directly into the tables that are accessed by the transient InfoProvider.

The biggest advantage of a transient provider is that the metadata in BW is not persisted, but always generated at runtime, i.e. if the source metadata is changed the Transient Provider is adapted automatically. The Transient Provider is therefore especially helpful in ad-hoc and/or frequent changing scenarios.

Transient InfoObject in the Transient Provider can reference to a “real” InfoObject and thus inherit its meta- and master data (like description, texts, display properties, display attributes and hierarchies). I.e. you can create a BEx Query on pure HANA data and model, but use a BW hierarchy and the BW hierarchy processing.

Refer the links below for more details.

http://www.saphana.com/docs/DOC-2129

https://www.experiencesaphana.com/docs/DOC-1463