# Client Management
000
- MC Master Client DEV QTY PRD
001
- CMC Copy Master Client 101 201 301
066
– Early Client Monitoring
1.
SCC4 - Local Client Creation.
2. SCCL – Local Client Copy
2. SCCL – Local Client Copy
3.
SCC9 - Remote Client Copy.
4. SCC5 – Delete Client
4. SCC5 – Delete Client
5.
SCC7 – Import
6. SCC8 – Export
6. SCC8 – Export
7.
SCC3 – To view Status of Copy
After creating
client using SCC4
Client - 101 User
– SAP* Pwd – PASS Then use
T-code SCCL & copy local client Note
- DDIC is super user in SAP.
setting up parameter value
Check parameters : T-code RZ10
select - instance profile
select - extended maintenance - change
parameter - browse - search by keyword (Login*)
parameter - login/noautomatic_user_sapstar - value 0
copy - back - copy - back - save - yes - copy - yes - tick - tick - yes - back.
To set client 101 by default in sap
c:\usr\sap\sys\profile change the value over here
CHANGE DOCUMENT
a) What data has been changed
setting up parameter value
Check parameters : T-code RZ10
select - instance profile
select - extended maintenance - change
parameter - browse - search by keyword (Login*)
parameter - login/noautomatic_user_sapstar - value 0
copy - back - copy - back - save - yes - copy - yes - tick - tick - yes - back.
To set client 101 by default in sap
c:\usr\sap\sys\profile change the value over here
CHANGE DOCUMENT
Business transactions in SAP are carried out
online by making use of standard documents such as Sales Orders, Purchase
Orders, and Vendor Invoices etc. Often the need arises for making changes to
these documents after they have been saved and created for the first time. It
is imperative that all such changes made must be recorded by the system.
If all changes are properly logged, we would be able to find out at any given
time for a particular document:
a) What data has been changed
b) When the change was made
c) Who made the change
Providing this kind of “trace mechanism” makes the
analysis of errors much easier and would enhance the robustness of the system.
1. log into the client to delete
2. go into SCC5 and delete client
3. log into another client and delete entry with SCC4
4. reorg database to recover database space.
Actually, if you check "on" the little "Delete Entry from T000" checkbox, you can skip step 3.
One other way of deleting a client which could give significant performance gain and save time is OS level using - R3trans
To delete a client 200, you have to create a command file "del200" with following entries
Clientremove
Client = 200
Select *
Place the command file in /usr/sap/trans/bin and execute with <SID>ADM user
$ cd /usr/sap/trans/bin
$ R3trans –w <log file name> -u 1 <command file name >
e.g $ R3trans -w del200.log -u 1 del200 or r3trans -w delete_SM7_200.log delete_SM7_200.ctl
To check the progress...
$ tail -f del200
Reorg the database post client delete.
# TO DELETE A SAP CLIENT
1. log into the client to delete
2. go into SCC5 and delete client
3. log into another client and delete entry with SCC4
4. reorg database to recover database space.
Actually, if you check "on" the little "Delete Entry from T000" checkbox, you can skip step 3.
One other way of deleting a client which could give significant performance gain and save time is OS level using - R3trans
To delete a client 200, you have to create a command file "del200" with following entries
Clientremove
Client = 200
Select *
Place the command file in /usr/sap/trans/bin and execute with <SID>ADM user
$ cd /usr/sap/trans/bin
$ R3trans –w <log file name> -u 1 <command file name >
e.g $ R3trans -w del200.log -u 1 del200 or r3trans -w delete_SM7_200.log delete_SM7_200.ctl
To check the progress...
$ tail -f del200
Reorg the database post client delete.
