Friday, March 20, 2015

SAP OS/DB Migration Successful Steps...!!!

1 Preparation Phase
2 Check if target OS, DB, R/3 release, language and code page is supported
3 Plan dates for GoingLive - Migration Check
4 Prepare project plan and signed contract "R/3 Migration Services" and send them to SAP
5 SAP approves migration and sends the migration tools and documentation
6 Request adaptation of the SAP license for the target system
7 Request installation package for the target system
8 Check if patches for the target operating and database system are available
9 Check if installation CDs, guides, and installation notes are available for the target system
10 Hardware installation of the target host and system network installation
11 Adapt operating system parameters on the target machine
12 Set up remote access to the source and target system
13 Determine customer migration ID (see "R/3 Heterogenous System Copy")
14 Analyze the source system
15 Distribution of file systems/raw devices on disks; NFS file systems, links, etc.
16 Database configuration (number of log files, size of tablespaces/dbspaces)
17 Configuration of the R/3 System, distribution of central instance and dialog instances
18 CCMS configuration (operation modes, profiles, etc.)
19 Interface to other applications/machines
20 Backup strategy
21 Batch jobs - which jobs are assigned to which host?
22 Methods of data archiving
23 Printer configuration
24 RFC configuration
25 Customer-specific adaptations for R/3 (scripts, data transfer from/to the R/3 System, etc.)
26 Additionally installed R/3 tools (sapcomm, ArchiveLink, SNA gateway, etc.)
27 Define for the target system:
28 which data/configuration has to be transferred to the target system
29 which additional tools have to be installed
30 which adaptations are to be done on the target system
31 of what size are file systems/raw devices/database
32 how will tables, tablespaces/dbspaces be distributed
33 new backup strategy
34 which patches are necessary for the operating system and the database system
35 Perform special consistency checks
36 If R3load method is used: check ABAP/4 Repository (Technical Settings) in the source system
37 Customer-specific modifications