End to end integrated Scenario of ECC, HANA and BO : HANA Modelling to IDT (Part 2)
This document contains end to end scenario of creating Universe in IDT by fetching data from SAP HANA. IDT is Information Design Tool under BusinessObjects.(details about IDT is given in below steps)
For DASHBOARD SCENARIO : Step by Step procedure of how to consume SAP HANA views in Dashboards.
Following are the step involved in :
Step-By-Step Development Process
A. UNIVERSE DEVELOPMENT
1. Project Creation
Login to IDT.
- Click START —> ALL PROGRAMS —-> SAP BUSINESS INTELLIGENCE —> SAP BUSINESSOBJECTS BI PLATFORM 4 CLIENT TOOLS —-> INFORMATION DESIGN TOOL
NOTE : The information design tool is an SAP BusinessObjects metadata design environment that enables a designer to extract, define, and
manipulate metadata from relational and OLAP sources to create and deploy SAP BusinessObjects universes.
Below is the Home screen to create universe. Left navigation panel gives us the already existing projects. Also Repository resources.
NOTE : A universe is an organized collection of metadata objects that enable business users to analyze and report on corporate data in a non-technical language.Here we create project for developing Universe.
- Click FILE —> NEW —> PROJECT
Specify Project name and location to workspace. Devendra_Po_Analysis is project name used in scenario.
- PROJECT_NAME —> PROJECT_LOCATION —> FINISH
- Insert Session or open the existing one from Repository Resource tab to left panel.
- Enter credentials for creating session.
NOTE : A session contains the Central Management Server (CMS) system name and authentication information needed to access resources stored in a repository. Workflows in the information design tool that require access to secured resources, prompt you to open a session.
- CONNECTIONS and UNIVERSE are two folders under session.
- After expanding connections we use one of the connection. HANA_CONN is JDBC secured connection used here.
NOTE : A Personal connection is created by one user and cannot be used by other users. The connection details are stored in PDAC.LSI file.
A shared connection can be used by other users through a shared server. The connection details are stored in SDAC.LSI file in the Business Objects installation folder. However one cannot set rights and securities on objects in a shared connection. Neither can a Universe to exported to repository using a shared connection.
A secured connection overcomes these limitations. Through it rights can be set on objects and documents. Universes can be exported to the central repository only through a secured connection. The connection parameters in this case are saved in the CMS
- Check whether connection is working properly or not.
- Right Click CONNECTION_NAME —-> CREATE RELATIONAL CONNECTION SHORTCUT
NOTE : If you need to access data from a table and regular RDBMS then your connection should be a relational connection but if your source is a application and data is stored in cube(technically there are tables involve which you normally do not see) then you would use a OLAP connection.
- Select PROJECT_NAME from local project.
- CONNC_NAME.cns file is added under PROJECT_NAME
3. Data Foundation
- Create Data Foundation layer under project.
- Right Click PROJECT_NAME —> NEW —> DATA FOUNDATION
NOTE : Data Foundation can consume one or more connections. So you can bring tables from multiple databases into a single Data Foundation. The Data Foundations contains the tables, joins, and contexts.
- Specify the Resource name and description for data foundation layer.
- Select Data foundation type.
NOTE : Single-source data foundations support a single connection. The connection can be local or secured, which means you can publish universes based on the data foundation either locally or to a repository.
Multisource-enabled data foundations support one or more connections. You can add connections when you create the data foundation and anytime later. Multisource-enabled data foundations only support secured connections, and universes based on this type of data foundation can only be published to a repository.
- Select connection from list to setup connection between HANA system to Universe.
- DF_PO_ANA.dfx is data foundation layer used in current scenario.
- We insert tables from HANA system as shown below.
- Click INSERT —-> INSERT TABLES
- Select the proper schema and tables which need to be called from HANA system.
- Click SCHEMA_NAME —-> TABLES_NAMES —-> FINISH
- At current screenshot, tables called into Data foundation layer.
4. Business Layer
- Right click PROJECT_NAME —-> NEW —-> BUSINESS LAYER
NOTE : Business layer is a collection of metadata objects that map to SQL or MDX definitions in a database, for example, columns, views, database functions, or pre-aggregated calculations. The metadata objects include dimensions, hierarchies, measures, attributes, and predefined conditions. Each object corresponds to a unit of business information that can be manipulated in a query to return data. Business layers can be created directly on an OLAP cube, or on a data foundation that is built on a relational database
- Select type of data source for Business layer.
- Specify resource name and description for business layer.
- Select Data foundation file.
- Select DF_NAME.dfx —-> FINISH
- Automatically all the dimensions and measures of particular tables or views are displayed to left panel under business layer.
- After creating business layer we need to publish it to repository.
- Right click BUSINESS_LAYER —-> PUBLISH —-> TO A REPOSITORY
- Publishing allows universe to publish to repository. So it is mandatory to check integrity for all connection.
- Select proper workspace for storing. Here we have used DEVENDRA folder.
- Click at FINISH.
Universe is published successfully at specified location.