1. How will you do client copy?
Answer: Client copy can be done via 3 different ways:
Initially you need to create client using T-code SCC4.
a.
Local Client copy:
-
Logon to the newly created client with user sap* and password pass
-
Execute T-code SCCL
-
Select profile, source client and start immediately
b.
Remote Client Copy:
-
Logon to the newly created client with user sap* and password pass
-
Execute T-code SCC9
-
Select profile, source destination RFC and start immediately
c.
Client Import/Export:
-
Client Export is done from source system using T-code SCC8, select profile,
target system and start immediately
-
Client Import is done from newly created client from target system by executing
T-code STMS_IMPORT and select the transport request number (TR) which was
created while doing export and import the selected TR
2. If SAP* is not available, then how will you do?
Answer: Check if the sap* user is there in table
USR02 from database level or not. Delete the user if present by executing sql
command:
SQL> Delete from <schema_name>.USR02 where
BNAME=’SAP*’ and MANDT=’<client>’ ;
Set the parameter login/no_automatic_user_sapstar = 0 in
profile file and restart the instance.
Now you can login with user SAP* with default password
“pass”.
3. After client copy, is tablespace and database sizes
will be increased or not?
Answer: Yes, the tablespace and database sizes will
increase after client copy as the data/entries is copied between client.
4. How to do client copy fast?
Answer: There are number of factors which determined
the speed of the client copy like database size, hardware capabilities.
Local client copy is faster. Also, to speed up the process,
you can increase the number of parallel process.
5. What are various profiles available for client copy?
Answer: The various profiles available for client
copy are:
|
S.NO |
Profile |
Description |
|
1 |
SAP_ALL |
All Client-Specific Data w/o Change Documents |
|
2 |
SAP_APPL |
Customizing and Application Data w/o Change Docs |
|
3 |
SAP_APPX |
SAP_APPL w/o Authorization Profiles and Roles |
|
4 |
SAP_CUST |
Customizing |
|
5 |
SAP_CUSV |
Customizing and User Variants |
|
6 |
SAP_CUSX |
Customizing w/o Authorization Profiles and Roles |
|
7 |
SAP_PROF |
Only Authorization Profiles and Roles |
|
8 |
SAP_UCSV |
Customizing, User Master Records and User Variants |
|
9 |
SAP_UCUS |
Customizing and User Master Records |
|
10 |
SAP_UONL |
User Without Authorization Profiles and Roles |
|
11 |
SAP_USER |
User Master Records and Authorization Profiles |
6. How to do transports between production and
development?
Answer: From application level, transport can be done
via T-code STMS_IMPORT.
From OS level, tp command is used to transport between
production and development system.
7. How to apply OCS patches?
Answer: T-code SPAM (Support Package Manager) is used
to apply OCS (Online Correction Support) patches.
8. How to do transports from OS level?
Answer: To transport the TR from OS level, follow the
below steps:
From Source System:
- Copy the data file and co-file of related TR from source
to target if not available using command:
Scp –pr <filename> <user>@<target
IP>:<path>
e.g. scp –pr K9000123.<SID> <SID>ADM@IP
address:/usr/sap/trans/cofiles (for co-file)
scp –pr R9000123.<SID> <SID>ADM@IP
address:/usr/sap/trans/data (for datafile)
From target system:
- Add the TR to the buffer, execute below tp command
Tp addtobuffer <transport request> <SID>
Client=<client number> pf=/usr/sap/trans/bin/TP_DOMAIN_<DOMAIN
SID>.PFL
- Import the TR, execute below tp command
Tp import <transport request> <SID>
client=<client number> pf=/usr/sap/trans/bin/ TP_DOMAIN_<DOMAIN
SID>.PFL
9. Where the transport data files will be placed?
Answer: The transport data files will be placed on
directory data under following location:
/usr/sap/trans/data/
10. How to make security authorization report?
Answer: The simplest way to get security
authorization report is by executing T-code SUIM (User Information System).
You can find different scenarios to get data like
- Find User by Complex criteria, unsuccessful logon, by
logon date and so on.
- Find Roles by user assignment, transaction assignment,
authorization object and so on.
- Change Documents for users, role assignment, roles,
profiles, security policies and so on.
11. In which table failed user login attempts will be
there?
Answer: Table USR02 contains the number of failed
logon attempts of the user.
12. How to see the table entry values?
Answer: You can see the table entry values using
T-code SE16 or SE11.
13. How will you give new authoriztion?
Answer: New authorization can be assigned to users
as:
- Create role using T-code PFCG
- Add the authorization object in that role, generate and
assign the user.
14. How to configure TMS?
Answer: For TMS configuration, select the domain
controller and member systems from the SAP landscape i.e. from Dev, Qas and Prd
which one should be Domain Controller and which one should be member systems.
Configuration steps:
a.
Execute T-code STMS in client 000 from domain controller system
-
A pop-up window prompt to configure domain controller
-
Specify the domain controller hostname
-
System Number
-
TMSADM user creation
b.
Execute T-code STMS in client 000 from member system
-
System will display the domain controller details
-
Click save to add the member system in the domain controller
-
Member system will be in waiting status and needs approval from domain
controller
c.
Approval from Domain Controller
-
Logon to the domain controller in client 000 and execute T-code STMS
-
Go to Overview→Systems
-
Select the member system and from the menu choose ‘SAP System’→Approve
d.
Configured Transport Route
-
The routes are created to transport the changes between the SAP systems in a
system landscape as configured in STMS
-
Two routes are created:
i.
Consolidation Route: From Dev to Qas system and
ii.
Delivery Route: From Qas to Prd system
-
Transport layers are only used in Consolidation route as it is assigned to all
development objects and need to be sent through same transport route
15. What is transport domain?
Answer: The SAP system within your system landscape
which is used to maintain and change transport management system configuration
is domain controller and all the system within the landscape is transport
domain.