Sap bi 7.3 Features


Published on

SAP BW 7.3 Features by samar reddy

Published in: Education, Technology, Business
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Sap bi 7.3 Features

  1. 1. SAP BW 7.3 – New Features Demo
  2. 2. <ul><li>Agenda </li></ul><ul><li>Introduction to SAP BW 7.3 New Features </li></ul><ul><li>Semantically Partitioned Info provider </li></ul><ul><li>Hybrid Provider </li></ul><ul><li>Data Flow Concept </li></ul><ul><li>BO Analysis </li></ul>
  3. 3. <ul><li>Introduction to </li></ul><ul><li>SAP BW 7.3 New Features </li></ul>
  4. 4. <ul><li>SAP BW 7.3 has lot of new features and enhancements of which the following will be covered in this session, </li></ul><ul><ul><li>Semantically Partitioned Infoprovider </li></ul></ul><ul><ul><li>Hybrid Provider </li></ul></ul><ul><ul><li>Data Flow Copy </li></ul></ul><ul><ul><li>Data Flow Migration </li></ul></ul><ul><ul><li>BO Analysis </li></ul></ul><ul><ul><li>The Key benefits of BW 7.3 are as follows, </li></ul></ul><ul><ul><li>Enhanced Scalability & Performance for faster decision making </li></ul></ul><ul><ul><ul><li>• Remarkably accelerated data loads </li></ul></ul></ul><ul><ul><ul><li>• Next level of performance for BW Accelerator </li></ul></ul></ul><ul><ul><li>2. Increased flexibility through SAP BusinessObjects BI and EIM integration </li></ul></ul>
  5. 5. <ul><li>Semantically Partitioned Info provider </li></ul>
  6. 6. <ul><li>Architecture </li></ul>
  7. 7. Semantically Partitioned Infoprovider <ul><li>A semantically partitioned object is an InfoProvider that consists of several InfoCubes or DataStore objects with the same structure. </li></ul><ul><li>Semantic partitioning is a property of the InfoProvider. We specify this property when creating the InfoProvider. Semantic partitioning divides the InfoProvider into several small, equally sized units (partitions). </li></ul><ul><li>Wizard based creation of data models + data flows </li></ul><ul><li>Reduced development and maintenance overhead </li></ul><ul><li>Easy re-modeling of the partitions on an ongoing basis and Embeddable into data flows or data models </li></ul><ul><li>In-Memory SAP NetWeaver BWA support </li></ul>
  8. 8. Demo
  9. 11. <ul><li>Hybrid provider </li></ul>
  10. 12. Architecture
  11. 13. Hybrid provider <ul><li>Hybrid provider consists of a DataStore object/Virtual Provider and an InfoCube. It has data flow in between them automatically generated while creating the hybrid provider. It combines the historic data with latest delta information when a query based on it is executed. </li></ul><ul><li>The „hybrid‟ structure of this InfoProvider ensures excellent performance with near real time reporting on high volumes of data, as it provides faster access to data. This becomes even more efficient when BWA is used. </li></ul><ul><li>There are two types of Hybrid Providers: </li></ul><ul><ul><li>1. HybridProviders based on direct access. </li></ul></ul><ul><ul><li>2. HybridProviders based on a DataStore object. </li></ul></ul>
  12. 14. <ul><li>HybridProviders based on Direct Access </li></ul><ul><li>HybridProvider based on direct access is a combination of a VirtualProvider and an InfoCube. The benefit of this InfoProvider is that it provides access to real time data without actually doing any real time data acquisition. </li></ul><ul><li>At query runtime, the historic data is read from the InfoCube. Also the near real-time or the latest up-to-date data from the source system is read using the Virtual Provider. </li></ul><ul><li>Hybrid Providers based on a DataStore object </li></ul><ul><li>The HybridProvider based on a DSO is a combination of DSO and InfoCube. Once this Hybrid Provider is created and activated, the different objects including (DTP, Transformation and process chain) that are used for the data flow from the DSO to the InfoCube are created automatically. </li></ul><ul><li>One should use HybridProvider based on DSO as InfoProvider in scenarios where there is need to load data using real time data acquisition. The DTP for real-time data acquisition from a real-time enabled Datasource to the DSO loads the data to the DSO in delta mode. The daemon used for real-time data acquisition immediately activates the data. As this daemon is stopped, the data is loaded from the change log of the DSO to the InfoCube. The InfoCube acts as storage for the historic data from DSO. </li></ul>
  13. 17. <ul><li>Data Flow Concept </li></ul>
  14. 18. Data Flow Concept <ul><li>Data Flow Wizard </li></ul><ul><li>Wizard based data flow modeling and generation of all related </li></ul><ul><li>data flow objects including new InfoObjects as needed </li></ul><ul><li>Data Flow Copy </li></ul><ul><li>Copy an existing SAP NetWeaver BW 7.x data flows, i.e. DataSources, data targets, and Transformations leveraging a “wizard like” user interface </li></ul><ul><li>Complete copy of an existing process chain (including related process variants) </li></ul><ul><li>Data Flow Migration </li></ul><ul><li>Migration of data flows with SAP NetWeaver BW 3.x objects </li></ul><ul><li>“ Workbench-like” UI for selecting data flows and objects to be migrated </li></ul><ul><li>Migration can be repeated/reversed as often as needed </li></ul>
  15. 19. <ul><li>BO Analysis </li></ul>
  16. 20. <ul><li>SAP BusinessObjects Analysis, edition for Microsoft Office, is a Microsoft Office Add-In that allows multidimensional analysis of OLAP sources in Microsoft Excel, MS Excel workbook application design, and intuitive creation of BI presentations with MS PowerPoint. </li></ul><ul><li>In the edition for Microsoft Office, you can use SAP BEx Queries, query views and SAP Netweaver BW InfoProvider as data sources. The data is displayed in the workbook in crosstabs. You can insert multiple crosstabs in a workbook with data from different sources and systems. If the workbook will be used by different users, it is also helpful to add info fields with information on the data source and filter status </li></ul>