nw74

Upgrade and Update GuideSAP NetWeaver 7.4 ABAP, SAP NetWeaver 7.4 SR1 ABAPPreparation and Follow-Up Activities

Target Audience System Administrators Technology Consultants

CUSTOMERDocument version: 1.3 2014-01-16

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: http://service.sap.com/instguides.

The following table provides an overview of the most important document changes.Version Date Description1.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.41.1 2013-09-13 Minor changes1.0 2013-07-15 Initial Version

2/26 CUSTOMER 2014-01-16

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

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

DataSources Web Service During the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 152.10 BW: Converting Data Classes of InfoCubes . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.11 BW: Checking Inconsistent InfoObjects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.12 BW: Migrating to the New Analysis Authorization Concept . . . . . . . . . . . . . . 172.13 BW: Preparing the System for Changed Data Type for

Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 Follow-Up Activities After the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1 Using the Application-Specific Upgrade Toolbox . . . . . . . . . . . . . . . . . . . . . . . 203.2 BW: Migrating Analysis Authorizations to TLOGO Objects . . . . . . . . . . . . . . . 203.3 BW: Optional: Improving Application Performance . . . . . . . . . . . . . . . . . . . . . 213.4 BW: Adapting Custom-Specific Coding due to Changed Data Type for

Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.5 BW: Enabling Transformations for SAP HANA Execution . . . . . . . . . . . . . . . . 213.6 BW: Creating Column Views in SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.7 BW: Converting Terminology for SAP Retail . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2014-01-16 CUSTOMER 3/26

3.8 Performing Application-Specific Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.9 Publishing ITS Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4/26 CUSTOMER 2014-01-16

1 Introduction

1.1 About this DocumentPurposeThis 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 Support Release 1 (SR1) ABAP. 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.This document supplements the document Update Guide Update of SAP Systems Using Software Update Manager which includes general planning, preparation and follow-up activities, information about using the Software Update Manager, and troubleshooting information.

IntegrationIn addition to this guide, you need the following documents: Upgrade Master Guide SAP NetWeaver 7.4 incl. SR1

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 http://service.sap.com/instguides SAP NetWeaver .

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

Updating SAP Systems Using Software Update Manager .

1.2 SAP NotesTo 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 (http://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.

1 Introduction1.1 About this Document

2014-01-16 CUSTOMER 5/26

SAP Notes for Preparing the UpdateYou 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 databaseSince these SAP Notes are updated regularly, make sure that you always use the latest version.

Other SAP NotesAs 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:SAP Note Number Description28022 Customer system: Where-used list of SAP objects46272 Implement new data class in technical settings737625 Parameter recommendations for the ICM851449 Changeability of BW objects during the upgrade888362 Helpful technical hints for installing and maintaining

MIC923176 Support situation authorization management BI70/

NW2004s1101143 Collective note: BEx Analyzer performance1139642 Hardware Requirements in Unicode Systems1494272 DataSource: Web service function group missing after

upgrade1600929 SAP BW powered by SAP HANA DB: Information1734333 BW Pre and Post Upgrade and Migration Tasks1823174 BW7.40 Changes and customer-specific programs1829728 BW Housekeeping Task List1879618 Pre-Upgrade-Activity for Upgrade/Update to 7.41911469 Check report for discontinued query features in 7.401953480 ColumnView Generation after Upgrade to BW 740 SP5

1.3 Accessing DocumentationBefore, 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

1 Introduction1.3 Accessing Documentation

6/26 CUSTOMER 2014-01-16

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.

ProcedureSAP NetWeaver Library on SAP Help PortalFollow the applicable path to the SAP NetWeaver Library on SAP Help Portal:Release PathSAP NetWeaver 7.4 http://help.sap.com/nw74 Application HelpSAP NetWeaver 7.3 including enhancement package 1

http://help.sap.com/nw731 Application Help

SAP NetWeaver 7.3 http://help.sap.com/nw73 Application HelpSAP NetWeaver Mobile 7.1 http://help.sap.com/nwmobile71 Application HelpSAP NetWeaver Mobile 7.1 including enhancement package 1

http://help.sap.com/nwmobile711 Application Help

SAP NetWeaver 7.0 http://help.sap.com/nw70 Application HelpSAP NetWeaver 7.0 including enhancement package 1


SAP NetWeaver 7.0 including enhancement package 2


Local Installation of the SAP NetWeaver LibraryBefore 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.

1 Introduction1.3 Accessing Documentation

2014-01-16 CUSTOMER 7/26

This page is left blank for documents that are printed on both sides.

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.ActionsYou 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 12] Only valid for: Business Warehouse ABAP |

BW: Executing automated Housekeeping Tasks [page 12]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Executing automated Before-Upgrade-Tasks [page 13]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |Using the Application-Specific Upgrade Toolbox [page 13]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Changeability of SAP BW Objects During the Upgrade [page 15]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Applying Corrections to Prevent the Loss of Function Groups for the DataSources Web Service During the Upgrade [page 15]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Converting Data Classes of InfoCubes [page 15]End of: Business Warehouse ABAP |

2 Preparations for the Update

2014-01-16 CUSTOMER 9/26

Only valid for: Business Warehouse ABAP |BW: Checking Inconsistent InfoObjects [page 16]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Migrating to the New Analysis Authorization Concept [page 17]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Preparing the System for Changed Data Type for Characteristi [page 17]End of: Business Warehouse ABAP |

2.1 Checking the Free Space RequirementsMake sure that at least the following free space is available in the system that you want to update:SUM Directory Approximately 20 GBDownload Directory (temporary space requirement)

Approximately 20 GB

DIR_TRANS Approximately 20 GBShadow System Approximately the space required for your source release instance, that is, the size of

the following directory: UNIX: /usr/sap/ Windows: :\usr\sap\ IBM i: /usr/sap/

2.2 Checking the Source Release of the SAP SystemNOTEThis step is not required if you apply a Support Package Stack.

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) usage type AS ABAP SAP NetWeaver 7.0 including enhancement package 1 usage type AS ABAP SAP NetWeaver 7.0 including enhancement package 2 usage type AS ABAP SAP NetWeaver 7.1 usage type AS ABAP (for banking services from SAP 7.0 and 8.0) SAP NetWeaver 7.3 SAP NetWeaver 7.3 including enhancement package 1 SAP NetWeaver 7.4End of: Application Server (AS) |

2 Preparations for the Update2.1 Checking the Free Space Requirements

10/26 CUSTOMER 2014-01-16

Only valid for: Business Warehouse ABAP | SAP NetWeaver 7.0 SPS 14 (and higher) usage type BI SAP NetWeaver 7.0 including enhancement package 1 use case Data Warehousing SAP NetWeaver 7.0 including enhancement package 2 use case Data Warehousing SAP NetWeaver 7.3 use case Data Warehousing SAP NetWeaver 7.3 including enhancement package 1 SAP NetWeaver 7.4End of: Business Warehouse ABAP |Only valid for: Source Release = SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.3 | Business Warehouse ABAP |

NOTESAP NetWeaver BW powered by SAP HANA databaseWith SAP NetWeaver BW, powered by SAP HANA database, SAP offers the SAP HANA database being the in-memory deployment option for the Data Warehousing use case.SAP HANA SPS05 as of revision 53 can be used as database platform for BW in SAP NetWeaver 7.4. We recommend to always apply the latest SAP HANA revision.For more information about implementation considerations and implementation sequence, see the End- to-End Implementation Roadmap for SAP NetWeaver BW, powered by SAP HANA on http://service.sap.com/upgradenw74 Planning and see SAP Note 1600929.If you want to update SAP NetWeaver Business Warehouse powered by SAP HANA database, the required source release is: SAP NetWeaver 7.3 use case Data Warehousing SAP NetWeaver 7.3 including enhancement package 1 use case Data Warehousing

End of: Source Release = SAP NetWeaver 7.3 EHP1;SAP NetWeaver 7.3 | Business Warehouse ABAP |Different SAP NetWeaver usage types have different minimum Support Package Stack levels. If you update an SAP NetWeaver system containing various usage types, make sure that your source system is on any acceptable Support Package Stack level for all usage types implemented in the system.

NOTEThe Software Update Manager checks whether your source release is supported for this update.

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.

ProcedureProcedure for ABAP SystemsTo determine the source release of the SAP system, log on to the system and choose System

Status .

2 Preparations for the Update2.2 Checking the Source Release of the SAP System

2014-01-16 CUSTOMER 11/26

The release appears in the Component version field.

2.3 Taking Note of Activated ICM ServicesThe Software Update Manager disables services of the Internet Communication Framework (ICF) for security reasons.

ProcedureCall transaction SICF and make a note of the activated services.Only valid for: Business Warehouse ABAP |

2.4 BW: Executing automated Housekeeping TasksWith the following SAP NetWeaver releases, task list SAP_BW_HOUSEKEEPING is available with several common tasks associated with housekeeping or upkeeping a SAP NetWeaver BW system: SAP NetWeaver 7.0 SPS 32 SAP NetWeaver 7.01 SPS 14 SAP NetWeaver 7.02 SPS 14 SAP NetWeaver 7.3 SPS 10 SAP NetWeaver 7.31 SPS 08For 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.

ProcedureRun the task list SAP_BW_HOUSEKEEPING in transaction STC01.

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

End of: Business Warehouse ABAP |

2 Preparations for the Update2.3 Taking Note of Activated ICM Services

12/26 CUSTOMER 2014-01-16

Only valid for: Business Warehouse ABAP |

2.5 BW: Executing automated Before-Upgrade-TasksWith the following SAP NetWeaver releases, the task list SAP_BW_BEFORE UPGRADE is available. It contains tasks to facilitate an update of an SAP NetWeaver BW system. SAP NetWeaver 7.0 SPS 31 SAP NetWeaver 7.01 SPS 14 SAP NetWeaver 7.02 SPS 14 SAP NetWeaver 7.3 SPS 10 SAP NetWeaver 7.31 SPS 08For 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.

ProcedureRun the task list SAP_BW_BEFORE UPGRADE in transaction STC01.End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

2.6 Using the Application-Specific Upgrade ToolboxThe 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 processingBefore 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.

2 Preparations for the Update2.5 BW: Executing automated Before-Upgrade-Tasks

2014-01-16 CUSTOMER 13/26

Prerequisites Your source release SAP system contains the add-on ST-PI 2008_1_ (where 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.

End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

2.7 BW: Checking for Discontinued Query FeaturesSome query features are no longer supported as of SAP NetWeaver 7.4. For more information, see the according release note at http://help.sap.com/nw74 Whats New Release Notes Support Package Stack 02 Business Warehouse Analytic Engine Obsolete Analytic Engine Functions (Deleted) .

ProcedureUse 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 Preparations for the Update2.7 BW: Checking for Discontinued Query Features

14/26 CUSTOMER 2014-01-16


2.8 BW: Changeability of SAP BW Objects During the UpgradeNOTEThis section is for your information only.

The upgrade program sets the SAP NetWeaver 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 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.For more information, see SAP Note 851449.End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

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

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

ProcedureTo 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.End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

2.10 BW: Converting Data Classes of InfoCubesIn 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.

2 Preparations for the Update2.8 BW: Changeability of SAP BW Objects During the Upgrade

2014-01-16 CUSTOMER 15/26

Procedure1. 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 462722. 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.

ResultAll 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.End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

2.11 BW: Checking Inconsistent InfoObjectsBefore you start the upgrade program, you check the InfoObjects and repair them if necessary.

Procedure1. 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

2 Preparations for the Update2.11 BW: Checking Inconsistent InfoObjects

16/26 CUSTOMER 2014-01-16

7. Execute the program.

ResultThe program repairs the inconsistent InfoObjects as far as possible. After the InfoObjects have been repaired, check them again, and manually correct any remaining inconsistencies.End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

2.12 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.

ProcedureFor 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.13 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.

ProcedureTo avoid problems during the upgrade or update to SAP NetWeaver 7.4, perform the steps described in SAP Note 1879618.End of: Business Warehouse ABAP |

2 Preparations for the Update2.12 BW: Migrating to the New Analysis Authorization Concept

2014-01-16 CUSTOMER 17/26

This page is left blank for documents that are printed on both sides.

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 operationDuring 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 operationYou can also perform these actions when the system is back to production operation.

ActionsYou have to perform the following actions before you resume production operation of your system: Only valid for: Business Warehouse ABAP |

Using the Application-Specific Upgrade Toolbox [page 20]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Migrating Analysis Authorizations to TLOGO Objects [page 20]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Optional: Improving Application Performance [page 21]End of: Business Warehouse ABAP |

Only valid for: Business Warehouse ABAP |BW: Adapting Custom-Specific Coding due to Changed Data Type for [page 21]End of: Business Warehouse ABAP |

3 Follow-Up Activities After the Update

2014-01-16 CUSTOMER 19/26

Only valid for: Source Release = SAP NetWeaver 7.0;SAP NetWeaver 7.0 EHP1;SAP NetWeaver 7.0 EHP2 |Performing Application-Specific Activities [page 23]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: Only valid for: Business Warehouse ABAP |

BW: Converting Terminology for SAP Retail [page 22]End of: Business Warehouse ABAP |

Publishing ITS Objects [page 23]Only valid for: Business Warehouse ABAP |

3.1 Using the Application-Specific Upgrade ToolboxThe application-specific upgrade toolbox (ASU toolbox) allows you to manage the preparation and follow-up activities you must perform for the technical upgrade.

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

More InformationFor more information, see Using the Application-Specific Upgrade Toolbox [page 13] in section Preparations for the Update.End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

3.2 BW: Migrating Analysis Authorizations to TLOGO ObjectsFrom 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).

ProcedureFor 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 WarehousingData Warehouse Management Authorizations Analysis Authorizations Migration of Analysis Authorizations .

End of: Business Warehouse ABAP |

3 Follow-Up Activities After the Update3.1 Using the Application-Specific Upgrade Toolbox

20/26 CUSTOMER 2014-01-16


3.3 BW: Optional: Improving Application PerformanceTo 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.

ProcedureFor more performance-relevant information regarding the reporting of BW objects, see SAP Note 1101143.End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

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.

ProcedureIf you have your own coding, switching to data type SSTRING could result in syntax and runtime errors.For more information see SAP Note 1823174.End of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

3.5 BW: Enabling Transformations for SAP HANA ExecutionAs of SAP NetWeaver 7.4, when using SAP HANA database as underlying database for SAP NetWeaver BW, transformations can be enabled for being executed in SAP HANA under certain conditions.For more information, see the release notes under http://help.sap.com/nw74 Whats New Release Notes Support Package Stack 05 Business Warehouse Data Warehousing: Modeling Transformation (Changed) .

3 Follow-Up Activities After the Update3.3 BW: Optional: Improving Application Performance

2014-01-16 CUSTOMER 21/26

Procedure1. 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 HANAWhen using SAP HANA database as underlying database for SAP NetWeaver 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.For more information, see SAP Note 1953480.

ProcedureExecute report RS_BW_POST_MIGRATION with the following settings: 12 - Create calc views cubes/infoobjects 15 - Adjust Snapshots and AnalyticalIndexesEnd of: Business Warehouse ABAP |Only valid for: Business Warehouse ABAP |

3.7 BW: Converting Terminology for SAP RetailPrerequisitesYou use SAP NetWeaver BW as part of the SAP Retail solution.

ProcedureIf 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 http://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.End of: Business Warehouse ABAP |

3 Follow-Up Activities After the Update3.6 BW: Creating Column Views in SAP HANA

22/26 CUSTOMER 2014-01-16

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

3.8 Performing Application-Specific ActivitiesProcedureSome 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 http://service.sap.com/releasenotes SAP Help Portal at http://help.sap.com/ (SAP NetWeaver version) Whats New Release

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

3.9 Publishing ITS ObjectsAfter 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.

ProcedureFollow the steps described in SAP Note 790727.

3 Follow-Up Activities After the Update3.8 Performing Application-Specific Activities

2014-01-16 CUSTOMER 23/26

Typographic Conventions

Example Description Angle brackets indicate that you replace these words or characters with appropriate

entries to make entries in the system, for example, Enter your .ExampleExample

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

Example Emphasized words or expressionsExample Words or characters that you enter in the system exactly as they appear in the

documentationhttp://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 Web123456 Hyperlink to an SAP Note, for example, SAP Note 123456Example 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 toolsEXAMPLE 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

24/26 CUSTOMER 2014-01-16

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

Copyright 2013 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.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.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. National product specifications may vary.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.SAP 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.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

DisclaimerPlease see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2014-01-16 CUSTOMER 25/26

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

Copyright 2013 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 NetWeaver 7.4 ABAP, SAP NetWeaver 7.4 SR1 ABAPTable of Contents1 Introduction1.1 About this Document1.2 SAP Notes1.3 Accessing Documentation

2 Preparations for the Update2.1 Checking the Free Space Requirements2.2 Checking the Source Release of the SAP System2.3 Taking Note of Activated ICM Services2.4 BW: Executing automated Housekeeping Tasks2.5 BW: Executing automated Before-Upgrade-Tasks2.6 Using the Application-Specific Upgrade Toolbox2.7 BW: Checking for Discontinued Query Features2.8 BW: Changeability of SAP BW Objects During the Upgrade2.9 BW: Applying Corrections to Prevent the Loss of Function Groups for the DataSources Web Service During the Upgrade2.10 BW: Converting Data Classes of InfoCubes2.11 BW: Checking Inconsistent InfoObjects2.12 BW: Migrating to the New Analysis Authorization Concept2.13 BW: Preparing the System for Changed Data Type for Characteristics

3 Follow-Up Activities After the Update3.1 Using the Application-Specific Upgrade Toolbox3.2 BW: Migrating Analysis Authorizations to TLOGO Objects3.3 BW: Optional: Improving Application Performance3.4 BW: Adapting Custom-Specific Coding due to Changed Data Type for Characteristics3.5 BW: Enabling Transformations for SAP HANA Execution3.6 BW: Creating Column Views in SAP HANA3.7 BW: Converting Terminology for SAP Retail3.8 Performing Application-Specific Activities3.9 Publishing ITS Objects

Copyright and trademarks

nw74

Documents

bwrelated sections bw

sap retail222014

sap notes51

update guidesap netweaver

sap hana execution

context of release upgrade

support package stack

documentpurposethis