SAP Upgrade Guide

IBM Global Business Services

SAP Upgrade Launching Pad for Future EnterpriseChandra Sekhar Sinha January 25, 2013

IBM Confidential Copyright IBM Corporation 2008


Agenda

Context and Objective-

Why Upgrade? Key Drivers Factors influencing SAP Upgrade Key Decision making aspects for an upgrade

IBMs Approach for SAP Technical Upgrade-

-

How IBMs addressing SAP Upgrade? Upgrade from Developers perspective

2

SAP Upgrade | 3-Nov-08| IBM Confidential

Copyright IBM Corporation 2008


Why Upgrade?Offerings

Based on NetWeaver platform, allows hassle-free integration with add-on functionalities. Consolidation of multiple industry solution portfolios Enhanced user experience and usabilityAccess to 300+ new functionalities Opportunities for Business Process Improvement SAP to discontinue support to versions 4.x and earlier Lower maintenance cost and TCO Stable core, supported by Enhancement Packages Achieve IT Strategy to stay current on SAP functionality Preparation for future projects (ERP Landscape Consolidation) Launching pad for enterprise service oriented architecture (eSOA)

Stability

Future

Moreover, upgrade is no longer a choice!

3




Factors Influencing SAP UpgradeBUSINESS STRATEGY INFORMATION TECHNOLOGY

Business Innovation ,competitive differentiation , collaboration and globalization

Changing legal requirements, IT System stability and Continuous System Maintenance

Continuous Improvement, Process Efficiency & Automation, Process standardization

Reduction in Hardware Costs, Software Costs, Maintenance Costs

OPERATIONAL EXCELLENCE

TOTAL COST OF OWNERSHIP




Types of SAP UpgradeTechnical Upgrade Fastest among all approaches Constant functional perimeter with minor user interface changes Opportunity to eliminate not used modifications and enhancements No new business functionality Average Duration : 1 5 months Functional Upgrade Is built on technical upgrade Provides opportunity to implement additional/ new functionalities Opportunity to reengineer business processes and eliminate unused enhancements Average Duration : 4 12 months Strategic Upgrade Driven by enterprise SOA Provides flexibility to business process innovation Represents significant technology improvements Average Duration : 12 18 monthsStrategic Business Improvement

Business Value

Functional Upgrade

Today Starting Point

Technical Upgrade

Time line5 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008


Key Decision Making Aspects for an Upgrade

START Upgrade Initiative

Key Decisions

Type

Strategy

System Landscape

Language Consideration

Database & OS

Technical Upgrade

Down Time Minimized

Satellite system 1st Then other systems As separate projects

Unicode

Only DB Upgrade

Only OS Upgrade Functional Upgrade Resource Minimized All systems together No Unicode Both DB & OS Upgrade Strategic Upgrade NO DB or OS Upgrade

6




Typical Upgrade Infrastructure Dual Landscape

Existing Landscape

DEV

QAS

PRDUpgraded Landscape

DV1

QA1Transports between systems Manual Changes

No transports between two landscapes Changes made in existing DEV must be manually redone in upgraded DV1




How IBM is Addressing SAP Upgrade?

Proven and Scaleable Methodology and Roadmap, that contain activities and deliverables for different types of upgrades IBM SAP Upgrade Factory Accelerators to size the level of effort, cost, technical approaches, building block of pre-defined unit and integration test scripts, and understanding functionality deltas IBM SAP Upgrade Factory Tools for scanning existing system to determine conflicts between different versions of SAP, optimizing performance, tracking and storage of deliverables, and helping to build your business case

8




The IBM Approach (Ascendant SAP Methodology) for Upgrades - our highly successful standard SAP ImplementationMethodBase Assessment1. Discuss Customer Situation 2. Show IBM Approach 3. Define next Steps

Business Improvement Workshop

Upgrade to target environmentAscendant SAP MethodologyFinal Preparation Project Preparation Realization Evaluation Business Blueprint Go live And Support Sustain

Operate target environment

Upgrade Assessment Strategic

Project Management and Change Management Planning, Analysis and Design Target Operating-Models Development, Analysis and Upgrade Unit and Integration Testing Security Conversions Training Knowledge Transfer Support Operate Old System Implement and Operate Target System Phase 0 Phase 1

Functional Workshop Functional

Upgrade Project

Operate Target Environm. Going live

Upgrade to target environmentAscendant SAP MethodologyProject Preparation Final Preparation Realization Evaluation Phase 0 Business Blueprint

Technical Workshop1. Analyze customer demand (Cross Brand) 2. High level project plan 3. Cost Estimation 4. Resource Definition

Technical

DB/2

Outsourcing

Virtualization

Rational

GBS Services

Storage

X-Series

P-Series

Z-Series

Operate target environment

Go live And Support

Sustain

Project Management and Change Management Planning, Analysis and Design Target Operating-Models Development, Analysis and Upgrade Unit and Integration Testing Security Conversions Training Knowledge Transfer Support Operate Old System Implement and Operate Target System Phase 1 Going live

People

ProcessKnowledge

People

9




IBMs Upgrade Approach in a nutshell

Create Project Plan Develop testing strategy Create Training Plan

Functional Unit Cycle 1

Security

String & Parallel Cycle 2

Communications

Phase 0: Evaluation and Project Preparation

Evaluate New FunctionalityCreateCommunications

Plan Upgrade Sandbox Conduct Project Team Delta Training Conduct Enterprise Platform Analysis

Phase 1: Technical Upgrade

Integration Test Cycle 3

Delta Training

Development Object Upgrade Analyze Development Objects

Mock Cutover

UAT & Regression Cycle 4

Cutover

10




IBMs Technical Upgrade Approach Phase 0

Presales Assessment

Upgrade Workshop

To access impact on: Hardware System landscape Development objects Functionality (Business Processes) Analysis

Upgrade Workshop Details Analyze SAP R/3 system, modifications, enhancements, and customer developments, security, modules, customer resourcesAction

Complete Upgrade Assessment

Create high level project plan for upgrade Do cost estimation Estimate Resources required by Role

- Timeline - Cost Estimate - Team Structure - ImpactsTech upgrade

Tools

-

Workshops and Interviews SAP QuickSizer IBM Insight IBM SAP Upgrade Explorer Tool

- Risk

11




IBMs Technical Upgrade Approach Phase 1Typical High Level Project Plan

IBM SAP Upgrade factoryOverview Overall Roles and Responsibilities KPI Reporting Delivery Model Workflow Tools and Accelerators Project Organization Governance

Phase wise IBM Responsibilities/DeliverablesProject Preparation Realization Testing Dry Run & Cut Over Post Go Live

This is a Sample plan and can change based on client system landscape complexities, breadth of functionalities and volume of custom developments

* Click on hyperlink to get detailed information12 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008


System wise activitiesPlay ground for developers. Get an idea of real system. Modification Adjustments to be done. Unicode Enabling to be done. All development related activities to be done. Unit Testing to be done. Delta modifications to be corrected here. Integration Testing to be done here. If Regression box is not available, UAT to be done here.Sandbox (Optional)

Development System

Quality System

If available, User Acceptance Testing to be done here. Real System to be run for production. Post go-live supports to be done here.13 SAP Upgrade | 3-Nov-08| IBM Confidential

Regression (Optional)

Production System



SAP Upgrade: Role of DevelopersRoles: Identification of development objects target for upgrade Create documentations for developments and corrections Modifications due to upgrade Technical upgrade of custom developments and interfaces Program coding and Unit testing Developments issue identification and resolution Resolution of development related test defects

14




SAP Upgrade: Responsibilities of DeveloperALV / Report BAdi Smart Form Function Module BAPI Menu Painter Data Dictionary Screen SAP Script ABAP Security

ALE / IDoc

DimensionsBASIS DEV Functionality

QAREG Production

Unit Testing IT Phase1

IT Phase2 UAT Post Go-Live Support

15




ScopesWhat is included in SAP and what is outside SAP spaceWhat is included in SAP All Standard and Customized SAP DDIC objects All Standard and Customized SAP Repository object All Functional and ALE related Configuration (Functional Team) All Basis activities for making underlying system ready for ECC 6. All Security and authorization issues (Security Team)

In Scope

What is not included in SAP

All Non-SAP Legacy systems EDI Configurations with Non-SAP systems BW/APO/XI systems (Scope dependent)

16



Out of Scope


Steps of SAP UpgradeDevelopment System Upgrade front-end software of project work-stations & end-users (if possible) Prepare the hardware of new Development server Install Operating System System Copy from Source Version Development / Production System Execute Pre-Upgrade Script Prepare Analyze results of Prepare in CHECKS.LOG file in upgrade directory. Release open transport requests and repairs. Inconsistent function groups to be corrected via transaction SE80 Add space to file-system/database as per logs with a 10-20% overhead. Confirm open support packages via transaction SPAM in client 000. Complete Outstanding updates / unresolved requests Rename data dictionary objects (data elements, domains, structures) that will be modified/dropped and are currently in use in custom tables. Execute Upgrade Routines

17




Steps of SAP UpgradeDevelopment System Stop in SPDD phase to adjust / accept changes to modified standard SAP DD Objects No need to process programs via transaction SPAU during upgrade. After upgrade, modify / accept changes to standard SAP Programs via SPAU Record SPDD & SPAU changes in a single transport request Execute transaction SAMT to perform syntax check on custom Programs Execute UCCHECK to determine Unicode relevant syntax errors (optional) Fix all errors as reported in SAMT & UCCHECK. Test programs as per project plan or earlier assessment. Make Security & Role Modifications For old SAP systems, convert authorization profiles to roles Execute transaction SU25 steps to identify roles, authorization objects that have been impacted Add/modify/delete authorization objects/values. Check password / login instance profile parameters.

18




PREPARE ToolsProductive operation

Follow up activities

Prepare

Prepare

Upgrade

P-MSG

.

Time

PREPARE: The PREPARE program uses a series of checks to support the preparation of the upgrade without affecting productive operation.

Benefits of PREPARE Extend checks during upgrade preparation Extended and improved database space check Display of objects to be adjusted (SPDD/SPAU) Forecast of the amount of database conversion Correction and modification analysis

19




Modification Adjustments:Different modified objects require different transaction adjustment. SPDD: Transaction SPDD is used to perform modification adjustments to certain ABAP Dictionary objects such as domains, data elements, table structures, transparent tables, pooled tables, cluster tables and tables technical setting. Not performing modification adjustment for these objects would cause data loss. Adjustments Adopt Modifications: Keeps old release (with customer modifications/applied notes) remains unchanged. Reset to Original: Accept original version (i.e. - Imported into the SAP System during the last upgrade).

Traffic Signals:

20




SPDD:

21




SPDD: Step1Execute the transaction SPDD in ECC system. After analyzing select the object and follow the screenshot. Here we have chosen a Domain.

Click on RESET TO ORIGINAL and a pop-up appears.22 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008


SPDD: Step2Click on the long text for more information

23




SPDD: Step3Click on the Tick mark and a warning pop-up appears informing the actual activity of making it Reset to Original.

24




SPDD: Step4Click on the Tick mark and a warning pop-up appears informing to make changes only if required.

.

25




SPDD: Step5Click on OWN REQUESTS and select the corresponding Workbench Request and Task no.

26




SPDD: Step6Select the corresponding task with your USER ID

27




SPDD: Step7A pop-up with the request no and description appears. Click on the Green tick mark.

28




SPDD: Step8Clicking on the tick mark this object is now Reset to Original.

Now Double-click on the icon appearing on the left of this domain29 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008


SPDD: Step9A Pop-up appears confirming for the agent. Choose the AGENT and continue by clicking on the COPY.

.30 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008


SPDD: Step10A pop-up appears requesting for confirmation. Confirm it by clicking on the CONFIRM.

31




SPDD: Step11Now the object is become as ECC (Reset to Original).

*Select for Transport Option32 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008


Modification Adjustments- SPAU:

SPAU: After activating the new repository, transaction SPAU is used to perform modification adjustments to certain ABAP dictionary objects (lock objects, views), all other repository objects (Module pools, ABAP Programs, Function Modules, Menus, Screens etc.) Adjustments Adopt Modifications: Keeps old release (with customer modifications/applied notes) remains unchanged. Reset to Original: Accept original version (i.e. - Imported into the SAP System during the last upgrade).

33




Modification Adjustments - SPAU:Usually 3 types of objects need adjustments which are Notes, Objects modified With Modification Adjustment, and Objects modified Without Modification Adjustment.

34




Modification Adjustments - SPAU:

35




SPAU OSS notes Correction:

36




SPAU OSS notes Correction contd

37





38





Clicking on Calculate will start the process Determine Adjustment modes either in background or foreground. Once this process is finished, the adjustment mode for the Note in question would change to either of the Examples 1 or 2. Following action should be taken considering the adjustment mode calculated.39 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008



40




With Modification Adjustments - SPAU:

41





42





43





44





45





46





47




Without Modification Adjustments - SPAU:

48




Without Modification Adjustments - SPAU:

49




SPAU: Reset To OriginalAccept original version (i.e. - Imported into the SAP System during the last upgrade).

50




SPAU- Reset to Original: Step1Execute the Transaction SPAU in ECC system. After Analyzing select the object and follow the screenshot.

51




SPAU-Reset to Original: Step2Click on RESET TO ORIGINAL and a pop-up appears

52




SPAU-Reset to Original: Step3Click on the long text for more information

53




SPAU-Reset to Original: Step4Continue by clicking on the green tick and the following pop-up appears

54




SPAU-Reset to Original: Step5A warning pop-up appears informing to make changes only if required. Click on the Tick mark

55




SPAU-Reset to Original: Step6A pop-up appears for the REQUEST NUMBER. Confirm the request no

56




SPAU-Reset to Original: Step7Select the agent/agents and click on the COPY button

57




SPAU-Reset to Original: Step8Make refresh the screen, this object disappears from the list.

The object is now Reset to Original

58




SPAU-Adopt Modifications: Step1After Analyzing select the object and follow the screenshot.

59




SPAU-Adopt Modifications: Step2The following warning pop up appears

60




SPAU-Adopt Modifications: Step3

A pop up asking for the Workbench Request. Choose OWN REQUESTS button.

Continue by clicking on to the green tick. The changes have been adopted, but the object would not active. So in ECC system, open the corresponding object and activate. If it is within 14 days of the system installation, access key for object is not required. Otherwise a pop asking for the access key when we try to activate.

61




SPAU-Adopt Modifications: Step4Continue and the modifications are now completed.

62




Unicode Enabling Tools for Unicode Enabling:SAP has provided with some transactions to check the ABAP source code for Unicode compliance: 1. Transaction UCCHECK Reports the static errors in the ABAP source code. 2. Transaction SCOV Runtime coverage analyzer.

Here We are going to discuss the UCCHECK Phase In Upgrade.

UCCHECK In Upgrade: Transaction UCCHECK is used to examine an Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. If you want to use UCCHECK to process program objects that have already set the Unicode attribute, then it can be done by un-checking the corresponding checkbox of UCCHECK selection screen.

63




Unicode Enabling contd..Execute Transaction UCCHECK. Bellow screen appears:

64




Unicode Enabling contdSelection Screen FieldsObject Type PROG CLAS FUGR FUGX FUGS LDBA CNTX TYPE INTF

Report Programs Classes Function Groups Function Groups (with Customer include and Customer area) Function Groups (with Customer include and SAP are) Logical Database Context Type Pool Interface

1

Check Boxes

2

Include only Objects with Object Repository Entry (TADIR): By activating this option those objects can be excluded which are not present in TADIR table. Exclude $* Packages: By activating this option, local objects can be excluded. Check modified SAP objects also: By activating this option, SAP standard objects which were modified in customer section can be included. Display lines that can not be analyzed statically: By checking this option, an overview of those portion which can not be checked statically for Unicode Syntax Error also included.

Show also Location Hidden with #EC*: By checking this, hide the warning using the pseudo comment ("#EC *).View Maintenance: Parts of the view maintenance generated in older releases are not Unicode-compatible. Obsolete Function Modules (UPLOAD/DOWNLOAD): The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode.65 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008


Unicode Enabling contd1

2

66




Unicode Enabling ContdThe Exception column of the report displayed with Red,Green and yellow traffic light Icon for each of the program.The system found no Unicode syntax errors for the object. Unicode flag can be set without changing the program.

The System found warnings for the object; it can be removed or ignored before making it Unicode enabled.

The System found errors for the objects; it must be corrected before making the program Unicode enabled.

Handling the object with green traffic:Select a record from the list which displayed with green traffic. Then click on

67




SAMT

Transaction SAMT allows us to perform tests on sets of associated inactive programs. There are a set of tasks which can be performed through SAMT. if you want to do a syntax check, select Syntax Check from the Short text for task and double click.

If you want to Extended Program Check (important tests), then select Extended Program Check (important tests). Generally SAMT used for Non-Unicode Syntax Check in upgrade for custom developments.

68




SAMTTransaction SAMT allows us to perform number of tasks according to the requirements.

69




SAMTAfter execution, all errors appear. By double clicking one can navigate each object and make them correct.

70



IBM Global Business Services ABAP TAC SPDD Process FlowBusiness Blueprint Realization Final Preparation Go Live

Method PhaseClient ABAP TAC

Communication & Coordination (all teams)

Ongoing Issue Resolution (all teams)

1. Get the SPDD list from Basis - comes up during system preparation phase 6. Send the details to Customers Business Analysts to take a call on the change

2. Decide Delivery Cell

11.Document all the changes made and share with Customer 12. Complete Knowledge management with Lessons Learnt and update methods .

3. Estimate

10. Mark the transport as released 5. Analyze the difference between two systems

Legend Task with Deliverable

4. Assign Work

9. QA Review

Task without Deliverable Process checkpoint

7. Modify as per Customer requirement

Sign off and Knowledge Transfer Handoff

8. Save all the changes in one transport

* This step requires a remote version comparison between existing prod and upgraded dev systems

71



IBM Global Business Services ABAP TAC SPAU Process FlowBusiness Blueprint Realization Final Preparation Go Live

Method PhaseClient ABAP TAC



1. Get the SPAU List from Basis - comes up during system preparation phase 6. Send the details to Customers Business Analysts to take a call on the change

2. Decide Delivery Cell

11.Document all the changes made and share with Customer 12. Complete Knowledge management with Lessons Learnt and update methods .

3. Estimate

10. Mark the transport as released 5. Analyze the difference between two systems

Legend Task with Deliverable

4. Assign Work

9. QA Review

Task without Deliverable Process checkpoint

7. Modify as per Customer requirement

Sign off and Knowledge Transfer Handoff

8. Save all the changes in one transport

* This step requires a remote version comparison between existing prod and upgraded dev systems

72



IBM Global Business Services ABAP TAC ABAP Custom Development Correction Process FlowBusiness Blueprint Realization Final Preparation Go Live

Method Phase 2. Decide Delivery Cell 3. Estimate 4. Assign WorkClient



1. Get the SUET Output List (Exclude any objects or application not in scope per the customer) 4. Prioritize the impacted object list 3. Run SAMT/UCCHECK for all in scope objects and get the impacted object list 5. Run Auto upgrade tool for T1 object types based on the prioritized object list to fix the errors 10.Document all the changes made and share with Customer

11.Test ( Functional, Integration and User Acceptance )

12 TPR

15.Document all the changes made and share with Customer 14. QA Review of the analysis and modifications (If any) 16. Complete Knowledge management with Lessons Learnt and update methods .ABAP TAC Legend

13 Technical support during customer onsite testing

9. Mark the transport as released

8. QA Review

Task with Deliverable Task without Deliverable

6 Again run UCCHECK for all in scope objects and get the revised impacted object list

7. Adjust the revised impacted list manually

Process checkpoint Sign off and Knowledge Transfer Handoff

73



IBM Global Business Services# Phase Template Purpose

1 Realization

SPDD Correction Log SPAU Correction Log

These document contain the list of objects appeared and required adjustments during that particular upgrade phase along with the difference found between the two systems for that object, SAP proposal for the change, decision from the customer on that change and the action taken for each impacted objects. This document contains the list of Custom objects having syntax errors or execution errors, the details of the error, action taken on the error, transport number used for making the changes and current status of the object.

2

Realization

ABAP Correction Log

3 Realization

SA P Upgrade Rev iew C hecklist

SAP Upgrade Review Checklist

SAP Upgrade checklist is used for reviewing the modification made by other and also it contains some general guidelines that should be followed for any upgrade.

Upgrade CDF 4 Realization Used to estimate Technical Upgrade efforts

Please visit : http://w3.tap.ibm.com/w3ki2/display/ABAPTAC/1+-+Technical+Upgrade+TAC+Templates+and+Standards74 SAP Upgrade | 3-Nov-08| IBM Confidential Copyright IBM Corporation 2008


Russian

GraciasSpanish

ObrigadoTraditional Chinese Brazilian Portuguese

Thank You !Simplified Chinese

MerciFrench

Arabic Thai

GrazieItalian Korea n

DankeJapanese German

75



SAP Upgrade Guide

Documents

Customer Upgrade Guide - Sage€¦ · Business Objects is.....

SAP NetWeaver Upgrade Master Guide Application Development.....

Master and Upgrade Guide for SAP Application Interface ...

SAP Disclosure Management 10.0 - Installation and Upgrade...

SAP Upgrade Higlight

Upgrade Guide for SAP S/4HANA 2020

SAP アップグレード SAP UPGRADE ASSESSMENT...

Common Upgrade Guide for SAP Customer Activity Repository...

SAP Extended Warehouse Management 9.5 Upgrade Master Guide

Efficient SAP NetWeaver BW Implementation and Upgrade Guide

Upgrade and Update Guide - SAP CRM 7.0 EHP4 ·...

Common Upgrade Guide CARAB 1.0 SPS5 - SAP€¦ · This...