SAP NetWeaver 7.3 – What's new and how to upgrade

2. SAP NetWeaver 7.3 – What's new and how to upgrade Dr. Berg Comerit Inc.

3. In This Session … This session explores the new features of SAP NetWeaver 7.3 and helps you gauge whether an upgrade makes sense for your organization. Learn how faster data loads can be accomplished through improved data activation, disabled delta consistency check for write-optimized DataStore objects and options to fetch only the last request View the new automated partitioning of InfoProviders using pre-delivered step-by-step Wizards, and learn how to monitor database usage and performance in the improved Administration Cockpit. Explore how SAP NetWeaver BW 7.3 improves hierarchy handling through integration into process flows, and allows for the loading of hierarchies from flat files using DataSources. Examine the new transformation options to support semantic groupings, along with the currency and unit conversions now available for DSOs and InfoSources. Gain insight into the technical and human resources required to upgrade to this new release, best practices for scoping, and potential challenges along the way. View a sample upgrade plan to reference during your own SAP NetWeaver BW 7.3 initiative.

4. What We’ll Cover … • SAP BW 7.3 Overview • 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 • New in-Memory Possibilities with BW 7.3 and BWA 7.2 • Planning and Executing the Upgrade • Wrap-up

5. The Reason for Upgrading SAP BW 7.3 is now available and has been well tested. Beta Shipment started in July 2010; Ramp Up started in November 2010. #1 reason for upgrade: “Because I had to!” BW has now been around for over 12 years!!

6. BW 7.3 Release History and Testing Seven customers and nine service partners partcicipated on the beta testing. The beta testing ended in November, 2010 with the following scores: Very Good Low Value 1 3 4 2 Assistance and Support BW 7.3 Quality & Reliability BW 7.3 Functional Completeness BW 7.3 Ease of Installation and Configuration 1 3 4 2 1 3 4 2 Very Satisfied Had Major Issues 1 3 4 2 BW 7.3 was tested extensivly in a beta program and in ramp-up for almost one year!

7. Ease of Installation - Wizards A major new feature of SAP BW is the ability to use a Wizard to install the system. This include the following Wizard ‘templates”: • ABAP Stack initial setup. • Connectivity initial setup • Templates for automated configuration • Business Suite-7 integration • Technical content reports for Initial Setup You can choose to use both an Java and/or a ABAP stack when installing 7.3

8. Specific Database Support – Teradata and IBM DB2 Teradata: 7.3 can now run on top of the Teradata database, including: • The ability to use BW-Accelerator on-top of Teradata. • The use of SAP’s system to manage transports between environments 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 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, BW has been unable to take advantage of vendor specific database features. This is changed & workarounds are less needed.

9. What We’ll Cover … • SAP BW 7.3 Overview • 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 • New in-Memory Possibilities with BW 7.3 and BWA 7.2 • Planning and Executing the Upgrade • Wrap-up

10. 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) • The use of BWA and sizes • Monitor for the actual use of OLAP/MDX Cache and hit ratios • DEAMON update information (i.e. RDA capacity status, usage) • A performance monitoring workbench for performance trends • Process chain monitoring (new transaction: RSCPM) with error and active chain monitoring, user specific displays, and performance threshold monitoring (for SLA) Solution Manager has also been updated to take advantage of these new monitors.

11. What We’ll Cover … • SAP BW 7.3 Overview • 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 • New in-Memory Possibilities with BW 7.3 and BWA 7.2 • Planning and Executing the Upgrade • Wrap-up

12. 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 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. When a SPO is created, a reference structure keeps track of the partitions. The structure is placed in the MultiProvider for querying. BW 7.3 with SPO SPO Wizards create all Data Transfer Processes (DTP), transformations, filters for each data store and a process chain automatically. BW 7.0 with hints Reference structure for partitioned objects AR 2008-11 GL 2008-11 Delivery 2008-11 SD 2008 SD 2009 SD 2010 SD 2011 AR 2008-11 GL 2008-11 Delivery 2008-11 SD 2008 SD 2009 SD 2010 SD 2011

13. What We’ll Cover … • SAP BW 7.3 Overview • 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 • New in-Memory Possibilities with BW 7.3 and BWA 7.2 • Planning and Executing the Upgrade • Wrap-up

14. The New Hybrid Provider and Real Time Data • The "HybridProvider" (HP) is new in BW v7.3. The core idea is to link the historical data inside BW with real-time data. • There are two ways of implementing a HP: • HP based on a DSO • HP based on a Virtual InfoCube

15. Option 1: The DSO Based HybridProvider • Core Features: • Real-time data is in the DSO and historical data in the BWA based InfoCube • The DSO use real-time data acquisition (RDA) to load data • 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

16. Option 1: The DSO Based HybridProvider 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

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

18. What We’ll Cover … • SAP BW 7.3 Overview • 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 • New in-Memory Possibilities with BW 7.3 and BWA 7.2 • Planning and Executing the Upgrade • Wrap-up

19. Faster Data Load and New Design Options - Activation During activation, BW 7.0 has to lookup in the NIRV table to see if the object already exist. This can be a slow process. In 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 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). For data transformations the option ‘Read from DataStore’ for a faster data look-up is also available. In addition, 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 look-ups during activation

20. New Data Design Options – Delta, Init and WebServices In NW 7.3 You can also create generic delta extraction for the Universal Data Connect (UD) and Database Connect (DB) options, as well as for flat files (i.e. comma de-limited files) In addition you can the new DataSource adapter “Web Service Pull” to periodically load data from external web services. You can even create generic WebServices delta loads, and load the new data straight into the staging area of BW (it does not support hierarchies yet). Great New Feature: When you use delta loads, the first time it is automatically defined as “init load” after that it automatically switches to “delta” as the InfoPackage mode (no need to define it anymore!).

21. New Data Design Options – Delta, Init and WebServices In NW 7.3 You can also create generic delta extraction for the Universal Data Connect (UD) and Database Connect (DB) options, as well as for flat files (i.e. comma de-limited files) The new DataSource adapter “Web Service Pull” can be used to periodically load data from web services. You can even create generic delta loads, and load new data straight to the PSA (WS does not support hierarchies). Great New Feature: When you use delta loads, the first time it is automatically defined as “init load” after that it automatically switches to “delta” as the InfoPackage mode (no need to define it anymore!).

22. Faster Data Load and New Design Options - During In SA38 you can use the new program “RS_SYSTEM_SHUTDOWN” can be used to restart an application server. The program suspends all RDA and process chains and re-starts them in a controlled manner, so that your data loads are no in “flux’ and you do not have to clean up partial loads.

23. What We’ll Cover … • SAP BW 7.3 Overview • 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 • New in-Memory Possibilities with BW 7.3 and BWA 7.2 • Planning and Executing the Upgrade • Wrap-up

24. BO BO Explorer gggg

25. What We’ll Cover … • SAP BW 7.3 Overview • 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 • New in-Memory Possibilities with BW 7.3 and BWA 7.2 • Planning and Executing the Upgrade • Wrap-up

26. In Memory Processing - General Highlights - BWA

27. In Memory Processing - Creating Indexes from external data Using the Index Designer in Data Services, you can also index data from external data files and data bases. It is important to note that the BO indexes are on dedicated blades. For BWA you should always have one 'spare' blade for failover. If a blade fails, the system can reload the indexes from the BWA file system (i.e. IBM's GPFS).

28. CompositeProviders: Unions of analytical indexes in BWA • With 7.3 you get a tool to create a new “CompositeProvider” to join analytical indices inside the BWA system. • This works similar to MultiProviders, but can be modeled ad-hoc and the joins are executed inside BWA and not inside the BW Analytical Enginge as in BW 7.0 (much faster) • All CompositeProviders, DSOs, MultiProviders and InfoCubes are available as standard InfoProviders for querying. gggg

29. The New SAP BW 7.3 Features – Modeling in BWA 7.2 With BW 7.3 and BWA 7.2 you can complete many of the joins and the aggregation that previously was conducted in the BI Analyitcal engine, and was therefore hard to performance tune. It also reduces the data being transferred to the app-server and therefore are much faster as well. Image source: SAP AG, 2011, SDN

30. The New SAP BWA 7.2 / BW 7.3 – Faster Performance Image source: SAP AG, 2011, SDN The major benefit of the BWA 7.2 on BW 7.3 is that you can move more of the calculation over to the accelerator and materialize the result in-memory. This improves the reads and calculations in the OLAP/ BI analytical engine on the BW side is substantially reduced. The following calculations is now included: SUM MIN MAX CNT (count all detailed values) CN0 (Count all values not zero or null) AVG (average) AV0 (Average for all values not zero or null)

31. The SAP BW 7.3/BWA 7.2 Limitations and Query Settings There are still some limitations. For example you cannot use the exception aggregation for single key figures in BWA if it uses: Virtual key figures Conversion before aggregation Formula calculation before aggregation Non-cumulative key figures Key figures with elimination of internal business volume You also get more detailed control on each query as to how it reads the BWA. Think of it as similar to Query read modes (more details at SDN : http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70950003-f7ef-2d10-b1bc-ee483800b25c?QuickLink=index&overridelayout=true

32. The BW 7.3 and SAP BW 7.2 Performance example Queries with large OLAP processes, such as average and counts benefits the most from the new BWA 7.2 system. SAP has published the following performance example: 90-95% FASTER!!

33. What We’ll Cover … • SAP BW 7.3 Overview • 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 • New in-Memory Possibilities with BW 7.3 and BWA 7.2 • Planning and Executing the Upgrade • Wrap-up

34. Team Lead Team Lead Basis Basis Technical reviewer Technical reviewer Upgrade Support Upgrade Support Regression Testers Regression Testers resource BW Developer External External Resources • A Dedicated team with a technical team lead (100%), a Basis resource (100%) and a technical reviewer (100% is required). • In addition, a dedicated “go-to” resource for technical issues is recommended. This should be an individual that have solid knowledge about the upgrade and have done his before. SAP resources should be considered, due to their contact network within the SAP organization. • Regression testing is required on behalf or the user community. This should be coordinated with the Power Users or existing developers.

35. BO BO Explorer gggg

36. Resources • BO Explorer Implementation Checklist by SAP • http://tinyurl.com/32v5ycw • SAP BOEx Product Website • http://www.sap.com/solutions/sapbusinessobjects/large/business-intelligence/search-navigation/explorer/index.epx • SAP BOEx Collaboration Workspace • https://cw.sdn.sap.com/cw/community/sap/sapbusinessobjectsexplorer • Inside SAP BusinessObjects Explorer - book • SAP PRESS, ISBN:978-1-59229-340-7, Ingo Hilgefort, Hardcover, 315 pages

37. 7 Key Points to Take Home • aa

38. Your Turn! How to contact me: Dr. Berg Bberg@ComeritInc.com

39. Disclaimer SAP, R/3, mySAP, mySAP.com, SAP NetWeaver®, Duet™®, PartnerEdge, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither owned nor controlled by SAP.