Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

Chapter 2. The SAP NetWeaver BI perspect... > SAP NetWeaver BI solution configurat... - Pg. 72

ODS objects are simply flat tables and generally hold very detailed data. They are often used as staging areas themselves to seed InfoCubes, or used as means to integrate different areas of data (sales, stock and so on) into secondary ODS objects to preprocess data before loading to InfoCubes. For example, it may be that complex update rules (transformations) can be managed in the ODS layer once, and then reused several times into many InfoCubes rather than having to run the update rules for each individual InfoCubes. ODS objects can also be used for simple SAP NetWeaver BI queries, such as for getting information about a single invoice. Finally, ODS objects may be used as input data store for other SAP NetWeaver BI or external system (by use of the infohub capability now in SAP NetWeaver BI). SAP NetWeaver BI InfoCubes are multi-dimensional data structures represented by multiple tables in a relational database (SAP sees this as an extended star schema). They are designed to isolate the master data from the dimensional models and potentially offer good performance. As with other data warehouses, online analytical processing (OLAP) is the primary use of the SAP NetWeaver BI. When executing a SAP NetWeaver BI query from the user interface, the query is transferred to the SAP NetWeaver BI application server, where it is processed by the OLAP processor. Based on the SAP NetWeaver BI meta data, the OLAP processor generates SQL statements that access the InfoCube, ODS, and master data tables. It then returns the SAP NetWeaver BI query result to the user interface. 2.2 SAP NetWeaver BI solution configuration: the logical views IBM has for many years been developing the Global Services Method 2 , which is an approach