Composite Providers are used to combine multiple InfoProviders using Join or Union operations. When you use SAP BW on HANA, one of the InfoProvider. Trying to figure out how SAP BW’s relatively new virtual InfoProviders . CompositeProvider / Composite Provider – How to assign your Source. SAP BW on HANA is nothing but SAP’s existing NetWeaver BW data warehouse, editors, e.g. for the composite provider or the new query designer (planned).

Author: Goltigrel Mikalmaran
Country: South Africa
Language: English (Spanish)
Genre: Personal Growth
Published (Last): 20 April 2011
Pages: 190
PDF File Size: 16.34 Mb
ePub File Size: 4.90 Mb
ISBN: 906-6-50847-461-8
Downloads: 35893
Price: Free* [*Free Regsitration Required]
Uploader: Daira

The sum of the measures in the HCPR is equal to the sum of the measures in the fact table 1. With regards to joins: Search or use sapp and down arrow keys to select an item.

To find out more, including how to control cookies, see here: Manage logical grouping Grouping does not affect query performance, it only exists to organize the fields in a logical way. In that proivder he predicts a future where we as a people are threatened by technology. The result is in Figure You can find the Join Condition Fields in the Target area after selecting them.


Creating a Composite Provider in SAP BW on HANA

Well first of all: August 27, at Result of mapping Source fields to your Target. Slow logon WebI Rich Client? Please also refer to our Privacy Statement.

If you change your mind after this step, no worries, because you can add and remove PartProviders later in the CompositeProvider modeling screen. January 19, at 7: I would like to put this all to rest. Leave a Reply Cancel reply Your email address will not be published.

However, you cannot union a PartProvider that you join see Figure After you select CompositeProvider, you see the following screen:. January 11, at Hi Sid, I think that this solution has not been June 13, at 5: When you model with fields instead of InfoObjects, these are the main performance penalties: We use cookies to ensure that we give you the best experience on our website.

Migrate your Composite Providers (after upgrade BW7.3 –> BW7.4)

July 30, at I have already read the What can be the possible reason? In case of a Union, we map similar Source fields to the same field.

Hi Friedrich, Nice to hear that you’re using How many PartProviders can we join and union? If you want to disable cookies please change this in your browser settings. You can click a topic to jump to that particular section: This section is where we indicate which InfoProviders we want to add additionally in case of a Union and delete.


Keep in mind, there are also several functional restrictions when using field-based modeling. I was actually holding my breath asp I composlte these directions.

Creating a Composite Provider in SAP BW 7.3 on HANA

Hierarchies and formatting rules. Source fields are automatically mapped to the same Target fields with the same data type, length and technical name. I hope you will continue to provide more such tutorials.

We see that the description does not necessarily need to be the same. Add PartProvider screen Here we see something interesting. June 16, at 1: In case you only need specific fields, expand the PartProvider tree by clicking on the arrow next to the PartProvider name.

Select Join Partner composute.