Skip to Content

The DataStore object (advanced) has been available since Business Warehouse 7.4, SP8 (with SAP Note 2070577), and you are probably eager to use it for new data models and also for existing data flows. We plan to offer a conversion tool for this. But in the meantime, until this tool is available, I would like to explain how to convert existing DataStore objects and InfoCubes into advanced DataStore objects.

The idea is as follows: you take an existing DataStore object or InfoCube and model an advanced DataStore object as a copy with exactly the same InfoObjects, structure and properties. We offer a feature, which makes it easy to copy and convert the metadata. The DataStore object (advanced) can be created using existing InfoProviders as templates, which I will now describe in more detail.

Converting an existing DataStore object

Open the BW Modeling Tools in Eclipse and create a new DataStore object (advanced). In the Wizard, choose the DataStore object you want to copy under “Create from Template”.


If you would like to compare your existing DataStore object with the one you are going to create, then you can also open the DataStore object (classic) you want to copy in the Data Warehousing Workbench.

The modeling properties are automatically set according to the type of the existing DataStore object.

Groups ensure that the DataStore object (advanced) has a similar structure to your existing DataStore object. You will have the groups Key (for the InfoObjects of the semantic key), Data (for the InfoObjects of the data fields), and Key Figures (for the key figures, which were part of the data fields).  Be aware that the InfoObjects of the semantic key are not marked as key fields of the DataStore object (advanced). The grouping of the DataStore object (advanced) is a semantic grouping, which can be expanded and also changed.

The navigation attributes are not defined at this level of modeling, as the DataStore object (advanced) is focused on the data persistency. To switch on navigation attributes, you need to define a CompositeProvider on top of the DataStore object (advanced). Here, you can define such query-related properties as navigation attributes. You can switch on the navigation attributes via the context menu on a CompositeProvider characteristic in the Output tab.


The following properties are automatically preserved:

  • The “SID Generation” option is automatically set the same as in your existing DataStore object for all the InfoObjects. If you like, you can now adjust this, as in your DataStore object (advanced) this option can be set individually or each characteristic.
  • If your existing DataStore object has indexes, these indexes will also be created for your DataStore object (advanced).
  • If your existing DataStore object is write-optimized, and the property “allow duplicate records“ is not set, then an additional unique-index is created for your DataStore object (advanced), which contains all characteristics (minus the technical characteristics).

Converting an existing InfoCube

Now we do the same for an InfoCube. Open the BW Modeling Tools and create a new DataStore object  (advanced). In the Wizard, choose the InfoCube you want to copy under “Create from Template”.

The modeling properties are automatically set according to your InfoCube type.


The “Activate/Compress” property means in this case a compression. However, you don’t need to compress data to report on it. It is possible to execute a query right after loading the data.

As we have seen with the conversion of a DataStore object, groups are used to model the dimensions.

The InfoProvider properties are not stored with the DataStore object (advanced) as these properties are related to queries. Such properties as read mode and cache mode of queries are now directly modeled in the query itself.

As we have seen before, navigation attributes are not switched on in the DataStore object but in the CompositeProvider on top of the DataStore object (advanced).

Converting a MultiProvider

If your DataStore object/InfoCube had a MultiProvider on top, then you can use a tool to convert this MultiProvider into a CompositeProvider – with the option to also copy the queries. The SAP Note 2080851 explains this procedure in detail. After the MultiProvider is converted, you need to exchange the InfoProviders the CompositeProvider is composed of with the new DataStore objects (advanced).

Some tips for converting the dataflow

Now that you have copied old InfoProviders into new DataStore objects (advanced), you need to consider your dataflow. I won’t go into every detail, but I would like to give you some tips.

In the Data Warehousing Workbench, you can first copy the transformation from your old InfoCube/DataStore object and enter the name of the new DataStore object (advanced) as a target or source. Then you can copy the relevant Data transfer process (DTP). In some cases, the DTP can’t be copied and you need to create a new DTP with the DataStore object (advanced) as a target.

This graphic shows you an example of the original data flow on the left and the new dataflow with its new InfoProviders on the right:


You can even leave out the 2nd level of DataStore objects according to the LSA++ architecture, if the InfoCube was only used to allow faster query access and has a 1:1 relationship to the 1st level DataStore object.

For process chains, the same processes are used as for the DataStore object (classic). Simply create a copy of the process chain, maintain the process chain variants, and use the newly created DataStore objects.

Now I have given you a few ideas on how to convert your existing InfoCubes/DataStore objects into DataStore objects (advanced), and hopefully, this will help you to get started!

Further information:

Documentation on creating DataStore objects (advanced)

Documentation on creating CompositeProviders

Related blog post: The “advanced” DataStore Object – renovating BWs persistency layer

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Pravender Kumar

    Good Document..

    Is there any specific reason why this functionality is not available in BW workbench? Will it be available in future or only limited to BW-MT?

    Thanks for clarifying,


    1. Tanja Wingerter Post author

      The strategy for BW is to bring the heavy-weight modeling UIs to the Eclipse-world. This allows a deep integration with the HANA Studio and Modeler for all “mixed-case scenarios”.



      1. Dominik Kacprzak

        Hi Tanja,

        Are there any plans to extend eclipse functionalities with functions for export aDSO definitions, Composite definitions…to file in table form (alv, xls, csv)? It would be nice to have Export definition to file.


  2. Jan Van Ansem

    Thanks for the clear instructions Tanja.

    I do have one question: When ‘converting’ I expect the old object to be gone and replaced with a new object, including the data.

    The procedure described above looks to me like there is a new object created, which is empty, and the old object still exists….

    Do you have any suggestions how to quickly populate the new object with data – especially for inbound DSO’s connected to external systems, where the original data might no longer exist or it might be expensive to extract again.

    Hopefully the conversion tool will deal with data as well – in which case I will wait with converting the large objects until this is available.



    1. Tanja Wingerter Post author

      You are right, it is not a real conversion, it is a copy of the old object, which creates a new object without data while the old object still exists. How to  quickly populate the new object with data is quite individual and depends on how the dataflow is defined. That’s why I didn’t include it in this blog because there are too many cases to consider …

      The conversion tool will also create only a copy. I cannot tell yet if there will be the possibility to migrate the data as well in future.



  3. Samani Nishil

    Hey Tanja,

    Great blog, this is really helpful. Since it has been a few months since you posted this, I wanted to ask if there is any update on the migration tool from SAP? (i.e is it available to users yet?)



  4. Ashok Oleti

    Hi Tanja,

    This is really very helpful document. Btw, did SAP release the tool for conversion of classic DSOs or InfoCubes

    “We plan to offer a conversion tool for this. But in the meantime, until this tool is available, I would like to explain how to convert existing DataStore objects and InfoCubes into advanced DataStore objects.”


    Ashok Oleti

    1. Tanja Wingerter Post author

      The tool is not yet generally available. It is available in the release SAP BW, Edition for SAP HANA, which is in ramp-up at the moment. The release will be generally available in July.



      1. Ashok Oleti

        Thanks for quick reply Tanja… 🙂

        any idea If it will be made available for BW 7.4 on HANA?

        Could you also please provide any reference link/doc which talks about the roadmap for the tool?


        Ashok Oleti

          1. Aaron Benner

            If existing DSO’s that are being converted into aDSO’s had export datasources,

            how are the export datasources on aDSO’s created?

            e.g. for sending data to other SAP systems.

  5. Sanketh Teegala

    Hi Tanja,

    Any idea .. if the tool for conversion from Standard DS0 to advanced DSO is available now ?
    If so can you please let me know from which SP for SAP NW 7.5 the tool is available.

  6. Tanja Wingerter Post author

    To everybody who is wondering when the conversion tool will be available:

    the tool is now available with SAP BW/4HANA Starter Add-On, a SAP NetWeaver 7.5 Add-On for preparing conversion to SAP BW/4HANA (see SAP note 2246699). This transfer tool creates only copies and converts the objects without the data.

    Therefore we are working on a smarter solution – the Transfer Toolbox. As you can see on the slides

    the Transfer Toolbox (planned for Q2/2017) can be used in BW 7.5 system to convert the historical BW objects tool based.

    The Starter-Add On is the prerequisite for using these conversion tools.

    However, these tools are meant to be used for an upgrade to SAP BW/4HANA. If you want to stay on BW 7.5, we cannot recommend to use these conversion tools. Please read SAP note 2246699 carefully.


Leave a Reply