Data migration and version-up

Former Member — Tue, 22 Apr 2008 04:53:37 GMT

Dear all friends,

i am new in SAP,

i plan to join Data mirgration and version-upgrade domain.

please help to show me : process step by step or your experience when upgrade system

ex : process to upgrade from SAP R/3 to SAP ECC.

what life-cycle, document, template should we use !?

thanks !

Edited by: Quoc Luc Nguyen on Apr 22, 2008 6:54 AM

Re: Data migration and version-up

Former Member — Tue, 22 Apr 2008 05:00:49 GMT

Hi,

Please check with the below links. They provide the information you are looking at.

[original link is broken]

http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22

http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm

SAP defined a roadmap for upgrade.

1) Project Preparation

Analyze the actual situation

Define the objectives

Create the project plan

Carry out organizational preparation for example identify the project team

2)Upgrade Blueprint

The system and components affected

The mapped business processes

The requirements regarding business data

3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.

4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning

5)Production Cutover and Support

The production solution upgrade

Startup of the solutions in the new release

Post processing activities

Solving typical problems during the initial operation phase.

SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.

STEPS IN TECHNICAL UPGRADE

• Basis Team will do the prepare activities. (UNIX, BASIS, DBA).

• Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.

• After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.

• Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.

• Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,

The main Category of Objects that needs to be Upgraded is –

• Includes

• Function Groups / Function Modules

• Programs / Reports

• OSS Notes

• SAP Repository Objects

• SAP Data Dictionary Objects

• Domains, Data Elements

• Tables, Structures and Views

• Module Pools, Sub Routine pools

• BDC Programs

• Print Programs