Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
IngoH
Active Contributor
5,182

Last week I provided a 1 hour webinar to our ASUG customers on the Integration between your SAP systems and SAP BusinessObjects 4.0. Now I would like to use that as a starting point for a more detailed blog series showing all the changes in the products related to the integration of SAP BusinessObjects 4.0 and your SAP systems like SAP NetWeaver BW and SAP ERP (yes - we will get to SAP HANA as well).

 

Now lets start this series with Crystal Reports and the connectivity towards SAP NetWeaver BW.

 

the first item you will notice is, that as part of SAP BusinessObjects 4.0 there are two versions of Crystal Reports.

 

Crystal Reports 2011, which is very similar to Crystal Reports 2008 and Crystal Reports for Enterprise 4.0 which is the new Java based Crysal Reports Designer. In regards to the data connectivity there are some important differences.

 

 

 

Crystal Reports 2011 - as shown above - is providing the connectivity like Crystal Reports 2008, means there is connectivity towards your SAP NetWeaver BW system and there is connectivity towards you SAP ERP system.

 

 

 

Crystal Reports for Enterprise 4.0 is focusing on leveraging the semantic layer and the newly recommended connectivity based on the BI Consumer Services towards SAP NetWeaver BW.

 

Now for the next couple of steps I will focus on using the recommended approach - which is the connectivity via the BI Consumer Services - with Crystal Reports for Enterprise 4.0.

 

 

Before we can connect Crystal Reports to our BEx Query we first need to establis a connection in our SAP BusinessObjects Enterprise system. For doing so we first logon to the Central Management Console (CMC).

 

 

 

In the CMC we can then navigate to the OLAP Connections and create a new Connection towards our SAP NetWeaver BW system. These OLAP Connections are not only leveraged by Crystal Reports for Enterprise 4.0 but are also leverage by other tools like Web Intelligence, SAP BusinessObjects Analysis, and so on.

 

 

 

As part of the connection details we need to provide our SAP NetWeaver BW system details so that our SAP BusinessObjects Enterprise system can establish the connection (as shown above).

 

As soon as we click on the "Connect" option in the screen we are presented with the list of available InfoProvider and BEx Queries. We can no establish a connection towards the InfoProvider or a single Query. In our example we are selecting the InfoProvider for now.

 

 

Now we are starting Crystal Reports for Enterprise 4.0 and when selecting the option to create a new report we are being asked to logon to the SAP BusinessObjects Enterprise system.

 

 

 

Because this is the first time we are using the product we first of all need to define the details for our SAP BusinessObjects system.

 

 

 

Here we need to provide the details of our server name, the port and the context of where the web services of our SAP BusinessObjects system are being depoyed (as shown above).

 

As soon as we finished that step we can logon to the SAP BusinessObjects system and are then shown with the list of connections.

 

 

Now remember that we established a connection to the InfoProvider but actually would like to connect our report to a BEx query - and this is a huge improvement in the SAP BusinessObjects 4.0 stack; as soon as the user has selected the connection the user is presented with a complete list of BEx queries for this InfoProvider available to him.

 

 

 

We then can select the BEx query and are presented with the query panel to define the data request for our report. Now as part of the SAP BusinessObjects 4.0 stack you will recognize that this query panel is shared across the tools which also means that the tools share the same meta-data coming from SAP NetWeaver BW.

 

 

In the query panel we are shown all the characteristics and keyfigures retrieved from the underlying BEx query. In addition we are shown the available hierarchies - here shown as Country Hierarchy 1.

 

We can then define our query for the report ...

 

 

... and then use the option to get a default report generated.

 

 

 

Now this was a quick rundown on how you can establish a connection towards your SAP NetWeaver BW system using Crystal Reports for Enterprise 4.0. In the next parts of this blog series we will look into the option to leverage hierarchies, conditions, and custom structures with Crystal Reports and also look at other client tools like Web Intelligence, SAP BusinessObjects Analysis as well as look at integration enhancements in areas like lifecycle management and user management.

17 Comments