Solution : https://service.sap.com/sap/support/notes/339721 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues related to missing long texts in the target client after client copy operations. It details prerequisites such as the necessity of identical code pages between source and target systems for separate text copies. The document outlines using R3trans and control files to transport text tables like STXH and STXL, with a recommendation to run the RCTXTCPY report post-transfer to mitigate losses in newly created texts. It emphasizes caution when transporting tables from client '000', advising this only in specific identical configurations, and reminds to follow proper post-processing steps with transaction SCC7 to finalize text migration.
Key words :
client copy/client transport, terms sapscript reason, text copying phase, complete text tables, including support packages, symptom long texts, client transport, client copy, support package, pstxb tables
Related Notes :
| 601196 | Client copy: Problems with report RCTXTCPY |
| 589886 | CC-ERROR: Performance with the remote SAPscript copying |
| 567573 | Client transport of forms |
| 511042 | Obsolete forms after upgrade/Support Package |
| 338578 | CC-TOPIC: Error in client transport as of 4.5 |
| 315837 | CC-ERROR: Texts are missing after RESTART |
| 206523 | CC-RELEASE: Client copy errors in 4.6C and 4.6D |
| 180541 | CC-INFO: Performance problem when copying text |
| 96732 | CC-INFO: DB2/390 - client copy is very slow |
| 68896 | R3trans: Performance problems and cluster |
| 42770 | missing long texts after client copy |
| 20497 | CC-INFO: Long texts with a client copy |