best practices for your sap netweaver business intelligence 7.x upgrade

© 2009 Wellesley Information Services. All rights reserved.

Best practices for your SAP NetWeaver Business Intelligence 7.x upgrade

Dr. Bjarne Berg

2

What We’ll Cover …

• Why upgrade End of supportNew support strategy & NetWeaverNew features and capabilities

• Creating an upgrade strategy for the futureContent Vs. Technical upgradesUpgrades with NetWeaver

• Planning and Executing the upgradeThe upgrade planThe business case Staffing, duration and scope

• Real-world examples• Wrap up• Bonus material: ideas for the business case

3

Why Upgrade – end of support…

Many upgrades are driven by end of support for a certain release.

SAP has now created a 5-1-2 maintenance system that consists of:

- mainstream maintenance

- extended maintenance

- customer-specific maintenance

#1 reason for upgrade:

“Because I had to!”

BW

Version

Release

date

End of mainstream

maintenance2.0B 8/14/00 12/31/2005

2.1C 12/18/00 12/31/2005

3.0A 11/15/01 12/31/2005

3.0B 5/13/02 12/31/2006

3.1C 11/11/02 12/31/2006

3.2/3.3 3/31& 8/30 2003 12/31/2006

3.5 3/31/04 3/31/2010

7.1 12/1/08 12/31/2013

4

Going forward, SAP will provide five years of mainstream (standard) maintenance, with the option to extend their maintenance coverage for a period of up to three years for small premiums over the standard maintenance rate.

1. Five years of mainstream maintenance at the standard maintenance fee

2. One year of extended maintenance at an additional two percent maintenance fee*

3. Two more years of extended maintenance at an additional four percent maintenance fee per year*. After these eight years, customer-specific maintenance begins, providing a program of support and services uniquely tailored to individual customer requirements.

The plan covers SAP solutions based on the SAP NetWeaver platform including mySAP SCM, SRM, PLM, CRM, and industry add-ons.

The 5-1-2 maintenance strategy

*check with your account executive to see what your fee may be

5

The Bigger Picture – NetWeaver ??

NetWeaver is a set of solution components that provides a comprehensive architecture.

All components of NetWeaver can use the same operating system release, and the same database release. All components can be run within a single physical server if it is a small configuration, thereby reducing the management of many systems & databases

Visual Composer BI

Kit

Visual Composer BI

Kit

UDI

XMLASAP

QueryJDBC ODBO

Business Explorer Suite (BEx)

BEx Query Designer

Information Broadcasting

Web Analyzer

WebApplication

Designer

MS Excel Add-in

ReportDesigner

BEx Web

DB Connect

BAPI ServiceAPI

File XML/A

BEx AnalyzerBI Pattern

BI Consumer Services

BI Platform

Data Warehouse

Enterprise Portal

Analytic Engine Meta Data Mgr

KM

6

Why Upgrade to NW BI 7.x?

One of the major reasons for upgrading your BW environment is the availability of new content and features in the next release. Let us take a look at some of the major new features of version BI 7.x:

Web Application Designer BI Accelerator BEx Broadcaster BEx Query Designer BEx Report Designer ReModeling Toolbox Security Changes New ETL Interface BPS Integrated Planning PDF print Real-time data warehousing BEx Web Analyzer

We will now take a quick look at these features

7

Web Application Designer is improved

The Web Application Designer is improved with new chart types (Heat Map, GANTT & Milestone Trend Analysis), as well as new layout elements such as ‘tab strips’.

WAD also has new step-by-step wizards for maps, command editing to create Web API Commands and charts, as well as a simplified wizard for layout elements such as radio buttons, action buttons etc.

This reduce the amount of custom coding required with the help of Command wizards, Auto complete and support for HTML tags.

WAD is a key tool for all SAP BI shops

and in BI 7.x the tool is simplified

and more powerful.

New: Integration with NW BI 7.x BEx Report

Designer.

8

Why upgrade? - BI Accelerator for BI 7.x

The SAP BI accelerator makes query response time 50-10,000 faster.

You use process chains to maintain the HPA engine after each data load

HP, Sun and IBM have standard solutions ranging from $32K to $250K+ that can be installed and

tested in as little as 2-4 weeks (+ SAP license fees)

SAP

BW

Any

tool

Blades with 32 Gb are now certified by SAP

9

New Object Types

You can broadcast BEx query views and formatted reports (“reports”) in addition to Web applications, queries and workbooks. Reports are a new BEx object type developed within the new BEx Report Designer tool.

New Output Formats

New output formats are based on the distribution type you select. But, you now can broadcast web documents as PDF files.

New Broadcaster features of BI 7.x

10

New Distribution Types

You can broadcast to any printer using Adobe’s PDF, Printer Common Language (psl) or Post Script (ps). (hint: Set up the printers under tools CCMS print).

You to broadcast user-specific information based on attributes in the master data attributes using a distribution list in BI (bursting of emails). The information can be controlled by the system so that users only see data related to them.

New Broadcaster features of BI 7.x

11

New Broadcaster Features of BI 7.x (cont.)

Exception broadcasting is now available in the Broadcaster. Create the exceptions in the query designer and select distribution type in the broadcaster. You can also use additional distributions types (subordinate) and create rules for when the exception report is “monitored”/ executed. Exceptions can be based on single events or levels of any performance measure.

You can use multiple distribution types to create a setting that broadcasts over many channels (e.g., the printer and the portal).

NOTE: To manage all alerts and workflow tasks from a single location, an alert is integrated with the portal’s universal worklist in the “central alert framework” of NW application server.

12

To increase the performance of key queries, you can fill the OLAP Cache, or the MDX Cache. This is useful if you have large numbers of users accessing a query, or you have a query that accesses a high volume of data.

The Fill Precalculation Store distribution type allows you to precalculate Web templates, and the Precalculate Value Set option allows you to fill precalculated value set variables with values for characteristic values. The precalculated value sets are then available as variable values in BEx queries.

Old Reporting Agent scenarios still run in NetWeaver BI 7.x. However, the Reporting Agent will not be developed any further and is removed from the BI 7.x Workbench. You can now only reach the

Reporting Agent using transaction code REPORTING_AGENT

New Broadcaster Features of BI 7.x (cont.)

13

BEx Query Designer gets a ‘facelift’

The 3.5x BEx Query Designer

Note:

The BI 7.x BEx Query Designer

This new property pane makes it easier to format and control displays than in the past.

You can choose if you want the old or the new look after

the upgrade

14

Why upgrade? - BEx Report Designer

This new 7.x tool was created to simplify the formatting of reports and fix many of the printing issues in previous versions of BW.

We now get color control, header-footer control and many new features such as location control of cells and integration of pictures, charts and fixed text.

For many, this tool may reduce the need for 3rd party tools to address structured reports.

Source: SAP AG, 2008

15

Why upgrade? – The Remodeling Tool Box

In the first releases of BI 7, you could not transport the new models, now you can. You can also:

Remove, exchange, replace, add & fill dimension characteristics and key figures.

NOTE: during (dictionary-based) conversion process, queries are not possible; aggregates will be automatically deactivated and must be rebuilt afterwards

NW BI 7.x goes a long way to address the complaints that BW is a hard to maintain environment with ‘forever’ fixed models.

Source: SAP AG, Richard Brown, Aug. 2008

In BI 7.x you get a new tool to add characteristics and key figures to your model.In older BW versions, if you forgot to include a field in your infocube , the rework was quite substantial and often involved reloading the infocube as well.

16

Why upgrade? - Better security features

There are many new security features in NW BI 7.x, and a conversion is needed (all or nothing).

Role menus are displayed in the portal and passwords becomes case sensitive. If you want to have downwards compatibility with old passwords set the parameter login/password_downwards_compatibility >= 3(SAP Notes 862989 & 1023437)

Authorizations are fundamental building

blocks of the new reporting concept and security contains both

the data value and hierarchy restrictions.

The new security can be built using new “RSECADMIN”

transactionSource: SAP AG

17

Why upgrade? - More Authorization Objects

You get the ability to use much lower security

granularity for developers and users!!

Source: SAP AG

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 objectsS_RS_TR: For transformation rules and their sub objectsS_RS_CTT: For currency translation typesS_RS_UOM: For quantity conversion typesS_RS_THJT: For key date derivation typesS_RS_PLENQ: Authorizations for maintaining or displaying the lock settingsS_RS_RST: Authorization object for the RS trace toolS_RS_PC: For process chainsS_RS_OHDEST: Open Hub Destination

Authorization objects for the Business Explorer:S_RS_DAS: For Data Access ServicesS_RS_BTMP: For BEx Web templatesS_RS_BEXTX: Authorizations for the maintenance of BEx texts

Authorization objects for the Admin of analysis authorizationsS_RSEC: Authorization for assignment and administration of analysis authorizationsS_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

18

Upgrading to BI 7.x Security

SAP has created an ABAP migration tool in SA38 (RSEC_MIGRATION) to help you upgrade security in NW BI 7.x.

Customer exit variables for the object 0TCTAUTHH does not migrate, and you will have to manually reassign all hierarchy nodes.

After technical upgrade, you can select new Concept (Notes: 820183 & 923176)

New BI authorizations are set in SPRO (maintained in RSECADMIN).

If you used an authorization concept in SAP BW 3.x, switch back to “Obsolete Concept with RSR Authorization Objects”.

19

Why Upgrade? – Better ETL Design (conversion needed)

1. RSSM_CREATE_REQDONE_FROM_SEL2. RSSM_HASH_ENTRIES_CREATE for all requests3. RSSTATMAN_CHECK_CONVERT_DTA 4. RSSTATMAN_CHECK_CONVERT_PSA

NW BI 7.0 has a new transformation concept that replaces transfer and update rules. Migration to new data flow is not mandatory, but assistance is available for several key objects.

A migration the complete data flow will require a significant effort. To do so, convert the DataSources and the Persistent Staging Area to the new DTP process, follow SAP Note 906789.

To test the conversion of the DataSources you should also run:

More work: To redefine BI Statistics, see notes 934848 & 964418. Also, use SM37 in production to find any other jobs that are scheduled, and

make sure they are also tested

20

Some upgrade hints

A step-by-step approach to moving to new data flow architecture usually makes the most sense. Identify key data flow scenarios and plan migration for those first.

Existing data flow scenarios are unchanged after the technical upgradeBI 7.0 objects use background processes and 3.x objects use dialog processes

The objects can co-exist but can potentially cause problems with batch windows and performance optimization

DataSource “emulation” allows mixed mode. It provides 3.x DataSources in the form of new runtime objects in 7.x

DataSource “migration” is optional

21

Why upgrade? - BPS Integrated Planning (still supported)

You can now create planning templates using the web based planning wizard to create models using patterns in the data (tool: “Road map Pattern”). Queries based on aggregation levels can now also write back to the InfoProvider

1 2 3 4 5 6

InfoProvider Aggregation Level Planning SequencePlanning FunctionFilter Pattern


22

Why upgrade? –PDF Print

You can also use the PDF to create reports based on BEx web applications, queries and reports using the Adobe DS (comes with BI 7.x).

The only Gotchas.. Your users now need to install Acrobat Reader (free at http://www.adobe.com/ products/acrobat/readstep2.html).

The PDF document can also be Broadcasted through BEx Broadcaster

The PDF options allows companies to protect reports from changes by

employees by taking a ‘snapshot’ of the data regardless of subsequent updates

to the data warehouse.

Risks: no link back to SAP BW is needed and security is not validated.

23

Better web printing – leveraging PDF and web controls

PDF based BEx Web printing now include a variety of functionality, such as:

1. Fit to page width

2. Repeat column headers

3. Fit to one page

4. Wallpaper

5. Page margins

6. Export Themes (e.g. black/white)

7. Format & Alignment

8. Additional Headers & Footers

9. Print graphics and tables10.Batch Printing via Broadcaster

24

Why upgrade? - Real-time Data warehousing gets better

NW BI 7.x has more features for updates that does not follow the typical asynchronomous (batch) updates. This include:

1. We can use XML to fill the PSA directly 2. Daemon-based update from delta queue (BW API)3. Daemon-based update of the ODS and minimal logging

Note: XML documents creates many tags that will slow down large data loads due to the size of each XML

record (relatively large)

However, it works great for smaller streams of data.

25

Why upgrade? - BEx web Analyzer integrates Excel

The Excel integration in the BEx analyzer is far better.

Unlike the old days of dynamic HTML, you can now use the BEx analyzer more like a real application without refreshing the whole page every time you click on something (this is due to the Java component in BI 7.x)


News: BEx browser went away in BI 7.x

26

Why upgrade? - Drag-and Drop in BEx web Analyzer

You can drag a characteristics into a filter area and automatically filter on that value, and you can also drag it into a column header or a row.

Building conditions and activating them was often confusing in earlier versions and exception based reporting was sometimes not easy to create for beginning users. BI 7.x has now simplified this with more wizards that helps users to build this step-by-step.

BEx web analyzer is a better user tool than in the past. You now get the best

world of Java & the web instead of the more ‘clunky’ user experience

related to Dynamic HTML

27

More Administrative tools for management & development

• Enhanced Dataflow control (split delta)• Administrator Cockpit (Web-based)• BI Accelerator (high performance BIA)• Enhanced InfoSets with InfoCubes• Re-modeling and repartitioning of InfoCubes• New Data Transfer Process (DTP)• Write-optimized DataStore objects• New Admin Workbench

Use transaction RSA1OLD to access the old Administrator Workbench

28

What is arriving soon?

SAP Acquired Business Objects in 2007/2008 and is working on integrating BOBJ into the core SAP BI offerings.

29

New Tools Roadmap

Source SAP AG, June 2008

Many of the tools we mention here goes in to standard maintenance in 2009, and can be leveraged until 2014-2016

30






31

BW Content Upgrades

Apply content when you need it, to the technical release you have!!

The new upgrade strategy from SAP is to provide BW technical releases as part of NetWeaver and BI content add-ons,

You do not need to perform a technical upgrade to update the business content.

We now have SAP BI 7.0 and the content releases 7.0.1 and 7.0.2 and 7.0.3 are now available. Planned upgrades should also include the content release 7.0.3.

Details around each content release is available at http://help.sap.comThe current content (7.0.3) is available at: http://help.sap.com/saphelp_nw04s/ helpdata/en/ 44/16e6f7a6f30d19e10000000a114a6b/RN_703_en_final.pdf

32

How can you weigh the choices of Technical or Functional?

32

Source: SAP AG

Source: JesperChristensen, 2008

Technical upgrades have a set of activates that can be separated from a functional upgrade

How much disruption and training can your organization absorb?

33

Weighing Towards a Technical Upgrade

• A technical upgrade is the “safest” way to proceed

• It is also the fastest and the least expensive

• Your user community will notice little to no change UNTIL you start rolling out the new functionality

Source: SAP AG

34

Weighing Towards a Functional Upgrade

• A functional upgrade (which includes all the technical activities) will make the biggest impression on your user community This will take longer –

and cost more money

• You will be able to sunset other solutions sooner

• You will get the most benefits – from usability and management

Source: SAP AG

35

Some hints on the upgrade – client, engines and usage types

We are in a transition period, when some items of BI 7.x are separate engines, some are clients, and other are usage types.

Key question: is you organization committed to java and the new BI 7.x direction? -- if so, go java ‘all the way’..

PS! SAP recommends having Java AS on dedicated servers

Source: SAP Installable software units May 2007

Note: standard system copy and SAP migration tools have no standard support for splitting or merging

systems with different usage types

36

Some upgrade choices – the architecture

Note: Depending on your current installation of SAP BW, you have different upgrade options

Upgrade Or

Source: SAP AG May 2006

Upgrade Or

Upgrade Or

1

2

3

37






38

Typical Training Requirements

38

SAP official delta training at the client site (DBW70R, DBW70E) seems to be valuable for many clients.

39

BW Version

Release date

End of mainstream maintenance

Can be upgraded to

2.0B 8/14/00 12/31/2005 2.1C, 3.0B, 3.1C, 3.50/3.512.1C 12/18/00 12/31/2005 3.0B, 3.1C, 3.50/3.513.0A 11/15/01 12/31/2005 3.0B, 3.1C, 3.50/3.513.0B 5/13/02 12/31/2006 3.1C, 3.50/3.513.1C 11/11/02 12/31/2006 3.2 and 3.3 must be applied before 3.53.2 3/31/03 12/31/2006 3.3 must be applied before 3.53.3 8/30/03 12/31/2006 3.53.5 3/31/04 3/31/2010

NetWeaver BI 7.x Upgrade paths

Still supported…

Current Release NW 2004s Release/supportBW 3.5 (min. SP04) and ABAP, any content release (3.5.x)

BW 3.1c (min. SP14) content 3.2 or 3.3BW 3.0B (min SP20)

BW 2.1C (min. SP18)

BW 2.0B (min. SP26 & Basis SP29)

OtherSAP BI 3.5 Java components (i.e. UDI) on WAS-Java System with usage type SAP AS Java

NetWeaver 2004s usage type ABAP, (usage BI java and EP can be add-ins or

separate systems.

Must be upgraded to SAP BW 3.5 first and then BI7.0 (upgrade with NetWeaver 2004s

Support release 1)

40

Some hints – Upgrade programs SAPup and SAPjup

You will need to install the NetWeaver Application Server Java and the specific user type, before you can use all the features of BI 7.x (i.e. Business planning and analysis services, Enterprise data warehousing, Reporting and analysis scenarios etc). You can install this as a separate system or as an add-in to the upgraded ABAP server.

SAP provides a software program called SAPup to help you upgrade the WAS (ABAP) and SAP BW. It is called a “system switch upgrade”.

Note: if you already have java installed, you can also use the upgrade program called SAPjup, to upgrade the WAS-java.

If the WAS-Java was installed on the same system as the WAS-ABAP (as an add-in) you need to run both the SAPup and SAPjup

programs in parallel (see the Master upgrade guide for more details).

41

Some hints on the upgrade - Unicode conversion

Unicode has been available since BW version 3.5.1. and is now highly recommended as part of the upgrade (hint web application designer is now also Unicode compliant).

Some things to remember and plan for:

يآلإلقفغ

غяь

фдФ

њщ

Ệẁ תשרחפא

ǻǼǽǿ

Area Recommended increased capacityMemory 20%Processing power 20-25%Disk space 20-30%45-50%

42

Planning Your Upgrade – a Hardware Example

Production

12 CPU

96GB RAM

Sandbox

4 CPUs

32GB RAM

Test

4 CPUs

32GB RAM

Development

4 CPUs

32GB RAM

This west coast company reallocated their Sun-6900 box (on Oracle) and have 3 Appservers on the production box..

More memory allows them to take better advantage of the parallel load of the BW system as well as to cache many of the frequently run queries (BEx Broadcaster)

The hardware also allows them to have a system where performance between the boxes are comparable.

Example

Key numbers: 3.1 Terabytes of data; 2810 named users and about 620 active users

43

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.

Team Lead

Basisresource

Technical reviewer Upgrade Support

External

Regression Testers

Team Lead

Basis Technical reviewerBW Developer

Upgrade Support

External

Regression Testers

44

Sample Timeline - complete landscape for large BW implementation

W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12

Project startup and Team training

Preparation for upgrade of Sandbox system and roll out of SAPGui

Upgrade Sandbox system

Test functionality and decide what to implement in upgrade (What has the best ROI)

Plan upgrade of production landscape

And roll out of new functionality to users

Upgrade development system

Test and validate upgrade

Implement new functionality

Upgrade Test system

(Copy of production if possible)

Test and validate Test system and user training & roll out of SAPGui

Upgrade Production system

Test and validate Production system

The more content you have the longer the upgrade(the more you have to

regression test)

The duration is driven by:1. The number of BW systems in your landscape.

2. The new functionality your are rolling out

3. The support technology needed

45

Minimum Timeline and Basic events:

Do initial upgrade guide and note research [1-2 days]

Upgrade BW sandbox and do cursory issues check [1-4 days]

Upgrade a copy of BW production – have key development leads regression test all live content (both systems must be connected to other landscape environments – testing extractors too!) [2-5 days (size/copy/hw depending)]

Once the initial regression test is complete, create correctional transports. [3-5 days]

Post-fix, have full team in for “Upgrade buy-in testing” that all works properly [2-3 workdays]

KEY: now freeze development and release transports, upgrade development and a test system, incorporating the fix transports generated from the upgrade regression test. This should be a clean 2-4 day process.

You need to have the SAP solution Manager to generate the key during the upgrade to NW2004 SR1, and you will need to be on Solution Manager

release 3.2 SP8 or higher to make it work (note: 805390).

46

Move into Landscape

• At this point you have a temporary BW Dev to test patch, and perhaps static training, production and production support systems.

• Ideally, you’d migrate the upgrade to these as soon as possible, but this is a stable point. You will have to decide, based on content, whether copying a test box to training makes sense (can preserve user master)

• For production and production support, you’ve already done a dry run – just do production and copy back to production support unless the size makes this impractical [~ >500GB]

Hardware requirements changed if you also did Unicode conversion (recommended)

47






48

Step -1: Hardware install and BWS Copy

BWX BWD BWQ BWP

BWS BWX BWX BWX

1

3

2 4

January Feb March April

21 28 4 11 18 25 3 10 17 24 31 7 14

Hardware install

Copy BWD to new BWS

Upgrade DB2 to latest version

Post processing of box

Rename/restore old BWS box

Download latest patches for upgrade

In this real example, we are also In this real example, we are also installing new Hardware. This gives installing new Hardware. This gives us lot of flexibility…us lot of flexibility…

First, we copy the old development First, we copy the old development system to the new Sandbox system to the new Sandbox (new HW)(new HW)

In this real example, we are also In this real example, we are also installing new Hardware. This gives installing new Hardware. This gives us lot of flexibility…us lot of flexibility…

First, we copy the old development First, we copy the old development system to the new Sandbox system to the new Sandbox (new HW)(new HW)

48

49

Step -1: BWS Unicode conversion, Java upgrade & test

BWX BWD BWQ BWP

BWS BWX BWX BWX

1 2


21 28 4 11 18 25 3 10 17 24 31 7 14

Start upgrade BWS

Start shadow instance

SPDD start

ICNV start

Start syst. downtime upgrade activity

Complete BWS upgrade

Post processing

Basis and functional testing

Unicode conversion

Java upgrade

3

4

At this stage you should document and At this stage you should document and test all work that occurs. Some time test all work that occurs. Some time has to be set aside for notes research has to be set aside for notes research and unforeseen issues.and unforeseen issues.

We want to creating a repeatable We want to creating a repeatable process, so no ad-hoc activities are process, so no ad-hoc activities are allowed.allowed.

At this stage you should document and At this stage you should document and test all work that occurs. Some time test all work that occurs. Some time has to be set aside for notes research has to be set aside for notes research and unforeseen issues.and unforeseen issues.

We want to creating a repeatable We want to creating a repeatable process, so no ad-hoc activities are process, so no ad-hoc activities are allowed.allowed.

50

Step -2: System copies

BWX BWX BWX BWP

BWS BWD BWQ BWX

1

3

2 4


21 28 4 11 18 25 3 10 17 24 31 7 14

Copy BWD

Development freeze

Rename BWD

Copy BWQ

Rename BWQ

Copy PDW (no rename yet). It is still the production system..

You now freeze the development and You now freeze the development and can take copies of the BWD and BWQ can take copies of the BWD and BWQ system and prepare for upgrades.system and prepare for upgrades.

The old BWP is still running as the The old BWP is still running as the productive system..productive system..

You now freeze the development and You now freeze the development and can take copies of the BWD and BWQ can take copies of the BWD and BWQ system and prepare for upgrades.system and prepare for upgrades.

The old BWP is still running as the The old BWP is still running as the productive system..productive system..

50

51

Step -3: BWD upgrade

BWX BWX BWX BWP

BWS BWD BWQ BWX

1

3

2 4


21 28 4 11 18 25 3 10 17 24 31 7 14

Complete Prepare on BWD

Apply fixes

Start upgrade BWD


SPDD start

ICNV start


Complete BWD upgrade

Post processing


Unicode conversion

Java upgrade

We now repeat the process. We now repeat the process. Remember, you have already upgraded Remember, you have already upgraded BWD once (in step-1) and should know BWD once (in step-1) and should know the need for any post processing.the need for any post processing.

Don't ignore the need for technical and Don't ignore the need for technical and functional testing.functional testing.

We now repeat the process. We now repeat the process. Remember, you have already upgraded Remember, you have already upgraded BWD once (in step-1) and should know BWD once (in step-1) and should know the need for any post processing.the need for any post processing.

Don't ignore the need for technical and Don't ignore the need for technical and functional testing.functional testing.

52

Step -4: The real test -- BWQ upgrade

BWX BWX BWX BWP

BWS BWD BWQ BWX

1

3

2 4

• •


21 28 4 11 18 25 3 10 17 24 31 7 14

Complete Prepare on BWQ

Apply fixes

Start upgrade BWQ


SPDD start

ICNV start


Complete BWQ upgrade

Post processing


Unicode conversion

Java upgrade

Functional test and go/no-go decision

Notice, the refreshed new BWQ from Notice, the refreshed new BWQ from BWP, so this is really a BWP upgrade…BWP, so this is really a BWP upgrade…Notice, the refreshed new BWQ from Notice, the refreshed new BWQ from BWP, so this is really a BWP upgrade…BWP, so this is really a BWP upgrade…

53

Step -5: The Big One: Cut-Over weekend….

BWX BWX BWX BWX

BWS BWD BWQ BWP

13

2 4


21 28 4 11 18 25 3 10 17 24 31 7 14 18 19 20 21

Java install

Remove data in new system

Rename BWP

Complete Prepare on BWP

Apply fixes

Start upgrade BWP


SPDD start

ICNV start


Complete BWP upgrade

Post processing

Basis testing

Functional test

Unicode conversion (TBD)

Contingencies should be made. I.e. notice Contingencies should be made. I.e. notice that is any showstoppers occur on 20that is any showstoppers occur on 20thth, the , the old BWP can be renamed back, or if the old BWP can be renamed back, or if the time becomes too short the Unicode can be time becomes too short the Unicode can be done the next weekend.done the next weekend.

Contingencies should be made. I.e. notice Contingencies should be made. I.e. notice that is any showstoppers occur on 20that is any showstoppers occur on 20thth, the , the old BWP can be renamed back, or if the old BWP can be renamed back, or if the time becomes too short the Unicode can be time becomes too short the Unicode can be done the next weekend.done the next weekend.

54

Other examples and lessons learned

Mfg. Retail Government Finance EnergyOld version 3.1C 3.5.3 3.5.3 3.1C 3.5.3Duration 10 weeks 9 weeks 10 weeks 12 weeks 14 weeks

Scope 3 Tb/900 users 6 Tb/300 users 1 Tb/80 users 7 Tb/1,200 users 4 Tb/500 usersNumber of environments 9 5 4 4 4Number of core team members 4 3 4 5 3Hardware switch No No Yes Yes NoTesting 2 weeks 2 weeks 3 weeks 4 weeks 2 weeksUnicode No Yes Yes Yes NoHardware Sun IBM Sun Sun IBM

Lessons Learned

Have the right people in place. Wait until they are available

and have a core business team for short bursts

of testing

Unicode took a bit longer than expected. Wait with rollout of

new functionality

until you have a stable

environment

If possible, reload the data during Unicode

conversion (faster).

Hardware switch removed a lot of risk and

made the upgrade faster.

Could have done this faster, if

business people had been

scheduled for testing earlier.

Otherwise smooth process.

Did not have the right technical

people involved. This added 6 weeks to an otherwise

straight-forward upgrade.

55

Some areas you should focus on

1. Web TemplatesA semi-automatic conversion is possible using the BI 7.0 WebApplication Designer. (SAP Notes 832713, 832712, 1074997 & 1026591)

Since Web templates are neither overwritten nor changed during migration, you can migrate templates as often as you want. Be prepared for manual intervention and fixes.

2. InfoSets can become inactive after the upgrade Use program RSQ_ISET_MASS_OPERATIONS to activate all InfoSets after the technical upgrade prior to running any queries

3. Transfer rules can become inactive after the upgradeUse program RS_TRANSTRU_ACTIVATE_ALL to activate all transfer rules after the technical upgrade prior to running any data loads

56

4. Query Conversion and Activation

Recommendation: Once you decide to move to the new BEx tools, perform a one-time conversion of all queries in the system to BI 7.0 to avoid having two query designer tools in use at the same time

Use WinRunner or a similar tool to open all queries in the BI 7.0query designer and save them. This will converts query to BI 7.0.

Run program RSR_GEN_DIRECT_ALL_QUERIES to regenerate all queries in the system

Some areas you should focus on

57






58

7 Key Points to Take Home

• Is it cheaper to upgrade to new content or risk reinventing the wheel?

• A BW architecture is part of a larger decision support landscape

• An upgrade strategy should contain all NetWeaver components

• You upgrade strategy must include both release and content upgrades

• Your upgrade time is largely a function of scope, your regression test strategy and the amount of content in your BW

• The BI 7.x upgrade is an extensive one and you should treat it as so.

• Cross reference new features & functionality with your organization’s pain points…and ensure the upgrade costs do not exceed the business benefits

59

Presentations, tutorials & articles www.COMERIT.net

The document “NW BI 7.x Upgrade master Guide“ is available at http://www.sdn.sap.com/

“Business content and extractors SAP BI 7.0.3” available at http://help.sap.com/saphelp_nw04s/helpdata/en/44/16e6f7a6f30d19e10000000a114a6b/RN_703_en_final.pdf

“Component upgrade guide SAP NetWeaver BI 7.x ABAP” available at http://help.sap.com

ResourcesResource

60

Your Turn!

How to contact me:Dr. Bjarne Berg

[email protected]

best practices for your sap netweaver business intelligence 7.x upgrade

Documents

maintenance strategy

maintenance coverage

maintenance system

years of extended maintenance

standard maintenance

percent maintenance

year of extended maintenance

customerspecific maintenance