Upload
camron-hines
View
213
Download
0
Tags:
Embed Size (px)
Citation preview
SAP Decision Support Environments in Higher Education
Todd Orr, Duke UniversityNeal Wormsley, University of Tennessee
Session Code: 2204
Duke University Background
• Duke University & Duke University Health System– $2.2 billion in revenue– 30,000 employees– DUHS composed of 3 hospitals, physician practices,
hospice, and other health related entities
• In production with FI/CO/MM/FM/PS/AM since March 1999– Initial focus on Health System; 1,800 current users– Rollout of financials to University in next two years
• Implementing SAP HR/Payroll - go live by end of 2001
If We Have R/3, Why DSS?
• Difference between OLTP and OLAP– OLTP: On Line Transaction Processing
- R/3– OLAP: On Line Analytical Processing -
DSS
• DSS/OLAP allows us to leverage the investment in R/3
• Existing Duke experience with query/OLAP tools
Role of Decision Support at Duke• Decision Support (DSS) key component of
our original design for R/3 strategy because:– Lack of easy-to-use query and reporting tools in
R/3– Problems associated with running reports &
queries against the production database– Limited accessibility of R/3 for query & reporting
• DSS planned to provide financial, procurement and HR/Payroll data
• DSS for Duke is not data warehousing
Original DSS Design
R/3 Production Database
Financial HR/Payroll Procurement
R/3 Decision Support Database
Summary FinancialData by Period
Position and Employee Data
Summary Procure- ment Data
Supported Query &Reporting Tool(s) -canned and ad hocreports
Hyperion
StandardFinancialReportingTool
Supported OLAPTool(s)
Security Authorization Layer
Data Extraction Layer •Monthly/Quarterly/Annual Updates•Pay Period Updates
Duke DSS Tool Environment• Investigated ETL tools
(Informatica, SAS)• DSS data stored in Oracle; use
standard Oracle tools• Front-end tools:
– Hyperion Enterprise– Hyperion Essbase– Query tools: Access, Brio Query
Why not BW?
• Duke reviewed BW in 1999 when it was at version 1.2; first version left a lot to be desired
• Existing investment in other OLAP tools (Essbase)
• Level of overhead associated with BW implementation
• BW in context of larger data warehouse strategy at Duke
• Door is still open
DSS Current Status
• Financial DSS was completed this month– Series of Oracle tables/views– Summarized actuals/budgets at the Fund-
Commitment Item-Fiscal Period-Fiscal Year level– Source for extracts to front-end tools (Essbase)– Directly accessible with query tools
• Procurement DSS– Requirements analysis underway– Will be looking at front-end tools
• HR/Payroll DSS - need to go live first
Financial DSS Model
R/3DSS Staging Area
DSS Tables
Hyperion Essbase
Hyperion Enterprise
Central/Mgt Ctr Users
Standard ABAP Extract each month
SQL/Oracle tools to load DSS tables
Standard monthly extract
Standard monthly extract
Queries via MS Access, Bio Query, etc.
Consolidated Health System financial reporting
University web-based financial reporting
Ad-hoc query & reporting
The University of Tennessee• Land Grant Institution in Tennessee• $1.2 billion in revenue• 30,000 active accounts• 24,300 employees
14,650 regular employees 2,050 temporary
7,600 student employees• 3,900 faculty
The University of Tennessee System• Chattanooga• Knoxville• Martin• Tullahoma• Medical School in Memphis• Institute of Agriculture• School of Veterinary Science• Institute for Public Service• University Administration
SAP Software
• Purchased SAP software in June 1999• Implementation began February 2000• Phased Go-Live
Financials - April and May 2001
Business Warehouse - May 2001HR and Payroll - July 2001
WorkPlace – Pilot May 2001Knowledge Warehouse/iTutor - ??
• 2,000 named users
SAP Business Information Warehouse
• A separate application (add on)
• Is independent from SAP R/3. Has its own release and shipment cycle.
• SAP R/3 processes the University’s day-to-day business activities with limited reporting
• BW is an application that supports business decisions and management
BW offers the best Solution for UT’s Data Warehousing• Integrated with SAP IRIS
• Delivered Business Content• WorkPlace Integration • WEB Enabled• Support Using existing knowledge base
– BASIS– ABAP
• Integrated front to back One Solution– Extraction– Administration– Query
Role of Business Warehouseat University of Tennessee
• To provide an integrated database used solely for management reporting
• To support automated standardized reporting for individuals who have MySAP.com Workplace
• To provide a warehouse for data generated from various systems within the University, including
- SAP R/3 - Legacy systems (Financial, HR and Payroll)- Student systems- Alumni and Development system
SAP BW Implementations & Architecture
ã 1999 SAP America, Inc. (L. Gulik) / 13
l BW is delivered with significant and increasingBusiness Content
w Delivered extraction from R/3
l Financials, Logistics, HR
l Key Performance Indicators
l Industry Specific information
l This enables tight integration when R/3 used as asource
w Drill down from BW to R/3 data
BW - A Complete Low-cost solution
SAP BW Implementations & Architecture
ã SAP AG 2000 BW Overall / 38
Business Content Growth Rates
0%100%200%300%400%500%600%700%800%900%
1000%1100%1200%1300%1400%1500%
1.2A 1.2B 2.0A 2.0B
InfoObjects InfoSources InfoCubes Queries
Workbooks Channels Appl./IBUs/NDIs
SAP BW Implementations & Architecture
ã SAP AG 2000 BW Overall / 36
2 months3% 3 months
18%
4 months18%
5 months6%
6 months31%
> 6 months24%
Implementations in 1999
l Implementation time varies depending on project scope
l Project Scope Averages
n Users 120 (20 to 500)
n InfoCubes 15
n Queries 40
n Team 7
SAP BW Implementations & Architecture
ã SAP AG 2000 BW Overall / 18
BW
SERVER
BEx
ODS 2.0B Architecture
Transfer RulesTransfer RulesTransfer RulesTransfer Rules Update RulesUpdate RulesUpdate RulesUpdate Rules
Operational Data StoreOperational Data Store
DataSource 1
PSA PSA
Update RulesUpdate RulesUpdate RulesUpdate Rules
OLAP Processor
3rd Party OLAP Clients
ODBOODBO
3rd Par tyOLAP Cl ients
3rd Par tyOLAP Cl ients
3rd Par tyOLAP Cl ients
3rd Par tyOLAP Cl ients
3rd Par tyOLAP Cl ients
3rd Par tyOLAP Cl ients
DataSource 2 DataSource 2
Transfer RulesTransfer Rules
BW Reporting Tool
• BEx Analyzer is implemented as an add-in to Microsoft Excel
• Tool that is used to:Define queriesExecute queriesData is analyzedWorkbooks are listed
Business Explorer Analyzer
Business Explorer Browser
ã S AP A G 2000 B W Overall / 9
Web Reporting
Thank you for attending!Please remember to complete and return your evaluation form following this session.
Session Code: 2204