Business Intelligence Training Siemens Engineering Pakistan Zeeshan Shah December 07, 2009.

Slides:



Advertisements
Similar presentations
CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
Advertisements

Business Information Warehouse Business Information Warehouse.
The database approach to data management provides significant advantages over the traditional file-based approach Define general data management concepts.
ICS 421 Spring 2010 Data Warehousing (1) Asst. Prof. Lipyeow Lim Information & Computer Science Department University of Hawaii at Manoa 3/18/20101Lipyeow.
Database Systems: Design, Implementation, and Management Tenth Edition
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Key.
UNWBW1 – Business Information Warehouse NetWeaver Support Consultant Training BW and BW Reporting Introduduction.
The Hierarchy of Data Bit (a binary digit): a circuit that is either on or off Byte: 8 bits Character: each byte represents a character; the basic building.
Database Management: Getting Data Together Chapter 14.
L The Difference Between Logical and Physical Views of Information l Databases and Database Management Systems l How You Can Develop Database Applications.
Data Warehousing - 3 ISYS 650. Snowflake Schema one or more dimension tables do not join directly to the fact table but must join through other dimension.
MIS 451 Building Business Intelligence Systems Logical Design (3) – Design Multiple-fact Dimensional Model.
13 Chapter 13 The Data Warehouse Hachim Haddouti.
Chapter 13 The Data Warehouse
Designing a Data Warehouse
A Comparsion of Databases and Data Warehouses Name: Liliana Livorová Subject: Distributed Data Processing.
XP Information Information is everywhere in an organization Employees must be able to obtain and analyze the many different levels, formats, and granularities.
UNWBW1 – Business Information Warehouse NetWeaver Support Consultant Training Data Loading.
Week 6 Lecture The Data Warehouse Samuel Conn, Asst. Professor
DATA WAREHOUSING IN SQL SERVER 2005/2008 BUSINESS INTELLIGENCE.
Datawarehousing Concepts | 7.0 9/7/2015 Datawarehousing Concepts.
Chapter 6: Foundations of Business Intelligence - Databases and Information Management Dr. Andrew P. Ciganek, Ph.D.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
DECISION SUPPORT SYSTEM ARCHITECTURE: The data management component.
Data Warehouse Overview September 28, 2012 presented by Terry Bilskie.
Session 4: The HANA Curriculum and Demos Dr. Bjarne Berg Associate professor Computer Science Lenoir-Rhyne University.
AN OVERVIEW OF DATA WAREHOUSING
Business Intelligence Zamaneh Jahed. What is Business Intelligence? Business Intelligence (BI) is a broad category of applications and technologies for.
Database Design Part of the design process is deciding how data will be stored in the system –Conventional files (sequential, indexed,..) –Databases (database.
Data warehousing and online analytical processing- Ref Chap 4) By Asst Prof. Muhammad Amir Alam.
DIMENSIONAL MODELLING. Overview Clearly understand how the requirements definition determines data design Introduce dimensional modeling and contrast.
MIS DATABASE SYSTEMS, DATA WAREHOUSES, AND DATA MARTS CHAPTER 3
1 Data Warehouses BUAD/American University Data Warehouses.
Object Persistence Design Chapter 13. Key Definitions Object persistence involves the selection of a storage format and optimization for performance.
MIS2502: Data Analytics The Information Architecture of an Organization.
CHAPTER 3 DATABASES AND DATA WAREHOUSES. 2 OPENING CASE STUDY Chrysler Spins a Competitive Advantage with Supply Chain Management Software Chapter 2 –
Building Data and Document-Driven Decision Support Systems How do managers access and use large databases of historical and external facts?
Decision Support and Date Warehouse Jingyi Lu. Outline Decision Support System OLAP vs. OLTP What is Date Warehouse? Dimensional Modeling Extract, Transform,
Ch3 Data Warehouse Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2009.
Data Warehouse. Group 5 Kacie Johnson Summer Bird Washington Farver Jonathan Wright Mike Muchane.
Data resource management
Chapter 3 Databases and Data Warehouses: Building Business Intelligence Copyright © 2010 by the McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Chapter 13 Designing Databases Systems Analysis and Design Kendall & Kendall Sixth Edition.
UNIT-II Principles of dimensional modeling
Chapter 5 DATA WAREHOUSING Study Sections 5.2, 5.3, 5.5, Pages: & Snowflake schema.
McGraw-Hill/Irwin ©2009 The McGraw-Hill Companies, All Rights Reserved CHAPTER 6 DATABASES AND DATA WAREHOUSES CHAPTER 6 DATABASES AND DATA WAREHOUSES.
Business Intelligence Transparencies 1. ©Pearson Education 2009 Objectives What business intelligence (BI) represents. The technologies associated with.
What is OLAP?.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 7 Storing Organizational Information - Databases.
1 Copyright © 2009, Oracle. All rights reserved. Oracle Business Intelligence Enterprise Edition: Overview.
 Definition of terms  Reasons for need of data warehousing  Describe three levels of data warehouse architectures  Describe two components of star.
The Need for Data Analysis 2 Managers track daily transactions to evaluate how the business is performing Strategies should be developed to meet organizational.
1 Database Systems, 8 th Edition Star Schema Data modeling technique –Maps multidimensional decision support data into relational database Creates.
Copyright © 2016 Pearson Education, Inc. Modern Database Management 12 th Edition Jeff Hoffer, Ramesh Venkataraman, Heikki Topi CHAPTER 9: DATA WAREHOUSING.
SAP NetWeaver Business Intelligence SAP Netweaver Business Warehouse (SAP NetWeaver BW) the name of the Business Intelligence,
1 Copyright © 2008, Oracle. All rights reserved. Repository Basics.
Data Mining and Data Warehousing: Concepts and Techniques What is a Data Warehouse? Data Warehouse vs. other systems, OLTP vs. OLAP Conceptual Modeling.
Business Intelligence Overview
Jaclyn Hansberry MIS2502: Data Analytics The Things You Can Do With Data The Information Architecture of an Organization Jaclyn.
Chapter 13 Business Intelligence and Data Warehouses
Data warehouse and OLAP
Fundamentals & Ethics of Information Systems IS 201
Chapter 13 The Data Warehouse
Data Warehouse.
Data Warehouse Overview September 28, 2012 presented by Terry Bilskie
CHAPTER SIX OVERVIEW SECTION 6.1 – DATABASE FUNDAMENTALS
Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2009
Introduction of Week 9 Return assignment 5-2
Data Warehousing Concepts
Data Warehouse and OLAP Technology
Presentation transcript:

Business Intelligence Training Siemens Engineering Pakistan Zeeshan Shah December 07, 2009

© SAP 2008 / Page 2 1.Introduction to the SAP Business Intelligence 1.1.Importance of BI Today 1.2.Data Warehouses 1.3 OLTP & OLAP 2.Components of the BI System 2.1 Source Systems 3.Modeling 3.1Objects in BI 3.2 Modeling 4.Classic Star Schema Agenda

© SAP 2008 / Page 3 Business Intelligence Business intelligence (BI) is a broad category of applications and technologies for gathering, storing, analyzing, and providing access to data to help enterprise users make better business decisions. BI allows information systems to meet the following requirements required by decision makers: Coverage of all business processes: cross-system and cross-process analyses are becoming increasingly important High-quality decision-making support: The BI system must support the requirements of both operative and strategic management; only then is it possible to support decisions fully Short implementation time with less resources: As well being quick to implement, a Data Warehouse must enable simple and quick access to relevant data, avoiding the labor-intensive preparation of heterogeneous data

Business Intelligence In summary, “Business Intelligence software is the collection of applications needed to make sense of business data”.

Data Warehouses  The Data Warehouse, a component of the Business Intelligence tool set, is the more specific tool responsible for the cleanup, loading, and storage of the data needed by the business. A Data Warehouse can help to organize the data. It brings together all operative DataSources (these are mostly heterogeneous and have differing degrees of detail). A warehouse has the following properties:: Read-only access: Cross-organizational focus: Data Warehouse data is stored persistently over a particular time period. Designed for efficient query processing:

Business Environments  Business environments are divided into: OLAP (BI/Data Warehouse System ) OLTP Differences Between a BI/Data Warehouse System (OLAP) and an OLTP System Level of detail: History: Archiving data in the OLTP area means it is stored with minimal history Changeability: Frequent data changes are a feature of the operative area,while in the Data Warehouse, the data is frozen after a certain point for analysis Integration: In contrast to the OLTP environment, requests for comprehensive, integrated information for analysis are very high Read access: An OLAP environment is optimized for read access. It is most advantageous to technically separate all aggregated reporting- related demands made on the Data Warehouse from the OLTP system.

Components of the SAP BI system

 The BI database is divided into self-contained business information providers (InfoProviders). You analyze the database of BI by defining queries against these InfoProviders in the BEx Query Designer Data analysis based on multidimensional Data Sources (OLAP reporting) allows you to analyze more than one dimension of an InfoProvider (Time,place, and product) at the same time. you can make any number of variance analyses (plan/actual comparison and business year comparison) You can analyze data in the following areas in the Business Explorer BEx Analyzer (Microsoft Excel-based analysis tool with pivot-table-like features) BEx Web Analyzer (Web-based analysis tool with pivot-table-like features) BEx Web Application Designer (customer-defined and SAP BI Content provided) BEx Report Designer (highly formatted Web output)

Components of the SAP BI system

The Data Warehouse architecture is structured in three layers: sourcing the data, storing It in the warehouse, and reporting on it with analytics. Source Systems A source system provides the BI system with data. BI distinguishes between source systems: mySAP Business Suite Non-SAP systems – Flat files – Multidimensional sources from other Data Warehouses – XML: – Relational data in other database management systems Data providers Databases (DB Connect) or complex sources You can send data from SAP and non-SAP sources to BI using SAP Exchange Infrastructure (SAP XI) Data transfer using SAP XI is based on (SOAP).

Modeling An InfoProvider is an object for which queries can be created or executed in BEx. InfoProviders are physical objects or sometimes logical views that are relevant for reporting InfoCubes are the primary objects used to support BI queries. They are designed to store summarized and aggregated data, for long periods of time. DataStore objects are another primary physical database storage object used in BI. They are designed to store very detailed (transaction level) records.

Classifying InfoObjects InfoObjects are primarily divided into the major types Key figures or characteristics. – Time characteristics, – technical characteristics, and – units. Characteristics InfoObjects are used to analyze key figures, for example, Customer (characteristic) Sales (key figure).

The Classic Star Schema: The EDW Database Schema This database schema classifies two groups of data: Facts (sales amount or quantity, for example) and dimension attributes (customer, material, or time, for example) The fact data (values for the facts) is stored in a highly normalized fact table. The values of the dimension attributes are stored from a technical perspective, in various denormalized dimension tables In the star schema design shown, the key of the dimension tables is a machine-generated dimension key (DIM ID) that uniquely defines a combination of dimension attribute values The DIM ID (a sequentially assigned number) is a foreign key in the fact table. In this way, all data records in the fact table can be uniquely identified.

The Classic Star Schema: The EDW Database Schema

A InfoCube consists of precisely one fact table* in which key figure values are stored. A fact table can contains a maximum of 233 key figures. A InfoCube usually has a minimum of four dimension tables and a maximum of 16. Of these, 13 of the 16 are customer-created and three are the SAP-supplied dimensions: Units dimension table Data Package dimension table Time dimension table Customer dimensions contain SIDs linked to a maximum of 248 characteristics InfoObjects. Data Package and Time dimension tables are always present in a InfoCube Additional information about characteristics InfoObjects is referred to as master data in the BI system. A distinction is made between the following master data types: Attributes Texts (External) Hierarchies

© SAP 2008 / Page 17 Thank you!