The most important CRM-specific issues that must be considered when performing a client copy within a CRM landscape are described below. If any additional problems arise, please open an OSS message for further assistance. Please bear in mind that any customer-specific requirements that do not correspond to the standard scenario described below may be considered a matter for consulting, in which case we advise that you obtain the services of an onsite consultant.
1. The client copy tools are delivered as part of the standard R3 Basis functionality. In addition to the steps described in this note, please ensure you have read all relevant client copy documentation provided by the Basis team and that all corresponding pre- and post-processing steps are followed.
2.When a client copy is performed within a CRM landscpae, SAP recommends that ALL systems within the landscape are copied. This is easiest for maintaining data consistency.
3. After the client copy has been performed, the newly-created clients usually have different logical system names from the source clients; but tables containing the logsys field still refer to the old value. Because of this, it is necessary to run BDLS 3 time in total.
(i) Once on the R3 Backend system, in order to convert the logsys entry from the old value to the new one in all relevant tables.
(ii) A further time on the CRM to convert all corresponding table entries from the old CRM logical system value to the new one.
(iii) Additionally, there are tables on the CRM which refer to the
logical system value of the R3; for this reason it is necessary to run BDLS a second time on the CRM, in order to convert entries from the old R3 Logical System value to the new one in these tables.
4. Table CRMRFCPAR must be modified on the R3 Backend system so that it points to the correct destination. This destination must also be created or updated in SM59 of the R3 Backend.
5. On the CRM Server, the destination of the newly-created R3 Backend must be maintained,
6. Site IDs are copied when profiles SAP_APPL and SAP_ALL are used. This is correct, since these profiles are used to copy all application data.
In release 3.0, the Site IDs are also copied when profiles SAP_CUST, SAP_UCUS, SAP_CUSV and SAP_UCS are used. This should not occur, since these profiles are not used to copy application data. For an explanation of why this problem occurs, along with the solution to it. This problem has been corrected in subsequent releases.