Basis Articles
Basis Articles
Basis Articles
Changing the system time zone on SAP system should not have any influence on
existing data, because the times/dates on database are stored with a certain time
stamp and these are not influenced by the time zone changes. The sequence and
the chronological order of the document will remain the same. In the transaction
STZAC you do have the following two time zone input fields:
System Time Zone
<If an application is started in a client it can use this
client time zone setting>
User's Default Time Zone <If a user is connected to a client and for this userid if
there is no time zone setting defined in the transaction SU01 of this client then the
user time zone will be automatically
set to the time zone value
which is defined in this field here>
How to check the timezone at different levels
Login to SAP system client
Run the report from Tcode SA38 -> TZCUSTHELP
Run the report from Tcode SA38 -> RSDBTIME
TZCUSTHELP
TZCUSTEX
RSDBTIME
Time diagnosis
So, Lock Users: Only administrator user IDs should be active and all other SAP user IDs should
be locked so that no user intervention can occur at the time of client copy in the source system
(SU01).
1. There must not be any background job running or in released status in the SAP system
(SM37).
2. Check for TMS configuration and ensure there are no updated errors in SM13 of
source client.
3. Make sure that there is enough space in target system table spaces and in Common
Transport directory.
4. To keep the User Master Records and Authorization Profiles same after client copy, take
the export of SAP_USER profile.
PRE-REQUISITES
1. For performing a client copy we must check the size of the client and availability of space
in the target system for copying that client.
2. Authorization required to copy client, to export and import client as well as to perform
the steps related to transport management system must be assigned to the SAP user
performing the Sap client copy as per SAP recommendations.
3. Source SAP system and Target SAP system should be same release.
4. Transport tools like tp and R3trans should be working accurately in the SAP systems.
5. No SAP users should be able to login to the source as well as target SAP system so that
there is no inconsistency in the SAP system.
PROCEDURE
Log on to source system - source client and make sure that all above steps have been
performed .Then go to tcode SCC8 for Export. Select a client profile according to data to be
copied as a Transport request. Mention target system into which the client should be copied.
Configure this as a background or dialogue process.
According to the client profile selected and the data available, maximum 3 transport requests will
be created and automatically exported to target system mentioned. The requests are like
<sid>KO<No> - For cross client data
<sid>KT<No> - For client specific data
Use the function Set to Released to set the request to Released automatically when you unlock
it. You can then no longer use this request.
Use the function Create transport of copies to create a new transport of copies when you unlock
change requests, and copy the object list of the request to the transport.
OS07N
SM02 System Message
Other Monitoring Tcodes: