h3. Introduction In my last post (Do you want to query SAP BW using SQL?), I discussed about the new Data Federator SQL connector for SAP BW. The performances, the architecture and its relational capabilities are extremely well aligned with the Universes (Business Objects semantic layer) and our ad-hoc Web Intelligence reporting tools. In this post, I will explain the step required to create a DF project pointing to an SAP BW Infoprovider (*Infocube*, *Multiprovider* or a *DSO*), generate the associated relational Universe and how to create a WebI report using this Universe. h3. Data Federator project Open Data Federator Designer and create a DF project (Webinar in our case). In this project, click on “*Add datasource*” And select the SAP BW source Enter your SAP BW instance connection parameters Then click on “*Get gateway parameters*” button, to retrieve the SAP gateway parameters. Once the gateway parameters have been retrieved, you can click on the “*target*” icon to list the Infoproviders available in your BW instance. Select the one you want to connect to (*I0D_DX_C03* InfoCube in my case) At this stage, the Infoprovider is exposed as a star schema containing 3 type of tables: ** Master Data tables, prefixed by “D” (Dimension) ** Text tables, prefixed by “T” (Text) Click on “*Make final*” to finalize the connection Now, the Webinar DF project has to be deployed in the Data Federator Query Server. The DF Query Server is the component in charge of the queries optimizations and executions. To do that, you have to deploy the current project into a DF Query Server catalog. 0.1. Click on “*Deploy*” in project toolbar0.1. Enter a name for the deployed project 0.2. In the “*Deployment address*” section, reuse ‘sysadmin’ for password0.1. Keep the default values for other parameters 0.2. Click on “*OK*” At this stage, the Webinar project has been deployed in the Query Server */WB* catalog and can be queried using SQL.Start the “*Quick Design Wizard*” and check the “*Click here to choose strategies*” option Define a new JDBC connection to to point to the Data Federator Query Server */WB* catalog. Click on Next 0.1. Enter a connection name for example “*SAPBW*”0.1. Select *Business Objects > Data Federator Server > JDBC Drivers*0.1. Click on *Next* Enter the Data Federator Query Server credentials for this connection. Note that: 0.1. The Query Server credentials (*sysadmin*/*sysadmin*)0.1. The hostname or the IP address of the machine running the DF Query Server (cdi in our case) 0.2. The name of the catalog used during the DF project deployment post fixed by “/*sources*”. For instance, “*WB/sources*” in our case 0.1. Test the connection by clicking on “*Test Connection*”0.1. Click on “*Next*”0.1. Click on “*Finish*”Enter a new Universe name and select the Universe Connection pointing to DF(SAPBW) Select the “*Data Federator Strategy*” strategy for the objects and joins Click on “*Next*” Select the generated Classes and Objects (select the root node of the tree view) then click on “*Add >>*” Click on “*Next*” Click on “*Finish*” to generate a relational SAP BW Universe automatically. You end up with a ready to use Universe. The star schema is visible on the right as well as the aliases to avoid the join loops. The business layer (tree view on the left) has been generated for you leveraging the metadata stored in SAP BW.Of course, you can customize the Universe if required then Export it to the CMS in order to create WebI documents. At this stage, you can start Web Intelligence to create your own queries and reports. In WebI start the Query Panel to define your query using the business objects available in the Universe we created. For instance, I created the following query to compare sales and billed plans. By clicking on “*SQL*” icon of the Query Panel, you can have a look to the generated SQL Click on “*Run Query*” to execute the query and create a default report layout. In my case, I updated the layout to create sections, breaks and add extra calculations including a ratio between billed and sales plan. In addition, I use the multi-block capability of WebI to associate graph with my table.