How To Handle SAP Notes During and After Upgrading a Support Package

Size: px
Start display at page:

Download "How To Handle SAP Notes During and After Upgrading a Support Package"

Transcription

1 How To Guide ABAP Task Manager for Lifecycle Management Automation Document Version: How To Handle SAP Notes During and After Upgrading a Support Package Using transaction SPDD and SPAU

2 Typographic Conventions Type Style Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. EXAMPLE <> Emphasized words or expressions. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAM PLE Keys on the keyboard, for example, F2 or EN TER SAP AG or an SAP affiliate company. All rights reserved. Typographic Conventions

3 Document History Version Date Change Initial version Document History 2013 SAP AG or an SAP affiliate company. All rights reserved. 3

4 Table of Contents 1 Introduction Procedure SAP AG or an SAP affiliate company. All rights reserved. Table of Contents

5 1 Introduction This document describes how to handle SAP Notes for the ABAP task manager for lifecycle management automation (task manager) and the task content during and after upgrading a support package. Manual steps of these SAP Notes, such as creating elements, texts, and documentation, are automated and created through executing a report, which is attached to the SAP Note. In this guide we describe the recommended procedure to solve modification adjustments with transaction SPDD and SPAU. SAP Notes for Task Manager and Task Content (10/13) SAP Note Title Task Manager for Technical Configuration (1. Improvements) Task Manager for Technical Configuration (2. Improvements) Task Manager for Technical Configuration (3. Improvements) Task Manager for Technical Configuration (4. Improvements) Task Manager for Technical Configuration (5. Improvements) Task Manager for Technical Configuration (6. Improvements) System Copy: Task Content (1. Improvements) System Copy: Task Content (2. Improvements) System Copy: Task Content (3. Improvements) System Copy: Task Content (4. Improvements) System Copy: Task Content (5. Improvements) System Copy: BDLS Task (1. Improvements) System Copy: BDLS Task (2. Improvements) System Copy: BDLS Task (3. Improvements) System Copy: BDLS Task (4. Improvements) Note For SAP NetWeaver Business Warehouse (BW) task content, additional SAP Notes are applicable. For the most actual list, see SAP Note Introduction 2013 SAP AG or an SAP affiliate company. All rights reserved. 5

6 2 Procedure 1. Start upgrading the support package. 2. Transaction SPDD allows you to adjust modifications to ABAP dictionary objects during an upgrade. During upgrade you are asked to solve the following dictionary modification adjustments: 1. Enter the following multiple selection values for Package: o STC* o S_LMCFG* o BW_CORE_TOOLS (for BW tasks) o RSAPI_CTC (for BW source system tasks) 2. Select root element Without Modification Assistant. 3. For all structures and tables, choose Keep Modifications. 4. For all other objects, choose Reset to Original. 3. Transaction SPAU allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade. When the upgrade is finished, you have to deal with the following remaining modification adjustments: 1. Enter the following multiple selection values for Package: o STC* o S_LMCFG* o BW_CORE_TOOLS (for BW tasks) o RSAPI_CTC (for BW source system tasks) 2. Select root element Without Modification Assistant and mark all objects. 3. Choose Reset to Original. Recommendation Due to the amount of objects we recommend to set everything back to original than accept every change of each single object. This means SAP Notes need to be re-implemented with doing manual activities (execute automation report) again. 4. Open the tree Notes Corrections and click for each SAP Note beginning on the top the traffic light symbol. o If the SAP Note is obsolete, it disappears either immediately, after getting the latest version or after calling transaction SNOTE again. o If the SAP Note is still valid, a dialog box is displayed where you are asked to implement corrections again: BEFORE implementing the corrections, it is necessary to read and re-execute the manual activities (execute automation report) again. CONTINUE implementing the corrections. (In case there are dependent SAP Notes it may be necessary to activate with errors, only when you have reached the last SAP Note everything should be consistent again that it can be activated without errors SAP AG or an SAP affiliate company. All rights reserved. Procedure

7 3 Note Not all dialog boxes, such as transport requests are documented as screenshot in this example. System release before update: 7.31 SP03 Only task manager SAP Notes (until 6.Improvements) are implemented. Note If you have implemented BW related SAP Notes, the list shows more SAP Notes. Likewise, the procedure described henceforth is an example, and must be executed for all SAP Notes and objects in the corresponding manner. System release after update: 7.31 SP05 (SAP_BASIS SP04 and SP05) 2013 SAP AG or an SAP affiliate company. All rights reserved. 7

8 SAP AG or an SAP affiliate company. All rights reserved.

9 Transaction SPDD During import, the system automatically recognizes whether a modification adjustment is required. You are prompted to perform the modification adjustment. 1. Enter the following multiple selection values for Package: o STC* o S_LMCFG* o BW_CORE_TOOLS (for BW tasks) o RSAPI_CTC (for BW source system tasks) 2. Choose Execute SAP AG or an SAP affiliate company. All rights reserved. 9

10 3. Choose Confirm. 4. Navigate to Without Modification Assistant Structures. You have to keep the current modification for each structure. Proceed as follows: Open the Structures tree. Navigate to the object. From the context menu, choose Adopt Modifications SAP AG or an SAP affiliate company. All rights reserved.

11 The structure of the support package and the current modification is identical 1. Choose Accept Proposal. 2. Confirm the dialog box SAP AG or an SAP affiliate company. All rights reserved. 11

12 3. Choose Yes. 4. Continue with next structure SAP AG or an SAP affiliate company. All rights reserved.

13 The structure of the support package and the current modification is different: 1. Go back. 2. Choose No. 3. From the context menu of the object, choose Version Management SAP AG or an SAP affiliate company. All rights reserved. 13

14 4. Choose Request text on/off Deselect the current activ version Select the version right before the SP Update Choose Retrieve SAP AG or an SAP affiliate company. All rights reserved.

15 8. Changes are saved on a workbench request. 9. Confirm the dialog boxes SAP AG or an SAP affiliate company. All rights reserved. 15

16 10. To update the list, choose Refresh SAP AG or an SAP affiliate company. All rights reserved.

17 11. Continue with next structure. 5. For all other objects, choose Reset to Original and proceed as follows: When a still valid SAP Note after the update will be implemented again, the objects will be created/adapted again by doing the manual steps (z_report) before SAP Note implementation Select root element Without Modification Assistant. Open and select all other objects under the root element. Choose Reset to Original. All objects are marked green and have been processed SAP AG or an SAP affiliate company. All rights reserved. 17

18 4. Choose Confirm Adjustment SAP AG or an SAP affiliate company. All rights reserved.

19 Transaction SPAU (OBJECTS): 1. Call transaction SPAU to adjust the remaining modification (You can also skip and do it later) 2. Enter the following multiple selection values for Package: o STC* o S_LMCFG* o BW_CORE_TOOLS (for BW tasks) o RSAPI_CTC (for BW source system tasks) 3. Choose Execute SAP AG or an SAP affiliate company. All rights reserved. 19

20 4. Open and select all the elements under Without Modification Assistant. 5. Choose Reset to Original SAP AG or an SAP affiliate company. All rights reserved.

21 6. Process the confirmation dialog boxes. All objects are marked green and have been processed SAP AG or an SAP affiliate company. All rights reserved. 21

22 SAP AG or an SAP affiliate company. All rights reserved.

23 SPAU (NOTES): Execute Listed SAP Notes 1. Beginning on the top, click the traffic light for each SAP Note. 2. There can be different actions for the SAP Note: o SAP Note is obsolete and disappears immediately. You will jump into SNOTE and afterwards it is recognized to be obsolete. These SAP Notes disappear in the SPAU listing, but are still listed in SNOTE with an inconsistent state; you can update the status in transaction SNOTE to obsolete by using the button Reset to reset the note implementation SAP AG or an SAP affiliate company. All rights reserved. 23

24 o SAP Note is valid and changes need to be implemented again. A dialog box appears for implementing corrections. Caution Before you implement SAP Notes, read and re-execute the post steps, typically the automation report, for this SAP Note. Through this step, objects that are set back to original state are created/updated again SAP AG or an SAP affiliate company. All rights reserved.

25 Re-executing Automation Reports for Task Manager 5. Improvements 2013 SAP AG or an SAP affiliate company. All rights reserved. 25

26 1. When post steps are done, continue with the implementation of the SAP Note: 2. Select all objects. 3. Activate with errors (Because a dependent SAP Note still needs to be implemented, only if last independent SAP Notes have been re-implemented the activation should be fine, in this case Task Manager for Technical Configuration (6. Improvements)) SAP AG or an SAP affiliate company. All rights reserved.

27 SAP Note is adjusted and continues with the last SAP Note. SAP Note wants to implement some corrections SAP AG or an SAP affiliate company. All rights reserved. 27

28 Caution Before you implement SAP Notes, read and re-execute the post steps, typically the automation report, for this SAP Note again. Through this step, objects that are set back to original state are created/updated again SAP AG or an SAP affiliate company. All rights reserved.

29 Re-executing Automation Report for Task Manager 6. Improvements 2013 SAP AG or an SAP affiliate company. All rights reserved. 29

30 When post steps are done, continue with the implementation of the SAP Note. As this is the last remaining SAP Note for modification adjustment, activation should run properly through SAP AG or an SAP affiliate company. All rights reserved.

31 As a result all SAP Notes are adjusted. In case SPAU is done within the update procedure, continue upgrading the support package SAP AG or an SAP affiliate company. All rights reserved. 31

32 SAP AG or an SAP affiliate company. All rights reserved.

33

34 Material Number 2013 SAP AG or an SAP affiliate company. 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. 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 for additional trademark information and notices.