1 / 62

A Comprehensive Guide to Building or Improving Your Enterprise Data Warehouse with SAP NetWeaver BW 7.3

A Comprehensive Guide to Building or Improving Your Enterprise Data Warehouse with SAP NetWeaver BW 7.3. Dr. Bjarne Berg COMERIT. In This Session …. Take a look at the latest enterprise data warehousing capabilities in SAP NetWeaver ® BW 7.3 Examine new data modeling capabilities

brant
Télécharger la présentation

A Comprehensive Guide to Building or Improving Your Enterprise Data Warehouse with SAP NetWeaver BW 7.3

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. A Comprehensive Guide to Building or Improving Your Enterprise Data Warehousewith SAP NetWeaver BW 7.3 Dr. Bjarne Berg COMERIT

  2. In This Session … • Take a look at the latest enterprise data warehousing capabilities in SAP NetWeaver® BW 7.3 • Examine new data modeling capabilities • Understand SAP’s vision for SAP NetWeaver BW, and its evolution into an in-memory EDW solution. Gain insight into the deployment of SAP HANA data marts. • Get insight into the new ETL interface, new management monitoring tools, the hybrid provider options for real-time data warehousing in SAP NetWeaver BW 7.3, and the capabilities of the Layered Scalable Architecture (LSA) • Understand how in-memory technology impacts data warehousing capabilities, existing SAP NetWeaver BW customers, and the SAP data warehousing roadmap

  3. What We’ll Cover … • New Administrative Cockpit Capabilities • The New Semantic Partition (SPO) Options • The HybridProvider and Real-Time Data • Faster Data Load and New Design Options • Front-End and Security Benefits • Using SAP NetWeaver BW 7.3 for Performance - Real Examples • New In-Memory Possibilities with SAP NetWeaver BW 7.3 and SAP NetWeaver BW Accelerator 7.2 • Wrap-up

  4. New 7.3 Performance and Admin Monitoring Capabilities • New monitors include: • Monitor of database usage and object sizes (i.e., InfoCubes, DSOs) • Query usage statistics are more visible (similar to RSRT, RSRV, RSTT) • We can see more of the use of SAP NetWeaver BW Accelerator and sizes • Monitor for the actual use of OLAP/MDX Cache and hit ratios • You can now selectively delete internal statistics in RSDDSTATWHM by date through the updated RSDDSTAT_DATA_DELETE ABAP program • There is also a new MDX Editor for coding and syntax assistance Solution Manager has been updated to take advantage of these new monitors.

  5. New 7.3 Performance and Admin Monitoring Capabilities (cont.) • Other new monitors include: • DEAMON update information (i.e., RDA capacity status, usage) • A performance monitoring workbench for performance trends • Process chain monitoring (new transaction: RSPCM) with error and active chain monitoring, user specific displays, and performance threshold monitoring (i.e., for SLAs) NLS: In SAP NetWeaver BW 7.3, the Near Line Storage has been enhanced to include archiving, support for write optimized DSOs, and database support for tools such as DB2 Viper (v9.5) and more 4

  6. New: Specific Database Support — IBM DB2 • IBM DB2: 7.3 supports specific database features: • DB2 v9.5 supports PSA, DSO, and fact table compressions for reduced disk volume (integrates with DB2 storage management) • Support for MDC clustering in the DB Cockpit. This is available in v9.5.2. or higher and is the default for all DSO tables and PSA in version 9.7. • Much faster request deletion if MDC clustering is used • DB2 v9.7 supports Index compressions for reduced disk volume • Support for IBM DB2’s DPF (Database Partitioning Feature) In the past, SAP NetWeaver BW has been unable to take advantage of vendor specific database features. This is changed, and fewer workarounds are needed.

  7. What We’ll Cover … • New Administrative Cockpit Capabilities • The New Semantic Partition (SPO) Options • The HybridProvider and Real-Time Data • Faster Data Load and New Design Options • Front-End and Security Benefits • Using SAP NetWeaver BW 7.3 for Performance - Real Examples • New In-Memory Possibilities with SAP NetWeaver BW 7.3 and SAP NetWeaver BW Accelerator 7.2 • Wrap-up

  8. Semantic Partitioned Objects (SPO) • When data stores and InfoCubes are allowed to grow over time, the data load and query performance suffers • Normally objects should be physically partitioned when the numbers of records exceed 100 million • However, this may be different depending on the size of your hardware and the type of database you use • In SAP NetWeaver BW 7.3 we get an option to create a Semantic Partitioned Object (SPO) through wizards • You can partition based on fields such as calendar year, region, country, etc.

  9. Semantic Partitioned Objects (SPO) (cont.) • When an SPO is created, a reference structure keeps track of the partitions. The structure is placed in the MultiProvider for querying. Source: SAP AG, 2011 SPO Wizards create all Data Transfer Processes (DTP), transformations, filters for each data store, and a process chain automatically.

  10. What We’ll Cover … • New Administrative Cockpit Capabilities • The New Semantic Partition (SPO) Options • The HybridProvider and Real-Time Data • Faster Data Load and New Design Options • Front-End and Security Benefits • Using SAP NetWeaver BW 7.3 for Performance - Real Examples • New In-Memory Possibilities with SAP NetWeaver BW 7.3 and SAP NetWeaver BW Accelerator 7.2 • Wrap-up

  11. The New HybridProvider and Real-Time Data • The “HybridProvider” (HP) is new in SAP NetWeaver BW 7.3. The core idea is to link the historical data inside BW with real-time data. • There are two ways of implementing an HP: • HP based on a DSO • HP based on a Virtual InfoCube

  12. Option 1: The DSO-Based HybridProvider • Core features: • Real-time data is in the DSO and historical data in the SAP NetWeaver BW Accelerator-based InfoCube • The DSO use real-time data acquisition (RDA) to load data • SAP NetWeaver BW automatically creates a process chain for the HybridProvder’s data flow • The process chain is executed for every closed request This solution provides for really fast queries, but delta logic has to be custom designed

  13. Option 1: The DSO-Based HybridProvider (cont.) • This solution provides for really fast queries, but delta logic has to be custom designed and may be complex. However, the solution allows for high-frequency updates and very rapid query response. This is a good option if you have a low volume of new records and a high number of queries or operational dashboards

  14. Option 2: The Virtual Cube-Based HybridProvider • Core features: • Data is read in real-time from SAP ECC, while historical data is read from SAP NetWeaver BW Accelerator • The difference depends on how often SAP NetWeaver BW Accelerator is loaded • Non-complex data logic can be applied • DTP is permitted if you do not filter the data set Virtual cubes with many users may place high-stress on the ERP system

  15. What We’ll Cover … • New Administrative Cockpit Capabilities • The New Semantic Partition (SPO) Options • The HybridProvider and Real-Time Data • Faster Data Load and New Design Options • Front-End and Security Benefits • Using SAP NetWeaver BW 7.3 for Performance - Real Examples • New In-Memory Possibilities with SAP NetWeaver BW 7.3 and SAP NetWeaver BW Accelerator 7.2 • Wrap-up Hint for Experts: The search feature in the SAP NetWeaver BW 7.3 Admin Workbench has been improved so that it is easier to search more items such as process chains.

  16. Faster Data Load and New Design Options — Activation • During activation, SAP NetWeaver BW 7.0 has to lookup in the NIRV table to see if the object already exists • This can be a slow process • In SAP NetWeaver BW 7.0 we may buffer the number ranges to compare the data load with records in-memory • This speeds up data activation • However, in SAP NetWeaver BW 7.3, the data activation is changed from single lookups to package fetch of the active table, resulting in faster activation and less locks on the lookup tables • The new method may result in 15-30% faster data activation (20-40% in lab tests)

  17. Faster Data Load and New Design Options — Activation (cont.) • For data transformations, the option “Read from DataStore” for a faster data lookup is also available • Additionally, the use of navigational attributes as sources in Masterdata transformations reduce overhead for lookups • Combined, this may lead to an additional 10-20% improvement The 7.3 initial load runtime option “Insert only” and the “Unique data records only” prevents all lookups during activation

  18. New Data Design Options — Delta, Init, and Web Services • In SAP NetWeaver BW 7.3 you can create generic delta extraction for the Universal Data (UD) and Database Connect (DB) options, as well as for flat files • Additionally, you can use the new DataSource adapter “Web Service Pull” to load data from external Web services • You can even create generic Web services delta loads and load the new data straight into the staging area of SAP NetWeaver BW 7.3 • While Web services does not support hierarchies yet, there is now integration of hierarchies into the standard process flow such as transformation and DTPs, as well as being able to load hierarchies from flat files using a new DataSource When you use delta loads, the first time SAP NetWeaver BW 7.3 automatically defines it as an “init load.” After that, it automatically switches to “delta” as the InfoPackage mode (no need to define it anymore!)

  19. New Options — ETL Interface and Shut-Downs • SAP NetWeaver BW 7.3 has a new interface to create and manage data flows graphically in a “drag-and-drop” manner, including: • Data Flow Copy to copy data flows and process chains • Data Flow Migration to migrate, or reverse migrate, data flows with automatic adoption of InfoPackages and process chains Source: SAP AG, 2011 Use “RS_SYSTEM_SHUTDOWN” to restart an application server and suspend RDA and process chains and re-start them in a controlled manner. Data loads are not in “flux” and you do not have to clean up partial loads.

  20. The New DataFlow Generation Wizard • A great benefit is that the wizards work against any InfoProvider; i.e., you can use the wizards to create loads from DSOs to DSOs or InfoCubes • SAP NetWeaver BW 7.3 has a new, step-by-step wizard that allows you to generate data flows from flat files or existing data sources This wizard reduces the number or manual steps needed to load data. It also simplifies the development process and makes ETL work much easier.

  21. Layered Scalable Architecture (LSA) – New Templates • The LSA consists logically of: • Acquisition layer • Harmonization/quality layer • Propogation layer • Business transformation layer • Reporting layer • Virtualization layer SAP BW 7.3 SP-3 has a set of 10 templates to help build a layered data architecture for large-scale data warehousing Source: sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/24800

  22. What We’ll Cover … • New Administrative Cockpit Capabilities • The New Semantic Partition (SPO) Options • The HybridProvider and Real-Time Data • Faster Data Load and New Design Options • Front-End and Security Benefits • Using SAP NetWeaver BW 7.3 for Performance - Real Examples • New In-Memory Possibilities with SAP NetWeaver BW 7.3 and SAP NetWeaver BW Accelerator 7.2 • Wrap-up

  23. Security Changes and New Mass Change Feature • When companies upgraded from SAP NetWeaver BW version 3.5 to 7.0, security migration was optional and many did only a technical upgrade and kept the “obsolete authorization” concept. A security migration is now required. Great BW 7.3 Security Admin Feature: You can make mass changes to authorizations instead of one-by-one. This can be done by cut-and-paste in a worklist, hierarchy nodes, and you can also add users to multiple analysis authorizations. SAP recommends you migrate to the new concept before upgrading a 7.0 system.(Notes: 931898; 938871; 946724, 958665; 1001652)

  24. Security Features in SAP NetWeaver BW 7.0 and 7.3 • Some companies did not do a security conversion in SAP NetWeaver BW 7.0 since items such as 0TCTAUTHH did not migrate (manually reassigned for the hierarchies) and passwords became case sensitive. Now it is required. • SAP NetWeaver BW 7.0 still has the ABAP migration tool. It can be used in SA38 (RSEC_MIGRATION), and migration can occur before the upgrade. Authorizations are building blocks of the 7.0/7.3 reporting concept and security contains both the data value and hierarchy restrictions. Security can be built using the “RSECADMIN” transaction 23

  25. BW 7.0 and 7.3 Authorization Objects Authorization objects for the Data Warehousing Workbench: S_RS_DS: For the DataSource or its sub objects (BI 7.x) S_RS_ISNEW: For new InfoSources or their sub objects (NW BI 7.x) S_RS_DTP: For the data transfer process and its sub objects S_RS_TR: For transformation rules and their sub objects S_RS_CTT: For currency translation types S_RS_UOM: For quantity conversion types S_RS_THJT: For key date derivation types S_RS_PLENQ: Authorizations for maintaining or displaying the lock settings S_RS_RST: Authorization object for the RS trace tool S_RS_PC: For process chains S_RS_OHDEST: Open Hub Destination Authorization objects for the Business Explorer: S_RS_DAS: For Data Access Services S_RS_BTMP: For BEx Web templates S_RS_BEXTX: Authorizations for the maintenance of BEx texts Authorization objects for the Admin of analysis authorizations S_RSEC: Authorization for assignment and administration of analysis authorizations S_RS_AUTH: Authorization object to include analysis authorizations in roles Changed Authorization Objects: S_RS_ADMWB (Data Warehousing Workbench: Objects): New sub objects: CONT_ACT – Installing Business Content; USE_DND - Drag & Drop to InfoAreas and application components; CNG_RUN - Attribute change run After the required security conversion you have access to lower security granularity for developers and users.

  26. What We’ll Cover … • New Administrative Cockpit Capabilities • The New Semantic Partition (SPO) Options • The HybridProvider and Real-Time Data • Faster Data Load and New Design Options • Front-End and Security Benefits • Using SAP NetWeaver BW 7.3 for Performance - Real Examples • New In-Memory Possibilities with SAP NetWeaver BW 7.3 and SAP NetWeaver BW Accelerator 7.2 • Wrap-up

  27. How To Leverage SAP NetWeaver BW 7.3 for Performance • In this section we will explore post implementation reviews from a few real companies and see how version 7.3 may help in achieving faster load, query, and response times • All examples come from real companies, but their names have been removed SAP NetWeaver BW 7.3 has many performance benefits that can be retrofitted to earlier implementations. The trick is to use the upgrade as an opportunity fix older designs.

  28. Background – BW System Overview Real Example • This system has the following characteristics: • The system is medium sized in terms of data volume, but has a substantial hardware configuration Database: Oracle version 10.2.0 BW system: BW version 7.0 with content 7.0.4; Patch level 7 BPC system: BPC content 7.0; Patch level 8 Operation systems: Linux 2.6 for BWA; AIX 6.1 for one app server and Solaris 10 for two app servers. Kernel: 701, patch level 94 (newer patches existed) This company should upgrade to SP-9, it contained performance improvements. Lessons learned: Keep an eye on new ServicePacks

  29. More System Background Real Example • The system has been in production for several years and has was upgraded two years ago • Currently, there are over 700 InfoProviders in the system Most InfoCubes followed standard development guidelines, but some had abnormalities such as InfoCubes feeding DSOs. Lessons learned: structured design review sessions should be undertaken as part of every project to assure that this does not continue.

  30. Users, Security, and Waits Real Example • In January, there were 474 users logged on to the system (including developers and basis staff) • Of these, 16 executed more than 400 navigation steps (high usage) • 90 had moderate activity • 368 had low activity • 2,271 users are allowed to see all reports in the system, and can also list the content of all database tables. This is an unusual security configuration that should be revisited as soon as possible. The customer should work with Network admin to determine capacity towards the servers. During dialog with the servers, the average user experienced a GUI wait time of almost 220 ms, indicating slow network connectivity to the servers.

  31. Database Growth and Cleanup Real Example • The database has grown between 12 and 344 Gb each month for the last year • Three months of the year saw data, logs, and PSA cleaned. Data volume declined between 63 and 275 Gb those months The database has grown by 732Gb (26%) in the last year, and the growth is uneven. To do: Schedule “housekeeping” jobs. Better management of cleanup would result in more predictable patterns. (i.e. we found PSA data that had 10 months of load history).

  32. Database Performance — RSA1  Manage InfoCubes Performance Real Example • Database statistics are used by the database optimizer to route queries.Outdated statistics leads to performance degradation. • Outdated indexes can lead to very poor search performance in all queries where conditioning is used (i.e., mandatory prompts) • The current sampling rates (3% for some cubes) are too low, and statistics should only be run after major dataloads, and be scheduled weekly Most database statistics are outdated and cause database performance to perform significantly poorer than otherwise would be the case. Sampling should be changed and process chains should be re-scheduled.

  33. DSO Design and Locks on Large Oracle Tables Real Example Many of the very large DSOs are not partitioned, and several objects have over 250 million records Additionally, 101 DSO objects are flagged as being reportable. This results in System IDs (SIDs) being created during activation. I.e., 87 million SIDs for 0CO_ITEM_NO and 65 million SIDs for 0DOC_NUMBER Combined, these result in frequent locks on the Oracle database and failed parallel activation jobs FIX: Partition DSOs. The lock on very large DSOs during parallel loads are well known and SAP has issued several notes on the topic: 634458 'ODS object: Activation fails - DEADLOCK' 84348 'Oracle deadlocks, ORA-00060.'

  34. BW 7.3 InfoCube Design Real Example • Many InfoCubes are very large and not partitioned • Several have over 100,000,000 records and one is approaching 0.5 billion (a stats cube where much of the data should be removed) • We strongly recommend that most of these cubes are physically partitioned, and that a multiproviders with hints are used instead • This can also be implemented in SAP NetWeaver BW Accelerator 7.2 if the relevant cubes are indexed. InfoCubes should be performance tuned if the number of records exceeds 30 million and partitioned before they are approaching 100+ million records. This creates faster loads, better query performance, and easier management.

  35. Recommended Use of MultiProvider Hints in 7.3 (non-SPO) Real Example • If a query has restrictions on this characteristic, the OLAP processor is already checked to see which part of the cubes can return data for the query. The data manager can then completely ignore the remaining cubes. Problem: To reduce data volume in each InfoCube, data is partitioned by Time period. A query must now search in all InfoProviders to find the data. This is very slow. Solution: We can add “hints” to guide the query execution. In the RRKMULTIPROVHINT table, you can specify one or several characteristics for each MultiProvider, which are then used to partition the MultiProvider into BasicCubes. An entry in RRKMULTIPROVHINT only makes sense if a few attributes of this characteristic (that is, only a few data slices) are affected in the majority of, or the most important, queries (SAP Notes: 911939. See also: 954889 and 1156681). Alternatively, some of the MP joins may be included on BWA v. 7.2

  36. InfoCube Design — High Cardinality Flags Real Example • High-Cardinality flag for large InfoCubes with more than 10 million rows • There are currently 11 InfoCubes with a ratio of more than 20% of the records in the dimensions vs. fact table • SAP recommends for Indexing and performance reasons to flag these as “high-cardinality” dimensions. However, it has minor impact to smaller cubes. • Currently there are four medium and large InfoCubes that are not following the basic SAP design guidelines, and subsequently exhibit slow performance Redesign large InfoCubes with high-cardinality to take advantage of the standard performance enhancements available.

  37. SAP NetWeaver BW 7.3 System Statistics — Data Volume Reduction Real Example • There are many statistical cubes with significant volume and no real benefits. During the BW upgrade, most of these were not cleared and are now creating poor system performance. For example: • 0TCT_C02 has 408 million rows; others also have millions of rows • Stats are collected for over 1,900 objects, queries, infoProviders, templates, and workbooks • There are 7 aggregates with over 2 million rows on the stats cubes • Creating aggregates on stats cubes inserts 1.9 million rows and takes 35.6 minutes for refresh each night • High-cardinality flags are set for small cube with only one million rows (0TCT_C21) • Run-time stats are not collected for all InfoCubes and cannot be analyzed To do: goto RSDDSTAT and select “Delete Data” for old stats and also schedule periodic jobs using standard process chains.

  38. Use of Line Item Dimensions for 7.3 InfoCubes not in SAP NetWeaver BW Accelerator • Line item dimensions are basically fields that are transaction oriented • Once flagged as a line item dimension, the field is actually stored in the fact table and has no table joins • This may result in improvements to query speeds for cubes not in SAP NetWeaver BW Accelerator • Today, there are very few InfoCubes that used this feature (mostly TCT cubes) BW 7.3 hint: Explore the use of line item dimensions for fields that are frequently conditioned in queries. This model change can yield faster queries. 37

  39. Re-Design 7.3 Data Loads Real Example • On an average daily dataextraction, transformation, and load process takes 44.8 hours if run sequentially • A substantial amount of the time is spent on data transformation (51%) and lookups are often done on large DSOs without secondary indexes. • Of the 371 million records extracted from the source, only 33.7% are written to disk • This is due to lack of ability to do delta processing for some files and also a substantial amount of transform and lookup logic in some of the ABAP rules Consider upgrading as soon as possible to a newer ECC version that allows for better integration of standard BW 7.x extractors. Also, revisit extractor design for lookups on source system instead of inside BW.

  40. B-Tree Indexes on Large Objects Real Example • InfoCubes that are not flagged as high-cardinality use a Bitmap index instead of a classical b-tree index for the joins. • This type of index does not get “unbalanced” since it uses pointers instead of “buckets” • When updating these large InfoCubes, dropping and recreating Indexes in the process chain can be very time consuming and actually take longer than the inserts • It can also result in locks when the objects are very large (100 million+ records) and when attempting to do this in parallel (see ORA-0060) Rebuilding bitmap indexes in load processing for large objects should not be a default answer for all designs. The process chains that do that, need to be revisited.

  41. Legacy SAP BW 7.0 Performance in 7.3 - Data Activation Real Example • During activation, there is limited use of buffering of number ranges for dimensions and InfoObjects, even when the number of entries are large. This results in many reads on the NRIV table that slows down data activation and process chains(see notes: 857998, 141497, 179224 and 504875) Objects: BID0003554; 4020; 3531; 4016; 2364; 2313; 2450; 3834 and 2309 Start buffering of number ranges of dimensions and InfoObjects (see tables above) Or use 7.3 data activation instead

  42. PSA Cleanup in SAP NetWeaver BW 7.3 Real Example • For this company there were over 1.6 billion rows in the PSA • An estimated 27Gb could be freed up if data older than one month is removed • A formal retention policy that is communicated and enforced should be implemented ASAP Lessons learned: Start PSA cleanup ASAP and schedule regular jobs that take care of this in the future

  43. Aggregates Are Not Needed with BW 7.3 and BWA 7.2 Real Example • At this company, there are 11 aggregates in the system • Four are related to the cube ZIR_C01 and seldom used and (two has never been used by any query) • The 7 other aggregates are used only by the statistical cubes. • Every day, 1.9 million records are inserted into the aggregates and take 35.6 minutes of processing time To do: delete unused aggregates. Also, by reducing the data volume in the underlying statistical cubes (cleanup), the remaining aggregates will reduce in size and processing time. If ZIR_C01 was in BWA, all four related aggregates can be deleted.

  44. The Memory Cache Size Utilization Real Example • The OLAP Cache is by default 100 MB for local and 200 MB for global use • The current system at this company was consuming no more than 80MB on average • This means that most queries were re-executing the same data

  45. SAP NetWeaver BW 7.3 OLAP Cache — Turned Off? Real Example • At one client, the OLAP cache was turned off for 131 out of 690 queries (excluding 4 planning queries in BW-IP) • The cache was also turned off for 24 out of 256 InfoCubes • The OLAP Cache mode for their IP queries should have been stored as “Binary Large Objects (BLOB),” that would speed up caching and very large reads, as is done in these queries Since many of the queries are using CKF and sums and sorts extensively, the cache read mode for most queries should be turned on ASAP at this company

  46. Broadcast to Pre-Fill the Cache — MDX Based SAP BusinessObjects Reporting Real Example • This company’s Java Stack did not communicate properly with SAP NetWeaver BW, and multiple logons were required • As a result, broadcasting could not be used until the connectivity was set up correctly To do: Set up Java connectivity ASAP and use the Broadcasting feature to prefill the MDX cache for BI analytical processing intensive functions such as CKF, Sorts, Exceptions, Conditions

  47. BPC on SAP NetWeaver BW 7.3 — Current System Real Example Consolidation Processes: Clearing Load Foreign Exchange Eliminations Optimizations • This BPC system was experiencing substantial load performance issues • Some of this was due to underlying SAP BW configuration, while some was due to the technical configuration of the data store architecture and data flow inside SAP BW Consolidation Cube (OC_CON) BPC Staging Cube (BPC_C01) GL Summary Cube (FIGL_C03) Production Issues include: Dependent jobs not running sequentially, i.e., load from Summary cube to Staging cube is sometimes executed before the summary cube data is loaded and activated, resulting in zero records in the staging cube. Long latency with 6 layers of PSA, DSOs, and InfoCubes before consolidation processes can be executed. Conformed Reportable DSO FIGL_D21 FIGL_D20 FIGL_D17 FIGL_D14 FIGL_D18 Write Optimized DSO FIGL_D15S FIGL_D13S FIGL_D10S FIGL_D08 FIGL_D11S Persistent Staging Area (PSA) ECC 6.0 Asia- Pacific ECC 6.0 North-America ECC 4.7 Latin-America R/3 3.1i EU will move to ECC6.0 ECC 4.7 ASIA Shut down in 2011

  48. BPC on SAP NetWeaver BW 7.3 — Possible Future System Real Example • Long-term the BPC system on SAP NetWeaver BW 7.3 should be simplified. This includes removing the conformed DSO layer, with BEx flags for data stores that are never reported on. • Also, the BPC staging cube serves little practical purpose since the data is already staged in the GL Summary cube and the logic can be maintained in the load from this cube directly to the consolidation cube. Consolidation Processes: Clearing Load Foreign Exchange Eliminations Optimizations Consolidation Cube (OC_CON) GL Summary Cube (FIGL_C03) Long-term benefits include reduced data latency, faster data activation, less data replication, smaller system backups as well as simplified system maintenance. Take advantage of the 7.3 features! Write Optimized DSO FIGL_D15S FIGL_D13S FIGL_D10S FIGL_D08 FIGL_D11S Persistent Staging Area (PSA) ECC 6.0 Asia- Pacific ECC 6.0 North-America ECC 4.7 Latin-America R/3 3.1i EU will move to ECC6.0 ECC 4.7 ASIA Shut down in 2011

  49. What We’ll Cover … • New Administrative Cockpit Capabilities • The New Semantic Partition (SPO) Options • The HybridProvider and Real-Time Data • Faster Data Load and New Design Options • Front-End and Security Benefits • Using SAP NetWeaver BW 7.3 for Performance - Real Examples • New In-Memory Possibilities with SAP NetWeaver BW 7.3 and SAP NetWeaver BW Accelerator 7.2 • Wrap-up

  50. In-Memory Processing — SAP NetWeaver BW Accelerator 7.2 and SAP NetWeaver BW 7.3 • BIG DEAL! - In SAP NetWeaver BW 7.3, you can also build analytical indexes • These are simply “data containers” from APD that is stored in SAP NetWeaver BW Accelerator • You can build queries on them • Using the Index Designer in SAP BusinessObjects Data Services, you can also index data from external data files and data bases and query it in SAP NetWeaver BW 7.3 It is important to note that currently, the SAP BusinessObjects indexes are on dedicated hardware blades.

More Related