Skip to Content
Author's profile photo Former Member

Procedure to Convert Multiprovider to Composite provider


This is Srinivas Dayana, Working for Cognizant Technology Solutions. I have 10 years of experience in BW and ABAP. I am working on SAP HANA for the past 4 years. As part of the Project requirement, we are currently Simplify few Processes and even want to use the optimised BW objects like ADSO and Composite Provider which will ease the migration from BW 7.4 to BW 7.5.


As part of the Project requirement we have build a new data model using the ADSO and Composite Providers and we came across the scenario where there are almost 100 workbooks which are created by Business and all the workbooks will be effected when we switch from old Model to New Data model and Business have to recreate all the workbooks again which will effect Business reporting. So we are using the below conversion tool to convert the Multiprovider to Composite Provider and then enhance the Composite provider with the newly created composite provider so that none of the Queries will be effected and there will not be any impact on the workbooks which will save  lot of time for the business users.

Key Outcomes:

  1. Easy conversion of Multiprovider to Composite Provider
  2. Pros of using the below conversion tools
  3. Points to remember while using the approach

Introduction: We have Business scenario to convert the old BW Multiproviders to Composite Provider, so that we can use some additional functionalities like Join and perform operations on top of the existing MPRO’s. Business has so many Queries and Workbooks that are created on the same and we don’t want to change the existing Reports and Workbooks as that may have impact on the Business reporting.

This Conversion method will ease the Process of converting the Multiproviders to Composite provider with out having impact on Queries and Workbook.

The Below is the step by step Procedure to convert multiprovider to composite Provider:

Step 1: Create a new multiprovider for testing purpose

Step 2: Select the required sources for the multiprovider


Step 3: Identify the Fields that are required and the source from which the data should be populated for the field

Step 4: Activate the Multiprovider

Step 5: Execute the program RSO_CONVERT_IPRO_TO_HCPR

Step 6: Select the Infoprovider which we want to convert to Composite Provider. In this case we will use the multiprovider, which we have created for the test purpose.

Step 7: In the above screenshot , provide the name of the composite provider

  1. If we want the infoprovider name and the composite provider name to be same then give the same name as the Infoprovider
  2. We can also give a new name depending on the requirement

*In this case we want to create the Composite provider with the same name, as none of the existing Queries or Workbooks will not get effected.

Step 8: We cannot execute the above Program without giving backup provider name if we are giving the same number as the Multiprovider


Step 9: Provide the Backup infoprovider name  and execute in Simulate mode to check whether the Infoprovider can be converted to Composite provider or not.

Step 10: if there are no errors then we can go ahead with the conversion of Multiprovider to  a Composite Provider

Step 11: Execute the Program providing all the required Inputs and use the setting “Convert Infoprovider and copy Queries”

Step 12: Select the required Queries that we want to backup.

Step 13: Select the Required fields for the Queries

Step 14: Provide the Backup Query name, we cannot give the Query name same as the Backup Query  name, in the below example the report 3 will give the error as we have given the same name

Step 15: Provide the proper backup Query name and Proceed

Step 16: Check if there are no errors and confirm

Step 17: Multiprovider is now converted to a Composite Provider

Step 18: Open Query Designer and check for the Target and we can see one set of actual Queries and another set of Backup Queries

Step 19: Test the report before and after the changes

*Output of Query on multiprovider

*Output of Query on Composite Provider

Note: If we collect all the changes in the same Transport then we need to import the changes twice and if everything works fine and if we want to delete the Backup Queries, collect the Queries in separate Transport and import them separately.

The conversion is successful and in case of issues and we need to restore back to the old MPRO , please execute step 20.

Step 20: If the Conversion has some issues and the reports are not working fine we have setting to restore the backup. Select the setting “Restore backup” so that we will be converting back to the Old MPRO.

Note: The setting should be same as the setting during conversion. We need to Provide the exact same setting that we have provided when we have initially converted the Multiprovider to Composite provider or else Restore will not work, so make sure we have backup of the settings. We always need to select the Overwrite Existing HCPR option while doing the restore backup option

Step 21: We can see the Composite provider is set back again to multiprovider

Benefits of this Approach

  • Easy Conversion of Multiprovider to Composite provider
  • None of the Queries will be effected due to the conversion from Multiprovider to Composite provider
  • Use the additional functionalities of composite provider
  • None of the workbooks created on the Queries will be effected, so there will not be much impact on the Business due to the conversion

Hope this post is useful and i will update further post on SAP BW and SAP HANA when i have some new learning.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Ragunathreddy S
      Ragunathreddy S

      Hi Srinivas,

      Thanks for sharing the knowledge.

      So you mean to say, by giving MP Name (same name) for Composite provider only this is getting possible.

      procedure remains same. if we give Different name for HCPR the  queries/ Workbooks will get effected. Correct

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Ragunathreddy,

      Good Question. If the Multiprovider name is different from Composite provider, then all the old queries which are existing on the multiprovider will still refer to the Multiprovider and the new set of Queries which we will be creating as part of the Copy functionality will be working on the new Composite provider. So there will be 2 sets of Queries one on the Old Multiprovider and another on New Composite Provider. So from report perspective we would have new Reports which will function exactly the same as the old report, but only the workbooks will have impact, as workbooks are still referring to the old multiprovider. Once we delete the Old multiprovider and Queries, the workbooks will be obsolete and we need to create new Workbooks again on the new reports.

      Hope i have answered your question

      Author's profile photo Markus Hofmann
      Markus Hofmann

      Hi Srinivas,

      thank you for your blog.

      I think that this is only working for simple scenarios. If your Multiprovider has a Navigational Attribute mapping from different sources (Navigational Attributes and Not Navigational Attributes), this cannot work properly. Composite Providers cannot handle Navigational Attribute sources mixed with Infoobject sources in a Multiprovider mapping.

      Do you agree?

      best regards


      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Markus,

      You are Correct, when there are Navigational attributes from Multiple sources, this program may not not work. This is the limitation from SAP itself, may be in further version they may improve the program. We can check if the conversion works fine or not by using the Simulate option.

      Author's profile photo Christoph Sommer
      Christoph Sommer

      Thanks for sharing,

      best regards, Christoph

      Author's profile photo Karan Sehjpal
      Karan Sehjpal

      Thanks for sharing, any document on how to convert Infosets to HCPR