Composite Providers with BW on HANA for Efficient data modelling


By this time most of you’ll have come throughout the time period composite suppliers BW programs on HANA. This paper takes a deeper have a look at this new kind of Information supplier and in addition seems to be at how modelling eventualities that beforehand have been time consuming may very well be made simply, in lesser time and in addition make use of the Calculation engine of HANA to its finest. This paper doesn’t give attention to the steps to be adopted for making a composite supplier.

Composite Supplier:

A Composite Supplier is an Information Supplier, which mixes information from a number of analytic indexes or from different Information Suppliers (by Be a part of or Union), and makes this information accessible for reporting and evaluation. UNION and JOIN operations are executed in HANA and never the appliance server. BEx Queries could be created on Composite Suppliers as on some other BW Information Supplier. That is performed in transaction RSLIMOBW.

The primary benefit of Composite suppliers is that: BW Information Suppliers could be mixed utilizing the JOIN operation permitting us to create new eventualities not attainable or very costly with customary methods (Multiprovider, InfoSet).

After we hear the phrase Union, what strikes our thoughts instantly is a Multi supplier. SAP Nonetheless suggests the utilization of Multiprovider in case your requirement is simply to make use of Unions. It’s because the OLAP engine is properly suited to this operation.

Composite suppliers nonetheless can be utilized on high of Multiproviders to execute Be a part of operations with Multiprovider as one of many information suppliers. This provides us further flexibility and even one further stage of modelling thus permitting us to create new eventualities that weren’t attainable earlier than.

For data on the best way to create Composite suppliers utilizing RSLIMOBW discuss with

Having seen the definition and a few of the advantages of Composite suppliers its time that we soar into some actual modelling state of affairs to see its actual profit.

Modeling State of affairs:

Most  or virtually all of us would have come throughout this typical state of affairs of constructing cubes in our initiatives. A dice is created as a ultimate vacation spot for supply information. This dice is loaded from a number of DSOs containing transaction information and throughout the loading there are a number of lookups written inorder to fetch grasp information attributes from different DSOs and cargo them within the dice.

See also  The Application Was Unable To Start Correctly 0Xc00007B For An Sdl2 Application

Common Modeling State of affairs – An instance :

Allow us to take an instance of a easy dice. Allow us to assume that the dice is used for monitoring gross sales data primarily based on buyer information and in addition primarily based on the product bought. So for the report back to have slice and cube capabilities we would want to have all of the attributes of Buyer in addition to Product to be part of the dice. This isn’t required in case the attributes will not be required traditionally. The place we will use them as Navigational attributes. For instance, to trace gross sales of a metropolis (an attribute of buyer) for a month, and to see its pattern previously, it might make sense to have metropolis as part of the dice and lookup and populate metropolis each month from buyer grasp, when information is loaded to the dice. This prevents a buyer from being disregarded if his Metropolis was modified traditionally. Equally, we even have product attributes like Product Class, Product Group and so on.

A typical information mannequin for the state of affairs described above would appear like the next:

Modeling Scenario.gif

This state of affairs depicted above is simply an instance contemplating one supply DSO, In real-time, the variety of DSOs loading to a dice is normally a couple of and in addition the variety of look-ups carried out could be greater than what’s depicted right here.

  • On this typical approach, we not solely retailer the identical data of the DSOs in an aggregated type within the dice, but additionally add further attributes added to the transaction information and saved once more within the cubes.
  • An addition of latest attribute to the dice which requires look-up from considered one of these DSOs can be a herculean activity,  as the brand new attribute must be added to the dice and all of the impacted transformations, DTPs must be transported once more with precision. The attribute would then must be added to the Multiprovider to be made accessible within the experiences. And on high of this a reload of historical past is required in case an attribute is required traditionally.
  • AlthoughSAP has offered a brand new rule kind within the transformation referred to as the “Learn DSO information” within the transformation, this could solely assist us in avoiding the ABAP a part of the look-up however not in lowering the trouble taken for adjustments and the bills.
See also  Kinesis Stream/Shard - Multiple Consumers

Modeling State of affairs utilizing Composite Supplier:

With the brand new Composite supplier it’s attainable to comprehend the dream of storing the identical information solely as soon as not less than for this state of affairs. The next case exhibits how we will mannequin the identical state of affairs utilizing a composite supplier and thus make use of the calculation capabilities of HANA DB.

In transaction RSLIMOBW, we create a Composite supplier that makes use of the three Information retailer objects, Gross sales Transaction, Buyer Grasp and Product Grasp as proven beneath.

Composite Provider.png

How this works:

  • The Gross sales transaction DSO is taken within the Composite Supplier with Binding Sort “Union”. By default there needs to be not less than one Information supplier of kind Union within the Composite supplier.
  • The fields of Gross sales Transaction DSO are dragged into the Central Composite Supplier.
  • The Buyer Grasp and the Product Grasp DSO are added to the Composite supplier with the binding kind “Be a part of”.
  • Grasp information fields required within the composite supplier are dragged and dropped into the composite supplier. (These are the fields for which look-ups have been written within the authentic state of affairs).
  • The fields Buyer quantity and Calmonth are used as Be a part of fields and a be part of situation is drawn between the Gross sales DSO and the Buyer Grasp.
  • Equally Product quantity and Calmonth are joined from the Product DSO with the composite supplier.
  • On this approach, the composite supplier will include all of the data current within the Gross sales transaction DSO with the corresponding attributes crammed primarily based on the Calendar Month.
  • The Joins and Unions are executed on the question execution time. UNION and JOIN operations are executed in HANA DB.
  • Be aware that SID era possibility needs to be checked within the DSO for it to be accessible as an information supplier for Composite supplier.
See also  What do you lubricate sway bar bushings with?


  • Improvement time & Value:
    • Utilizing this method, quite a lot of time taken to develop look-ups and preserve complicated information fashions is saved.
    • Addition of a brand new attribute (adjustments) to cubes, which required altering quite a lot of objects within the earlier state of affairs could be very easy now. The one place the place the attribute should be added is within the supply DSO (Grasp DSO) and within the composite supplier Upkeep).
  • Loading time:
    • The time taken for loading large quantities of information by way of a number of layers (staging and additional) in BW is lowered because the Composite suppliers could be modeled utilizing the DSOs within the EDW layer itself.
    • The time taken for performing look-ups to derive attributes can be saved throughout loading.
  • DB Measurement:
    • A variety of DB –area is saved since we solely retailer data as soon as and use it at totally different locations as a substitute of executing a lookup and storing them each time within the dice.
  • Flexibility:
    • Additional to what’s proven above and as within the case with many of the actual time programs, not only one DSO masses to a dice. In that case, a Multiprovider is created on high of those DSOs will also be used within the Composite supplier to ship the specified outcomes.


With the brand new Composite supplier and SAP BW on HANA there are quite a few capabilities that may be explored to save lots of time and value on your firm. In every case it’s good to judge these prospects and make a clever choice.

NOTE : Please do not copy -

Leave a Reply

Situs Judi Slot Online Terpercaya

Link Slot Gacor

Slot Anti Rungkat

Slot Gacor Maxwin