Skip to Content

Saving your content & data from the BW on HANA trial system


I know many of you have been using the BW on HANA trial offer right from day 1 of the offering.  This means you are close to the end of the 30 day trial period.  And as you are all aware these systems cannot be extended beyond the 30 day trial period.  Once the clock runs down to 00:00, there is no turning back.  Lot of you have built quite a bit of content and could potentially have lot of data in these systems.  The ‘Million dollar’ question is how you can save this content & data that you have created.  Potentially bring up another ’30 day trial system’ and reuse it in there without losing any valuable time & effort you have put into creating this content.

I created this 2 part guide will help you preserve you content and data.

Part 1 : This part will walk you through the steps of getting your content out of the system.

  1. Login to the BW system, go to the Data Warehousing Workbench and select ‘Transport Connection’ on the left hand pane.
    Ensure ‘Object Types’ is selected in the list.
  2. It’s a good idea to separate out the different types of objects into different transports. There is no hard & fast rule that says you have to do so, but doing so will make things much more manageable. For example bunch the following objects into individual transport requests:
    - Info-objects & corresponding Info-areas
    - Source System, Datasources
    - Data targets (DSO’s, Cubes, Open Hub Destinations, Info-areas, etc…), Transformations
    - DTP’s, Info-packages, Process chains, etc…
    - Queries, Query objects (Restricted Key-figures, Calculated Key-figures, Variables, Structures, etc…)
    - Analysis authorization objects, roles, etc…
    - Any additional objects like ABAP Programs, Function modules, Class, CMOD enhancements, etc…
    - System configurations that you might have changed like RZ10 parameters, etc…
    Basically any objects that you have manually created in the system.

  3. Once you have created all the necessary transports go to ‘Transport Organizer’ (transaction SE09).

    Click display to look up all the transports you have created to collect all your objects.

  4. Most of you objects should show up under ‘Workbench’ request type.

    Depending on the type of objects some might fall under the ‘Customizing’ request type.
  5. Release each individual task and request one by one.
    1. First click on the individual task of a request and click ‘Release Directly (F9)’ button.

      Repeat this step until all the tasks of a single request have been released.

    2. Next release the request itself.

    3. Once successfully released you should see the request under a new folder called ‘Released’.

  6. Repeat step 5 to release as many request (if you followed step 2 to create multiple requests) as you have.  After all the requests have been released successfully, the system creates transport files at the OS level which you need.

    You can go directly to the Linux OS (where HANA & BW have been installed) in the ’30 day Trial’ offer or you can use any tool (I like WinSCP, free SFTP and FTP client for Windows) which you can install in the Windows box (where BI server & client tools are installed) which allows you to get the Linux file system.

    Locate the /usr/sap/trns directory.  The two main folders are /cofiles & /data. You will need to locate all the files (one for each transport request that you released in the BW system). Copy them over to your local system.

    As you noticed the transport number in the BW system was called VBWK900017 and the corresponding transport file at the OS level is R900017.VBW (for the datafile) & K900017.VBW (for the cofiles).

  7. At this point you have successfully exported out your content from the BW system.  Next step is to get these transport files (and the content it hold) into another BW system (of course with similar release / SP, basically into another BW on HANA 30-day trial system).
    For this you login to the OS level of the target BW system and copy the datafile & cofile to the corresponding directories in the new system (K*.VBW goes into the “/usr/sap/trans/cofiles” directory & R*.VBW goes in the “/usr/sap/trans/data” directory).

  8. Once the files are placed in the directory in the new target system.  Login to the target BW system using the SAP GUI and go to ‘Transport Management System’ (transaction STMS).

         Click ‘Import Overview’.

  9. In the next screen double click on VBW (the system into which you would like to import your content).

  10. In the following screen, use the menu  Extras -> Other Requests -> Add

  11. In the popup screen use the value help to look up the transport file that you placed at the OS level (basically lookup the files from cofiles & data directory).

    Once you locate the file, select it and hit ok.

    If you are asked if the transport request should be added to the import queue, select yes.

  12. This should add the transport request to the import queue.  At this point the content is ready to be imported into the target BW system.

    Repeat step 10 & 11 to add every transport request that you created in step 2 to this queue.

  13. The final step is to import every request.  Make sure you import the requests in the right order.  This is to ensure any dependencies between BW objects are taken into consideration.
    As an example if you collected all the objects in the BW system and grouped them into transport requests as mentioned in step 2, then you will need to import the requests in the same order as it was created.

  14. To start the actual import process, click the transport request in the queue and select ‘Import request’
  15. In the following popup screen, enter ‘001’ (the client used to login to the BW system) in the target client field.  Use the default values for the ‘Date’ tab & ‘Execution’ tab.

    Under the ‘Options’ tab select the following values.

    In the following popup screen select ‘Yes’ to accept the options.

  16. Ensure the import process of the transport was successful.

    You can check the logs to confirm the import was successful.
  17. Repeat steps 14 through 16 to import all your transport requests (in the correct order) to import all your content in the BW system.

  18. Now in the Data Warehousing Workbench you should be able to see all your content just like in the previous BW system.

The above steps will allow you to move your content from one BW trail system to another BW trial system.  Also you can use this procedure to move your content from an on-premise system to this BW on HANA trail system without having to manually create content.

  If you used flat file to load data to the BW on HANA trail system and would like to continue to use those files to load data into the new target system, you do not need part 2 of this guide.

Part 2 : This part will walk you through the steps of getting your data out of the system.

The above procedure can only be used to move content from one system to another.  In addition to content if you would like to also move your data out of the system, you can use ‘Open Hub’ functionality.  This mechanism allows you to move data out of any data target (especially if you want to extract data out of targets where data has gone through multiple transformations) from the BW on HANA trial system.

  1. Go to the data warehousing workbench.
  2. Select Open Hub Destination from the left hand pane.

  3. Navigate to a specific info-area
  4. Right click and select ‘Create Open Hub Destination…’
  5. In the popup screen provide the following values:
    • Open Hub Destination = <Unique Technical Name for the open hub destination>
    • Description = <Description for Open Hub destination>
    • Info area = <Info-area where the Open Hub destination will reside>
    • Object type = <Fields used to build the Open Hub destination is derived from this Template>
    • Name = <Technical name of the template object>
    • Do not select ‘Create Transformation and DTP’

      Click Ok.
  6. The next screen displays few default values.  These can be changed based on your requirement.
    • Destination Type = Database Table.  But this can be changed to Flat File or Third Part tools.
    • Deleting Data from Table = If exporting to table, you can choose to empty the table before the next export is started.
    • Technical or Semantic key = you can choose to use the key of your source or create a new technical key for export to table.
    • If export type is database table, a table name is provided by the system.

      If export type is flat file, you have to specify the server name as to where the file gets exported and the file name for export.


  7. The second tab ‘Field Def.’ is used to specify which fields from your source you are planning to export.
  8. Click the Check button on the top tool bar to ensure the settings are all correct.
  9. Now click the activate button to save and activate the Open Hub destination.
  10. Hit the Esc button once or the green left arrow to leave the open hub destination screen.
  11. Next step is to create a transformation to link the source DSO object to this open hub destination.
    For this right click on the open hub destination just create and select ‘Create Transformation…’

  12. On the popup screen retain the default value for ‘Target of the Transformation’ section.  For the ‘Source of the Transformation’ select the appropriate object type and also provide the corresponding object technical name.
  13. In the next screen the system displays the mapping between the source DSO object and the target open hub destination. Click on the activate button to save and activate the default transformation.
  14. Confirm that you receive a success message at the bottom left hand corner.
  15. Hit the Esc button once or the green left arrow to leave the transformation screen.
  16. Next step is to create a Data Transfer Process (DTP) which is used to trigger the extraction of data from the source to Open Hub destination.  For this right click on the Open Hub Destination and select ‘Create Data Transfer Process…’

  17. In the popup screen accept the default values.  These values are generated based on the values provide for creating the transformation from step 12.

  18. In the following screen the system displays the Extraction tab.
    The default value for extraction mode is delta.

  19. Click the activate button to save and activate this DTP.|
  20. Confirm that you receive a success message at the bottom left hand corner of the screen.
  21. Under the Execute tab click the execute button to start the process of moving the data out of the target to the flat file or DB table (depending on what was chosen in step 6).

Help documentation

Transport Management System

Transporting BW objects

Change request (Workbench Requests & Customizing requests)

     There should be no need to have to recreate the content every time a new BW on HANA trail system is created.  Once the content & data are created and setup correctly, using this guide you can take your content & any data that you have used to demonstrate the functionality with you.  Hope this guide will help you demonstrate the new feature functionality of BW on HANA system and continue to learn way beyond the 30 day trial period.

Former Member