upgrade and update guide customer preparation and...

Upgrade and Update GuideDocument version: 1.5 – 2014-10-06

SAP NetWeaver 7.4 ABAPPreparation and Follow-Up Activities

CUSTOMER

Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: service.sap.com/instguides.

The following table provides an overview of the most important document changes.

Table 1

Version Date Description

1.5 2014-10-06 Information regarding SAP BW updated

1.4 2014-07-15 Updated version; Changes and enhancements related to Support Release 2 of SAP NetWeaver 7.4, and related to terminology changes

1.3 2014-01-16 ABAP guide only: Important corrections and enhancements in the BW-related sections BW: Executing automated Housekeeping Tasks and BW: Executing automated Before-Upgrade-Tasks.

1.2 2013-12-20 Changes and enhancements related to Support Release 1 of SAP NetWeaver 7.4

1.1 2013-09-13 Minor changes

1.0 2013-07-15 Initial Version

2

CUSTOMER© Copyright 2014 SAP AG.All rights reserved.

SAP NetWeaver 7.4 ABAPDocument History

http://service.sap.com/instguides

Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Naming Conventions and Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4 Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Preparations for the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Checking the Free Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Checking the Source Release of the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3 BW: Executing automated Housekeeping Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 BW: Executing automated Before-Upgrade-Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.5 Using the Application-Specific Upgrade Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.6 BW: Checking for Discontinued Query Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.7 BW: Changeability of SAP BW Objects During the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.8 BW: Applying Corrections to Prevent the Loss of Function Groups for the DataSources Web

Service During the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.9 BW: Converting Data Classes of InfoCubes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.10 BW: Checking Inconsistent InfoObjects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.11 BW: Migrating to the New Analysis Authorization Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.12 BW: Preparing the System for Changed Data Type for Characteristics . . . . . . . . . . . . . . . . . . . . . . . 17

3 Follow-Up Activities After the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1 Using the Application-Specific Upgrade Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2 BW: Migrating Analysis Authorizations to TLOGO Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3 BW: Optional: Improving Application Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.4 BW: Adapting Custom-Specific Coding due to Changed Data Type for Characteristics . . . . . . . . . . . . 203.5 BW: Enabling Transformations for SAP HANA Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.6 BW: Creating Column Views in SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.7 BW: Converting Terminology for SAP Retail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.8 Performing Application-Specific Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.9 Publishing ITS Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

SAP NetWeaver 7.4 ABAPContent

CUSTOMER© Copyright 2014 SAP AG.

All rights reserved. 3

4

CUSTOMER© Copyright 2014 SAP AG.All rights reserved. SAP NetWeaver 7.4 ABAP

1 Introduction

1.1 About this Document

Purpose

This document describes the preparation and follow-up activities that you need to perform when you update your SAP system to SAP NetWeaver 7.4 ABAP or SAP NetWeaver 7.4 ABAP including Support Release 1 (SR1) or 2 (SR2). It also describes the preparation and follow-up activities that you need to perform when you apply Support Package Stacks on top of SAP NetWeaver 7.4 ABAP (or subsequent Support Release).

For clarity and readability, the generic term “update” is used in this document in the context of release upgrade, enhancement package installation and Support Package Stack update.

As of November 2014, the generic term "product instance" replaces the terms “usage type” and “technical usage” for SAP systems based on releases 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731.

This document supplements the document Update Guide – Update of SAP Systems Using Software Update Manager <version> which includes general planning, preparation and follow-up activities, information about using the Software Update Manager, and troubleshooting information.

Integration

In addition to this guide, you need the following documents:

● Upgrade Master Guide – SAP NetWeaver 7.4

The Upgrade Master Guide guides you through the complete update process and refers you to the required documentation for each step.

To find the latest version of this document, see SAP Service Marketplace at service.sap.com/instguidesSAP NetWeaver SAP NetWeaver <Release> Upgrade .

● Update Guide – Update of SAP Systems Using Software Update Manager <version>

To find the latest version of this document, see SAP Service Marketplace at service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation System Maintenance Updating SAP Systems Using Software Update Manager <version> .

1.2 Naming Conventions and Terminology

NoteSee also the SUM guide for more naming conventions.

SAP NetWeaver 7.4 ABAPIntroduction



http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1877731&_NLANG=en&_NVERS=0

http://service.sap.com/instguides

http://service.sap.com/sltoolset

Update

For clarity and readability, the generic term “update” is used in this document as a collective term for all the software logistics processes that you can perform using the Software Update Manager (such as performing release upgrades, installing enhancement packages, or updating a system with Support Package Stacks).

Usage Type, Technical Usage, and Product Instance

The term “product instance” replaces the terms “usage type” and “technical usage” for SAP systems based on SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731. Note that there is no terminology change for older releases and all mentioned terms can be used as synonyms.

1.3 SAP Notes

To prepare and perform the update of your SAP system, you require some additional information that is not included in this document. This information is in a range of SAP Notes in SAP Support Portal (service.sap.com/notes), some of which you have to read before you start with the preparations. When you actually perform the update, you may need information from some additional SAP Notes. These SAP Notes are named at the appropriate places in this document.

SAP Notes for Preparing the Update

You have to request the following SAP Notes from SAP Support Portal before you start the update process:

● Central Software Update Manager Note

● Application-specific update Note: 1751237

● SAP Note for your database

Since these SAP Notes are updated regularly, make sure that you always use the latest version.

Other SAP Notes

As well as the SAP Notes you need for the preparation, this document also refers you to other SAP Notes that contain additional information. The following list contains these SAP Notes:

Table 2

SAP Note Number Description

28022 Customer system: Where-used list of SAP objects

46272 Implement new data class in technical settings

737625 Parameter recommendations for the ICM

851449 Changeability of BW objects during the upgrade

888362 Helpful technical hints for installing and maintaining MIC

923176 Support situation authorization management BI70/NW2004s

1101143 Collective note: BEx Analyzer performance

1139642 Hardware Requirements in Unicode Systems

6




http://service.sap.com/notes

http://service.sap.com/notes










SAP Note Number Description

1494272 DataSource: Web service function group missing after upgrade

1600929 SAP BW powered by SAP HANA DB: Information

1734333 BW Pre and Post Upgrade and Migration Tasks

1823174 BW7.40 Changes and customer-specific programs

1829728 BW Housekeeping Task List

1879618 Pre-Upgrade-Activity for Upgrade/Update to 7.4

1911469 Check report for discontinued query features in 7.40

1953480 ColumnView Generation after Upgrade to BW 740 SP5

1.4 Accessing Documentation

Before, during and after the update, you require the SAP online documentation.

There are different ways to access the online documentation:

● SAP NetWeaver Library on SAP Help Portal

You can access the documentation for all maintained product releases on SAP Help Portal.

● Local installation of the SAP NetWeaver Library

Before the update, make sure that you can read the documentation DVD offline. After the update, you need to install the documentation for the target release.

Procedure

SAP NetWeaver Library on SAP Help Portal

Follow the applicable path to the SAP NetWeaver Library on SAP Help Portal:

Table 3

Release Path

SAP NetWeaver 7.4 help.sap.com/nw74 Application Help

SAP NetWeaver 7.3 including enhancement package 1 help.sap.com/nw731 Application Help


SAP NetWeaver Mobile 7.1 help.sap.com/nwmobile71 Application Help

SAP NetWeaver Mobile 7.1 including enhancement package 1 help.sap.com/nwmobile711 Application Help














http://help.sap.com/nw74



http://help.sap.com/nwmobile71

http://help.sap.com/nwmobile711



Release Path


Local Installation of the SAP NetWeaver Library

Before and during the update, you have to read the online documentation for the target release on the DVD.

RecommendationIf there is a Support Package available for the documentation, use the documentation version on SAP Help Portal.

8




2 Preparations for the Update

This part of the document contains information about the preparations that you need to make before you update your system.

You can prepare for the update while the system is in production operation. Careful preparation of the update is the best guarantee that it runs without errors.

The Software Update Manager supports you here by making a range of checks automatically in the preparation roadmap steps (Initialization, Extraction, Configuration, and Checks). To make sure that all requirements are met, run the preparation roadmap steps of Software Update Manager as soon as possible. You can reset and repeat the preparation roadmap steps as often as you need by choosing Back before you start the actual procedure in roadmap step Preprocessing. The successful execution of the preparation roadmap steps is a prerequisite for starting the roadmap step Preprocessing.

Actions

You perform the following actions before you start the Software Update Manager:

● Checking the Free Space Requirements [page 10]

● Checking the Source Release of the SAP System [page 10]

● Taking Note of Activated ICM Services [page 0 ]

● Only valid for: Business Warehouse ABAP |

BW: Executing automated Housekeeping Tasks [page 12]

End of: Business Warehouse ABAP |


BW: Executing automated Before-Upgrade-Tasks [page 12]



Using the Application-Specific Upgrade Toolbox [page 13]



BW: Changeability of SAP BW Objects During the Upgrade [page 14]



BW: Applying Corrections to Prevent the Loss of Function Groups for the DataSources Web Service During the Upgrade [page 15]



BW: Converting Data Classes of InfoCubes [page 15]



BW: Checking Inconsistent InfoObjects [page 16]


SAP NetWeaver 7.4 ABAPPreparations for the Update




BW: Migrating to the New Analysis Authorization Concept [page 17]



BW: Preparing the System for Changed Data Type for Characteristi [page 17]


2.1 Checking the Free Space Requirements

Make sure that at least the following free space is available in the system that you want to update:

Table 4

SUM Directory Approximately 20 GB

Download Directory (temporary space requirement) Approximately 20 GB

DIR_TRANS Approximately 20 GB

Shadow System Approximately the space required for your source release instance, that is, the size of the following directory:

● UNIX: /usr/sap/<sapsid>● Windows: <Drive>:\usr\sap\<sapsid>● IBM i: /usr/sap/<SID>

2.2 Checking the Source Release of the SAP System

Note● This step is not required if you apply a Support Package Stack.

● See also the PDF document, which is attached to the central SUM note, for a graphical representation of the supported update and upgrade paths.

● The Software Update Manager will check whether your source release is supported for this update.

Before the update, your SAP system should be running on one of the source releases that have been released for this update and apply to all databases:

Only valid for: Application Server (AS) |

● SAP NetWeaver 7.0 SPS 14 (and higher) – product instance AS ABAP

● SAP NetWeaver 7.0 including enhancement package 1 – product instance AS ABAP

● SAP NetWeaver 7.0 including enhancement package 2 – product instance AS ABAP

● SAP NetWeaver 7.1 – product instance AS ABAP (for banking services from SAP 7.0 and 8.0)

● SAP NetWeaver 7.3

● SAP NetWeaver 7.3 including enhancement package 1

10




End of: Application Server (AS) |

Only valid for: Business Warehouse ABAP |

● SAP NetWeaver 7.0 SPS 19 (and higher) – product instance BI

● SAP NetWeaver 7.0 including enhancement package 1 – use case Data Warehousing


● SAP NetWeaver 7.3 – use case Data Warehousing

● SAP NetWeaver 7.3 including enhancement package 1



Only valid for: Source Release = SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.3 | Business Warehouse ABAP |

NoteSAP BW powered by SAP HANA database

With SAP BW, powered by SAP HANA database, SAP offers the SAP HANA database being the in-memory deployment option for the Data Warehousing use case.

In combination with SAP BW 7.40 SPS 08 (or higher) it is necessary to use SAP HANA SP 08 or higher. Revision 82 is the minimum revision for SAP HANA SP 08. We recommend to always use the latest available SAP HANA SP 08 revision

For more information about implementation considerations and implementation sequence, see the End- to-End Implementation Roadmap for SAP BW, powered by SAP HANA on service.sap.com/upgradenw74Planning and see SAP Note 1600929.

If you want to update SAP Business Warehouse powered by SAP HANA database, the required source release is:

● SAP NetWeaver 7.3 – use case Data Warehousing


End of: Source Release = SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.3 | Business Warehouse ABAP |

Different SAP NetWeaver product instances have different minimum Support Package Stack levels. If you update an SAP NetWeaver system containing various product instances, make sure that your source system is on any acceptable Support Package Stack level for all product instances implemented in the system.

CautionIf you have to apply Support Packages to your source release shortly before the update, check whether the equivalent Support Package Stack for the target release is already available. Otherwise, this may delay your update schedule.

Procedure

Procedure for ABAP Systems

To determine the source release of the SAP system, log on to the system and choose System Status .

The release appears in the Component version field.




http://service.sap.com/upgradenw74



2.3 BW: Executing automated Housekeeping Tasks

With the following SAP NetWeaver releases, task list SAP_BW_HOUSEKEEPING is available with several common tasks associated with housekeeping or upkeeping a SAP BW system:

● SAP NetWeaver 7.0 SPS 32





For more information, see SAP note 1829728. This note also contains the necessary coding for the SAP_BW_HOUSEKEEPING task list creation.

If you are on a Support Package lower than the ones mentioned above, the note provides you with information in which Support Package stacks you could apply it the SAP_BW_HOUSEKEEPING task list creation.

NoteWe strongly recommend the automated approach provided by the task list. If you don't use the task list, you can run the ASU toolbox (see in this guide section Using the Application-Specific Upgrade Toolbox [page 13]) in conjunction with the usual manual tasks.

Procedure

Run the task list SAP_BW_HOUSEKEEPING in transaction STC01.

NoteWe recommend to run the task list days or weeks before the upgrade.



2.4 BW: Executing automated Before-Upgrade-Tasks

With the following SAP NetWeaver releases, the task list SAP_BW_BEFORE UPGRADE is available. It contains tasks to facilitate an update of an SAP BW system.






12




For more information, see SAP note 1734333. This note also contains the necessary coding required for the SAP_BW_BEFORE UPGRADE task list creation.

If you are on a Support Pack below the ones mentioned above, the note provides you with information in which Support Package stacks you could apply it for the task list creation.

NoteWe strongly recommend the automated approach provided by the task list. If you don't use the task list, you can run the ASU toolbox (see in this guide section Using the Application-Specific Upgrade Toolbox [page 13]) in conjunction with the usual manual tasks.

Procedure

Run the task list SAP_BW_BEFORE UPGRADE in transaction STC01.



2.5 Using the Application-Specific Upgrade Toolbox

The application-specific upgrade toolbox (ASU toolbox) allows you to manage the preparation and follow-up activities you need to perform for the technical upgrade.

It consists of two parts:

● Application-specific content (ASU content definition) in the form of an XML file

The XML file contains a list of manual and automatic steps. It is included in the upgrade export and updated with the correction package for the upgrade program.

● Interface that interprets the XML file and presents the steps to the user for processing

Before the upgrade, this interface displays the preparation activities. After the upgrade, it displays the follow-up activities.

Using the interface, you can enhance the XML file with your own activities and comments.

Prerequisites

● Your source release SAP system contains the add-on ST-PI 2008_1_ <x> (where <x> stands for one of the following: 46C, 620, 640, 700, 710).

● You require authorization for the following transactions:

○ /ASU/START

○ /ASU/UPGRADE

○ /ASU/SSM

● You have the authorizations that you require for the individual activities in the ASU toolbox step list.





RecommendationOperate the ASU toolbox with a user with SAP_ALL authorizations.

Procedure

● Execute the ASU Toolbox before and again after the upgrade by calling transaction /ASU/START. Select the appropriate ASU content definition.

● During the upgrade in roadmap step Checks, the upgrade program prompts you to call transaction /ASU/UPGRADE.

For more information, see SAP Note 1000009.

NoteYou can perform the follow-up activities listed in the ASU toolbox in parallel to adjusting repository objects using transaction SPAU.



2.6 BW: Checking for Discontinued Query Features

Some query features are no longer supported as of SAP NetWeaver 7.4. For more information, see the according release note at help.sap.com/nw74 What’s New – Release Notes Support Package Stack 02 Business Warehouse Analytic Engine Obsolete Analytic Engine Functions (Deleted) .

Procedure

Use report SAP_QUERY_CHECKER_740 to check the queries in your system that contain features, which are not supported any longer in SAP NetWeaver 7.4.

For more information, see SAP Note 1911469.End of: Business Warehouse ABAP |


2.7 BW: Changeability of SAP BW Objects During the Upgrade

NoteThis section is for your information only.

The upgrade program sets the SAP BW system to “not changeable” in the LOCKEU_PRE phase (for preconfiguration mode low resource use) or at the latest in REPACHK2 phase (for preconfiguration mode standard

14






resource use or high resource use). Depending on the Support Package level of your source release, you are able to change some objects and info packages until the beginning of downtime.




2.8 BW: Applying Corrections to Prevent the Loss of Function Groups for the DataSources Web Service During the Upgrade

During the upgrade of an SAP BW system, you may experience a loss of the generated function groups for the DataSources web service.

Procedure

To prevent losing function groups for the DataSources web service during the upgrade, proceed as described in SAP Note 1494272. After the correction is available in your system, nevertheless run report RSDS_DATASOURCE_ACTIVATE_ALL once to generate the function groups properly.



2.9 BW: Converting Data Classes of InfoCubes

In the customer system, DDART data classes were set up that do not correspond to the naming conventions described in SAP Note 46272. These data classes were assigned to InfoCubes in the maintenance transaction RSDCUBE. These data classes are lost during the upgrade since only data classes that use the naming conventions are saved. This means that the tables that are generated for an InfoCube cannot be activated correctly.

You can use the RSDG_DATCLS_ASSIGN report to change the assignment to a correct, valid data class.

Procedure

1. Check in your system if DDART data classes exist that do not correspond to the naming conventions:

1. Call transaction SE16 and check the table RSDCUBE.

2. Select OBJVERS equal ‘M’, ‘A’; and check the entries for the fields DIMEDATCLS, CUBEDATCLS, ADIMDATCLS, and AGGRDATCLS.

All InfoCubes are listed with their assigned data classes.

3. Compare the data classes with the naming conventions for data classes described in SAP Note 46272.

2. If you find incorrect data classes, correct them as follows:








1. Set up a new data class as described in SAP Note 46272

2. Execute the RSDG_DATCLS_ASSIGN report.

With this report, you can switch the data class for multiple InfoCubes in one run. For example, you can assign the valid data class “ZABC” to all InfoCubes that have assigned the invalid data class “ABC” in one run.

Result

All processed InfoCubes that have previously been assigned to the invalid data class are now assigned to the new data class, including their metadata and the generated database tables. Problems connected with data classes no longer occur during the upgrade.



2.10 BW: Checking Inconsistent InfoObjects

Before you start the upgrade program, you check the InfoObjects and repair them if necessary.

Procedure

1. Log on to the SAP system.

2. Call transaction RSD1.

3. Choose Extras Repair InfoObjects (F8) .

4. Choose Execute Repair .

5. Choose Expert Mode Select Objects .

6. On the following screen, in addition to the default checkbox selection, activate the following checkboxes:

○ Check Generated Objects

○ Activate Inconsistent InfoObjects

○ Deletion of DDIC/DB Objects

○ Display Log

7. Execute the program.

Result

The program repairs the inconsistent InfoObjects as far as possible. After the InfoObjects have been repaired, check them again, and manually correct any remaining inconsistencies.


16





2.11 BW: Migrating to the New Analysis Authorization Concept

As of SAP NetWeaver Business Warehouse 7.0, a new analysis authorization concept has been introduced. The previous reporting authorization concept is no longer supported and can no longer be used. Therefore, you need to migrate from the old to the new authorization concept.

Procedure

For more information about migrating from the old to the new concept, see SAP Note 923176.

In addition, see the analysis authorizations documentation at: help.sap.com/nw74 Application Help Function-Oriented View Business Warehouse Data Warehousing Data Warehouse ManagementAuthorizations .



2.12 BW: Preparing the System for Changed Data Type for Characteristics

Previously, the maximum length of characteristic values was 60 characters. With SAP NetWeaver 7.4 and higher releases, the maximum length is now 250 characters, which corresponds to 500 bytes. Domain RSCHAVL has therefore been changed from CHAR60 to SSTRING 1333.

Data elements that use the domain RSCHAVL are used in generated tables. This means that problems can occur when upgrading or updating to SAP NetWeaver 7.4. For example, if the associated field is used in the table key, the maximum key length can be exceeded.

The program attached to SAP Note 1879618 replaces the data elements, which use the domain RSCHAVL, with data elements of type CHAR60. These data elements do not cause problems during the upgrade or update.

Procedure

To avoid problems during the upgrade or update to SAP NetWeaver 7.4, perform the steps described in SAP Note 1879618.








3 Follow-Up Activities After the Update

This part of the document contains information about the follow-up activities that you need to perform after you have updated your SAP system.

When you perform follow-up activities, note the following information:

● Before you start the follow-up activities, you need to have run the update up to and including the MODPROFP_UPG phase.

The Software Update Manager stops in the MODPROFP_UPG phase and prompts you to start several follow-up activities. It then executes the last phases and completes the update. At the same time, you can already perform the specified follow-up activities.

The follow-up activities are divided into three blocks:

● Actions needed before resuming production operation

These actions ensure that all the processes that are relevant to system operation are available again. You can start these actions while the Software Update Manager is finishing the update.

● Actions during limited production operation

During this time, your SAP system is already consistent and all the processes that are relevant to system operation are available. However, this system state does not yet contain measures for optimizing performance, or actions for resuming standard operation (resuming background processing, or adjusting authorizations, for example). Check the actions that are listed in this block and if necessary, perform them before you restart production operation.

● Actions during production operation

You can also perform these actions when the system is back to production operation.

Actions

You have to perform the following actions before you resume production operation of your system:


Using the Application-Specific Upgrade Toolbox [page 19]



BW: Migrating Analysis Authorizations to TLOGO Objects [page 19]



BW: Optional: Improving Application Performance [page 20]



BW: Adapting Custom-Specific Coding due to Changed Data Type for [page 20]


● Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

Performing Application-Specific Activities [page 22]

End of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

You can perform the following actions during production operation of your system:

18


SAP NetWeaver 7.4 ABAPFollow-Up Activities After the Update


BW: Converting Terminology for SAP Retail [page 21]


● Publishing ITS Objects [page 22]


3.1 Using the Application-Specific Upgrade Toolbox

The application-specific upgrade toolbox (ASU toolbox) allows you to manage the preparation and follow-up activities you must perform for the technical upgrade.

Procedure

Execute the ASU Toolbox after the upgrade by calling transaction /ASU/START. Select the appropriate ASU content definition.

More Information

For more information, see Using the Application-Specific Upgrade Toolbox [page 13] in section Preparations for the Update.



3.2 BW: Migrating Analysis Authorizations to TLOGO Objects

From SAP NetWeaver 7.3 on, an analysis authorization is a TLOGO object (analytics security object) and can be transported to other systems. If you have upgraded from SAP NetWeaver releases lower than 7.3 to SAP NetWeaver 7.4 and already implemented the new analysis authorizations concept in your source release, you have to migrate these analysis authorizations to the transportable analysis authorizations (TLOGO).

Procedure

For more information about the migration of analysis authorizations, see the Help Portal at: help.sap.com/nw74 Application Help Function-Oriented View Business Warehouse Data Warehousing Data Warehouse Management Authorizations Analysis Authorizations Migration of Analysis Authorizations .






3.3 BW: Optional: Improving Application Performance

To improve the performance of your application after the upgrade, we recommend that you perform several follow-up activities described in the SAP Notes mentioned below.

Procedure

For more performance-relevant information regarding the reporting of BW objects, see SAP Note 1101143.



3.4 BW: Adapting Custom-Specific Coding due to Changed Data Type for Characteristics

Previously, the maximum length of characteristic values was 60 characters. With SAP NetWeaver 7.4 and higher releases, the maximum length is now 250 characters, which corresponds to 500 bytes. Domain RSCHAVL has therefore been changed from CHAR60 to SSTRING.

In the case of characteristics with texts, the long text can now be designated as Extra Long and can then be up to 1333 characters in length. Texts are therefore not transferred in structure RSTXTSML any more. They are now transferred in structure RSTXTSMXL instead.

The fields have the same name, although field TXTLG in structure RSTXTSMXL is of type SSTRING.

Procedure

If you have your own coding, switching to data type SSTRING could result in syntax and runtime errors.

For more information see SAP Note 1823174.



3.5 BW: Enabling Transformations for SAP HANA Execution

As of SAP NetWeaver 7.4, when using SAP HANA database as underlying database for SAP BW, transformations can be enabled for being executed in SAP HANA under certain conditions.

For more information, see the release notes under help.sap.com/nw74 What’s New – Release NotesSupport Package Stack 05 Business Warehouse Data Warehousing: Modeling Transformation (Changed) .

20






Procedure

1. Activate the transformations. During activation, the system checks whether the transformation can be performed in SAP HANA. Note that besides the activation no further activities are necessary to enable transformations for SAP HANA execution.

2. For transformations that can be performed in SAP HANA, select processing type "SAP HANA Execution" in the data transfer process.



3.6 BW: Creating Column Views in SAP HANA

When using SAP HANA database as underlying database for SAP BW, after upgrading your system to SAP NetWeaver 7.4 and applying SPS 05, you have to create Column Views for InfoObjects and InfoProvider once again.


Procedure

Execute report RS_BW_POST_MIGRATION with the following settings:

● 12 - Create calc views cubes/infoobjects

● 15 - Adjust Snapshots and AnalyticalIndexes



3.7 BW: Converting Terminology for SAP Retail

Prerequisites

You use SAP BW as part of the SAP Retail solution.

Procedure

If you want to convert the user interface of your BW system to retail-specific terms, proceed as described in the documentation about retail content. You can find this documentation on SAP Help Portal at help.sap.com/nw74 Application Help Function-Oriented View BI Content & BI Content Extensions BI Content Industry Solutions Trading Industries Retail Terminology . Convert the short texts only after you have imported Support Packages, otherwise new texts overwrite texts that have already been converted.








Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.8 Performing Application-Specific Activities

Procedure

Some applications require you to perform application-specific follow-up activities, without which the applications cannot run. These application-specific activities are described in the Release Notes for the particular application.

The Release Notes are available on:

● SAP Service Marketplace at service.sap.com/releasenotes

● SAP Help Portal at help.sap.com/NW74 What’s New – Release NotesEnd of: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |

3.9 Publishing ITS Objects

After the update of your SAP NetWeaver system, ITS services might not be executable in the integrated ITS or the services that start might not behave as expected. You have to publish all ITS services available in the system to the integrated ITS.

Procedure

Follow the steps described in SAP Note 790727.

22



http://service.sap.com/releasenotes

http://help.sap.com/NW74


Typographic Conventions

Table 5

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

SAP NetWeaver 7.4 ABAPTypographic Conventions



http://www.sap.com



www.sap.com

© Copyright 2014 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. The information contained herein may be changed without prior notice.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE's or its affiliated companies' strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://www.sap.com

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

upgrade and update guide customer preparation and...

Documents