How to open the client in SAP system?

This article answers the following queries:

How to open the client in SAP system?
How to view when was the client settings last changed?
How to view who has last changed the client settings?
What are the various client settings and their significance


Often in business scenarios, there will be requirements which cannot be transported and
which have to be modified directly in respective tables and other repository objects. To
perform these operations client to be opened.

Go to transaction SCC4. This lists clients overview as below:





From the above screen, we can make out what are the existing clients in the SAP system,
their names and the date they are last modified.

Double click on the client to be opened. It displays similar screen as below with the
complete client details like last changed date, last changed by, client role and associated
logical system of the client




In the above screen, we can see the highlighted option that no changes allowed and no
changes to repository and cross-client customizing objects. These 2 settings means that
client is NOT opened.

To open the client we should set the client settings as shown below for a client:




And Click on Save.


Finish.









Create Client

Go to SCC4 ---> Change Mode --- >Make an entry of new client.

After that configure STMS for that client and add it to the TMS rout.

Now go to BD54 and create logical client.



SCC4



Click on Change icon.



Click ok



then click on New Entries



Here enter a 3 digit client number, description, Currency, Client Role.


Now go to BD54 to make logical system.

SND For
Testing
275
Anything
INR
City


Click on new entries and enter logical client name here is SNDCLNT500

After this again go to SCC4 and enter the logical system name.




Finish.


Example of a screen-
<SID>CLNT<CLIENTNO>









Local Client Copy-
First Create a new client then
To perform the local client copy, first we need to login into the target client( i,e newly created
client)
Logging in to the new client :-
you may use the following credentials to login into the newly created client.
user = sap*
password = pass
If you are unsuccessful,
Then please change the parameter "login/no_automatic_user_sapstar" = 0 in default profile and try
logging in again with above credentials.
Enter transaction SCCL
The following screen appears


Choose SAP_ALL


Execute and Continue by pressing schedule job.

press continue.
Here you will get RFC error then create RFC through FINB_TR_DEST wizard.
Note-
This document is quite generic, for a ERP based system a client copy should include the creation
of and RFC for FINB_TR_DEST wizard and after creation RFC in that may one more is wizard is
appears there do the same for that also.
Check there is yellow button click on that to make RFC connection.
Once the copy is started, you can now check the logs in scc3

Note-
1. You need to monitor Log area continuously else Client copy will be failed once it is full.
Check in SLOG and ALOG file.
2. Also take care of Temp Table space if you are working in Oracle Database.









Remote Client Copy-

1. create the new client in the target system via tcode SCC4
2. log on to the target client of the target system with the user SAP* and password PASS
3. for the planned copy run, you must define the RFC connection between the R3 systems
as the source client, if this has not already been done.
4. you should also protect the source client of the source system against changes during
the copy. To do this, log on to the source system and lock the source client: In scc4 (
change mode ), choose the option " Currently locked Due to client Copy "
5. you can start the copy in the target system. Execute tcode SCC9
6. using the profile, choose the data to be copied
7. choose the RFC connection. The source system and client are chosen automatically for
the RFC connection.
8. before the actual copy, test the RFC connection using the RFC system check. In
addition to testing the connection, the R3 system releases are checked.
9. start the copy in background ( in test mode )
10. check the status of the copy procedure from the target system. You can do this at any
time by choosing Client Administration.tcode SCC3
11. start the copy in background ( in final mode )
12. check the status of the copy procedure...SCC3



Post processing steps in remote client copy-
Yes, there are post processing after client copy. You will have to first run transaction code BD54
In case of BI System(BDLS) to change the logical system name and adapt to the new system.
Apart from this you will have to carry out tasks like:
Check Tcode SICK
SE06: select database copy , and click on post installation processing after client copy
STMS (on client 000),check and recreate if necessary
SE38, run RSBTCDEL
RZ04 delete old instance schema and regenerate a new one
SM37, reschedule all non-system jobs / Delete if required
SM36 create jobs standers (Default scheduling) and suppress duplicate jobs / Using user DDIC
SCC4 (client from production to Test if necessary) and change role of the client to Test
RZ10 execute import profiles of active server and delete the production profiles
DB13: reorganize jobs if scheduled.

Check sm21, st22, sp01 for any errors and troubleshooting.







Remote Client copy process in BI-
*First off all assign enough space in target system as in source system.
*After that client period should be opened (SCC4)
*STMS must be configured 000 with super user (using STMS) in Source system.
*RFC connection (in target system define source system using sm59)
* In case of BI and BO system client copy -----> inactivate the entire cockpit by login through
another user id in the target system. TCODE- LBWE (Lo Data Extraction)
* Then SCC9 for Remote client copy
* First we have to do test run and then original
* Schedule background process
* Check this status in SCC3 tcode

Note If client copy processes is too slow or not responding then cancel the
process from SM50 and restart the server and again using SCC9 do client copy in
Restart Mode (option is there) it will resume from last stage.
If you did not restart the server then you cant run SCC9 for 2-3 hours because the
process which you canceled that is in waiting stage.


If in SCC3 status is showing Processing from long period of time then -
*Check the last table entry in SCC3
*Now check that table in DB20, enter table name and refresh.
*if process is not working then it will display table does not exist and if it is working then it will
show how much is inserting.
*Check the Tablespace size using DB02 according that if necessary then extends the tablespace.
*In order to extend the tablespace go to RUN or window key + R and type
telnet 142.147.101.30 and enter now you are on the HOSTAGE(On AIX command prompt ).
*Now login with ORASID and type BRTOOLS and choose option Space management.
*Suppose you want to extend 6 GB then enter 6144 (6*1024) on black screen.
*After complete this you can check the data file size using df -g Command.

*Now switch the user using su - sidadm command.
*And check using who am I command.

*Now Stop and Start SAP Server using STOPSAP and STARTSAP command.
*Now cancel the process and again does client copy by selecting restart mode option.
*If still some tables are not copying then cancel client copy and copy all table manually
From source to target system by making DB Link or whatever ways are there.









TCODE - LBWE (Lo Data Extraction)
Inactivate the entire cockpit by login through another user id then client copy in the target
system.



If you get errors in SCC3 as given below





Then Delete the setup tables using SIBW TCODE from Both Source and Client System. (This
should done by BI/BW USER)
To delete the setup tables
Go to T-Code SBIW and Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 Sales & Distribution) and Execute
And Delete the Outbound Queue using SMQ1 from source & target system OR
Best way to delete OUTBOUND QUEUE in bulk using Standard Sap Report RSTRFCQDS.
Before doing this I think restart the server.



Error and Solution-



Solution-
Activate all these 6 tables.