upgrade to bw 7 - a248.g.akamai.neta248.g.akamai.net/n/248/420835/f83e9620dca9efd338b... · upgrade...

Upgrade to NetWeaver BW 7.3x

New features with ABAP Upgrade

to 7.30 and 7.31 (EhP 1 for 7.30)

Roland Kramer, Product Expert PM EDW/HANA/IQ

July 2012 November 2013 June 2016

Please refer to Document - http://scn.sap.com/docs/DOC-30452

http://scn.sap.com/docs/DOC-30452

© SAP AG 2009. All rights reserved. /

Agenda

1. Technology/Roadmap facts

2. What’s new with the Upgrade to BW 7.3x

3. Usage of the ASU toolbox for BW

4. General checks prior to the Upgrade

5. Details of the Upgrade Process


Evolving In-Memory Footprint in SAP

NetWeaver BW 7.30 and 7.31

Planning Engine

Data Manager

InfoCubes

DataStore Objects

Analytic Engine

Data Persistency

and Runtime

Data

Modeling

Ente

rprise D

ata

Ware

house a

nd D

ata

Mart

Mod

elin

g w

ith

SA

P N

etW

ea

ve

r B

W

BWA instead of

aggregates

Filter +

aggregation

BWA-only

InfoCubes

BWA reporting

for DSOs

In-Memory

optimized

DataStore Objects

In-memory

planning engine

First calculation

scenarios in BWA

Additional

calculations

in-memory

MultiProvider

handling and

flexible joins

BW 7.0

DB + BWA 7.0

BW 7.3

DB + BWA 7.2Planned: BW 7.3 on HANA

SP5 and beyond

EDW Processes

In-Memory

optimized

InfoCubes

Consumption of

HANA models in

BW

HANA data for

BW Staging

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality

mentioned in this presentation. 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 assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.


SAP NetWeaver BW 7.30 vs. 7.31

choose the Go-To Release for NetWeaver BW

SAP NW BW 7.3

(on HANA) SP07

• Already General

Available

• All SAP NW BW 7.3

functionality plus SAP

HANA enablement

SAP NW BW 7.31 (on HANA) SP05

• New Installation on anyDB/HANA available: Q2/2012

Upgrade/EhP1 on any DB available: Q2/2012

Install of EhP1 on HANA available: Q3/2012

• All SAP NW BW 7.3 functionality plus:

• Improved fresh Installation based on 7.31 SP04

• Simplified Upgrade with SAP Upgrade Manager (SUM) 1.0

• All Post Copy Automation - BW Basis functionality is included in SP04

which enables a quick and stable migration to BW on HANA

• From every NetWeaver 7.0x Release, the Installation/Upgrade of the

SEM Add-on 7.36 is possible.

• The Gateway Add-on (OData) can be implemented for BW EasyQuery

access on a NW 730 EhP1 system.

• BW 7.31 SP04 is released between SP07/08 for BW 7.30

(which includes 3 Month of further development)

Recommendation for the upgrade to BW 7.31 SP04 : Customers on ≤ NW BW 7.0 should upgrade directly

Customers on NW BW 7.3 should plan the EhP 1 upgrade for their next regular maintenance cycle


Upgrade to BW 7.3x - ABAP

NetWeaver Java 7.3x is now shipped together with BW 7.3x. Mandatory you should separate

the Java Stack prior to the Upgrade of the ABAP Backend, if not already done.

The new split/deinstallation tool for the Java Stack is expected to be available November

2011. If you are already in the process, consider the manual deinstallation of the Java Add-In

until it’s availability.

The BICS are moving to the upcoming SAP BusinessObjects Application Platform BI 4.x,

which is also a prerequisite for the full usage of the BEx successor - Analysis -

The Java component BW-IP modeler is redeveloped for BW 7.3x in ABAP HTTP, so the Java

Server will not be used anymore for the BW-IP infrastructure in the future after BW 7.3x

The new BI Authorization concept is now mandatory. Despite the fact that you either create a

7.0x System beforehand to migrate the old BW Authorization, a potential Upgrade from BW

3.5 to 7.3x would be possible.

NetWeaver 7.0 EhP3 is merged into NetWeaver 7.3x EhP1 (there is no 7.03, only 7.31).

All Components are using one consolidated Version of the Kernel (7.20 Unicode-EXT 64-BIT).

For compability reasons there are non UC/non EXT Versions available (no 32-BIT anymore)

The full (currently only limited by size of the DB) BW on HANA Support is available

with 7.30 SP07 and 7.31 SP04

Note 1641432 - SAP Product Master Releases

Some technology facts and updates

https://service.sap.com/sap/support/notes/1641432


Solution Manager pre requisites

incorrect stack.xml can create unwanted follow up errors

In order to successfully work with the Solution Manager to create necessary

stack.xml, which is a new requirement in NetWeaver based upgrades the following

checks had to be fulfilled prior to the creation of the stack.xml.

■ Sufficient privileges for the s-user, which is connected to the Service Market Place (SMP)

■ Updated PPMS data, to ensure the correct processing of the desired Upgrade Target‘s

■ Note 1603103 - SMSY: NetWeaver 7.3 upgrade

■ Latest SP‘s/correction/Notes for the correct usage of the Solution Manager applications

For more information about the Maintenance Optimizer, see SAP Support Portal at

■ http://service.sap.com/solman-mopz

Furthermore if you have ERP components installed, e.g. the SEM Add-On, consider

■ Note 1326576 - SAP NetWeaver Systems Containing SAP ERP Software Components

■ Note 1927083 - SAP NetWeaver Systems with SEM-BW

new Option allows you more flexibility, see Blog

Good News - Easier Modeling of the SEM Add-On in Solution Manager


http://service.sap.com/solman-mopz


http://service.sap.com/sap/support/notes/1927083

http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2013/11/13/good-news--easier-modeling-of-the-sem-add-on-in-solution-manager



Note 1532805 - Add-On Compatibility of SAP NetWeaver 7.3

There is a SEM Add-On (only for the Upgrade) available with BW 7.30. The SEM (6.34) Add-

On is available since end of Q1/2011 for all Customers. See Notes 1539356 and 1531022 for

more details. SEM 6.34 cannot be installed on a fresh BW 7.30 Installation

SEM 6.34 is HANA enabled, see Note 1648413 for more Details.

The direct update from BW 7.0/SEM 6.0 to BW 7.31/SEM 7.36 is possible (Note 1326576)

An Upgrade to NetWeaver 7.31 (7.3x EhP1 equal with 7.0 EhP3) is possible, when SP02 or

higher is available for 7.31 and the equivalent SP for SEM 7.36.

This Combination is currently in Rampup (November 2011) and will run until End of May 2012

There is also the BPC 10.0 Add-On available with BW 7.30 which is currently in Rampup

(GA expected for November 2011). With NetWeaver Version there is no Windows Server

necessary anymore (web based maintenance). See Notes 1585589 and 1620027 for details.

It is planned with SP06 (CPMBPC 800) to be HANA enabled

Additional Add-On´s like GRC or DMIS will be enabled for the Upgrade to NetWeaver 7.31

Decision about installed Add-On´s




SEM Add-On Implications - http://help.sap.com/sem

BW 7.3/SEM 6.34

(specific case for EhP4)

Upgrade to

NetWeaver 7.31

SEM 7.36

possible!

Choose your NetWeaver BW Start Release

BW 7.01/SEM 6.04

(specific case for EhP4)

Upgrade to

NetWeaver 7.3

SEM 6.34

possible!

BW 7.0x/SEM 6.0x

(generic EhP approach)

Upgrade to

NetWeaver 7.03/7.31*

SEM 7.36

possible!

(Note 1326576 and

1927083)

BW 7.0/SEM 6.0

(EhPs except EhP4)

Upgrade to

NetWeaver 7.3

SEM 6.34

possible!

Consider Options in Notes 1539356 (7.30), 1681435 (7.31) and 1531022 (SEM)

Blog: Good News - Easier Modeling of the SEM Add-On in Solution Manager

Recommended Option: 1927083 - SAP NetWeaver Systems with SEM-BW

Change to Add-On Product Version of SAP SEM (CISI)

http://help.sap.com/sem

http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2013/11/13/good-news--easier-modeling-of-the-sem-add-on-in-solution-manager



New BI 4.0 Installation for SAP BW Customers

Platform View - Proposal

SAP BW 7.0

Physical Server

(optional)

SAP NetWeaver

SAP NetWeaver

Functions

J2EE 7.0

ABAP 7.0

SAP Usage Type and

SAP BusinessObjects

Tiers, Apps, Services

The XI 3.1/BI 4.0 Java apps can deployed either on an existing SAP J2EE 7.0x or 7.3x Engine, or ideally

capsulated with BI with Tomcat. Consider the SAPJVM 4.1. A JVM switch tool is available as well

SAP BW 7.01

J2EE 7.01

BEx Web

BICS

EP

ABAP 7.01

Split

J2EE 7.3x

BEx Web

BICS

EP (opt)

SAP BW 7.3x

ABAP 7.3x

BI Java

EP

BI Java

EP

BI Java EP

LCM ClientBI Launch Pad

… (*)

BI 4.x

BI Reporting & Infrastructure Services

BI Web Apps

BI Web Tier

BO XI 3.1

BOE XI Web Tier

XI Reporting & Infrastruc. Services Migr.


J2EE Options for BI 4.0 together with BW 7.3x

use the recommendation with the BI 4.0 inbuilt Java Server

BI 4.0

SAP NetWeaver J2EE

7.3x

Other J2EE

(see PAM)

BI 4.0 SP2

BICS

BEx Web

BI 4.0 SP2 Only

BICS

BEx Web

BI 4.0 SP2

Usage Type EP

Usage Type BI Java

(BICS, BEx Web)

BEx Web Limitations*

- No Broadcasting (Portal/KM)

- No Documents (Portal/KM)

- No Xcelsius BW Connection

InstallUpgrade from BW 7.0xInstall

BEx Web Limitations*

- No Broadcasting (Portal/KM)

- No Documents (Portal/KM)

- 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.x and 7.x Web templates. 3.x Web template to not require BI-JAVA 7.x


Single ABAP 7.0x Stack

Dualstack Options prior to the Upgrade BW 7.3x

separation of ABAP and JAVA easies the upgrade process

BW 7.0x Dualstack

Deinstall JAVA Add-In Use Split tool

Upgrade

to JAVA 7.3x*

Upgrade

to BW 7.3x ABAP

Fresh Install of

JAVA 7.3x (without ADS)

BW 7.3x

ABAP Stack

NetWeaver 7.3x

JAVA Stack (with ADS)JAVA 7.3x Upgrade limitation*

- no automatic file system 7.x

- no automatic SAPCryptoLib

- disable SNC configurationADS = Adobe Document Services (obsolete with NetWeaver 7.3x BI-Java)

Deinstall JAVA 7.0x Stack Deinstall JAVA 7.0x Stack


SAP Business Intelligence Architecture 2013

Choose the suitable combination

BW 7.3x UpgradeJAVA fresh Install

(Not the central EP)

BI 4.0 Upgrade

BI 4.1 fresh Install

BW 3.5

BW 7.0

BW 7.0x

Depended from

SEM Add-On and

Analysis Authorizations

Deinstall/Split Java Add-In

Deinstall JAVA Instance

BW 7.01 SP08 and higher

BW 7.0 (not recommended)

BW 3.5 (not recommended)

JAVA

7.0x

Add-On

or sep.

Install

Deinstall/Split Java Add-In

Deinstall JAVA InstanceFresh JAVA 7.3x Install

Upgrade/Migrate to BI 4.x

Fresh BI 4.x Install

Use BI 4.x In-Build JAVA

Application Server

XI 3.1 XI 3.1 SP04Fresh JAVA 7.01 Install

Fresh JAVA 7.3x Install

Upgrade/Migrate to BI 4.x

Use BI 4.x In-Build JAVA

Application Server

BI 4.0/4.1 together with BW

7.3/7.31 (Note 1750236)


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.3x

■ You cannot switch back to the former concept

■ New Transaction RSECADMIN, see SAP Notes 942799 and 944929


Example Project schedule for the Migration

Combined technical Upgrade & Authorization Migration

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

KickOffLegend: Duration Milestone

Start Upgrade

1st month 2nd month 3rd month 4th month 5th month <month>

GoLive

Remark

Overall project duration dependents on the system complexity.

Given example is based on a higher complexity.

To match with typical technical Upgrade Plan, start two month in advance.


General Guidelines and Notes

ALM BW operations page in SCNhttp://scn.sap.com/docs/DOC-7856#section8

NetWeaver BW 7.3 Online Helphttp://help.sap.com/saphelp_nw73/helpdata/en/ca/6fbd35746dbd2de10000009b38f889/frameset.htm

Useful Notes

Note 586648 - Invalid SID entries in /BI 0/SIOBJNM

Note 1022704 - Upgrade Phase EHP_INCLUSION und SPSTACK_REQUEST

Note 1088717 - Active services for Web Dynpro ABAP in transaction SICF

Note 1390477 - Additional info for upgrade to SAP NetWeaver 7.3 (using SUM)

Note 1403832 - Central Note: Upgrade Systems on SAP NetWeaver 7.3

Note 1539356 - Upgrade to NW 7.3 with SEM-BW, FINBASIS, SAP_BS_FND, WEBCUIF

Note 1405878 - SAP Solution Manager - Basic functions SP22 and higher

Note 1484437 - BI_CONT 7.35: Information about installation and upgrade

Note 1543092 - Upgrade of BP_BIADMIN 1.0 to BP_BIADMIN 3.0(BP BW ADMINISTRATION)

Note 1562522 - SAPINST aborts during central instance installation

Note 1603103 - SMSY: NetWeaver 7.3 upgrade

Note 1636053 - Upgrade to SAP NetWeaver 7.3x: BW server: Useful note

Note 1627683 - SCWB/SNOTE/SPAU: Changed development package

Note 1528990 - SP Equivalence for update/upgrade to SAP NW 7.3x

Note 1636841 - Version management: Compatibility with SAP BASIS 7.x0


http://help.sap.com/saphelp_nw73/helpdata/en/ca/6fbd35746dbd2de10000009b38f889/frameset.htm

















Agenda







SAP Upgrade Manager (SUM) 1.0

The SUM 1.0 as part of the SL Toolset 1.0


The Software Update Manager for the SAP

Business Suite

The Software Update Manager is the Software Maintenance Tool for the SAP

Business Suite 7 Innovations 2011*).

*) For further information on the currently available Software Update Manager, see SAP Central Note - Software Update Manager 1.0

SP03 – 1591328 and regarding replaced tools, see Replacements of outdated tools via SL Toolset – SAP Note 1589311.


SAP Upgrade Manager (SUM) 1.0

outlook for 2012

It is planned that future versions of the Software Update Manager will replace

well known tools.

For further information on tool replacements, see Replacements of outdated tools via SL Toolset – SAP Note 1589311.


System Switch Upgrade

New upgrade directory now located at \\sapmnt\<SID>\upg

New with NetWeaver EhP1 onwards


New Upgrade UI

following the EhP development guidelines


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


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 and all other files

in the download directory

■ Create your XML File for ABAP Support Packages in the MOPZ


New Preconfiguration Modes available

Or manual selection see Upgrade Guide Page 46


Update to SAP BW 7.40 and higher

Option “resource minimized” is replaced by “single system”

whenever try to use the “Single System” configuration (transport based load option)

Blog – SUM: introduction to shadow system

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2014/04/02/sum-introduction-to-shadow-system


Upgrade Planning

working until Downtime is possible now


Changeability of BW Objects during Upgrade


Agenda







Accelerated Upgrade to NetWeaver BW 7.3x

Your single source for all pre and post upgrade steps

Use the predefined content for:

upgrade to NetWeaver 7.x BW

upgrade to ERP 6.0 EhPx (upcoming)

upgrade to any SAP Product based on

the NetWeaver 7.x Platform

create/modify own content (XML based)

Complete Business Suite 7

connectivity (with EhP1):

abap - java connection (available) for

connection BW-IP, EP, ESS/MSS, etc.

abap - abap (with EhP1) for backend

connection e.g. ERP, CRM, BW, PI, etc.

java - java (upcoming) for frontend

connection e.g. FPM, etc.

Note 1178800

Lower your TCO and time efforts

by Managing your Upgrade with innovative tools

1. ASU toolbox (incl. BW Content)

one single truth for all pre/post Upgrade Steps

(Note 1000009)

2. CTC for BW-Java

automatic connection between Abap and Java(Note 983156)

Check out the success story from the German Customer Karcher:

http://service.sap.com/~sapidp/011000358700000162292010E/

http://service.sap.com/~sapidp/011000358700000162292010E/


Application Post

checks and functional

tests

Technical post Steps

and Go-Live

Preparation

Application testing

New 7.0 EDW features

Technical testing

BI-Java CTC and

testing of new 7.0

features

Application checks/

cleansing and

Upgrade Preparation

Technical checks and

Upgrade preparation

Agree on result

Last checks

PREPARE

UPGRADE

Pre Upgrade

Steps

PREPARE/

UPGRADE

Post Upgrade

StepsTesting

Upgrade Process with the ASU toolbox for BW

in average 3 days per systems

1 day 1 day 1 day 1 Week

Note: Elapsed time may be longer due to scheduling and lags, etc.

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, Remarks, Documentation can be added immediately as well

XML editor makes adoptions to other SAP upgrades easy.


Typical Scenario for an Upgrade

See Details in SAP Note 1000009

SAP Solution Manager SAP UP SAP System

Start Upgrade RoadMap

Start ASU-Toolbox

before Upgrade Phase(download Content from SMP)

Start Prepare Running Prepare-Jobs

Running ASU-Reports via

Schedule Manager

Start technical UpgradeASU-Toolbox

before Upgrade Phase finished

Prepare finished

Running technical Upgrade

Start ASU-Toolbox

after Upgrade Phase

Technical Upgrade finished

Running ASU-Reports via

Schedule Manager

ASU-Toolbox

after Upgrade Phase finished

Monitoring of all started

ASU-Reports via

Solution Manager

ASU-Upgrade-Note-Display


Typical Upgrade Project Plan

typical duration 6-8 weeks for a 3-System Landscape

Start after first comp. Stack (3d/Sys)

3d

3d + 1w Test

Ongoing (several weeks)

Steps/Milestones

3d + 1w Test

3d

Start after first Upgrade (2d/Sys.)

2w

Upgrade Tasks

Upgrade Planning

Upgrade of Development

Additional testing

Setup of BWA or BW on HANA

Upgrade of Test

Upgrade of Production

SAP Java Server/EP

Go Live BWA or BW on HANA

todayLegend: Duration Milestone 6 weeks 8 weeks

Time in total: 9d Upgrade, 10+d testing, 6d Java Inst, 9d het. Systemcopy, conversion IC/DSO individually, BW on HANA testing individually


Pre Steps of ASU toolbox for BW - 1


Post Steps of ASU toolbox for BW - 1


ASU toolbox – BW specific

Install latest ST-PI 2008 Add-On (SP05)

XML can now be changed within the

same screen, e.g. new or changed

items/checks can be added immediate.


Agenda







New with NetWeaver 7.0x Daemon process

Stop all Daemon Process with Transaction RSRDA


Activate all DataStore Objects

Valid for all BW Releases 3.x and 7.0x


Repair Inconsistent InfoPackages

Transaction RSBATCH


Further general Upgrade Checks

SAP_DROP_TMPTABLES and RSUPGRCHECK


Check the Secure Storage with SECSTORE

e.g. if System is a copy from Test/Production


Transaction SECSTORE


Check for missing TLIBG entries

New check from NetWeaver BW 7.0x onwards (Note 783308)

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"

proceed as follows:

1. TA: SE80

2. Select the 'Function Group' option from the dropdown menu

3. Enter: XXXXX

4. Follow the instructions.

5. Continue with the upgrade.

or run the report RSTLIBG to avoid these errors in the PREPARE beforehand.


Check for wrong source systems assignments

Note 1564964 - Source system XYZ does not exist

use function module RSAR_LOGICAL_SYSTEM_DELETE in advance to remove old

source systems.

Note 1546842 - Message SY530 in the transport log RS_DTRF_AFTER_IMPORT

minimum start release for Upgrade 7.01 SP08 or higher (see also Note 1469150)

Note 1649901 - Time-critical processes in BW upgrade/Support Package import

table RSADMIN REPL_D_AFTER_IMPORT = X

to prevent long runtimes in upgrade step AIN_NEWBAS/XPRAS_AIMMRG.

In advance run report RS_LOGSYS_ACTIVATE before/after the upgrade

Note 1894463 - Upgrade terminates with error RS0 871 or RS0 876

table RSADMIN RSVERS_BI_IMPORT_ALL = ‘ ‘

Note 1870559 - IMPORT ALL(4): ASSERTION_FAILED in SAPLRSVERS

import prior to the upgrade to NetWeaver 7.3x

Note 1668456 - DTP: Fehlermeldung RSO851 bei Upgrade / Content-Installation

import prior to the upgrade to NetWeaver 7.3x, see also Note 1633805

Inconsistent source system can create long runtimes in XPRAs








Usage of the SAP Solution Manager

Create the Stack XML File

Transaction SOLMAN_WORKCENTER


Choose the Option Upgrade for your source system




Choose the Option Maintenance for the Upgrade



Confirm the Major Target



The XML File is created and available for download or in the EPS inbox


Agenda







New SUM procedure for all SAP releases

Available since SUM 1.0 SP12 onwards

Blog: Update has never been easier …

http://scn.sap.com/community/bw-hana/blog/2014/12/19/upgrade-was-never-been-easier


Upgrade UI – Start Page

http://<server>.<domain>.<ext>:4239

http://iwdf3102.wdf.sap.corp:4239/


SAP JVM location/environment variables

start DSUGui.bat separately, if the Web Browser is not working


Upgrade UI

Details for Step Initialization


Upgrade Password provided in Note 1403832

Put all updates from SMP into the download directory

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


Include the Stack XML from Solution Manager

A correct configured Maintenance Optimizer is a prerequisite now


Add all main DVD here

Remove empty lines in advance Add-On’s as SAINT packages


Solution Manger Upgrade Key ready

Solution Manager – MOPZ connection later necessary


Upgrade UI Note 96317 and 962955

check with Page 88 of the Upgrade Guide modify /etc/hosts


Non Unicode Upgrade to 7.3x is possible

To save time the Unicode decision can be done later


New Upgrade pre configuration options

Low resource use (long downtime, slow import, archiving off)


Overview of upgrade configuration

Accept choice


Overview of manual upgrade configuration

Manual selection will not apply maximum values


Procedure with further Add-On’s

Add additional packages as SAINT packages into EPS/in


Mandatory connection to MOPZ needed

See Notes 1539356 (7.30) 1681435 (7.31) how to handle SEM Add-On


Decision about EhP1 during Upgrade to 7.3x

Note 1022704 EHP_INCLUSION and SPSTACK_REQUEST


Further decision about Add-On’s

UPG WITH SAINT PACK or DELETE (for ST-PI possible)


Decision about included Support Packages


Problem occurs with the archive LUP.SAR

follow the mentioned Note for the component LUP

You have to give the Source out of DVD/zip from Number 51041560

there is the missing component LUP.SAR (SL controller)

See also:

Note 1562522 - SAPINST aborts during central instance installation

Note 1432609 - Inst.Systems Based on NW 7.3 - UNIX




Decision about included SPAM update


Optional: include SPDD and/or SPAU request


ASU toolbox for BW

Even that ASU toolbox is optional, it contains ALL pre and post steps


Installing BI_CONT on SAP NetWeaver 7.3

3800300version „7.35“


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,

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.01)


Decision about SPDD prior the ACT phase

For BW type system you can continue without adjustments


Unlock/Lock the shadow system is necessary

A friendly reminder/recap

D:\usr\sap\trans\bin>tp unlocksys FBM pf=TP_DOMAIN_FBM.PFL

This is tp version 372.04.65 (release 700, unicode enabled)

tp finished with return code: 0

meaning:

Everything OK

D:\usr\sap\trans\bin>tp unlock_eu FBM pf=TP_DOMAIN_FBM.PFL



meaning:

Everything OK

D:\usr\sap\trans\bin>tp locksys FBM pf=TP_DOMAIN_FBM.PFL



meaning:

Everything OK

D:\usr\sap\trans\bin>tp lock_eu FBM pf=TP_DOMAIN_FBM.PFL



meaning:

Everything OK


Reset the Upgrade with report RSUPGRES

Another friendly reminder/recap (run with user DDIC in client 000)

Note 417670 - Additional information on resetting upgrade as of Release 6.10

Note 1518145 - FM DD_DB_MISSING_OBJECTS returns incorrect no. of objects




Decision about ACT phase

Accept non-severe errors will be solved in a later phase


Old “PREPARE” is now finished

Until this phase working with the system was possible


End of phase Preprocessing

To ensure the recovering please backup the upgrade directory


End of phase Downtime backup of DB

Upgrade is already over the top


End of phase Postprocessing

Think about the start of BTCTRNS2 after the post work is finished



Think about the start of SGEN after the post work is finished



Might not occur with higher support package



Decision about SPAU create transport for further upgrades



Your technical Upgrade is finished


Technical Upgrade has ended

End of phase Finalization


Example runtime for BW 7.3x upgrade

Running at the end of the technical upgrade


Post work after 7.3x upgrade – new

Note 1165059 - ALE: Generating and reading change pointers after upgrade

Run Report RBDCPMIG_ALL_WITHOUT_MIG_FLAG in Test and Productive Mode


Migrate the BI Authorization to 7.3x

More Details:

■ http://help.sap.com/saphelp_nw73/helpdata/en/45/5ae49cee142a50e10000000a11466f/frameset.htm

http://help.sap.com/saphelp_nw73/helpdata/en/45/5ae49cee142a50e10000000a11466f/frameset.htm


Post Activities after Upgrade to BW 7.3x


Note 1720495 - Invalid deimplementation of obsolete notes by SNOTE tool

Note 1553608 - Changelog Deletion Variant doesnt work in BW 7.01-7.3x

Note 1572695 - MDX: System-wide call of old parser implementation

Note 1678212 - Deleting DTPs that do not have a transformation not possible

Note 1668991 - BW730: exception aggregation - new and old implementation

Note 1709947 - SP29:Field length wrong in source and target of TRF











Note 1610259 - Controlling 'Returncode' behavior in update rulesRSAU_RETURNCODE_NEW = X

(optional: this simplifies the migration of the update rules to a transformation).

You can switch on/off the new behavior for BAdI in 7.3x

Note 1489064 - DataSource problems after BW upgrade from 7.0 to 7.3

run Report RSAR_PSA_NEWDS_MAPPING_CHECK to check inconsistencies in

DataSources after Upgrade

Note 1521903 - Regenerate all inconsistent BAdI's

run Report ENHS_BADI_ANALYZE_GENERATE_ALL or BADI_RSANALYZE

Note 1633303 - RSMDATASTATE inconsistencies after upgrade from 7.0x to 7.3x

run function module RSDDTREX_AFTER_UPGRADE_70X_73X after the Upgrade

Note 1632284 - Program RSCOMPCONS should generate warning messages (SP06)

run Report RSCOMPCONS and repair the compounding of MultiProviders is necessary

Note 1532874 - Upgrade: Changing the HTTP reauthenticationAdd the profile Parameter icf/user_recheck =1 to the instance profile

Note 1026944 - New cache mode with no directory for BI 7.0

transaction RSRT2 mass maintenance

Note 1635588 - Problems with Start / End routine created at BW 7.0+ Release (SP06)

Note 1572882 - Problems loading 3.5 views after upgrade to 7.0/7.01 (SP07)

Note 1716329 - Planning function formula: Syntax error in generated program














SEM/FINBASIS 6.34/6.36 related

In most cases the Note 603642 solves the Problem with UCWB and UCMON startup,

however Note 948201 has to be also take into consideration.

Note 603642 - FinBasis: Manual deletion of obsolete read buffers

run report UGMD_DEL_BUFFER

Note 948201 - Dump MESSAGE_TYPE_X in

IF_UC_APPLICATION_MODEL~READ_CHAR_HRY

Note 1629760 - Syntax error in webdynpro FINBASIS/SEM-BW (UGWB_EVENT)

Check after the upgrade your MultiProvider against DeltaPair classes

goto MuliProvider additions DeltaPairs

Note 1148288 - Reports for the Migration of Package Data

run report RS_MIGRATE_PACKAGES for customer owned packages, if needed.







BI-JAVA/EP related

Please Note that a lot of corrections are done with the current Patch set

Note 1622303 - Delivery of BI Java v.13 in NW 7.30 SP7#30 and other clients

the HotFix for SP7#30 is expected for Week 27, 2012

Hinweis 1512355 - SAP NetWeaver 7.30: Schedule for BI Java Patch Delivery

Note 1535174 - Post upgrade step for AFP in NW Portal 730 and 702

if the related JAVA was upgrade from previous Version you must run the described

migration procedure from the Note.

Note 1371703 - WPC for SAP NetWeaver 7.3 - Upgrade Information






Post work after 7.3x upgrade - existing

Get everything which is needed here:

Managing your Upgrade with Innovative Toolshttp://scn.sap.com/docs/DOC-7856

The „upgrade Bible“ to 7.x from page 52http://scn.sap.com/docs/DOC-11608

Check the generic post upgrade steps from here

http://service.sap.com/installnwbw72



Thank you!

Roland Kramer Product Management EDW/HANA/IQ

@[email protected]


mailto:[email protected]



No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. 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, if any. Nothing herein should be construed as constituting an additional warrant.

© Copyright 2009 SAP AG

All Rights Reserved