Client Export and Import
Adopting SAP System:
The System is setup but it needs to customize according to the requirements of the customer.
The Adoption is performed on development, tested on Quality and finally available in production
The objects will be developed, created, modified only on development system (system is set to modifiable).The other systems in the
landscape are set to not modifiable. (Except sandbox system but changes are not carried forward to any other system in the landscape)
Customizing
(No development takes Place) it is only Client Specific
It is the process of making entries into the tables without changing basic structure of the system.
Integration between Modules: The Data entered in table is automatically available to other related tables and modules. These changes are
recorded to Customizing Requests
Cross Client Customizing:
The Change made to the tables which are cross client. These changes are recorded to workbench change requests.
Customizing change requests are Specific to Client
Workbench change requests are specific to the System
Pre Requisites of Client Copy
Ensure that we have enough space in DB to perform client copy.
The size of the client is determined by using report RSTABLESIZE or RSSPACECHECK
These are executed in transaction SA38
Ensure that you have at least two background work processes in the system.
Perform client copy from target client only
Choose the profile to determine what data to copy during client copy. [By default we choose SAP-CUST]
Establish RFC connection with necessary authorizations during a remote client copy.
Ensure that you have enough space in usr/sap/trans directory during client export and import.
Perform a test client copy before starting the actual copy [it will check the resources that are required for client copy]
Schedule client copy always in the background mode. (So, that it will run when the screen is closed)
Client copy logs are available in SCC3 and monitor the progress using SM37, SM50 and SM66.
While performing remote client copy and client export and import ensure that the systems has same version and release.
While performing client copy ensure that users are not working on the system.
Always perform local and remote client copies from the target system only. [It is a pull mechanism, not a push mechanism]
Export & Import Method :
Pre- Checks:
Ensure that all users are locked except Euro-Administrators
While taking exports or doing import processing ORAARCH directory may get full
After copying data files, co-files , Need to provide proper permissions for files ( Read Write eg .664 & Group permissions)
Client export and import or client Transport:- It is used to perform the client copy between two systems which are not connected. [LAN,
WAN or MAN] It is used by customer to export the customizing templates.
Execute Transaction SCC8 in the target system.
Specify the profile
Specify the target system name and schedule it in the background.
Based on the profile ‘KO, KT, KX’ are generated. [K means control files]
Client export generates six types of files based on profile.
1 KO, R0: - are used to transport cross client data.
2 KT, RT: - are used to transport client specific data.
3 KX, RX: - are used to transport client specific text.
These files are generated in usr/sap/trans/cofiles and data files directories.
Copy these files in to target system usr/sap/trans
Execute Transaction STMS, Go to import overview.
Select the transport request
Specify the client. and import it into the target Client
Post processing of client copy:-
Go to ‘SCC7’ to perform the post processing of client copy.
SAP Note: 1537913 - Client Copy: Local & Remote copies, Client Export/Import and Client deletion
