Documente Academic
Documente Profesional
Documente Cultură
Project Name:
Delivery Engine
Sub team:
Basis
Category:
Prepared By
Document Owner(s)
Project/Organization Role
Santosh sarkale
Delivery Engine/Basis
Date
Author
Change Description
0.1
25 jan 2010
Santosh sarkale /
Balaji shelake
Confidential
250375029.doc1
Last printed :Not Yet
Introduction_________________________________________________________3
Deliverables__________________________________________________________4
2.1
2.1.1
2.1.2
Scope Details_________________________________________________________6
3.1.1
3.1.2
Assumptions/Limitations______________________________________________19
Summary___________________________________________________________19
Confidential
Page 2
11/7/2014
1 Introduction
Objective is to build the Basis Workbench which will consist of various utilities for
automating System refresh pre and post steps. Many of these tasks could be automated
to reduce the effort and rework. This will also allow lesser experienced team members to
work on the system refresh tasks with minimal training. Following section documents the
benefits of each individual utility which will be part of the system refresh Workbench.
For example, using system copies, you can use system copy to set up a landscape for:
a) Development
b) Quality assurance tests
c) Integration tests
d) Upgrade Tests
e) Backup and Restore Tests
f) Training Systems
g) Demonstration Systems
h) Operating system migration
i) Database migration
j) Change of hardware
k) Unicode conversion
While reasons a) - g) on this list imply the creation of a cloned system or system
landscape (where the source systems are duplicated), the last four items h) k) refer to
changes on the production environment. In this latter case, the production landscape is
not duplicated but moved to another hardware or software environment instead. This
procedure is also included in the terms SAP System Copy or SAP System Landscape
Copy although it does not deliver a second instance of the system or system landscape.
Unless noted otherwise, when speaking of system copy we will usually refer to a real
second copy created from a productive source system.
Instead of using the standard procedures for installing, setting up, and customizing SAP
systems, the SAP system copy procedure can be used to create a new target system
landscape or to refresh the data of an already existing target system landscape. The
advantage of a system copy is that it enables you to perform many system setup
activities at once, because the whole system environment with its customizing, support
packages, modifications, corrections, plug-ins and other technical settings are all copied
to the target system (instead of being manually recreated). After the copy, these settings
need only to be adjusted.
Confidential
Page 3
11/7/2014
2 Deliverables
2.1
Confidential
Page 4
11/7/2014
2.2
Confidential
Page 5
11/7/2014
3 Scope Details
This section defines the scope for developing Basis Workbench which should consists
of all of the following utilities to perform various Systems refresh tasks during the
maintain phase of the project.
Basis Workbench is a concept which is similar to a cockpit or a central location from
where all of the following utilities could be launched. It could be SAP menu if the utilities
are developed in OS Script/.bat Files, ABAP/4 or .net Frame work.
3.1
3.1.1
3.1.2
Confidential
Page 6
11/7/2014
Note: Currently when we are sending system messages thought SM02. We have to login
into each clients which are exist in that server. Our tool is able send System Message
across the all clients.
3.1.3
Confidential
11/7/2014
3.1.4
Confidential
Page 8
11/7/2014
3.1.5
Once all the distribution models have been added to the transport, release the
request
Verify that the datafile and cofile for the request exist in ..\usr\sap\trans\.. on the
transport host
Confidential
Page 9
11/7/2014
3.1.6
3.1.7
Confidential
Page 10
11/7/2014
Confidential
Click Start Immediately button and confirm the dialog box to continue
Make a note of the transport request numbers
Go to transaction se01, enter the transport request number and view the logs to
verify that the user tables were exported successfully
Page 11
11/7/2014
3.1.8
Verify that the datafile and cofile exists in ..\usr\sap\trans\.. on the transport host.
Confidential
Page 12
11/7/2014
3.1.9
Go to transaction SCOT
Double-click each client and save a screenshot
Step-2 Double
Click Internet Set
Confidential
Go to transaction STRUST
Right click on Systems
Page 13
11/7/2014
Confidential
Page 14
11/7/2014
Go to transaction SCC4
Double-click each client and save a screenshot
Go to transaction SM02
save a screenshot
Confidential
Go to transaction RZ04
Save a screenshot
Page 15
11/7/2014
Confidential
Go to transaction SMQR
Save a screenshot
Page 16
11/7/2014
Go to transaction SMQS
Save a screenshot
Go to transaction SMLG
Save a screenshot
Confidential
Go to transaction RZ12
Save a screenshot
Page 17
11/7/2014
Go to transaction SLICENSE
Record the license information
Alternatively you can retrieve the license key from the Data Maintenance area
of the SAP Service Marketplace
Confidential
Page 18
11/7/2014
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.2.8
3.2.9
Confidential
Page 19
11/7/2014
3.3
3.3.1
All the below steps which are in SAP has to be done in target system after
system refresh and by logging in to the default client.
Confidential
Go to EDIT Install License, give the required information and press Install.
Page 20
11/7/2014
3.3.2
Configure TMS
Log onto the TMS domain controller and delete the <TSID> system
Log into <TSID>/000 as DDIC go to STMS transaction
Click on Other configuration to include this system to domain and give the
domain system details and save
Go back to the domain controller and approve the addition of <TSID> back into
the transport domain
Reconfigure the transport routes if needed and redistribute
3.3.3
Confidential
Page 21
11/7/2014
3.3.4
Confidential
Page 22
11/7/2014
3.3.5
Import printers
Confidential
Give the change request number which is exported in 3.1.6 and click OK
Page 23
11/7/2014
3.3.6
Confidential
Page 24
11/7/2014
Confidential
Page 25
11/7/2014
3.3.7
Confidential
Give the change request number which is exported in 3.1.4 and click OK
Page 26
11/7/2014
3.3.8
Confidential
Page 27
11/7/2014
Confidential
Give the change request number which is exported in 3.1.5 and click OK
Page 28
11/7/2014
3.3.9
Confidential
Give the change request number which is exported in 3.1.15 and click OK
Page 29
11/7/2014
Confidential
Page 30
11/7/2014
Give the child system logical name in our e.g. TSTCLNT100 and press Enter and
save
Confidential
11/7/2014
Confidential
Page 32
11/7/2014
Go to transaction RZ10
Delete the profiles for SSID from the database: Profile -> Delete -> All Versions
-> Of a profile. Choose Yes when asked to delete all versions, then CHOOSE
NO when asked to delete the files at the OS level. Repeat this step for each
profile Default, Start, and Instance.
Import the modified profiles for TSID: Utilities -> Import Profiles -> Of Active
Servers
Confidential
Page 33
11/7/2014
Go to SMLG click on Create and give the details (from the screen we have
copied in step 3.1.17)
Confidential
Go to transaction SCC4
Reconfigure the client settings as needed. Use the screenshot saved in step
3.1.12 as a guide
Page 34
11/7/2014
Confidential
Make changes if any required and click on execute to configure standard basis
jobs.
Page 35
11/7/2014
Go to RZ04 click on Create and give the details take the reference of the
screen shot took in step 3.1.14
Confidential
Page 36
11/7/2014
Confidential
Page 37
11/7/2014
Confidential
Go to SMQR click on Registration and give the required fields and press
OK (Take the reference of the screen shot of 3.1.16)
Go to SMQS click on Registration and give the required fields and press
OK (Take the reference of the screen shot of 3.1.16)
Page 38
11/7/2014
Confidential
Go to SCOT double click on SMTP and click on INTERNET and give all the
details and same (Take the reference of the screen shot 3.1.9)
Page 39
11/7/2014
Go to SICK or SM28 to find errors if any and solve it first before you go to declare
readiness of the system.
Go to SM21 to find errors if any and solve it first before you go to declare
readiness of the system
Go to SM02 Click on create and give the details and click on OK.
Confidential
Page 40
11/7/2014
Click on filter and give last system copy date and press OK
Confidential
Page 41
11/7/2014
4 Assumptions/Limitations
5 Summary
Approved By:
_____________________________
Confidential
Page 42
11/7/2014