Service Report
SAP OS/DB Migration Check
Remote Project Audit
SAP System ID
SRP
SAP Component
R/3
Release
4.0B
DB System
Oracle
Customer
<Customer Name>
<Address>
<Country>
Service Center
Telephone
Fax
SAP Support
+xx xxxx xxxx
+xx xxxx xxxx
Date of Session
Date of Report
Author
xx.xx.xxxx
xx.xx.xxxx
XX
<Watermark>
<dat_dummy>
Session No.
Installation No.
Customer No.
0010000XXXXX
0120XXXXXX
0000XXXXXX
Project Audit Summary
Project Audit Summary
Your migration project is approved by SAP.
Before starting the project, check this report to see if there are any
recommendations that you want to incorporate into the project.
Note:
All recommendations provided in this report are based on our general experience only. We advise you to
test our recommendations before using them in your production system.
Action Plan
Priority Short step description
Deadline
Technical Consultant
<Consultant’s Name> is registered as a certified technical consultant with additional certification for
OS/DB Migration and fulfills the requirements for executing OS/DB migration projects.
Please address all questions concerning the migration project to this person first before opening a
customer message.
Migration Tool Kit
SAP sent you a Migration Tool Kit containing several CDs with various versions of the migration tools. The
appropriate version of the tools for your migration is named in table 'Tool Information' in the chapter 'Planning
Check'. Select the corresponding CD from the Migration Tool Kit, the tool version may be higher than the release
of your R/3 System.
Use only this CD for your project. and ignore all other CDs in the package.
The CD contains the migration tools for both the source and target platform and the documentation
(Heterogeneous System Copy Guide). Do not use the FAX form from the CD for requesting a migration key.
Normally, the keys are printed in table 'Tool Information'. If not, or if this key does not work, log on to the SAP
Service Marketplace and generate the key online.
OS/DB Migration Service Report 10.01.2002
2
Planning dates for Development System
Planning dates for Development System
Platform Check for Development System
Kind of data
Source system
DB SIZE (GB)
HOSTNAME
CURRENT RELEASE
RELEASE FOR MIGRATION
SID
OPERATING SYSTEM
DATABASE SYSTEM
30
sapdev
4.0B
4.0B
SRD
WIN-NT
ORACLE
Target system
sapdeve
4.0B
TGD
AIX
INFORMIX
This part of the planning is OK.
Schedule Check for Development System
Project phase
PREPARATORY PHASE
MIGRATION TEST RUNS
TESTS ON THE TARGET SYSTEM
FINAL MIGRATION
Start date
End date
19.11.2001
06.12.2001
21.12.2001
16.12.2001
10.12.2001
15.12.2001
10.01.2002
19.12.2001
The schedule is OK.
Tool Information for Development System
Kind of information
Version / Code
VERSION OF TOOLS TO USE
MIGRATION KEY
KEY EXPIRATION DATE (YYYYMMDD)
MIGRATION ID (INFORMATION ONLY)
4.0B
CZ70X3Z7FU
20991231
TAYG0YTZY0
Planning dates for Production System
Platform Check for Production System
Kind of data
Source system
DB SIZE (GB)
HOSTNAME
CURRENT RELEASE
RELEASE FOR MIGRATION
SID
OPERATING SYSTEM
DATABASE SYSTEM
30
sappro
4.0B
4.0B
SRP
WIN-NT
ORACLE
Target system
sapprod
4.0B
TGP
AIX
INFORMIX
This part of the planning is OK.
OS/DB Migration Service Report 10.01.2002
3
License Keys for the Migration Tools
Schedule Check for Production System
Project phase
PREPARATORY PHASE
MIGRATION TEST RUNS
GOINGLIVE ANALYSIS SESSION (PROPOSED DATE)
TESTS ON THE TARGET SYSTEM
FINAL MIGRATION
START OF PRODUCTION
Start date
End date
19.11.2001
06.12.2001
10.01.2002
21.12.2001
11.01.2002
14.01.2002
10.12.2001
15.12.2001
10.01.2002
10.01.2002
13.01.2002
14.01.2002
The schedule is OK.
Tool Information for Production System
Kind of information
Version / Code
VERSION OF TOOLS TO USE
MIGRATION KEY
KEY EXPIRATION DATE (YYYYMMDD)
MIGRATION ID (INFORMATION ONLY)
4.0B
CZ70X3Z7FU
20991231
TAYG0YTZY0
License Keys for the Migration Tools
When you start working with the migration tools, you will be asked to enter a migration key before you can
continue. To be prepared for this event, please read the documentation (Heterogeneous System Copy Guide)
carefully.
We have generated migration keys for you (one for each system that is to be migrated) based on the information
contained in your project plan. Please check data in table 'Migration Tool Info'.
Normally, when the information in your plan is correct and the data will not change during project execution, this
key will work. For releases where a migration ID exists, we have also computed this ID and mentioned it in the
report. If a migration ID is given, you should generate this ID on your system during project execution (as
described) and compare it with the value in the report. If both values are the same, you can use the migration key
from the report. If the IDs are not the same, you should log on to the SAP Service Marketplace (alias
'migrationkey') and generate the key online.
Remote Performance Sessions
We have planned a GoingLive (Migration) Check for your production system. Please find the date of the first
remote session in the table containing the schedule of your production system (look for confirmed date). You
should be prepared to support the delivery of this session that day and the days before.
You will be contacted some days before this date to prepare the session. If you change your plans and this
session cannot be performed on the given date, please contact us as soon as possible to arrange a new date.
The date for the second session will be scheduled during the first session.
OS/DB Migration Service Report 10.01.2002
4