Diagnosis
The client copy has been cancelled.
System Response
This can be because:
1. The program was stopped by a user.
2. The program terminated due to an error in an application EXIT module.
3. The SAP System has been shut down.
4. An inconsistency occurred in the database with the Data Dictionary (DDIC) of the SAP System (Nametab or table definitions).
5. You received an ABAP database inconsistency error message.
6. You get an ABAP dump, e.g. with error cause timeout.
Procedure
To solve the problem, you must first identify the cause, as follows:
1. The Client Copy Log (transaction SCC3) tells you where the error occurred, i.e. the last phase processed and the last exit program (for phase N?) or the last table processed (for phase C?). The associated file log often contains further information.
2. If the copy was scheduled in the background, analyze the job log and any background job (transaction SM37) spool.
3. If the program was cancelled before the reason for the cancellation could be logged, check the SysLog (transaction SM21) and the Runtime Analysis (transaction ST22). If it is a remote copy, check the SysLog in the source system.
4. For table definition (DDIC) problems, check the table with the Database Utility (transaction SE14).
If the error occurred in an exit program or application function module, you can get the application component of the exit from the log (either directly in the overview page, or under Details -> Exit Program). Search for a note in the note system with the name of the application exit. When you have resolved the error, you can continue the copy, in restart mode if the copy phase had already been reached.
