Copy Client Sap
You are doing SAP Client Copy and want to see the progress. You do it from Tools - Administration - Administration - Client Administration - Copy Logs or Transaction Code SCC3. Check SAP Client Copy Logs. The report RSCCEXPT is the advanced configuration of SAP client copy.Roughly, the report enable you to activate special client copy copy options and exclude tables from the copy.You can get the page settings from transaction code SE38 or SCC9 / SCCL (from the top menu, go to Edit Expert Settings). 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. 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. Using SAP SCC1 client copy transaction to copy data between clients is not rocket science so i will be quick. First login to the client you want the data to be copied into. Maybe you have made some changes in client 100 which are now in a transport and now you also want the changes in client 200. Therefore log into the target client 200.
Last year from S/4 1909 SAP released a few client administration transaction codes, SCCLN is one of them. The major advantage of this transaction is speed and security, I will explain both of these terms below.
Speed - This transaction is super fast to copy a client within the system, for example, to copy a 200GB client it took almost 40 to 45 minutes with 5 parallel processes.
Disclaimer - copy duration may vary based on hardware configuration, I had moderate configuration so it took me that much of time.
Security - Normally to perform a local client copy we need to enable SAP* and if we forget to disable it after client copy this will be a big threat to the business system if network security is not tightened. SCCLN removes this worry and now we don't need to enable SAP* to perform the copy because SCCLN will be executed from the source client not target like traditional process.
High-level steps to use SCCLN on S/4 1909 onwards.
- Log in to the source client.
- Create a target client in SCC4
- Create logical system name in BD54 and assign it to the newly created client - Mandatory step for SCCLN
- Execute SCCLN, provide the source and target client, and required profile like SAP_ALL, SAP_CUST, etc.
- Choose other processing settings like lock source client, use exclusive locks, etc. also provide parallel processes based on server configuration.
- Click on Direct Execution.
Symptom
Customer often encounter various problems during client copy, and client copy performance issue may be the biggest headache.
SAP product support team can receive kinds of incidents about performance issues, for example,
why client import time is much longer than client export time?
it took 30 hours to finish client copy last year, but it took 50 hours for the same client this year, why?
client copy seems hang, how can I see if it's still running?
....
We will introduce client copy related information/KBA/notes here to give you a clear picture about it.
Besides, we also collected some well-known errors during client copy which may help you avoid such problems during client copy.
Read more...
Environment
Keywords
Client Copy performance, slow, PSAPUNDO, PSAPTEMP, client size, size of client, tablespace, parallel process, HANA, Sybase, Oracle, MSS, SCC3, SCC4, SCC5, SCC7, SCC8, SCC9, SCCL, client transport, SM50, DIR_TRANS, DDIC error, RBDLSMAP, compute_overflow, CX_SY_CONVERSION_OVERFLOW, CONVT_OVERFLOW, Source client, MESSAGE_TYPE_UNKNOWN, RC: 10, not exist in nametab, Double Key table , KBA , BC-CTS-CCO , Client Copy (For ByD issues select BC-TLM-CP) , Problem
Sap Client Copy Tcode
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).Sap Scc9
Search for additional results
Client Copy Sap_appl
Visit SAP Support Portal's SAP Notes and KBA Search.