# Component CRM\_MIDDLEWA\_CRM - CRM Middleware Configuration

### Symptom <a href="#componentcrm_middlewa_crm-crmmiddlewareconfiguration-symptom" id="componentcrm_middlewa_crm-crmmiddlewareconfiguration-symptom"></a>

* After System Landscape Copy is performed in a CRM landscape, the SITE ID values in CRMM\_BUT\_CRMOBJ and SMOHSITEID do not match.
* When business partner changes are loaded from CRM to ECC, the system sends a full update rather than just a modification, even though the BP exists on both systems.

### Environment <a href="#componentcrm_middlewa_crm-crmmiddlewareconfiguration-environment" id="componentcrm_middlewa_crm-crmmiddlewareconfiguration-environment"></a>

* SAP Customer Relationship Management (CRM)
* SAP enhancement package for SAP CRM
* SAP enhancement package for SAP CRM, version for SAP HANA

### Cause <a href="#componentcrm_middlewa_crm-crmmiddlewareconfiguration-cause" id="componentcrm_middlewa_crm-crmmiddlewareconfiguration-cause"></a>

* SID-Refresh™-1.4.0 includes table SMOHSITEID among the list of tables to be exported and imported. If the target systems of the system copy use different GUID values than the source system, there will be a mismatch between tables CRMM\_BUT\_CRMOBJ and SMOHSITEID. As a result, when subsequent loads of Business Partner data changes are sent to the ECC, all the BP data will be sent instead of just the field that has been modified. This is because FM "BUPA\_OUTBOUND\_GET\_MAIN checks the state of a BP by comparing the values in CRMM\_BUT\_CRMOBJ and SMOHSITEID. This will not lead to data inconsistency but may cause an unnecessary overhead due to the extra volume of data being sent.

### Resolution <a href="#componentcrm_middlewa_crm-crmmiddlewareconfiguration-resolution" id="componentcrm_middlewa_crm-crmmiddlewareconfiguration-resolution"></a>

* Do not select table SMOHSITEID for export and import during system copy unless it is intended that the target systems use the same site ID values as the source systems.