Upgrade to NetWeaver BW 7.

30
New features with ABAP Upgrade

Roland Kramer, Solution Architect BW/BI/In-Memory June 2011

Agenda

1. Technology/Roadmap facts 2. What’s new with the Upgrade to BW 7.30 3. Usage of the ASU toolbox for BW 4. General checks prior to the Upgrade 5. Details of the Upgrade Process

© SAP AG 2009. All rights reserved. / Page 2

Planned Roadmap HANA & SAP NetWeaver BW

BW 7.3 / BWA 7.2
Major step on Enterprise Data Warehousing scalability and flexibility BW Accelerator: additional performance Integration Improvements with SAP BusinessObjects Data Services

BW 7.3x
BW running on HANA as the underlying In-Memory DB Platform In-Memory for Enterprise Data Warehousing Integrated Planning InMemory enabled

BW 7.0 EhP1 (7.01) BW 7.0 / BWA 7.0
Major release BW Accelerator New features and improvements across all components Go-to release for integration with SAP Business Objects BI

2006

2009

2010

2011
HANA V1.0

Future direction HANA V1.x
Additional calculation capabilities Primary persistence layer under BW; eliminates need for separate database Models for SAP business content enabling new applications

SAP NetWeaver BW evolving to a fully In-Memory enabled EDW solution on top of HANA

Real-time operational analytics on mass data Rapid creation of agile data marts Non disruptive deployments of HANA side by side ERP and/or BW

This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

© SAP AG 2009. All rights reserved. / Page 3

BW 7.30 - Executive Summary

Major benefits of SAP NetWeaver BW 7.3 are:
Enhanced Scalability & Performance for faster decision making
Remarkably accelerated data loads Next level of performance for BW Accelerator

Increased flexibility through SAP BusinessObjects BI and EIM integration
Tighter integration with SAP BusinessObjects Data Services Enhanced integration with SAP BusinessObjects Metadata Management

Reduced TCO and improved development efficiency
Automated creation of Semantic Partitioned Objects Graphical data flow modeling and best practice data modeling patterns

Simplified configuration and operational management
Admin Cockpit integrated into SAP Solution Manager Wizard based system configuration Important timelines
This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

NetWeaver 7.30 including BW is GA since 30th of MAY 2011!

© SAP AG 2009. All rights reserved. / Page 4

ABAP Some technology facts and updates NetWeaver Java 7.30 would be possible.34) Add-On is available since end of Q1/2011 for all Customers.30. which is also a prerequisite for the full usage of the BEx successor . All rights reserved.0x System beforehand to migrate the old BW Authorization.30 is now shipped together with BW 7.30 The new BI Authorization concept is now mandantory. © SAP AG 2009. so the Java Server will not be used anymore for the BW-IP infrastructure in the future after BW 7.1 and BI 4.x together with DS XI 3.Upgrade to BW 7.x accessing non-SAP Systems and data lineage The BICS are moving to the upcoming SAP BusinessObjects Application Platform BI 4.Analysis The Java component BW-IP modeler is redeveloped for BW 7. if not already done.30 in ABAP HTTP. Optionally you can separate the Java Stack prior to the Upgrade of the ABAP Backend. The Upgrade of a Doublestack is also supported You can do either: The new split tool for the Java Stack in SAPInst is available with EhP2 or with the SAPInst delivered with Abap 7. BW 7.2 and DI 4.30 There is a SEM Add-On available with BW 7.0 accelerated together with BOe XI 3. Despite the fact that you either create a 7. / Page 5 . The SEM (6. a potential Upgrade from BW 3. See Notes 1545831 and 1531022 for more details.30 and BWA 7.30 .30 brings together some new improvements not only for the SAP usage together with Explorer 2.0.30.5 to 7.

or ideally capsulated with BI with Tomcat.0x or 7.0 Installation for SAP BW Customers Platform View .x Migr.1. All rights reserved.0 J2EE 7. BI Web Tier BI Reporting & Infrastructure Services The XI 3.0 ABAP 7. A JVM switch toll is available as well © SAP AG 2009.30 Engine.Proposal SAP BW 7.New BI 4.01 SAP BW 7. Consider the SAPJVM 4.01 BEx Web BI Java BICS EP EP J2EE 7.30 Split J2EE 7.1 XI Reporting & Infrastruc.30 BEx Web BI Java BICS BI Launch Pad Physical Server (optional) SAP NetWeaver SAP NetWeaver Functions SAP Usage Type and SAP BusinessObjects Tiers.0 Java apps can deployed either on an existing SAP J2EE 7.0 BI Java SAP BW 7. Services EP EP (opt) LCM Client BO XI 3. Apps. Services BOE XI Web Tier BI Web Apps … (*) BI 4.1/BI 4.30 ABAP 7.01 ABAP 7. / Page 6 .

J2EE Options for BI 4.0 inbuilt Java Server BI 4.0x BI 4.No Xcelsius BW Connection Install BEx Web Limitations* .x © SAP AG 2009.0 BICS BEx Web Install BEx Web Limitations* . 3.No Broadcasting (Portal/KM) .0 together with BW 7.No Broadcasting (Portal/KM) .x and 7.No Xcelsius BW Connection *Broadcasting is either a direct ABAP process (Excel) or an ABAP HTTP process publishing in a separate SAP EP Distinguish between 3. / Page 7 .No Documents (Portal/KM) .0 SP? Only BICS BEx Web BI 4.JAVA 7.x Web template to not require BI .30 use the recommendation with the BI 4.30 Other J2EE (see PAM) BI 4. All rights reserved. BEx Web) Upgrade from BW 7.0 SP? Usage Type EP Usage Type BI Java (BICS.0 SAP NetWeaver J2EE 7.x Web templates.No Documents (Portal/KM) .

30 BI-Java) .no automatic SAPCryptoLib .30* JAVA 7.30 ABAP Stack NetWeaver 7. / Page 8 BW 7.30 (without ADS) Upgrade to BW 7.30 Upgrade limitation* .30 JAVA Stack (with ADS) ADS = Adobe Document Services (obsolete with NetWeaver 7.Doublestack Options prior to the Upgrade BW 7.0x Stack Deinstall JAVA 7.no automatic file system 7.0x Stack Fresh Install of JAVA 7.30 ABAP Upgrade to JAVA 7.disable SNC configuration © SAP AG 2009.30 separation of ABAP and JAVA easies the upgrade process BW 7. All rights reserved.x .0x Stack Single ABAP 7.0x Doublestack Deinstall JAVA Add-In Use Split tool Deinstall JAVA 7.

New authorization concept must be in place Former and new authorization concept It is mandatory to setup/migrate to the new concept prior to the upgrade The former authorization concept is no longer supported with BW 7.30 You cannot switch back to the former concept New Transaction RSECADMIN. / Page 9 . All rights reserved. see SAP Notes 942799 and 944929 © SAP AG 2009.

start two month in advance. / Page 10 . Given example is based on a higher complexity.Example Project schedule for the Migration Combined technical Upgrade & Authorization Migration 1st month 2nd month 3rd month 4th month 5th month <month> Plan phase (6 weeks) Upgrade Authorizations DEV system (4 weeks) Upgrade & Test Authorization migration QAS system (5 weeks) Upgrade & Test Authorization Test PRD system (1 weekend) Upgrade & GoLive Cutover & Golive Legend: Duration Milestone KickOff Start Upgrade GoLive Remark Overall project duration dependents on the system complexity. To match with typical technical Upgrade Plan. All rights reserved. © SAP AG 2009.

General Guidelines and Notes Managing your Upgrade with Innovative Tools http://www.Central Note: Upgrade Systems on SAP NetWeaver 7.sdn.BI Administration Cockpit: Upgraded from 7.35: Information about installation and upgrade Hinweis 1022704 .com/irj/sdn/index?rid=/webcontent/uuid/b039ebc5-304f-2b10-499e-97dabda45e48 New Features with BW 7.30 Online Help http://help.30 http://www.sap.com/saphelp_nw73/helpdata/en/ca/6fbd35746dbd2de10000009b38f889/frameset.[INTERN] Solution Manager: PPMS Produktdaten fehlen Note 1405878 .sdn.Additional info for upgrade to SAP NetWeaver 7.htm Useful Notes Note 586648 .3 (using SUM) Note 1484437 .Basic functions SP22 and higher Note 1088717 .sap.BI_CONT 7.Upgrade Phase EHP_INCLUSION und SPSTACK_REQUEST Hinweis 1171648 . All rights reserved.com/instguides NetWeaver BW 7.sap.com/irj/sdn/bw-73 Links to Guides (Master and Upgrade) http://service.30 release © SAP AG 2009.Invalid SID entries in /BI 0/SIOBJNM Note 1403832 .SQL Server: wrong compatibility level in system copy Note 1543092 .Active services for Web Dynpro ABAP in transaction SICF Note 1476239 .SAP Solution Manager . / Page 11 .3 Note 1390477 .00 to 7.SAP system migration to Windows 2008/2008 R2 Note 1503599 .sap.

Technology/Roadmap facts 2.30 3. Usage of the ASU toolbox for BW 4. General checks prior to the Upgrade 5. / Page 12 . Details of the Upgrade Process © SAP AG 2009. What’s new with the Upgrade to BW 7. All rights reserved.Agenda 1.

All rights reserved. / Page 13 .System Switch Upgrade New with NetWeaver EhP1 onwards New upgrade directory now located at \\sapmnt\<SID>\upg © SAP AG 2009.

New Upgrade UI following the EhP development guidelines © SAP AG 2009. / Page 14 . All rights reserved.

All rights reserved. / Page 15 .New Upgrade UI Providing the JCE Jurisdiction Policy Files beforehand New Security Concept used: See Notes 1240081 and 1238121 Start of SAPup STARTUP „JCE_POLICY_ZIP = <jce policy zip file>" If JCE_POLICY_ZIP already set in the Environment you can directly use STARTUP without Parameter © SAP AG 2009.

All rights reserved.Put all components/patches/updates to one directory and all Add-On‘s as SAINT packages All Add-On’s/Patches will be found automatically in the EPS inbox Create your XML Files for ABAP Support Packages on SMP © SAP AG 2009. / Page 16 .

New Preconfiguration Modes available Or manual selection see Upgrade Guide Page 46 © SAP AG 2009. All rights reserved. / Page 17 .

All rights reserved. / Page 18 .Upgrade Planning working until Downtime is possible now © SAP AG 2009.

/ Page 19 . All rights reserved.Changeability of BW Objects during Upgrade © SAP AG 2009.

What’s new with the Upgrade to BW 7. / Page 20 .Agenda 1. Details of the Upgrade Process © SAP AG 2009. Usage of the ASU toolbox for BW 4. General checks prior to the Upgrade 5. Technology/Roadmap facts 2.30 3. All rights reserved.

EP. All rights reserved. BW.0 EhPx (upcoming) upgrade to any SAP Product based on the NetWeaver 7.java (upcoming) for frontend connection e.java connection (available) for connection BW-IP. abap . BW Content) one single truth for all pre/post Upgrade Steps (Note 1000009) Use the predefined content for: upgrade to NetWeaver 7.abap (with EhP1) for backend connection e.g. ASU toolbox (incl. CRM. ESS/MSS. etc. CTC for BW-Java automatic connection between Abap and Java (Note 983156) 1. ERP.x Platform (upcoming) create/modify own content (XML based) Check out the success story from the German Customer Karcher: https://websmp204.de/~sapidp/011000358700000162292010E/ © SAP AG 2009.g.30 Your single source for all pre and post upgrade steps Lower your TCO and time efforts by Managing your Upgrade with innovative tools Complete Business Suite 7 connectivity (with EhP1): abap .sap-ag. / Page 21 . FPM. etc. PI.x BW upgrade to ERP 6. Note 1178800 2. etc.Accelerated Upgrade to NetWeaver BW 7. java .

/ Page 22 .Upgrade Process with the ASU toolbox for BW in average 3 days per systems 1 day 1 day 1 day 1 Week Pre Upgrade Steps Application checks/ cleansing and Upgrade Preparation Technical checks and Upgrade preparation Agree on result PREPARE/ UPGRADE Last checks PREPARE UPGRADE Post Upgrade Steps Application Post checks and functional tests Technical post Steps and Go-Live Preparation Testing Application testing New 7. Note: Elapsed time may be longer due to scheduling and lags. © SAP AG 2009.0 features Key Highlights of the ASU toolbox for BW One single source of all pre and post steps for a successful upgrade Clear distribution of tasks between SAP Basis Administration and the Application Development Additions. etc. All rights reserved. Documentation can be added immediately as well XML editor makes adoptions to other SAP upgrades easy. Remarks.0 EDW features Technical testing BI-Java CTC and testing of new 7.

/ Page 23 . All rights reserved.Typical Scenario for an Upgrade See Details in SAP Note 1000009 SAP Solution Manager Start Upgrade RoadMap SAP UP SAP System ASU-Upgrade-Note-Display Start Prepare Start ASU-Toolbox before Upgrade Phase (download Content from Marketplace) Running Prepare-Jobs Prepare finished Running ASU-Reports via Schedule Manager ASU-Toolbox before Upgrade Phase finished Start technical Upgrade Running technical Upgrade Technical Upgrade finished Start ASU-Toolbox after Upgrade Phase Running ASU-Reports via Schedule Manager ASU-Toolbox after Upgrade Phase finished Monitoring of all started ASU-Reports via Solution Manager © SAP AG 2009.

10+d testing.Typical Upgrade Project Plan typical duration 6-8 weeks for a 3-System Landscape Upgrade Tasks Upgrade Planning Upgrade of Development Upgrade of Test Additional testing Upgrade of Production SAP Java Server/EP Setup of BOe/Explorer/BWA BU Requirements/BWA Start after first Upgrade (2d/Sys. All rights reserved.) Start after first comp. / Page 24 . 6d BOe/Explorer. 5+d SBO Explorer Implementation © SAP AG 2009. Stack (2d/Sys) 2w Steps/Milestones 3d 3d + 1w Test 3d + 1w Test Ongoing (several weeks) 3d Legend: Duration Milestonetoday 6 weeks 8 weeks Time in total: 9d Upgrade. 6d Java Inst.

All rights reserved.Pre Steps of ASU toolbox for BW .1 IT/SAP Basis/Application Owner Application Owner IT/SAP Basis © SAP AG 2009. / Page 25 .

All rights reserved.2 Application Owner © SAP AG 2009. / Page 26 .Pre Steps of ASU toolbox for BW .

All rights reserved.1 Depending on timing/after Post Steps IT/SAP Basis Application Owner © SAP AG 2009. / Page 27 .Post Steps of ASU toolbox for BW .

All rights reserved.2 Depending on Project/existing App. Application Owner © SAP AG 2009. / Page 28 .Post Steps of ASU toolbox for BW .

© SAP AG 2009. All rights reserved.g. e. new or changed items/checks can be added immediate.ASU toolbox – BW specific Install latest ST-PI 2008 Add-On XML can now be changed within the same screen. / Page 29 .

General checks prior to the Upgrade 5. What’s new with the Upgrade to BW 7.Agenda 1. Usage of the ASU toolbox for BW 4. Technology/Roadmap facts 2. Details of the Upgrade Process © SAP AG 2009. / Page 30 .30 3. All rights reserved.

New with NetWeaver 7. All rights reserved. / Page 31 .0x Daemon process Stop all Deamon Process with Transaction RSRDA © SAP AG 2009.

0x © SAP AG 2009. All rights reserved. / Page 32 .Activate all DataStore Objects Valid for all BW Releases 3.x and 7.

/ Page 33 .Further general Upgrade Checks SAP_DROP_TMPTABLES and RSUPGRCHECK © SAP AG 2009. All rights reserved.

g. if System is a copy from Test/Production © SAP AG 2009.Check the Secure Storage with SECSTORE e. / Page 34 . All rights reserved.

/ Page 35 .Transaction SECSTORE © SAP AG 2009. All rights reserved.

Check for missing TLIBG entry New check from NetWeaver BW 7.0x onwards 2EETG013 "Function group frame program" "CRM_BUPA_FRG0060_BAPI" "exists without TLIBG entry" 2EETG013 "Function group frame program" "LXE_SE63_Z_EDITOR" "exists without TLIBG entry" © SAP AG 2009. / Page 36 . All rights reserved.

All rights reserved.Create the Stack XML File Use the Maintenance Optimizer from your Solution Manger © SAP AG 2009. / Page 37 .

sap.corp:1080/sap/bc/webdynpro/sap/wda_mopz_plan?sap-language=EN © SAP AG 2009. All rights reserved.wdf. / Page 38 .Create the Stack XML File The upgraded System must appear here for selection Example: http://sptmain.

All rights reserved.Create the Stack XML File Choose the Option Maintenance for the Upgrade © SAP AG 2009. / Page 39 .

All rights reserved.Create the Stack XML File Confirm the Major Target © SAP AG 2009. / Page 40 .

All rights reserved. / Page 41 .Create the Stack XML File The XML File is created and available for download or in the EPS inbox © SAP AG 2009.

Technology/Roadmap facts 2. General checks prior to the Upgrade 5. as the technical Upgrade Procedure for 7. Details of the Upgrade Process Please Note: Some of the screenshots might contain 7.30 is the same.30 3. Usage of the ASU toolbox for BW 4. All rights reserved. © SAP AG 2009. What’s new with the Upgrade to BW 7.Agenda 1.20 as release. this has no impact on the shown steps. / Page 42 .

Upgrade UI – Start Page http://<server>. / Page 43 .<ext>:4239 © SAP AG 2009.<domain>. All rights reserved.

bat jce_policy_zip=c:\java\SAPJVM6_crypto. All rights reserved. / Page 44 .Start the Software Upgrade Manager (SUM) startup.zip © SAP AG 2009.

SAP JVM location/environment variables start DSUGui. / Page 45 . All rights reserved.bat separately © SAP AG 2009.

/ Page 46 . All rights reserved.Upgrade UI Details for Step Initialization © SAP AG 2009.

Upgrade Password provided in Note 1390477
Put all updates from SMP into the download directory

startup.bat "jce_policy_zip=SAPJVM6_crypto.zip" Password: KEYWORD: 6782622

© SAP AG 2009. All rights reserved. / Page 47

Add all main DVD here
Remove empty lines in advance Add-On’s as SAINT packages

© SAP AG 2009. All rights reserved. / Page 48

Include the Stack XML from Solution Manager
A correct configured Maintenance Optimizer is a prerequisite now

© SAP AG 2009. All rights reserved. / Page 49

Solution Manger Upgrade Key ready
Solution Manager – MOPZ connection later necessary

© SAP AG 2009. All rights reserved. / Page 50

Check for missing ABAP corrections This will also appear even if you on the right SP Stack Level © SAP AG 2009. All rights reserved. / Page 51 .

All rights reserved.Upgrade UI Note 96317 and 962955 modify /etc/hosts check with Page 88 of the Upgrade Guide © SAP AG 2009. / Page 52 .

New Upgrade pre configuration options High resource use (minimal downtime. All rights reserved. archiving off) © SAP AG 2009. / Page 53 . fast import.

All rights reserved.Overview of upgrade configuration Accept choice © SAP AG 2009. / Page 54 .

/ Page 55 .Overview of manual upgrade configuration Manual selection will not apply maximum values © SAP AG 2009. All rights reserved.

All rights reserved. / Page 56 .Procedure with further Add-On’s Add additional packages as SAINT packages into EPS/in © SAP AG 2009.

/ Page 57 .Mandantory connection to MOPZ needed As alternative create a Stack XML for BW 7.30 (no EhP included) © SAP AG 2009. All rights reserved.

All rights reserved. / Page 58 .30 Note 1022704 EHP_INCLUSION and SPSTACK_REQUEST © SAP AG 2009.Decision about EhP1 during Upgrade to 7.

/ Page 59 . All rights reserved.Further descission about Add-On’s UPG WITH SAINT PACK or DELETE (for ST-PI possible) © SAP AG 2009.

All rights reserved. / Page 60 .Decision about included Support Packages © SAP AG 2009.

/ Page 61 . All rights reserved.Decision about included SPAM update © SAP AG 2009.

All rights reserved.Optional: include SPDD and/or SPAU request © SAP AG 2009. / Page 62 .

it contains ALL pre and post steps © SAP AG 2009. / Page 63 . All rights reserved.ASU toolbox for BW Even that ASU toolbox is optional.

All rights reserved.3 version „7. / Page 64 .Installing BI_CONT on SAP NetWeaver 7.35“ 3800300 © SAP AG 2009.

01) © SAP AG 2009. All rights reserved. / Page 65 . even that you are not jet in the downtime phase Query structures InfoPackages definitions Process Chains This behavior didn’t changed from former BW Upgrades prior to EhP1 (7.Development is locked after this Phase Depending on your Upgrade preconfiguration Please Note: from BW Perspective is is now not possible anymore to change the following objects.

All rights reserved.Decision about SPDD prior the ACT phase For BW type system you can continue without adjustments © SAP AG 2009. / Page 66 .

04.PFL This is tp version 372.04.PFL This is tp version 372.Unlock/Lock the shadow system is necessary A friendly reminder/recap D:\usr\sap\trans\bin>tp unlocksys FBM pf=TP_DOMAIN_FBM. All rights reserved.04.PFL This is tp version 372.65 (release 700.PFL This is tp version 372.65 (release 700. unicode enabled) tp finished with return code: 0 meaning: Everything OK © SAP AG 2009. unicode enabled) tp finished with return code: 0 meaning: Everything OK D:\usr\sap\trans\bin>tp locksys FBM pf=TP_DOMAIN_FBM. unicode enabled) tp finished with return code: 0 meaning: Everything OK D:\usr\sap\trans\bin>tp lock_eu FBM pf=TP_DOMAIN_FBM. unicode enabled) tp finished with return code: 0 meaning: Everything OK D:\usr\sap\trans\bin>tp unlock_eu FBM pf=TP_DOMAIN_FBM.65 (release 700.04.65 (release 700. / Page 67 .

Additional information on resetting upgrade as of Release 6.Reset the Upgrade with report RSUPGRES Another friendly reminder/recap Note 417670 .10 © SAP AG 2009. / Page 68 . All rights reserved.

All rights reserved. / Page 69 .Decision about ACT phase Accept non-severe errors will be solved in a later phase © SAP AG 2009.

All rights reserved. / Page 70 .Old “PREPARE” is now finished Until this phase working with the system was possible © SAP AG 2009.

All rights reserved.End of phase Preprocessing To ensure the recovering please backup the upgrade directory © SAP AG 2009. / Page 71 .

All rights reserved.End of phase Downtime Upgrade is already over the top backup of DB © SAP AG 2009. / Page 72 .

/ Page 73 . All rights reserved.End of phase Postprocessing Think about the start of BTCTRNS2 after the post work is finished © SAP AG 2009.

All rights reserved.End of phase Postprocessing Think about the start of SGEN after the post work is finished © SAP AG 2009. / Page 74 .

/ Page 75 .End of phase Postprocessing Might not occure with higher support package © SAP AG 2009. All rights reserved.

End of phase Postprocessing Decision about SPAU create transport for further upgrades © SAP AG 2009. All rights reserved. / Page 76 .

/ Page 77 .End of phase Postprocessing Your technical Upgrade is finished © SAP AG 2009. All rights reserved.

All rights reserved. / Page 78 .Technical Upgrade has ended End of phase Finalization © SAP AG 2009.

/ Page 79 . All rights reserved.30 upgrade Running at the end of the technical upgrade © SAP AG 2009.Example runtime for BW 7.

30 upgrade .ALE: Generating and reading change pointers after upgrade © SAP AG 2009.Postwork after 7.new Note 1165059 . / Page 80 . All rights reserved.

/ Page 81 .30 More Details: http://help.com/saphelp_nw73/helpdata/en/45/5ae49cee142a50e10000000a11466f/frameset.sap.htm © SAP AG 2009. All rights reserved.Migrate the BI Authorization to 7.

/ Page 82 .com/irj/sdn/index?rid=/webcontent/uuid/b039ebc5-304f-2b10-499e-97dabda45e48 The „upgrade Bible“ from page 52 http://www.30 upgrade .Postwork after 7.sdn.sap. All rights reserved.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60ecc07d-3a4b-2b10-ef83-c988e6ecabf6 © SAP AG 2009.existing Check the generic post upgrade steps from here Get everything which is needed here: Managing your Upgrade with Innovative Tools http://www.sap.sdn.

All rights reserved.com/irj/sdn/edw-ops © SAP AG 2009.com http://www.kramer@sap.sdn. / Page 83 .sap.Thank you! Solution Architect BW/BI/In-Memory Roland Kramer Mobil +49 (151) 4260 3219 roland.

z9. POWER5. RETAIN. XHTML and W3C are trademarks or registered trademarks of W3C®. PowerPC. Windows. Business Objects and the Business Objects logo. BatchPipes. z/OS. System i5. RACF. iSeries.S. Java is a registered trademark of Sun Microsystems. Business Objects is an SAP company. Oracle is a registered trademark of Oracle Corporation. World Wide Web Consortium. Data contained in this document serves informational purposes only. Excel. POWER. SAP. OpenPower. BusinessObjects. All rights reserved. System i. System p5. UNIX. z/VM. Linux is the registered trademark of Linus Torvalds in the U. if any. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. and other countries. Redbooks. Inc. SAP NetWeaver. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only. i5/OS. National product specifications may vary. MetaFrame. PartnerEdge. Citrix. xSeries. System z. / Page 84 . IBM. Adobe. HTML. XML. System z10. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services. X/Open. and MultiWin are trademarks or registered trademarks of Citrix Systems. System x. Intelligent Miner. DB2 Connect. DB2 Universal Database. POWER6. POWER6+. AIX. Microsoft. S/390 Parallel Enterprise Server. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Crystal Reports. Xcelsius. POWER5+. MVS/ESA. BladeCenter. WebSphere. Web Intelligence. DB2. Netfinity. OSF/1. R/3. and Motif are registered trademarks of the Open Group. z10. The information contained herein may be changed without prior notice. HACMP. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.© Copyright 2011 SAP AG All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. zSeries. without representation or warranty of any kind. OS/2. System z9. System Storage. Duet. JavaScript is a registered trademark of Sun Microsystems. and SAP Group shall not be liable for errors or omissions with respect to the materials. eServer. ICA. OS/390. OS/400.A. WinFrame. PowerVM. the Adobe logo. Inc. Acrobat. Crystal Decisions. ByDesign. Parallel Sysplex. These materials are subject to change without notice. used under license for technology invented and implemented by Netscape. GPFS. Massachusetts Institute of Technology. PostScript. pSeries. VideoFrame. © SAP AG 2009. S/390. Program Neighborhood. System p. 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 other countries. Outlook. and PowerPoint are registered trademarks of Microsoft Corporation. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Power Architecture. Inc. SAP Business ByDesign.. in the United States and in other countries. AS/400. All other product and service names mentioned are the trademarks of their respective companies. Nothing herein should be construed as constituting an additional warrant.