> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/sid-refresh/troubleshooting/crm-middleware-configuration.md).

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itconductor.com/user-guide/sid-refresh/troubleshooting/crm-middleware-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.