1 / 23

SAP Decision Support Environments in Higher Education

SAP Decision Support Environments in Higher Education. Session Code: 2204. Todd Orr, Duke University Neal Wormsley, University of Tennessee. Duke University Background. Duke University & Duke University Health System $2.2 billion in revenue 30,000 employees

thuyet
Download Presentation

SAP Decision Support Environments in Higher Education

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SAP Decision Support Environments in Higher Education Session Code: 2204 Todd Orr, Duke University Neal Wormsley, University of Tennessee

  2. 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

  3. 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

  4. 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

  5. Original DSS Design Supported Query & Reporting Tool(s) - canned and ad hoc reports Hyperion Supported OLAP Tool(s) Standard Financial Reporting Tool Security Authorization Layer R/3 Decision Support Database Summary Financial Data by Period Position and Employee Data Summary Procure- ment Data Data Extraction Layer • Monthly/Quarterly/Annual Updates • Pay Period Updates R/3 Production Database Financial HR/Payroll Procurement

  6. 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

  7. 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

  8. 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

  9. Financial DSS Model Standard ABAP Extract each month DSS Staging Area R/3 SQL/Oracle tools to load DSS tables DSS Tables Standard monthly extract Standard monthly extract Queries via MS Access, Bio Query, etc. Hyperion Enterprise Hyperion Essbase Central/Mgt Ctr Users Consolidated Health System financial reporting University web-based financial reporting Ad-hoc query & reporting

  10. 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

  11. 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

  12. SAP Software • Purchased SAP software in June 1999 • Implementation began February 2000 • Phased Go-Live Financials - April and May 2001 Business Warehouse - May 2001 HR and Payroll - July 2001 WorkPlace – Pilot May 2001 Knowledge Warehouse/iTutor - ?? • 2,000 named users

  13. 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

  14. 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

  15. 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

  16. SAP BW Implementations & Architecture

  17. SAP BW Implementations & Architecture

  18. SAP BW Implementations & Architecture

  19. SAP BW Implementations & Architecture

  20. BW Reporting Tool • BEx Analyzer is implemented as an add-in to Microsoft Excel • Tool that is used to: Define queries Execute queries Data is analyzed Workbooks are listed

  21. Business Explorer Analyzer

  22. Business Explorer Browser

  23. Thank you for attending! Please remember to complete and return your evaluation form following this session. Session Code: 2204

More Related