Creating an Enterprise Reporting Bus with SAP BusinessObjects

Transcription

1 September 10-13, 2012 Orlando, Florida Creating an Enterprise Reporting Bus with SAP BusinessObjects Kevin McManus LaunchWorks Session : 0313

2 Learning Points By consolidating people, process, data and technology more can be accomplished together than alone By combining the benefits of a BICC, BUS, DW, and Adhoc Query Create a Common platform and standards for the creation and maintenance of reporting features that can be used across multiple applications that need reporting Create value added ways for users to access, analyze, and interact with data using web based tools that can be reused across projects (i.e. analysis grid, project calendar, Gantt charts)

3 Learning Points SAP BusinessObjects customers have a powerful reporting platform for creating reporting services that other web and mobile applications can tap into. Many Fortune 500 companies are using the technique of an enterprise reporting bus to integrate SAP BusinessObjects WebI and SAP Crystal Reports directly into the applications that end users need to report on. The flexibility of the universe and reports to connect to so many data sources make SAP BusinessObjects an excellent choice for connecting users to their data, no matter which application they are using.

4 Return on Investment Maintain a cohesive strategy by establishing guidelines, standards and governance around tool selection Reduce redundant effort/costs with new projects by using a centralized set of technology and services Reduce redundant effort/costs with new projects Reduce training costs with consistent User Interfaces

5 Takeaways 1. The top 10 SAP BusinessObjects reporting features that all your customer apps can use. 2. How to get started using SAP BusinessObjects in other applications. 3. The knowledge to introduce your company to the benefits of an enterprise reporting bus.

6 The Data Warehouse Institute (TDWI) BI Maturity Model Where are we? Most organization s IT have grown beyond running the company on spreadsheets. The next challenge is moving the current BI strategy into an Adult level Enterprise Data Warehouse and Sage Level BI/Reporting Services. 6 6

7 Summary Adhoc Query BI Portal Enterprise Reporting Bus Enterprise Data Warehouse 7

8 Definition of Terms BI Platform A platform supporting a layer of business logic on top of one or more databases used for canned reports, adhoc reporting & dashboards Reporting Tool An application supporting reporting functionality that is integrated into other applications to support the needs of that application s unique requirements around operational and management reports

9 Definition of Terms Adhoc Reporting Creation of new reports and queries where the tool, taking instructions from the user, writes the query based on rules captured in the semantic layer How the query needs to join between tables, and which calculations to use in a formula, are designed into the semantic layer before reports are created For example, the user is given control over the following features: Data Content, Report Layout, Query Filters, Prompts Adhoc Query Creation of new results where the tool connects the user to the data source and allows the user to write the query How the query needs to join between tables, and which calculations to use in a formula, are written by the user The user is given control over the following features Tables, Joins, Database Columns, Query Filters

10 The Data Warehouse Institute (TDWI) BI Maturity Model Are we here yet? 10 10

11 Gartner BI Maturity Model Are we here yet? Source: Gartner (2008) 11

12 Best Practices 1) Establish a Business Intelligence Competency Center (BICC) that oversees the tool selection, design, and governance during delivery of new reporting projects 2) Support an Enterprise Data Warehouse - accessed primarily by Web Intelligence for adhoc reporting - compliment with multi-source joining of data, dashboards and mobile - enable evaluation of OLAP tool consolidation later 3) Establish and analyze reporting requirements through a standard set of tool selection criteria. - Web Intelligence will access data in the Enterprise Data Warehouse for adhoc reporting.

13 Architecture Common Portal ERP SFA HR / PM Ordering EIS Enterprise Reporting Bus BI Platform Semantic Layer ODBC XML RDBMS Cubes DW Stored Procs

14 Best Practices Shared Authorization Layer Database, Active Directory, LDAP, SSO Standardized User Interface Report Lists, Report Menus, Integrated report calls, Scheduling Standardized User Interaction Elements Prompts, Parameters, Context Report Execution Initially Crystal Reports Future Potential Web Intelligence, Dashboards, Analysis, etc Output Interactive Viewer, , Distribution, Export (PDF, XLS, CSV), Alerts Authenticate & Authorize User Report List / Menu Prompts & Parameters Report Execution Report Output Interaction

15 Best Practices Create a POC of the Enterprise Reporting Bus using component requirements from one of the current and/or upcoming reporting initiatives 1) Created a common way to call reports to the standard viewer for View / Print / Export functionality on canned reports 2) Add common Prompt Handlers shared between applications + Prompt UI components are created based on report metadata vs. hard coding screens + Add Prompt types supporting Hierarchical dimension support 3) Add User Controlled Prompt Sets + Gives ability to Save, Retrieve and Share combinations of filter selections that users find valuable 4) Add an Interactive Viewer that takes the query output and provides additional functionality such as : + Grid View + Graph View + Column and sort control

16 Adhoc Query Introduce an Adhoc Query tool Introduce Web Intelligence Rich Client for building adhoc queries with direct access to databases where data is not yet part of the Enterprise Data Warehouse Web Intelligence Rich Client reports provide advanced data organization tools that can be run on the user s desktop Web Intelligence Rich Client documents, would then be shared, published, and supported through publication to BusinessObjects. With adhoc query content published to a server, rather than remaining on a user s local desktop, the risk of losing business knowledge is reduced This increased visibility will contribute to a data analysis process as part of the overall BI strategy By continuously analyzing the data, IT can best determine future data warehouse needs without inhibiting users from getting the data they need today

17 Adhoc Query Data Availability Joining Data Sources Local Data Sources Ability to publish / share in an editable format including viewing SQL and formulas

18 Adhoc Query Create a feedback loop where Adhoc reporting creates a queue of requirements for an incrementally enhanced Enterprise Data Warehouse (SWDW) while still meeting user s immediate needs for data Production Attribute needs for improved analysis are identified and prioritized (i.e. product, customer, geography) Create a process where the business rule input into new product attributes in the DW is gained from adhoc analysis feedback and publication to a shared repository using the PowerPivot tool

19 Adhoc Query Feedback Loop 1) Adhoc Need Identified 2) Source Identified 8) Training and Education on availability and use 3) Attributes Defined 7) SWDW dimension attributes expanded 4) Query / Business Rule Developed 5) Adhoc Need Met 6) Results Published and Reviewed

20 Moving Forward 1) Choose an current project that has Adhoc Reporting requirements Project #1 Embedded and On Demand Crystal Reports or Web intelligence Begin on Enterprise Reporting Bus Build Prompt Screens based on metadata vs. hard coded Add Grid View for column and sort control Build database connection as configurable based on application Work with BICC team on sourcing into Data Warehouse Project #2 Embedded and On Demand Crystal Reports or Web intelligence continued on Enterprise Reporting Bus Continue method of defining prompts started from first project Add report templates for Month, Week, Quarter and Year Calendars Add visibility through SharePoint plug-in/web UI to report list Work with BICC team on sourcing into Data Warehouse

21 Moving Forward 2) Introduce an Enterprise Reporting Bus (ERB) application as the standard method of delivering operational reporting functionality to custom web applications and portals An ERB is a shared web application tied to the BusinessObjects reporting engine The ERB will allow any web application that has reporting requirements to call the SRB as a method of embedding reporting functionality Introduce a shared BI portal (i.e. SharePoint, etc) as the preferred location of access to BI portal content. Review opportunities to consolidate from other portals Going forward, each new reporting requirement should be evaluated against its ability to utilize and contribute to the Enterprise Reporting Bus Create value added ways for users to access, analyze, and interact with data using web based tools that can be reused across projects (i.e. analysis grid, project calendar, Gantt charts) Leave 3 rd party applications as they are, unless new report integration is necessary and vendor technology allows linking

22 Best Practices State of Current Report Tools Report Types and Usage Functionality integrated into Applications Assess Timeliness of reports Processes of report creation Skills being used for reporting Recommend technological changes Recommend process changes including governance Strategize Establish guidelines for tool selection and usage Present future state benefits Formulate plan for reaching future state Plan Include applications, technology, and process components Prepare communication of results of assessment to key stakeholders Implement Assist with implementation of recommendations as needed

23 Demo Demo

24 Thank you for participating. Please provide feedback on this session by completing a short survey via the event mobile application. SESSION CODE: 0313 Learn more year-round at