End-to-End Scenarios With Xcelsius 2008

Transcription

1 End-to-End Scenarios With Xcelsius 2008 Applies to: BusinessObjects Enterprise XI Release 3.0, Crystal Reports 2008, Xcelsius 2008, Live Office, Query-as-a- Web Service. Summary This document outlines the required steps to leverage Crystal Reports, Live Office, OLAP Universes and Query as a Web Service to connect to SAP systems and build Xcelsius dashboards. Author Ingo Hilgefort Company: Business Objects, an SAP company Created on: 5 September 2008 Author Bio Ingo Hilgefort started in 1999 with Seagate Software / Crystal Decisions as a Trainer and Consultant. He moved to Walldorf for Crystal Decisions by end of 2000 and worked with the SAP BI Development team on integrating Crystal Reports with SAP BW. He then relocated to Vancouver in the year 2004 and worked as Product Manager / Program Manager (Engineering) on the integration of Business Objects products with SAP products. He is now focusing on the topic of Embedded Analytics for the SAP Solutions SAP AG 1

2 Table of Contents Configuration of SAP Authentication...3 Enable SAP Authentication...4 Configure Global Options for the SAP Authentication...7 Import SAP Users and Roles...10 Xcelsius with Crystal Reports and Live Office...13 Crystal Reports and SAP BW...13 Crystal Reports and SAP BW Query Elements...13 Live Office and SAP data sources...25 Using Crystal Reports objects in Live Office...25 Xcelsius and Live Office...33 Creating an Xcelsius Dashboard with Live Office...33 Xcelsius and Universe and Query as a WebService (QaaWS)...40 Creating a Simple OLAP Universe...41 SAP BW OLAP Universes...41 Creating a Query as a WebService (QaaWS)...59 Xcelsius and QaaWS...65 Xcelsius and QaaWS...65 SAP Connectivity Overview...70 SAP Connectivity Options...71 SAP Connectivity for Crystal Reports...71 SAP Connectivity for Web Intelligence...72 SAP Connectivity for Query as a Web Service (QaaWS)...73 BW Queries and BW Cubes. SAP Connectivity for Live Office...73 SAP Connectivity for Live Office...74 SAP Connectivity for Xcelsius...75 Copyright SAP AG 2

3 Configuration of SAP Authentication In this unit, you will learn about the necessary steps to configure SAP authentication for BusinessObjects Enterprise. After completing this unit, you will be able to: Enable SAP authentication Configure global options for the SAP authentication Import SAP users and SAP roles to BusinessObjects Enterprise 2008 SAP AG 3

4 Enable SAP Authentication The SAP authentication allows the administrator to leverage the SAP users and roles and it allows the end user to leverage functionality like single-sign-on with BusinessObjects Enterprise. To enable the SAP authentication 1. Log onto the Central Management Console. 2. Navigate to Authentication SAP AG 4

5 3. Double-Click SAP. 4. Enter the system ID and client number from the SAP system into the fields System and Client. 5. Enter either a combination of Message Server and Logon Group or Application Server and System Number into the corresponding fields. Note: If you configured the SAP landscape to leverage load balancing you need to enter the details on message server and logon group, otherwise you can use a particular application server. 6. Enter Username, Password, and Language. Note: The used SAP account needs to be configured for the SAP authentication plug-in. The exact needed authorizations are listed in the Installation Guide of the BusinessObjects Integration Kit for SAP. 7. Click Update. Note: The system ID and client number are combined and entered as an entry in the list of logical systems SAP AG 5

6 Activity: Enable SAP Authentication Objective Enable the SAP authentication for the SAP server Scenario You are an administrator and need to enable the SAP authentication for the BusinessObjects Enterprise system. Instructions 1. Log onto the Central Management Console. 2. Navigate to the SAP authentication. 3. Create a new entitlement system for the SAP BW system. 4. Verify the SAP authentication by logging onto BusinessObjects Enterprise using your SAP account. Note: Why are you not able to log onto BusinessObjects Enterprise? 2008 SAP AG 6

7 Configure Global Options for the SAP Authentication The SAP authentication includes a number of options that you can customize when integrating BusinessObjects Enterprise with your SAP systems. For instance, you can enable/disable SAP authentication and/or configure BusinessObjects Enterprise to temporarily disable SAP authentication for SAP systems when they become unavailable. To configure the SAP authentication options 1. Log onto the Central Management Console. 2. Navigate to Authentication. 3. Double-click SAP. 4. Navigate to the Options tab. Enable SAP Authentication Clear this check box if you want to disable SAP authentication completely. (To disable SAP authentication for specific SAP systems, select the system s Disabled check box on the Entitlement Systems tab.) Max failed entitlement system accesses and Keep entitlement system disabled [seconds] Use these fields together to configure how BusinessObjects Enterprise handles SAP entitlement systems that are temporarily unavailable. BusinessObjects Enterprise uses these settings to determine when to stop communicating with an SAP system that is unavailable, and when it should resume communication with that system. In the Max failed entitlement system accesses field, type the number of times that BusinessObjects Enterprise should re-attempt contacting an SAP system to fulfill authentication requests. Setting the value to -1 allows BusinessObjects Enterprise to attempt to contact the entitlement system an unlimited number of times before ceasing. Setting the value to 0 limits BusinessObjects Enterprise to making one attempt to contact the entitlement system. In the Keep entitlement system disabled [seconds] field, type the number of seconds that BusinessObjects Enterprise should wait before resuming attempts to authenticate users against the SAP system. For example, if you type 3 for Max failed entitlement system accesses, BusinessObjects Enterprise allows a maximum of 3 failed attempts to authenticate users against any particular 2008 SAP AG 7

8 SAP system; the fourth failed attempt results in BusinessObjects Enterprise ceasing its attempts to authenticate users against that system for the amount of time specified by Keep entitlement system disabled [seconds]. Max concurrent connections per system Use this field to specify how many connections you want to keep open to your SAP system at the same time. For example, if you type 2 in this field, BusinessObjects Enterprise keeps 2 separate connections open to SAP. Number of uses per connection Use this field to specify how many logons you want to allow to the SAP system per connection. For example, if you specified 2 for Max concurrent connections per system and 3 for Number of uses per connection, once there has been 3 uses on one connection, BusinessObjects Enterprise will close that connection and restart it. Note: Number of uses refers to actual transactions (or RFC calls) towards the SAP system. Content folder root Use this field to specify where you want BusinessObjects Enterprise to begin replicating the BW folder structure in the CMC and InfoView. To change this value, you must change it both in the CMC and the Content Administration Workbench. This value is relevant for the publishing integration with Crystal Reports. Automatically import users Select this check box if you want BusinessObjects Enterprise to create user accounts and user folders for all role members when you actually import the roles. Clear the check box to have BusinessObjects Enterprise create user accounts and user folders dynamically, when users log on for the first time with valid SAP credentials. Concurrent users / Named Users Use this option to specify if new user accounts are configured to use concurrent user licenses or named user licenses. Default system In this list, select the SAP entitlement system that BusinessObjects Enterprise uses as the default system (that is, the system that is contacted to authenticate users who attempt to log on with SAP credentials but without specifying a particular SAP system). 5. Configure the options as required. 6. Click Update SAP AG 8

9 Activity: Configure SAP Authentication Options Objective Configure the SAP authentication options Scenario You are an administrator and need to configure the SAP authentication options for the BusinessObjects Enterprise system. Instructions 1. Log onto the Central Management Console. 2. Navigate to the SAP authentication. 3. Navigate to the Options tab. 4. Configure the options to import SAP users as concurrent users. 5. Define the SAP BW entitlement system from the previous activity as the default system. 6. Save the changes SAP AG 9

10 Import SAP Users and Roles By importing SAP roles into BusinessObjects Enterprise, you allow role members to log onto BusinessObjects Enterprise with their usual SAP credentials. In addition, single-sign-on is enabled so that SAP users can be logged onto BusinessObjects Enterprise automatically when they access reports from within the SAP GUI or an SAP Enterprise Portal. For each role that is imported BusinessObjects Enterprise generates a user group. Each group is named with the following naming convention: [SAP system ID] ~ [SAP client [SAP role] For example: CIM~003@BOBJ_TRAIN_ROLE_01 You can view the new groups in the groups management area of the CMC. You can also use these groups to define object security within BusinessObjects Enterprise. To import SAP roles to BusinessObjects Enterprise 1. Log onto the Central Management Console. 2. Navigate to Authentication. 3. Double-click SAP. 4. Navigate to the Role Import tab SAP AG 10

11 5. Select the logical system for the SAP server. 6. Select the roles from the list of available roles. 7. Click Add >. 8. Click Update. Note: After the import of the SAP roles has been completed, users that are members of these SAP roles are able to log on with their SAP account to BusinessObjects Enterprise SAP AG 11

12 Activity: Import SAP Roles to BusinessObjects Enterprise Objective Import SAP roles to BusinessObjects Enterprise Scenario You are an administrator and need to import SAP roles to BusinessObjects Enterprise so that members of these roles can log onto BusinessObjects Enterprise with their SAP credentials. Instructions 1. Log onto the Central Management Console. 2. Import the following SAP roles from SAP BW to BusinessObjects Enterprise: BUSINESSOBJECTS_PM_TECHED08 3. Add the role to the Administrator role in the CMC. 4. Verify the import by logging onto BusinessObjects Enterprise with users from the imported roles SAP AG 12

13 Xcelsius with Crystal Reports and Live Office This lesson provides you with an overview of using Xcelsius in combination with Live Office to retrieve SAP data. In this lesson, you will learn about: Creating a simple Crystal Report on top of SAP Connecting Live Office to SAP data sources Creating an Xcelsius dashboard using Live Office as a data source Crystal Reports and SAP BW This lesson provides you with an overview of the connectivity for Crystal Reports against SAP BW. In this lesson, you will learn about: Understanding SAP BW metadata in Crystal Reports Crystal Reports and SAP BW Query Elements When connecting to an SAP BW query with Crystal Reports the underlying metadata from the SAP BW query is leveraged and matched to Crystal Reports elements. The table below shows how SAP BW metadata is used in Crystal Reports. BW Query element Characteristic Hierarchy Keyfigure Calculated Keyfigure Restricted Keyfigure Filter Navigational attribute Display attribute SAP variables Crystal Reports designer element Separate fields for key and description per characteristic. Fields representing a parent-child relationship. Measure element in a grouping called Keyfigure. Each Keyfigure can have up to three elements: numeric value, unit, and formatted value. Measure element in the folder Keyfigure. (Information about the details of the calculated keyfigure is not available in Crystal Reports.) Measure element in the folder Keyfigure (Information about the details of the restricted keyfigure is not available in Crystal Reports.) Filters will be applied to the underlying query but are not visible in the Crystal Reports designer. Separate fields for key and description per navigational attribute. Each display attribute becomes one field in the field explorer. The display attributes are grouped together with the actual characteristic. Parameters SAP AG 13

14 Dimension and Characteristics The image shows an SAP BW query in the BEx Query Designer. The rows of this query include characteristics and the columns several keyfigures. On the left side, the actual cube structure is shown with the cube dimensions (not to be confused with characteristics) SAP AG 14

15 Building a Crystal Report on top of such an SAP BW query will result in the following elements: Each characteristic in the query will result in an element in the field explorer with a key and a description item (Example: Product Key and Product Medium Name). In addition each characteristic will also generate a Node ID and a Parent Node ID which can be used for hierarchical reporting. Each characteristic will also generate a Member Unique Name field which represents the technical key value SAP AG 15

16 Display Attributes and Navigational Attributes Display attributes are InfoObjects which are logically assigned or subordinated to a characteristic. For example: The characteristic customer has a display attribute called Industry Keys Characteristics can be defined as navigational attributes in the BW cube, which then makes these attributes available for navigational purposes in the reporting tools. Navigational attributes are treated identically to a characteristic. The following screen shows an SAP BW query in the BEx Query Designer SAP AG 16

17 Building a Crystal Report object on top of such an SAP BW query will result in the following elements: Each characteristic in the query will result in an element in the field explorer with a key and a description field. Each navigational attribute in the query will result in an element in the field explorer with a key and a description item Each display attribute will create an element in the field explorer underneath the corresponding characteristic (for example, Customer with several display attributes). Crystal Reports will include all available display attributes for the characteristic and not only the display attributes that are included in the SAP BW query SAP AG 17

18 Keyfigures, Units, and Currencies Each keyfigure used in an SAP BW query can have up to three elements: Numeric value of the keyfigure. Unit or currency information. Formatted value, representing the user-specific formatting. The image shows the result of two keyfigures in Crystal Reports: Each keyfigure is represented with a field in a group called Key Figures. In the case the keyfigure is configured in SAP BW with a unit, an additional field will be added representing the unit information. The Formatted Value represents the numeric value formatted as a string value following the user-specific formatting settings SAP AG 18

19 Hierarchies Hierarchies can be activated for characteristics in the BEx Query Designer and offer the user the capability to navigate along a hierarchical structure. The image shows the field explorer in Crystal Reports based on an SAP BW query with a hierarchy. A hierarchy results in a parent-child relationship SAP AG 19

20 Using the Database Explorer Crystal Reports lists the two SAP BW query connectivity in the standard Database Explorer. To create a new report with the Database Explorer 1. Start Crystal Reports Designer (Start > Programs > Crystal Reports 2008 > Crystal Reports 2008). 2. Select the menu File > New > Standard Report. 3. Double-click on Create New Connection. Note: The SAP connectivity is listed as part of all available connectivity sorted alphabetically. 4. Double-click SAP BW MDX Query. Note: The list of SAP server entries is derived from SAP Logon. 5. Select the SAP server from the list of available SAP systems SAP AG 20

21 6. Click Next. 7. Enter Client, Username, and Password. 8. Click Finish. 9. Click Finish SAP AG 21

22 10. Right-click the SAP server entry. 11. Select the menu entry Options. 12. Enter the filter in the field Table name LIKE. 13. Click OK. 14. Double-click the QC (Queries) entry. 15. Select the SAP BW query from the list of available queries 16. Click the right arrow to move the query to the list of selected queries SAP AG 22

23 17. Click Next. 18. Select the needed fields and click the right arrow. 19. Click Next. 20. If required, define grouping by selecting the field and clicking the right arrow. 21. Click Next. 22. If required, define a record selection. 23. Click Next. 24. Click Finish SAP AG 23

24 Activity: Create a New Report Against a Simple SAP BW Query Objective Creating a new report against an SAP BW query Scenario You are a report designer and need to create a Crystal Report object on top of an SAP BW query. Instructions 1. Start Crystal Reports. 2. Create a new report using the SAP BW MDX query connectivity. 3. Use the BI Query BusinessObjects Community Day Query 3 (technical name: DALSEGNO/BUSINESSOBJECTS_QRY_03). 4. Use the following fields in your report: Product Medium Name Keyfigure January February March April May June July August September October November December 5. Preview the report. 6. Save the report into the folder for your SAP reports on your BusinessObjects Enterprise system. 7. View the report with the SAP account in InfoView SAP AG 24

25 Live Office and SAP data sources In this unit, you will learn about how you can use Live Office to connect to SAP data sources. After completing this unit, you will be able to: Create a Live Office document with SAP data sources Using Crystal Reports objects in Live Office After creating the Crystal Reports document, you can now build the Live Office document leveraging the existing Crystal Report object. To create a new Live Office document: 1. Start Microsoft Excel. 2. Select the menu Live Office > Options. 3. Navigate to the Enterprise tab SAP AG 25

26 4. Set the option Use specified logon criteria. 5. Enter the web service URL following the syntax: 6. Select SAP as Authentication. 7. Click OK SAP AG 26

27 8. Select the menu Live Office > Insert > Crystal Reports content. 9. Use your SAP Credentials in the format [System ID]~[Client]/[Username] to authenticate (example: CIM~003/i819882) 10. Select the previously created report from BusinessObjects Enterprise SAP AG 27

28 11. Click Next. 12. Click Switch to Fields SAP AG 28

29 13. Double-click the fields to add them to the list of Selected Fields. 14. Click Next. 15. Click Next. 16. Click Finish SAP AG 29

30 17. Select the menu Live Office > Properties for all objects. 18. Navigate to the tab Prompts. 19. Select the prompt and click Parameter Values SAP AG 30

31 20. Select the option Choose Excel data range and select a cell on a separate sheet in your document. Note: This will be used to provide input to the parameter. 21. Select the menu Live Office > Publish to BusinessObjects Enterprise > Save to BusinessObjects Enterprise. 22. Enter the File name. 23. Click Save. 24. Close Microsoft Excel SAP AG 31

32 Activity: Create a New Live Office Document Based on Crystal Reports Objective To build a new Live Office document using Crystal Reports as a source Scenario You are a report designer creating an Xcelsius dashboard and building the underlying Crystal Report and Live Office documents. Instructions 1. Create a new Live Office document using the previously created Crystal Report document as a source. 2. Save the Live Office document to BusinessObjects Enterprise SAP AG 32

33 Xcelsius and Live Office In this unit, you will learn how you can use Xcelsius to connect to a Live Office document with SAP data sources. After completing this unit, you will be able to: Use Xcelsius with Live Office Creating an Xcelsius Dashboard with Live Office You created a Crystal Report document retrieving data from SAP BW and used Live Office to show the data in Microsoft Excel. As a next step, you will use the Live Office document as a source for the Xcelsius dashboard. To create the Xcelsius dashboard 1. Start Xcelsius Designer (Start > Programs > Xcelsius > Xcelsius Designer). 2. Select the menu Data > Import from Enterprise. 3. Authenticate against the BusinessObjects Enterprise system. 4. Click OK SAP AG 33

34 5. Select the Live Office document you created previously. 6. Click Open. 7. Select the menu Data > Connections. 8. Click Add SAP AG 34

35 9. Select Live Office Connections. 10. Select the newly created connection SAP AG 35

36 11. Replace the entry <webserver> with your webserver name. 12. Click the Usage tab. 13. Set the Refresh on Load property. 14. Close the Data Manager. 15. Drag and drop a Stacked Bar Chart component onto the Xcelsius canvas. 16. Double-click the Stacked Bar Chart to open the properties. 17. Click on the icon next to the Data Values SAP AG 36

37 18. Mark the complete range in for the values and select the option Data in rows 19. Click OK. 20. Click Preview. Note: Because you are not authenticated against BusinessObjects Enterprise at this time a logon mask will come up and ask for BusinessObjects Enterprise credentials. Use the SAP Authentication and the SAP credentials to leverage Single-Sign-On from the Xcelsius Dashboard to Live Office and Crystal Reports SAP AG 37

38 21. Select the menu File > Export > BusinessObjects Platform. Note: When exporting to the BusinessObjects Platform the actual Xcelsius document is being stored on the platform. When selecting the menu File > Save as the design of the Xcelsius design document is being stored to BusinessObjects Enterprise. 22. Select a folder on your BusinessObjects Enterprise system. 23. Enter a file name. 24. Click Save. 25. View the Xcelsius dashboard in InfoView using the SAP authentication SAP AG 38

39 Activity: Create a New Xcelsius dashboard with Live Office Objective To build a new Xcelsius dashboard using Live Office as a source Scenario You are a report designer creating an Xcelsius dashboard and building the underlying Crystal Report and Live Office documents. Instructions 1. Create a new Xcelsius dashboard using the previously created Live Office document as a source. 2. Show a Stacked Bar Chart with order mount per region. 3. Configure the Live Office connectivity to refresh on each load. 4. Save the Xcelsius file to BusinessObjects Enterprise. 5. View the dashboard with Single-Sign-On in InfoView SAP AG 39

40 Xcelsius and Universe and Query as a WebService (QaaWS) This lesson provides you with an overview of using Xcelsius in combination with OLAP Universes and Query as a Web Service. In this lesson, you will learn about: Creating a simple OLAP Universe Creating a QaaWS on top of the OLAP Universe Creating a Xcelsius dashboard with QaaWS as a source 2008 SAP AG 40

41 Creating a Simple OLAP Universe In this unit, you will learn about OLAP Universes and how the meta-data from SAP BW is leveraged inside the OLAP Universes. After completing this unit, you will be able to: Describe the elements of SAP BW OLAP Universes SAP BW OLAP Universes The following table shows a list of SAP BW query elements and how these elements are used in an OLAP Universe. BW Query element Cube Dimension Characteristic (incl. Time and Unit) Hierarchy Keyfigure Calculated keyfigure Restricted keyfigure Navigational attribute Display attribute Query filter SAP variables Custom structure OLAP Universe element Class A class with dimension and detail objects (detail objects for key and description). A class containing a dimension and detail objects for each hierarchy level. Measure element in a class named Keyfigures. Measure element in a class named Keyfigures (Information about the calculation is not available). Measure element in a class named Keyfigures (Information about the restriction is not available). A class with dimension and detail objects (detail objects for key and description). Each display attribute becomes a detail object underneath the related dimension object. Filters will be applied to the underlying query but are not visible in OLAP Universe. Query filter as predefined object which can be optional or mandatory. Dimension object 2008 SAP AG 41

42 Dimension and Characteristics The screenshot below shows an SAP BW query in the BEx Query Designer. The Rows area of this query includes several characteristics and the Columns area includes several keyfigures. On the left side, the actual cube structure is shown with the cube dimensions (not to be confused with characteristics). In the image you can identify one dimension and four characteristics. The dimension is Customer (technical name Z_BOBJ1) and the characteristics are City, Country, Customer, and Region SAP AG 42

43 Building an OLAP Universe on top of such an SAP BW query results in the following elements: The cube dimension from SAP BW results in a class in the OLAP Universe (for example, dimension Customer). Each characteristic in the query results in a class with dimension and detail objects. Level 00 objects represent the aggregated view on this characteristic representing the All member from the underlying cube SAP AG 43

44 Display Attributes and Navigational Attributes Display attributes are InfoObjects which are logically assigned or subordinated to a characteristic. For example: The characteristic customer has two attributes: Phone number Fax number Characteristics can be defined as navigational attributes in the BW cube, which then makes these attributes available for navigational purposes in the reporting tools. Navigational attributes are treated identically to a characteristic. The following screen shows an SAP BW query in the BEx Query Designer. The row structure includes a characteristic Customer with four display attributes (Geographical Height, Postal Code, Sector Code, and Area Code) SAP AG 44

45 In addition the BW query contains three navigational attributes in the rows: Regional Code, Postal Code, and Area Code. Note: A navigational attribute can easily be identified by the double underscore ( ) in the technical name of the navigational attribute. Building an OLAP Universe on top of such an SAP BW query results in the following elements: The cube dimension from SAP BW results in a class in the OLAP Universe (for example, dimension Customer not to confuse with the characteristic Customer). Each characteristic in the query results in a class with dimension and detail objects. Level 00 objects represent the aggregated view on this characteristic representing the All member from the underlying cube (characteristic Customer resulting in a class Customer2 with dimension L00 Customer and L01 Customer). Each navigational attribute in the query results in a class with dimension and details objects (Navigational attribute Postal Code resulting in a class Postal Code with dimension L00 Postal Code and L01 Postal Code) SAP AG 45

46 The image shows the display attributes from characteristic Customer and how these display attributes are treated in an OLAP Universe. Each display attribute for the characteristic results in a detail object for the corresponding dimension objects in the universe. Note: The OLAP Universe includes all available display attributes for the characteristic and not only uses the display attributes that are included in the SAP BW query SAP AG 46

47 Keyfigures, Units and Currencies Each keyfigure used in an SAP BW query can have up to three different sets of information: Numeric value of the keyfigure. Unit or Currency information. Formatted value, representing the user-specific formatting. The image shows the result of two keyfigures in the OLAP Universe. Each key figure is represented with a measure object in a class Key Figures. In the case the keyfigure is configured in SAP BW with a unit, an additional dimension object will be added representing the unit information. The formatted value represents the numeric value formatted as a string value, following the user-specific formatting settings SAP AG 47

48 Hierarchies Hierarchies can be activated for characteristics in the BEx Query Designer tool and offer the user the capability to navigate along a hierarchical structure. The image shows an OLAP Universe class Sales with a subclass Sales Person. For the characteristic Sales Person a hierarchy has been activated and therefore the OLAP Universe has generated the number of levels required to leverage the complete hierarchy in the universe. Each level of a hierarchy will result in a dimension object SAP AG 48

49 To create a new OLAP Universe 1. Start the Universe Designer (Start > Programs > BusinessObjects XI Release 3 > BusinessObjects Enterprise > Designer). 2. Enter the User Name and Password. 3. Click OK. 4. Select the menu File > New SAP AG 49

50 5. Click New to create a new connection. 6. Click Next SAP AG 50

51 7. Select SAP Business Warehouse 3.x from the list. 8. Enter a Connection Name. 9. Click Next. 10. Enter the User name, Password, and Language SAP AG 51

52 11. Enter the Client, Application Server, and System Number based on the SAP server details. Note: The connection dialog allows you to select between an Application server and a Message server connection. 12. Set the Authentication Mode to Use Single Sign On when refreshing reports at view time. Note: For this activity we will leave it to Use specified username and password and will change this after we created the web service on top of the Universe. Note: Using single-sign-on in combination with an SAP system requires the SAP authentication to be configured for the SAP system in the Central Management Console of BusinessObjects Enterprise SAP AG 52

53 13. Click Next. 14. Open the list of available cubes by clicking the plus sign next to OLAP Cubes SAP AG 53

54 15. Navigate to the required cube. 16. Open the list of available queries for the selected cube by clicking the plus sign next to the cube SAP AG 54

55 17. Select the required query and click Next. 18. Click Finish. 19. Enter a name for the Universe into the field Name SAP AG 55

56 20. Navigate to the Controls tab. 21. Uncheck all Query Limits. 22. Click OK. 23. Select the menu File > Export. Note: The Universe needs to be saved before it can be exported SAP AG 56

57 24. Click Save. 25. Select a Domain. 26. Select the Groups that should be assigned to the Universe. 27. Click OK. 28. Click OK SAP AG 57

58 Activity: Create a New OLAP Universe Objectives Create a new OLAP Universe Create a new Web Intelligence report using the OLAP Universe Scenario You are a report designer and need to create a new Web Intelligence report on top of a new OLAP Universe. Instructions 1. Start the Universe Designer. 2. Create a new OLAP Universe using the query BusinessObjects Community Query 4 (technical name: DALSEGNO/BUSINESSOBJECTS_QRY_04). 3. Save and export the OLAP Universe to BusinessObjects Enterprise SAP AG 58

59 Creating a Query as a WebService (QaaWS) After creating the OLAP Universe, you can now create the web service on top of the OLAP Universe. To create a new QaaWS web service 1. Start Query as a Web Service (Program > BusinessObjects XI Release 3 > BusinessObjects Enterprise > Query as a WebService). 2. Click Add. 3. Enter the Name and CMS. 4. Click OK SAP AG 59

60 5. Click Close. 6. Enter the User and Password. 7. Click OK SAP AG 60

61 8. Click New. 9. Enter a name for the web service. 10. Click Advanced Parameters. 11. Select secsapr3 as Authentication mode. 12. Click OK SAP AG 61

62 13. Click Next. 14. Select the Universe which will be used for the web service. 15. Click Next. 16. Use the query panel to create the query for the web service SAP AG 62

63 17. Click Next. Note: A preview of the data is shown. 18. Click Publish. 19. Copy the URL to the clipboard so that it can be used later on in the Xcelsius Designer. 20. Click Close SAP AG 63

64 Activity: Create a New QaaWS Web Service Objective To build a new QaaWS on top of an OLAP Universe based on an SAP BW query Scenario You are a report designer creating an Xcelsius dashboard and building the underlying QaaWS web service. Instructions 1. Create a new QaaWS based on the previously created OLAP Universe. 2. Include the field Calendar Year. 3. Publish the web service SAP AG 64

65 Xcelsius and QaaWS In this unit, you will learn how you can use Xcelsius to connect to a QaaWS web service with SAP data sources. After completing this unit, you will be able to: Use Xcelsius with QaaWS Xcelsius and QaaWS After creating the OLAP Universe and the web service based on top of the OLAP Universe, you can now create the Xcelsius dashboard using the web service. To create the Xcelsius dashboard 1. Start Xcelsius Designer (Start > Programs > Xcelsius > Xcelsius Designer). 2. Re-open the Xcelsius file from the previous activity 3. Select the menu Data > Connections. 4. Click Add SAP AG 65

66 5. Select Query as a Web Service. 6. Select the newly created connection. 7. Paste the URL from the created QaaWS web service into the field WSD URL. 8. Click Import. 9. Click on the row folder of the Return Values. 10. Click the icon next to the range. 11. Mark the required range in the Excel spreadsheet. 12. Click OK SAP AG 66

67 13. Navigate to the Usage tab. 14. Set the Refresh on Load property. 15. Click Close. 16. Add a list box component to the Xcelsius canvas. 17. Double-click the list box component SAP AG 67

68 18. Set the Insert Type option to Value. 19. Select the range for the Source Data and point it to the previous marked cells for the web service. 20. Select the range for the Labels and point it to the previous marked cells for the web service. 21. Set the Destination to the cell in the spreadsheet that was marked previously to be the input for the parameter in Live Office. 22. Select the menu Data > Connections. 23. Select the existing Live Office connection SAP AG 68

69 24. Navigate to the Usage tab. 25. Click the icon next to Trigger Cell. 26. Mark the cell that will contain the value from the list box. 27. Select the option When Value Changes. 28. Click Close. 29. Click Preview SAP AG 69

70 SAP Connectivity Overview This lesson provides you with an overview of the connectivity towards SAP BW and SAP R/3 for the BusinessObjects products. In this lesson, you will learn about: SAP connectivity options for BusinessObjects products 2008 SAP AG 70

71 SAP Connectivity Options In this unit, you will learn about the available SAP data sources for BusinessObjects products After completing this unit, you will be able to: Describe the available SAP data sources for BusinessObjects products SAP Connectivity for Crystal Reports Crystal Report SAP Table, Cluster and SAP InfoSet ODS BW MDX BW Query Function SAP R/3 SAP BW Direct access BEx Query Classic InfoSets SAP Queries ABAP Functions Table and Cluster MultiProvider InfoCube MultiProvider InfoCube ODS InfoSet The available SAP data sources for Crystal Reports are: SAP R/3 Tables and cluster (Open SQL). ABAP functions. Classic InfoSets. SAP queries and InfoSet queries. SAP BW Tables and cluster (Open SQL). ABAP Functions. Direct ODS access BW queries and BW cubes SAP AG 71

72 SAP Connectivity for Web Intelligence The available SAP data sources for Web Intelligence are: SAP BW BW queries and BW cubes SAP AG 72

73 SAP Connectivity for Query as a Web Service (QaaWS) The available SAP data sources for Query as a WebService are: SAP BW BW Queries and BW Cubes SAP AG 73

74 SAP Connectivity for Live Office Live Office Crystal Reports Web Intelligence SAP Table, Cluster and SAP InfoSet ODS BW MDX BW Query Function OLAP Universe SAP R/3 SAP BW Direct access BEx Query Classic InfoSets SAP Queries ABAP Functions Table and Cluster MultiProvider InfoCube MultiProvider InfoCube ODS InfoSet Live Office is able to leverage the following source documents: Crystal Reports. Web Intelligence. Universes (including OLAP Universes). Based on the list above, the available SAP data sources for Live Office are: SAP R/3 Tables and cluster (Open SQL). ABAP functions. Classic InfoSets. SAP queries and InfoSet queries. SAP BW Tables and cluster (Open SQL). ABAP Functions. Direct ODS access (without the need for an SAP BW query). BW queries and BW cubes SAP AG 74

75 SAP Connectivity for Xcelsius Xcelsius is able leverage the following sources for connectivity 1. Web Services 2. Live Office Based on the list above the available SAP data sources for Xcelsius are: SAP R/3 Tables and cluster (Open SQL). ABAP functions. Classic InfoSets. SAP queries and InfoSet queries. SAP BW Tables and cluster (Open SQL). ABAP Functions. Direct ODS access (without the need for an SAP BW query). BW queries and BW cubes SAP AG 75

76 Copyright 2008 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, System i, System i5, System p, System p5, System x, System z, System z9, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. Any software coding and/or code lines/strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent SAP AG 76