Presentation Transcript

1. BUSINESS INTELLIGENCE (BI) SOLUTION FOR SALES ANALYSIS PROCESSUSING SAP NETWEAVER BUSINESS WAREHOUSE (BW) 7.3

   Satakarni Bommuluri Masters of Science Thesis Defense
2. Agenda Brief Review of Literature Motivation for the Study Objectives of the Study Assumptions Constraints Research Hypothesis Questions Project preparation Project blueprint and analysis Project realization Reports and results Go-live and support activities Revisiting - Research Hypothesis Questions
3. Brief Review of Literature – Big Data Big Data: sheer magnitude of data - volume, variety and velocity - structured and unstructured data. Goal : Structured Big Data  Analytical-reports OLTP vs. OLAP
4. Brief Review of Literature – Data Warehouse Data warehouse is a centralized and consistent collection of an organizational data in a structured format to enable users to interpret data for meaningful information and to gain knowledge from those interpretations. It is NOT a: Product, Language, Project, Data model, or a Copy or backup of transaction data. It organizes information with a: Subject-orientation, Integration, Granularity, Non-volatility, Partitioning of data, Evolutionary model.
5. Source Systems Data Warehouse BI Tools Data Mart ETL Tools Database ERP Server Data Mart Data Mart Flat Files Data Mart Staging Brief Review of Literature – Data Warehouse: Architecture
6. Brief Review of Literature – Data Mart: Star Schema Star Schema: General Extended Star Schema (SAP innovation)
7. Brief Review of Literature – BI Business Intelligence (BI) architecture is a framework of applications and technologies that includes ETL tools, data marts (of a data warehouse) and technology components that aid in the activities of DSS, query and reporting, OLAP, statistical analysis, forecasting, and data mining
8. Review of Literature – Need for BI Single version of truth Consolidated, harmonized and centralized information Establishment of Centralized or Enterprise Data Warehouse (EDW) Competitive Advantage Improved performance of an OLTP system
9. SAP Product History 40 years of SAP company history – refer Section 1.1.5.
10. SAP NetWeaver
11. History of SAP BW
12. (11)Portal (10)Excel (8)BEx Analyzer (9) W.A.D (7) BEx Query Designer (6)InfoProvider InfoCube, DSO, MultiProviders, etc (5) D.T.P (4)Transformation (2) DataSource/PSA (3) InfoPackage Source System: SAP, Non-SAP, Flat files Basic Concepts in BW
13. Case Study: VirtualXYZCorp : Organization Elements
14. Case Study: VirtualXYZCorp : SAP LANDSCAPE
15. Statement of the Problem Analysis-driven reports will facilitate the management and decision-makers of an organization: Market Competitiveness Establish future goals for the organization Off-loads OLTP system for reporting needs. To address these issues we propose using the SAP BW 7.3 system to build a data warehouse.
16. Motivation for the Study Unlike OLTP projects, it is not a step-by-step engineered methodology. BW Project is considered as an art with a principled center approach. we consider a Sales and Distribution (SD) Billing scenario of a hypothetical retail business company termed as VirtualXYZCorp – to devise successful strategies
17. Objectives of the Study Comprehend and present the concepts pertaining to Business Warehouse. Understand the SAP company and its history. Understand the (contemporary) products and solutions offered by SAP Gain practical knowledge and technical concepts to work with the SAP BW 7.3 system and SAP ECC 6.0 system. Study, consolidate, and execute the best implementation strategies. Derive conclusions, recommendations, and standard procedures for SAP BW 7.3implementation based on our thesis work.
18. Assumptions The SAP BW system is implemented in an existing SAP landscape. No attempt to compare the performance, easiness, or cost of the implementation of SAP BW 7.3 with other open source or vendor specific BI systems.
19. Constraints New implementation (do not discuss the upgrade strategies). The procedure for installation, configuration, and deployment of an SAP landscape is not explained. Data extraction from the SAP ECC system only. The scope of the project is limited to Sales and Distribution (SD) – Billing module.
20. Research Hypothesis Questions Based on the functional requirement document of Appendix A, can a BW system be developed to generate the following reports: For a given year and region (input by the user), what are the top selling products with their prices (in local currency) and net profits? For a given year and region (input by the user), what are the least selling products with their prices (in local currency) and net losses? For a given year and region (input by the user), what are the sales offices in descending order that are reporting high numbers of cash inflow? For a given year and region (input by the user), what are the sales offices in descending order that are reporting low numbers of cash inflow? Can the implementation strategies used in answering Hypothesis Question #1 be applied across various other business scenarios as a standard procedure?
21. How to assess BI solutions offered by various vendors? Define and state short-term goals and long-term goals. Draft a blueprint of the existing IT infrastructure. Estimate the size of data warehouses and the data movement for ETL processes. Document the roles and the number of participants. Do preliminary research through the internet, clients’ feedback, forum discussions, white papers and varia. BI vendor’s performance in stock exchanges and their future endeavors. End-to-end BI solution. Maturity in the Market Demo session.
22. Why we choose SAP BW? Visionary and global leader. Existing Landscape. Establishment and reputation (95% of fortune 500 + 47,000 clients) BI Content
23. Project Preparation – BW Team
24. Project Preparation – Requirement Gathering Interview stakeholders Understand the data What are the source systems for the data? Is the data scattered in multiple source systems? What is the volume of the data for daily ETL batch jobs? Should the daily data updates be delta or full? Do the data loading requirements demand real-time processing or batch jobs? Gather sample reports
25. Project Preparation – Requirement Gathering Our Findings Scope of the project: Billing process within Sales and Distribution (SD) subject area. The reporting requirements of the business are stated in Hypothesis Question. We have to execute two different ETL processes : Master data require a full update on a weekly basis. Transaction data need 1) a one-time full update of historical data and 2) consecutive nightly delta updates.
26. Functional Model Documentation Gathered Requirements  F.M.D. Gary Nolan “The better the effort up front getting this document as robust as possible, the better and more efficient the implementation process.” Refer Appendix A for F.M.D of current project.
27. Project Preparation Cont… BW Timelines BW Objects Naming Conventions (Table 3.1) Map Source R/3 Fields to BW InfoObjects (Refer Appendix B and Appendix C)
28. Gap analysis If a requirement matches exactly with a BC object specification, then install, activate, and use the BC object in the project. If a requirement matches vaguely with a BC object specification, then install, make necessary changes, activate, and use the BC object in the project. If a requirement match cannot be found in the SAP BC, then build a custom BW object, activate, and use the custom object in the project. Refer Section 3.9 for the gap analysis performed for current thesis.
29. Conceptual Model Functional specification + Object Matrix + Gap Analysis  Technical Specification Sold-to-party Characteristic InfoObject.(Appendix D) Billing-Quantity KeyFigure InfoObject.(Appendix E) DSO. (Appendix F) Standard InfoCube. (Appendix G)
30. Project Realization (Refer Ch. 4) Install and Activate Business Content Create Characteristic InfoObject Catalog Create Characteristic InfoObject Create KeyFigure InfoObject Catalog Create KeyFigure InfoObject Create DSO Creating InfoCube Master Data Extractions from ECC to BW Transaction Data Extractions from ECC to BW Building Queries
31. BEx Reports – Live Demo Sample Report
32. Go-live Transport Management Testing (Unit, Integration, Stress, Operational Readiness ) Cutover Plan Go-Live
33. Answering Hypothesis Questions Hypothesis Question #1 Yes, we were able to develop a BW system that is compliant with the functional document posted in Appendix A to generate the reports as per Section 1.7. Hypothesis Question #2 We able to present BW implementation strategies that can be applied to various other business scenarios, such as Account Payable (AP), Account Receivable (AR), General Ledger (GL), and Material Management (MM).