SAP HANA and BOBI 4.0 - Universe Design Guide (Multi Source) V2

________________________________________________________________________

SAP HANA and BOBI 4.0 Knowledgebase

Universe Design Guide (Multi Source)

A SAP HAN Community Service

Author: Pals Nagaraj, PMP SAP HANA Certified Solutions Architect SAP BusinessObjects Enterprise Certified Lead/Manager [email protected]

Chief Architect:: A SAP HANA Community Services Jothi Periasamy SAP HANA/EPM/BI/EIM Community Thought Leader 01/10/2012 SAP BPC/BOBJ/BI/MDM Community Domain Champion [email protected], (916)-296-0228 - Cell

CloneSkills, Inc., http://www.CloneSkills.com , [email protected] , 1.800.836.8959, Page - 1

________________________________________________________________________

Table of Contents Executive Summary: ............................................................................................... 4 Universe Development – Implementation Steps: .................................................. 10 Launching Information Design Tool ...................................................................... 12 Create a Project .................................................................................................... 13 Create a Session .................................................................................................. 15 Create a Relational Connection to InfoCube......................................................... 17 Create a Data Foundation from InfoCube ............................................................. 27 Create a Business Layer from Data Foundation ................................................... 33 Create Classes & Objects ..................................................................................... 39 Create Actual & Plan Folder(class) ............................................................................... 41 Create Category Dimension .......................................................................................... 43 Create Other Dimensions and Measure ........................................................................ 45

Create Year and Month from Time Dimension ...................................................... 46 Create Month Dimension .............................................................................................. 47 Create Year Dimension ................................................................................................ 49

Create Parameters and List of Values .................................................................. 51 Create List of Values .................................................................................................... 51 Create Parameters ....................................................................................................... 58 Parameters and List of Values at Data Foundation Level.............................................. 61

Filters .................................................................................................................... 62 Prevent technical data from business users ......................................................... 66 Publish the Universe ............................................................................................. 68 Creating Web Intelligence Document from the published universe ....................... 71 Preview the data ........................................................................................................... 74 Using Filters.................................................................................................................. 75 Filter - Plan Category Only............................................................................................ 75 Filter - Actual Category Only ......................................................................................... 76 Filter – Cost Center France........................................................................................... 77 Filter – France and Germany data ................................................................................ 78




________________________________________________________________________ Filter – Actual Category for Germany and India for Q1 ................................................. 82

Parameters ........................................................................................................... 83 Category Parameter ..................................................................................................... 83

Aliases and Contexts ............................................................................................ 90 Aliases and contexts are used to resolve loops in the schema...................................... 90 Aliases .......................................................................................................................... 92

Using OLAP Connection ....................................................................................... 93 Insert a OLAP Connection ............................................................................................ 94 Publish the OLAP Connection ...................................................................................... 99 Create a new Webi Document .................................................................................... 100 Select BEx as Data source ......................................................................................... 101 Select the OLAP Connection and the query ................................................................ 102 Create a Webi Document from OLAP ......................................................................... 103 Publish the webi document to the server. ................................................................... 106

Using Single Source MS Access Connection ..................................................... 109 SAP Note on creating and using OLAP connection in Information Design Tool . 110 Disclaimer: .......................................................................................................... 111 _________________________________________________ .......................... 111 SAP Community Contributors: ............................................................................ 111




________________________________________________________________________

Executive Summary: The purpose of this document is to demonstrate step by step implementation instruction on how to design and implement multi source universe functionality in SAP BOBI 4.0. It is assumed that the reader has enough proficient in SAP HANA and SAP BOBI terminologies and technologies and also the application navigating in SAP HANA and BOBI user interfaces. In this implementation guide, SAP BusinessObjects Information Design Tool has been used to build out the multi source Universe.

Business Drivers:

Access enterprise business information through single source Maintain single version of the truth Enable self servicing report functionality Combine data from multiple sources to analyze business insights Reduce technical complexity in data analysis and report development, including Data model Data architecture Data dictionary Meta data Data flow Data filter Table join SQL complexity Easy access of business information irrespective of source systems Business driven , and IT enablement …much more




________________________________________________________________________

Multi Source Universe Architecture:

Source # 1: SAP HANA Source # 2: SAP BW 7.3




________________________________________________________________________


Source # 1: SAP HANA | Application Navigation




________________________________________________________________________


Source # 1: SAP HANA | Connection Information

Author: Pals Nagaraj, PMP SAP HANA Certified Solutions Architect SAP BusinessObjects Enterprise Certified Lead Lead/Manager [email protected]


CloneSkills, Inc., http://www.CloneS eSkills.com , [email protected] , 1.800.836.8959, Page ge - 7

________________________________________________________________________


Source # 2: SAP BW 7.3 | Application Navigation




________________________________________________________________________

Multi Source Universe Architecture: Source # 2: SAP BW 7. 7.3 | Connection Information




________________________________________________________________________

Multi Universe Development – Implementation Steps:





________________________________________________________________________

Multi Universe Development – Implementation Steps:





________________________________________________________________________

Launching Information Design Too Tool Option 1

Option 2




________________________________________________________________________

Create a Project

Select - File – New Project. Enter project Name. Leave Project Location as default and click Finish.

The project created will be listed in the Local Projects




________________________________________________________________________




________________________________________________________________________

Create a Session

Under the Repository Resources, click on the down arrow next to green + sign, and select Insert Session

Enter your login credentials in the Open Session window and click OK. By creating a session you are logging into the Repository, to publish the connection to the source and business layer/universe to the repository. So that it can be used by any presentation presentation/reporting tools ls like Crystal Reports, Web Intelligence, Dashboards, etc.




________________________________________________________________________

Once you are connected to the repository all the Connections and universes published to the repository will be listed under Repository Resources.




________________________________________________________________________

Create a Relational Connection to InfoCube

Under the Repository Resources right click on Connections and select Insert Relational Connection




________________________________________________________________________ In the New Relational Connection window, enter the resource name and description and click next.




________________________________________________________________________ In the Database Middleware Driver selection window, select SAP Java Connector (JCO) under SAP NetWeaver BW and click Next.




________________________________________________________________________ In the Create an SAP NetWeaver BW Connection window, enter the BW server credentials and click Test Connection. If the credentials are correct and valid, Test Result window will display with “Test Successful” message. Close the Test Result Window. (Contact your system administrator for BW server credentials)




________________________________________________________________________

After the Test Connection is successful, click on the button with three dots (…) at the end of the InfoProvider line.




________________________________________________________________________ After click on the (…) button, “Select an InfoProvider Fact Table” window will display with list of all InfoProviders for the BW system.

InfoProviders listed will be IOBJ – InfoObject CUBE – InfoCube MPRO – MultiProvider VIRT- Virtual Provider ODSO – Operational Data Store. By selecting object of your interest the list will be filtered and only fact tables of selected type will be displayed.




________________________________________________________________________ Here CUBE is selected, so Fact tables of InfoCube type are displayed.

List can be searched for a particular cube by selecting the search icon and entering the letters in the cube description, to search the cube of your interest. Once the cube is displayed select it and click OK. Here in the example, entering 33 brought up the BOBJ Class 3312 cube. This cube will be selected.




________________________________________________________________________ The selected cube will be displayed in the InfoProvider field of the Create an SAP NetWeaver BW Connection window. Click Finish.

The connection will be created and published to the repository. Following Info window will be displayed. Select Yes for “Do you want to create a shortcut?”




________________________________________________________________________

At this point connection to the InfoCube (or any other info source) is published to the repository and a short to the connection is also created in the local computer. Connection published to the repository will be used by the reports, created based on this universe, during run-time. The connection shortcut that is saved locally in the development system will be used during development time.




________________________________________________________________________ Shortcut connection is listed under Local Projects with extension .cns

Connection published to the repository is listed under Repository Resources without any extension.




________________________________________________________________________

Create a Data Foundation from InfoCube

Select File-New-Data Data Foundation. In the New Data Foundation window, enter the name for the data foundation and click next. Enter the name of the Data Foundation and click Next.




________________________________________________________________________ In the Select Data Foundation Type, select MultisourceEnabled and click Next.




________________________________________________________________________ Click Next in the CMS user Authentication window.




________________________________________________________________________ In the Select Connections window select the appropriate connection. (if the project has more than one connection, all connections in the project will be listed here) NOTE: the connection listed here is shortcut connection (.cns extension). Click Next.




________________________________________________________________________ In the Define connection properties for connection window, click on Advanced and select “Automatically create tables and joins” option. Click Finish.




________________________________________________________________________ • • • • •

Data foundation with the given name (DF_UNIV_DEV) will be created. It will be created with the extension .dfx (DF_UNIV_DEV.dfx) and listed under local project A data foundation tab with data foundation name (DF_UNIV_DEV.dfx) will open Fact table and dimensions with join will be displayed. List of tables and joins will also be displayed




________________________________________________________________________

Create a Business Layer from Data Foundation

Select File – New – Business Layer Select Relational Data Source in the New Business Layer (Select the type of data source for the business layer) window and click next.




________________________________________________________________________ Enter name and description for the Business Layer and click Next.




________________________________________________________________________ In the Data Foundation selection window, click on the (…) button, to open data foundation list.




________________________________________________________________________ Select the data foundation created before and click OK.




________________________________________________________________________ Selected data foundation will be populated in the Data Foundation selection window. Select the option for “Automatically create classes and objects for SAP NetWeaver BW connections” and click Finish.




________________________________________________________________________ •

• •

•

Business Layer will be created with the given name (BL_UNIV_DEV.blx) with the extension .blx and listed under the project in the Local Projects area (will not be in the Repository Resources yet) Business Layer tab with the name (BL_UNIV_DEV.blx) will be open Created classes (folders) and objects (dimensions and measures) will be displayed (since “Automatically create classes and objects for SAP NetWeaver BW connections” option was selected in the previous step) Data foundation from which the business layer was created will be displayed




________________________________________________________________________

Create Classes & Objects

Naming in BI 4.0 and before BusinessObjects V 4.0

BusinessObjects V3 and before

Folder

Class

Dimension

Object

Measure

Object

Parameter

Prompt

Creating business user friendly objects is the main task of universe design where the columns that contain business data are translated to appropriate business domain friendly terms to make business user independent from technical domain. Security, Parameters, Paramet List of values are also defined in universe design.




________________________________________________________________________

The following table describes the Dimensions and Measure that will be created in this exercise using the objects in the above screenshot. Class and Objects to be created in this exercise Name

Type

Source

Actual & Plan

Folder

-

Category

Dimension

Category

Account

Dimension

P_ACCT

P Activity

Dimension

P_ACTIVITY

Cost Center

Dimension

P_CC




________________________________________________________________________ Data Source

Dimension

P_DATASRC

Report Currency

Dimension

RptCurrency

Year

Dimension

Time

Month

Dimension

Time

Revenue

Measure

Revenue

The example data set contains Actual & Plan data. So Actual & Plan data folder(class) will be created to contain dimensions and a measure. Create Actual & Plan Folder(class) Right click on the universe name – select New - Folder




________________________________________________________________________ In the Folder Properties window enter the name of the folder – Actual & Plan and enter description if any. Actual & Plan folder should appear in the Business Layer listing.




________________________________________________________________________ Create Category Dimension Right click on the Actual & Plan – select New –Dimension.

In the Dimension Properties window enter the dimension name – Category and click on the SQL Assistant Window.




________________________________________________________________________ SQL Expression Editor window will open. 1. In the Business Layer section expand category folder and select Category dimension by double clicking. 2. Selected dimension – Category will appear in the SQL Expression section. 3. Validate and click OK.

SQL Expression editor will close and Category dimension selection expression @select(CON_UNIV_DEV\Category\Category) will show up in Dimension




________________________________________________________________________ properties window and the Category dimension will be listed under Actual & Plan folder.

Create Other Dimensions and Measure Repeat the above steps to create Account, P Activity, Cost Center, Data Source, Report Currency dimensions and Revenue measure. (Refer to the table few pages above for the source) Save the universe.




________________________________________________________________________ After creating all the dimensions and measure the Actual & Plan class(folder) should appear as shown below.

Create Year and Month from Time Dimension The time data in the data set is in YYYY.MMM format as a string variable. By getting the first 4 characters will return Year and last 3 characters will return month.




________________________________________________________________________ Create Month Dimension Follow the steps to create a dimension. In the SQL Expression window: 1. Go to the Functions list 2. Navigate to Database Functions – CharString and double click Rightpart function 3. Rightpart (right())functions syntax and description will appear at the bottom. Also the function template, right($1,$2), will be add to the expression window. 4. Delete $1 from right($1,$2) template. Navigate to Time dimension in Business Layer and double click it. Template will change to right(@Select(CON_UNIV_DEV\Time\Time),$2) nd 5. Change the 2 parameter to 3 in function template. The right($1,$2) function finally should be right(@Select(CON_UNIV_DEV\Time\Time,3) 6. Validate and click OK.




________________________________________________________________________ Checking the Month values Back in Dimension Properties window for Month dimension, click on Show Values.. button to preview the values for Month.




________________________________________________________________________

All the unique values for the Month Dimension will be displayed in the “Show Values for Month” tab. Close it after checking the values. Create Year Dimension Follow the steps for creating Month dimension from year. Instead of right() function use left($1, $2) function to get the Year from Time (in the format YYYY.MMM).




________________________________________________________________________ After adding all dimensions and a measure the final list of objects should be as shown here in the folder Actual & Plan

Save the universe.




________________________________________________________________________

Create Parameters and List of Values

Parameters: Parameters are used during run run-time time to prompt the user to select values to filter the data. Selected parameter values will be used in the where clause. List of Value (LOV): Predefined set of data for an object. Mostly used in combination with parameters. Create List of Values The following exercise creates list of values for Category, Cost Center and Account In the Business Layer tab, click on the Parameters and Lists of Values button, below the Queries button. Parameter and List of Value editor will open. Click on the down arrow button in List of values values.. There will be 3 choices to create list of values 1. List off values based on business layer objects 2. Static list of values 3. List of values based on custom SQL In this exercise first option will be used to create list of values values.. Select the 1st option.




________________________________________________________________________




________________________________________________________________________ In the Business Object LOV Properties window enter the name for the LOV (Category LOV) and click on Edit Query.. to open Query Panel




________________________________________________________________________ In the Query Panel, double click on Category under Actual & Plan folder so that it will in Result Objects for Query #1. Click OK to go back to Business Object LOV Properties window (shown above)




________________________________________________________________________ Back in Business Object LOV properties window, click Preview button, the values available in the LOV will be listed (Category LOV has 2 values “ACTUAL” and “PLAN” ). Values can be sorted using the sort menu. Close the Preview Values window.




________________________________________________________________________ Created LOV (Category LOV) should be listed in List of Values.

Repeat the above steps to create Cost Center, Account LOVs. Save the universe




________________________________________________________________________ Category LOV, Cost Center LOV and Account LOV should be listed under List of Values.




________________________________________________________________________ Create Parameters 1. Click on the Insert Parameter icon (green +). Parameter Properties will open 2. Enter name for the parameter (prompt) 3. Check Prompt to users option (this will display the Prompt Text at run-time) 4. Enter Prompt Text: (the text entered here will be displayed at run-time) 5. Click (…) button to get list of LOVs to associate with this parameter (prompt)




________________________________________________________________________ In the Select a List of Values window, select Universe List of Values. All the LOVs created in the previous section will be listed. Select Category LOV and click ok.

Selected LOV will be associated with the parameter. Allow multiple values : This option allows entering or selecting (from LOV) more than one value during run-time for a prompt. When this is checked, where clause in the SQL generated, will have “column in (value1, value2, etc.)” If this option is not selected then the where clause would be “column= value1” Keep list values: This option saves the values selected from LOV or entered for the next run-time. For example. If Category=PLAN was selected and ran a report. Next time when the report is run, it will populate Category=PLAN automatically.




________________________________________________________________________ Category Prompt/Parameter with Category LOV

Repeat the above steps to create Cost Center parameter and Account parameter. Save the universe. Finally the all the parameters and LOVs created should appear as shown in the following screenshot.




________________________________________________________________________

Parameters and List of Values at Data Foundation Level Parameters and List of values can be defined at data foundation level also. When defined at data foundation level, all Business Layer that uses the data foundation inherits those parameters and list of values. NOTE: More than one Business Layer (universe) can be defined based on one data foundation. Ex. data foundation can have all the enterprise data from which Sales, Inventory, and Product etc universes can be built




________________________________________________________________________

Filters Filters are objects that will be used in the “where clause” of the generated SQL. Like dimensions and measures, filters are also named in business terms like – Plan Category only, Actual Category Only, Cost Center France, Cost Center Germany, etc. so that business users can understand and use them to filter appropriate data. Steps to create Filters are same as those of creating dimensions and measures. Right click on the Actual & Plan folder and select Filters. In the Filter Properties window: • Enter the filter name and description. • Select Business for Filter type: o Native Filter: defined using SQL o Business Filter: define using objects in business layer. • Click Edit Filter




________________________________________________________________________ In the Edit Custom Filter window, Double click on Category in Actual & Plan folder. Category object will appear on the Filter Objects column in the right Select “Equal to” from the operation dropdown. Enter PLAN for the value. (Category LOV can also be used to get the value PLAN) Click OK.




________________________________________________________________________ Filter “Plan Category Only” will appear under the dimensions and measure in the Actual & Plan folder /class and Filter definition (Category=’PLAN’) will be displayed in Filter Properties

Repeat the steps to create Actual Category Only, Cost Center France, Cost Center Germany, Cost Center India, Q1, Q2, Q3 and Q4 filters. For Q1 uses Month In (JAN; FEB; MAR) (note semicolon between months). Repeat the steps to create Q2 and Q3 filters. Save the business layer.




________________________________________________________________________ The final list of dimensions, measures and filters, in this exercise, should be as shown in the screenshot below




________________________________________________________________________

Prevent technical data from business users The objects in the folder with the connection name (CON_UNIV_DEV) contains name of the columns from the underlying data source. This should be prevented from business users during report creation by them. Only the folder Actual & Plan with business termed dimensions, measures and filters should be visible to business users. To achieve this, the folder with technical names (CON_UNIV_DEV) can be hidden. (any object can be hidden from run-time)




________________________________________________________________________

Save the universe/business layer.




________________________________________________________________________

Publish the Universe

Right click on the business layer Select Publish – To Repository




________________________________________________________________________ In the Check Universe integrity window, select “Check all” and click Next. Check Integrity: checks if the underlying data source schema is changed between the times, when data foundation retrieved the schema and when publishing the universe. If changed, the integrity check will fail. In that case, data foundation must be updated to synchronize with data source schema before publishing. Otherwise, runtime error may occur.




________________________________________________________________________ Select the folder to publish the business layer/universe (top level folder “Universes” is chosen here) and click Finish.

Business layer/ Universe will be published to repository and listed under Repository Resources also.




________________________________________________________________________

Creating Web Intelligence Document from the published universe Before creating a Web Intelligence document, you need to log into BI Lauchpad (browser based) or Start Web Intelligence Rich Client (Windows based). BI LaunchPad

Optionally you can enter the url: http::8080/BOE/BI in the browser. Web Intelligence Rich Client

In this exercise Web Intelligence Rich client will be used. Launch the Web Intelligence Rich Client and enter the login credentials.




________________________________________________________________________ Double click the published universe (BL_UNIV_DEV) from the universe list.




________________________________________________________________________ Query panel will open with all the Dimensions, Measures, Filters, Parameters and List to values developed in the Information Design Tool business layer.




________________________________________________________________________ Preview the data This exercise uses Query Panel to demonstrates filters, parameters and LOVs and preview the results in the Data Preview panel. The query can be converted to report by selecting Close-Apply changes and Close menu item, which will transfer the objects to a web intelligence report that can be saved. Select all the dimensions and the measure (click on Category first and hold shift on Revenue to select all objects in between them). Drag the selected objects into Result Objects section. Click Refresh in the Data Preview section, to preview the all the data in the cube. NOTE:SQL generated can be view using SQL script viewer.




________________________________________________________________________ Using Filters Filter - Plan Category Only Double click the “Plan Category Only” filter or drag and drop into Query Filters section and click Refresh and verify only PLAN data is retrieved.




________________________________________________________________________ Filter - Actual Category Only Replace the Plan Category Only filter with Actual Category Only filter and verify the data retrieved.




________________________________________________________________________ Filter – Cost Center France Replace the previous filter with Cost Center France filter and refresh. Verify data for only France is retrieved.




________________________________________________________________________ Filter – France and Germany data Add Cost Center Germany filter to the Cost Center France filter. When you add second filter both will be joined with “And”. Click on “And” to change it to “Or”

NOTE: Filters on same columns should have “OR” operator. Filters on different columns should have “AND” operator.




________________________________________________________________________ Refresh and verify that data for France and Germany only retrieved.




________________________________________________________________________ Filter – Actual data for France and Germany Add Actual Category Only filter to the previous filter. When you add the Actual Category Only filter the filters may have OR operator. The proper filter should be (Actual Category Only) AND (Cost Center France or Cost Center Germany) Cost Center France and Cost Center Germany need to be grouped together To group Cost Centers, click and hold on Cost Center Germany, push it towards Cost Center France and release the mouse. This will group Cost Center France and Germany together and isolate Actual Category Only as a separate group.

Click on the “And” and “Or” to toggle them appropriately as shown here.




________________________________________________________________________ Refresh and verify only Actual Category data is returned for France and Germany.




________________________________________________________________________ Filter – Actual Category for Germany and India for Q1




________________________________________________________________________

Parameters Parameters are also kind of filters, but filters have pre-defined filter values, where as parameters (or prompts) prompts the user to enter or select values to filter the data. Category Parameter In the Query Panel remove all filters. Drag and drop Category dimension into the Query Filters section. Click on the down arrow and select Prompt as show here.




________________________________________________________________________ Click on the ? icon to open Parameter




________________________________________________________________________ In the Parameter properties window, Select Use Universe Parameters. This will list the parameters defined in the Universe. Select Category Parameter and Click Ok.

In the query panel click refresh icon. Prompt window will appear as shown below. It will use the parameter defined in the universe. The following image shown how the parameters defined in the universe are used during run-time.




________________________________________________________________________




________________________________________________________________________ Select PLAN from the LOV and click ok. Verify only PLAN data is retrieved.

Repeat the above steps to add Account parameter to the category parameter. Click Refresh.




________________________________________________________________________ Two prompts will be displayed – one for Category (added in previous step) and another for Account

Select two values for the Account (CE00004210, CE0004020) and click ok. Verify that select Accounts data and selected Category data only is retrieved.




________________________________________________________________________




________________________________________________________________________

Aliases and Contexts Aliases and contexts are used to resolve loops in the schema. Context – A group of joins with a name Alias - A table with another name. The following schema illustrates a loop. If two columns are selected – one from Table A and another from Table C, the result may include • Table A, Table B and Table C • Table A, Table E, Table D and Table C The first option is better than the second since the second involves 3 joins which will be more restrictive and product incorrect result. If the SQL is created manually we have control to select Table A and Table C going through intermediate Table B. Bu Butt in BusinessObjects the SQL is generated behind the scene based on the dimensions and measures selected by the user. When such multiple paths are available, the system can be directed to select the best path by defining one or more contexts.

The following table describes all the possible contexts that can be defined to resolve the above loop. With these context definitions in BO for the above scenario it is possible to navigate between any tables to produce appropriate results. Author: Pals Nagaraj, PMP SAP HANA Certified Solutions Architect SAP BusinessObjects Enterprise Certified Lead Lead/Manager [email protected]



________________________________________________________________________

Context Name

Join(s) in the Context

Used by BO when Dimensions and Measures selected from

AB

Join AB

Table A and Table B

ABC

Join AB and Join AC

Table A, Table B and Table C Table A and Table C

BC

Join BC

Table B and Table C

BCD

Join BC and Join CD

Table B, Table C and Table D Table B and Table D

CD

Join CD

Table C and Table D

CDE

Join CD and Join DE

Table C, Table D and Table E Table C and Table E

DE

Join DE

Table D and Table E

DEA

Join DE and Join EA

Table D, Table E and Table A Table D and Table A

EA

Join EA

Table E and Table A

AE

Joins AB, BC and CD

Table A, B, C and D




________________________________________________________________________

Aliases Aliases are e used to break a loop situation situation.. For example the above loop can be eliminated by defining an alias table for one of the tables. The following illustrates this by defining an alias for Table D.

One of the disadvantages of this approach is that, two set of object need to be created from rom Table D. Users need to be educated when to use objects from Table D and Table D alias.




________________________________________________________________________

Using OLAP Connection In Information Design Tool OLAP connection can be created and published. But universes cannot be built on top of OLAP connection in Information Design Tool. This is the limitation currently exists in Information Design Tool (SAP NOTE regarding this is attached at the end of this document) document).. Reports can be directly built on the published OLAP connection. Steps in creating,, publishing and using an OLAP connection.




________________________________________________________________________ For Steps 1 and 2, an existing project and session can be used. If not follow the steps explained before in this guide guide. Insert a OLAP Connection

In the Repository Resources section, right click Connections and select Insert OLAP Connection.




________________________________________________________________________

In the New OLAP connection window enter the connection name and click Next.




________________________________________________________________________

In the OLAP Middleware Driver Selection, expand SAP- SAP Netweaver BI 7.x and select SAP BICS Client and click Next.




________________________________________________________________________

Enter all the connection parameters and click Next.




________________________________________________________________________

In the Cube Selection window, select the cube of interest, which was created in the BW system, from which reports need to be created. Click Finish. NOTE: In this example, the Consolidation cube is used from the Starter Kit. But the steps are applicable to any OLAP connection and reporting.




________________________________________________________________________

Publish the OLAP Connection

The previous step, when Finish button is clicked, will publish the connection to the repository. Verify that the OLAP connection is published to the repository. The created OLAP connection must be listed under Connections folder in the Repository Resources.




________________________________________________________________________

Create a new Web Intelligence Document

Launch Web Intelligence Rich Client. New Document window will open on launching the Web Intelligence Rich client.




________________________________________________________________________

Select BEx as Data source

In the new document window click on More.. link under BEx




________________________________________________________________________

Select the OLAP Connection and the query

In the Select elect a BW BEx query window, • Select the published OLAP connection from Folders section on the left. • Select the query from the query list on the right section. • Click OK.




________________________________________________________________________

Create a Web Intelligence Document from OLAP

Query Panel will open will all the BEx query objects listed under Universe outline. (In this example, there are Time and Account dimensions and SignData)




________________________________________________________________________

In the query panel, • Double click on the desired dimensions and measure to add them to the Result Objects section. • Run the Query • Preview the data returned by the query in the Data Preview section • Select Apply Changes and close

Query will be saved and a Web Intelligence document will be generated based on the OLAP query and will be displayed.




________________________________________________________________________




________________________________________________________________________ Publish the web document to the server. Select the Save – Publish to...




________________________________________________________________________ Publish a document to the server window will open. • Select a folder for the report (under Public Folders) • Enter a report name • Save.




________________________________________________________________________ Log into to server using BI Launch Pad, navigate to the folder and run the report and verify.




________________________________________________________________________

Using Single Source MS Access Connection This section will cover the creating connection to single source connection to efashion MS Access database. All other steps before creating the connection and after are the same as for multi-source SAP Netweaver connection. In the Database Middleware Driver Selection step, select MS Access 2007- ODBC Drivers and click Next

Enter the credentials for database connection and test the connection. NOTE: The ODBC source must be configured for the MS Access database in the windows OS level before using the MS Access data source.




________________________________________________________________________

SAP Note on creating and using OLAP connection in Information Design Tool




________________________________________________________________________

Disclaimer: This description is a preliminary version and not subject to a license agreement or any other agreement with SAP®. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this preview is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This preview is provided 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 noninfringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected.

_________________________________________________ SAP Community Contributors: Author:

Chief Architect:

Pals Nagaraj, PMP SAP BOE Certified Lead/Manager SAP HANA Certified Solutions Architect TOGAF 8 Certified Technical Architect SAP HANA Community Member [email protected]

Jothi Periasamy SAP HANA/EPM/BI/EIM Community Thought Leader SAP BPC/BOBJ/BI/MDM Community Domain Champion [email protected] (916)-296-0228 - Cell

Contact Us For:

Universe Design Leading Practices Multi Source Universe Design and Implementation Universe Design Audit , and Much More …




SAP HANA and BOBI 4.0 - Universe Design Guide (Multi Source) V2

Recommend Documents