SCC3 SAP TCode - Client Copy Log SAP TCode (Transaction Code) - SCC3 The SAP TCode SCC3 is used for the task: Client Copy Log. The TCode belongs to the STRM package. This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required). Search for additional results. Visit SAP Support Portal's SAP Notes and KBA Search.
Scc Sapphire
Source: SAP
This was an ASUG webcast given last month. It was a repeat of a session given at SAP TechEd Bangalore. Special thanks to SAP’s Carine Tchoutouo Djomo for arranging this for ASUG.
Abstract: The client copy tool has been renovated and will include multiple updates, starting with SAP NetWeaver Application Server for ABAP 7.54. Join us as our speakers dive into these renovations, including the SAP HANA-optimized local and remote client copy, client deletion, client export and import tool, client comparison tool, and client size estimation tool. (source: SAP)
Please note that this is about ABAP tools, not Java
Source: SAP
Not official roll out
If share information regard outlook, usual disclaimer applies
Source: SAP
Why revisit? Existing client copy tool existed for 20 years
Why revisit? Driver was S/4HANA Cloud and SAP HEC had similar requirements
Cloud has no system downtime, no server restart, reduce runtime of copy
Log is now written to a table, not a file
High coverage of test automation
Compare business configuration in 2 clients
Right shows KPI’s and constraints
Source: SAP
Logon to target client
New architecture – automate, box to the right lower column
Introduce tasks in task manager tool; strategic UI for all related processes, from client 0 copy is started
Transfer from one to another
Remote scenario – data pulled from another system
ABAP stack – pure movement of data process – could be done on a database
Application exits, domain executed code
Application excludes certain tables
Source: SAP
Timeline: started in 2017 Acdsee photo studio home 2020.
Decided to reimpliment tool
May 2019 in S/4HANA Multi tenant environment – new automation, productive use in cloud
In 1909 in September
Intend new tool as standard, plan to deprecate old tool
Source: SAP
New client copy tool comes with task list, and new log, an ALV-based table instead of log files
Back end transaction for tool and log
Completely reinvented
Source: SAP
Improved performance; new tool is 10 times faster than old
Remote copy is 5 times faster
Usability is improved
Do not need SAP* user
New stability – handle large database, and can split tables so it can run parallel
Source: SAP
Old tool: logon to target client
New tool – run in tool in client 000
Advantage is SAP* user is not needed
Source: SAP
Data remains in database layer
Data does not reach ABAP Layer
Source: SAP
New client import and export ool
New transactions, task list
Use SCC8N
Use SCC7N
Advantage is the offline client copy
Source: SAP
Scc3 Sap Login
New client comparison
Two modes – checksum — fast compare, less details
Detailed comparison for troubleshooting
Source: SAP
Calculation based on size of table in database divided by rows in client
Panorama maker 6 serial killer. Source: SAP
New log, ALV-based
New transaction – SCC3
Replay is here
Timestamps:
- About the Speakers- 1:50
- Agenda- 3:57
- Requirements from SAP S/4HANA Cloud- 4:48
- New Client Copy Architecture- 11:40
- Timeline- 14:31
- New Client Copy Tool- 17:24
- Execution from a Third Client- 20:58
- Improved Performance: Data Remains on Database Layer- 22:55
- Client Export/Import and Comparision- 24:29
- Client Size Determination and Copy Log- 27:46
- Demo- 30:00
Question & Answer:
Does this tool work with SAP SRM and SLM?
It is available with S/4HANA 1909 onwards only (and other SAP Products on same BASIS Stack)
What is the transaction to check this client copy log?
SCC3 (same as before, it checks if copy was made with new tool, then new log is shown)
What will happen when we don’t select option “Lock source client” while doing local client copy. Can we anticipate wait time?
source system has 100K database tables – worst case could lead to inconsistent tables
How does the Client export works for Huge databases for eg 5 tb to be used for system refresh Prod to QA.How efficient is it now compared to before?
client export – no change for large db tables; client export works on transport request
Step by Step Procedure to create a copy of a client locally in the same SAP server.
1.Logon to SAP server
2.Use Transaction Code SCC4
3.Go to change mode
4.Create a new client, assign client number & description as per request
5.Logoff from current client.
6.Login to newly created client using the following credentials :
i.Client Number : Newly created one
ii.User Id : SAP*
iii.Password : PASS
7.Use Transaction Code SCCL for local client copy
8.Give reference client for copy and profile as per the request
9.Use SCC3 Transaction code to monitor progress of Client Copy.
Golden rules for CLIENT Copies
1. Master data can not be copied without copying transactional data and transactional data can not be copied without copying master data.
2. Application data (transactional and master) should not be copied without copying configuration data.
3. Client copy requires a valid client as the destination client. Make sure that the client exists in T000 table and you can logon to that client.
Scu3 Sap Tcode
4. The transport system and the transport management system of 4.0 are the only proper tool to be use to keep multiple systems in sync by transporting development and customizing changes to another instance.
5. When you copy a client from one system to another, client-independent tables should only be copied if they are not yet modified in the target system.
Scu3 Sap
6. We recommend the users to read all the OSS notes regarding client copy that applies to their SAP release. It is always better to schedule the client copy job in the background for the night run when normal work is not taking place.
7. Always check the database space before performing a client copy.
8. To avoid data inconsistencies all the users working in the source and target clients should logoff from the system.
9. RSCLICHK program should be run in the target system remotely before doing a client export. This program will give information about the missing definitions from the data dictionary in the target. After executing this program and getting successful results you can ensure that the client copy will have no problems. In case some tables are different; you can use SE11 to compare and adjust the table structure in both the system before the client copy. A remote test client copy also can be executed to know the differences between source client and target client.
Sap Scc3 Post Processing Required
10. If you are not in release 2.2 then do not use R3trans to copy a client.