1

2

3

4

5

6

Additional Notes for 7.31 upgrade:

The Main Message is: you can upgrade from any NetWeaver 7.0x Release (also 3.5

should work) including Add-On’s (like SEM, BPC, etc.) to NetWeaver 7.31

The Step goes via 7.03 and then to 7.31, while the maintenance task (7.03 => 7.31) is

not affecting the Upgrade from application perspective

Note 1326576 - SAP NetWeaver Systems Containing SAP ERP Software

Components

Note 1681435 - Upgrade NW703 to NW731 (SAP SEM 736, ERECRUIT, LSOFE)

Other related Notes

Note 1680769 - Central Note - Software Update Manager 1.0 SP05 [lmt_006]

Note 1651309 - Install Add-On SAP Management of Change 100 on NW 731

Note 1704901 - Installing or Updating CPMBPC 801 to SAP NetWeaver 7.31

Note 1536525 - GRC Access / Process Control - Upgrade add-on handling

Note 1731988 - Upgrade to NetWeaver 7.00 Enh.Pack 3 with GRCPINW V1000_731

Further Add-On implications:

http://service.sap.com/~sapidb/011000358700000890142012E

7

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)

8

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

Note 1927083 - SAP NetWeaver Systems with SEM-BW

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 (CPM8.0) 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

9

10

11

12

13

14

15

16

17

18

19

20

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

21

22

Software Logistics Toolset 1.0 - OVERVIEW AND CONCEPT

SL Toolset Basic Concept:

Software Logistics Toolset (SL Toolset) stands for a product-independent delivery

channel for software logistics tools.

It enables the delivery of up-to date software logistics tools and a unified consumption

experience with the target to reduce total cost of ownership.

For further general information, see Central Release Note for Software Logistics

Toolset 1.0 – SAP Note 1563579

23

For more information, see SAP Release Note for SL Toolset 1.0 SPS05 – 1702987

24

SAPup is listed as replaced, still it is used inside the SUM for AS ABAP systems.

JSPM not to be used any longer

SPAM can still be used, see discussion on later slide

*) For further information regarding replaced tools, see Replacements of outdated

tools via SL Toolset – SAP Note 1589311..

SUM is delivered with Software Logistics Toolset 1.0

Regular updates are delivered with the Software Logistics Toolset 1.0 updates

New features and enhancements are available in short timeframe

Some features are „available on request“ before general availability, examples

are:

near Zero Downtime (nZDM) for SAP Business Suite Systems (SAP Note

1678565)

Customer Transports included in update (SAP Note 1759080)

Deployment Optimization Option (SAP Note 1759081)

25

After you have started the SUM on the primary application server, you can open a

browser window on your local PC, and connect to the SUM process. The browser

window will then start a java web start application, using a different port.

Working locally with browser windows on your PC, you may connect to several SUM

instances running on several hosts in parallel.

The SUM includes parts that are based on the SAPup that was also part of the SAP

Enhancement Package Installer (SAPehpi).

The SAPJup part was redesigned, so it is named Java services here.

26

27

Additional Note:

■ Note 1734333 - BW Pre and Post Upgrade and Migration Tasks

Upon successful implementation of this note's manual activities and pre-requisites, four

task lists will be created: SAP_BW_BEFORE UPGRADE, SAP_BW_AFTER

UPGRADE, SAP_BW_BEFORE MIGRATION, SAP_BW_AFTER MIGRATION. Each

task listed in a task list is further described by the documentation available in the task list

manager (Transaction STC01). Please be aware that these tasks lists are intended to

alleviate some of the manual tasks required by users. They do not fully replace the

execution of ALL tasks required during the different phases of an Upgrade or Migration.

As such they should be used in conjunction with available upgrade guides.

Specifically, the pre update tasklist, SAP_BW_BEFORE UPGRADE should be executed

at the same timepoint (activity in the upgrade) as when the ASU toolbox prompts the

user to action from within Software Update Manager. See note 1000009 for more

details.

29

31

32

33

35

Location of the SAP first guidance document – BW on HANA

■ http://scn.sap.com/docs/DOC-29915

36

37

38

Check for wrong source systems assignments, TMS and XPRA errors in advance. 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: Error msg RSO851 during upgrade or Content installation import prior to the upgrade to NetWeaver 7.3x, see also Note 1633805

39

Additional Notes for optimizing the phase MAIN_NEWBAS/XPRAS_AIMMRG:

Note 1801400 - Error FINB_TR 032 during upgrade in phase XPRAS_AIMMRG

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

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

Note 1668456 - DTP: Error msg RSO851 during upgrade or Content installation

Note 1813468 - Web Dynpro: Conversion for non-printable chars (NON-UNICODE)

Note 1835882 - Error in XPRAS_AIMMRG phase during EHP installation for BADI Multiple

active implementations

Note 1701115 - Error in phase XPRA_* during support packs update: Job RDDEXECL fails

with SYNTAX_ERROR

40

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

Check for missing TLIBG entries

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.

41

42

43

Post Activities after Upgrade to BW 7.3x - BEx 3.5/7.x related

• http://scn.sap.com/docs/DOC-35785

This page is subject to frequent updates! Stay tuned

• http://wiki.sdn.sap.com/wiki/display/BI/BEX+Reporting

Post Activities after Upgrade to BW 7.3x - ABAP related 1/2

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

• Note 1720495 - Invalid deimplementation of obsolete notes by SNOTE tool

• Note 1731980 - Incorrect A versions of InfoObjects after BW 7.30 upgrade

• Note 1794441 - Incorrect sign inversion after upgrade

• Note 1553608 - Changelog Deletion Variant doesn't 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 1610259 - Controlling 'Returncode' behavior in update rules RSAU_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 1387166 - Master Data Read Class

in fact related to 7.0 upgrade, Unfortunally never checked at this state

44

Additional Information:

• Note 955990 - BI in SAP NetWeaver 7.0: Incompatibilities with SAP BW 3.x

• Note 820183 - New authorization concept in BW

• Note 923176 - Support situation authorization management BI70/NW2004s

• Note 1125108 - You are using the obsolete 3.x authorizations in BW 7.0

• 1685338 - Analysis Authorizations missing, deleted or inactive after upgrade to 730

• http://wiki.sdn.sap.com/wiki/display/BI/Inconsistancies

• Please Note, that the above step is not a complete authorization migration, as this

only activates the necessary InfoObjects. Details for the Migration see:

http://help.sap.com/saphelp_nw73/helpdata/en/4c/ebcb871e6d5972e10000000a15

822b/content.htm?frameset=/en/45/5ae49cee142a50e10000000a11466f/frameset.

htm

• Check the setting in transaction RSCUSTV23 after the upgrade

• Reports (Included in Transaction RSECADMIN):

• RSEC_GENERATE_BI_ALL

• RSEC_MIGRATION

45

Post Activities after Upgrade to BW 7.3x - ABAP related 2/2

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

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

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

• 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 reauthentication Add 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

• 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

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

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

46

Post Activities after Upgrade to BW 7.3x - JAVA related

• Note 1636057 - Upgrade to SAP NetWeaver 7.30: BI Java: Useful note

• Note 1789842 - Patch Level 0 for BI Java Installation

• 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 1446099 - Web Dynpro application not displayed in customer theme

check for the latest style sheets via the Information in the Note

• Note 1645590 - Java/Server SPs dependencies (and SupportDeskTool)

the update of BI-JAVA is not necessary, if the standard usage is chosen.

• Note 1371703 - WPC for SAP NetWeaver 7.3 - Upgrade Information

• Note 1761327 - NoSuchMethodError in XSSEncoder after BW upgrade

• Note 1787619 - Planning Modeler Runtime as of BW 7.30

• Note 1735436 - BEx Web: Supportdesk: Incorrect warning SPS7/30 on SPS5

• Note 1679761 - Report Item: Gridlines missing or no white background

47

48

Post Activities after Upgrade to BW 7.3x - miscellaneous

• Note 1646816 - BWA: Optimal setup of the indexes after upgrade to 73x

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

• Note 1626804 - Trouble with query on BWA and Multiprovider

• Note 1733169 - Performance: BICS_PROV_SET_STATE takes too long in 730

• Note 1530858 - MDX: Runtimes are long when the member rowset is determined

• Note 1151957 - Interesting facts about the OLAP Processor/Analytic Engine

• Note 1439348 - Extended security settings for sapstartsrv

• Note 927637 - Web service authentication in sapstartsrv as of Release 7.00

• Note 1600846 - JSPM/SUM calls sapcontrol without user credentials

• Note 1805116 - RSLDQREORG/RSBGRFCCLR missing in TCOLL in 731 and 702

• Note 1394392 - Contents of the table TCOLL in SAP_BASIS 730

• Note 1693998 - MPP-DBMS: Generating SID for DataStore objects

• Note 1800066 - RUN_OFFLINE_MIGRATION step takes a long time to complete

• Note 1756034 - BW 7.02, 7.30, 7.31: Dun & Bradstreet incorrectly installed

49

50

© 2014 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

BusinessObjects Explorer, StreamWork, SAP HANA, 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 Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are

registered trademarks of Crossgate AG in Germany and other

countries. Crossgate 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

warranty.

www.sap.com