- Creating Universes with SAP BusinessObjects
- Taha M. Mahmoud
- 267字
- 2021-09-03 09:40:12
Introduction to Universes and the Information Design Tool
All reporting tools use semantic layers for the same purpose. However, they just give it different names such as Framework in IBM Cognos, Project in Oracle BI, and Universe in SAP Business Objects. All semantic layers have exactly the same functionality: isolation of the technical part from the end business user by acting like a translator. They will translate the business requests into technical SQL queries submitted to the database. Also, they interpret the data returned into a format that can be understood by the end user.
SAP BO introduced a new tool to create your Universe (SAP BO semantic layer) in SAP BO 4.1; this is the Information Design Tool. They are still supporting the old Universe designer tool for compatibility purposes, but they clearly mention that they will stop supporting the Universe designer soon, and you will be able to create your Universes using the Information Design Tool only.
Before we conclude this chapter, let's have a look at the main components of Universe:
- Connection: Every Universe should have at least one data connection. The data connection will define how Universe will access the data based on the connection type. If you have an Oracle connection, for example, you will need to define your Oracle database and set your connection parameters. We will talk about this in detail later on.
- The Data Foundation layer: This is the physical layer in the Universe.
- The Business layer: We define our business model in this layer. We might have more than one Business layer that shares the same Data Foundation.
- 新形勢下中國投入產出核算的變革與實踐
- 新中國審計制度變遷
- 會計信息化基礎(金蝶版)
- Citrix? XenMobile? Mobile Device Management
- 審計實務案例與實訓教程
- 非線性經濟關系的建模
- 陜西國家統計調查專題研究集萃(2006—2015)
- Getting Started with Citrix VDI-in-a-Box
- AO2011實用手冊
- 《企業內部控制基本規范》合規實務指南
- 2017年度注冊會計師全國統一考試專用教材(圖解版):審計
- 公司內部審計
- 統計原理與實務
- Windows Server 2016 Administration Fundamentals
- Hyper-V Best Practices