During data replication between ECC and CRM, the archived BPs or customers are not automatically filtered. So you would have to implicitly set the filter to achieve this.

1. If you want to set filters for object BUPA_MAIN in R3AC1, you could perform the following steps:

     1> Run T-code SM30, enter table name SMOFFILFLD.

     2> Create entry as follows. That is because that table SMOFFILFLD is the controlling table for allowed filter fields. In the standard only the mentioned table/field names are provided but you are able to add more as you see fit.

     3> Run T-code R3AC1, click on tab "Filter settings", add filter for object BUPA_MAIN:

This part has been pointed in my KBA 2163871 - How to set up filters for archived BP for object BUPA_MAIN

2. If you want to set filters for object CUSTOMER_MAIN in R3AC1, you could perform the following steps:

     1> Go to Tcode R3AC1 of CRM system.

     2> Choose object CUSTOMER_MAIN and click on the "Filter settings" tab.

     3> Add the filter as KNA1-LOEVM unequal to "X".

This part has been pointed in my KBA 2336339 - How to set up filters for archived Customer for object CUSTOMER_MAIN

3. If you want to set filters in SMOEAC for archived BP, you could add the filters as below:

Regarding how to generate filters in SMOEAC, you could refer to the KBA 1834681.

Here I also want to remind you the difference of the filters in R3AC1 and SMOEAC:

- Filters maintained in R3AC1 works for the following scenario:

>> Initial load of objects, both in the direction of ECC to CRM and from CRM to ECC.

>> Delta load from ECC to CRM.

- Filters maintained in SMOEAC works for the following scenario:

>> Upload from CRM to ECC.

Hope this blog could help you.

In my previous blog "How to debug the transfer flow for the replication between CRM and ECC", I summarized how to debug the transfer flow in general including which queue you need to stop. In this blog, I will take the delta load for customer as an example to introduce the detailed steps to debug the download process and the involved function modules.

1. Run tcode XD02, and perform change to trigger the delta load. In my case, I change the name of my customer. Then put /h to activate the debugger, and press save.

2. PI_BP_CUSTOMER_BTE_1321: For customer delta load, the transaction event 1321 is raised. This function module can be found in table TBE31 for object BC-MID and event 1321.

3. PI_BP_MAP_CUST_TO_BUPA: This function module mapped the complex structure data into the BAPIMTCS structure. You could check the local table LT_MAIN_EXTERN (for central data) and LT_REL_EXTERN (for relationship) for complex structure data.

4. PI_BP_REL_TO_BAPIMTCS/PI_BP_REL_TO_BAPIMTCS: convert the complex data into the BAPIMTCS structure.

5. CRS_SEND_TO_SERVER: This function module send the BAPIMTCS structure into the middleware.

• It calls function module CRM_FILTER_DOWNLOAD_DATA to do filter as per the setting in R3AC1 of CRM system.
• It determines the RFC destination as per the setting in table CRMRFCPAR.
• It determines the queue name as R3AD_CUSTOME* as per the setting in table CRMQNAMES.

You could stop the CRM inbound queue in SMQR to debug the CRM side. Here I stop the queue with name R3AD_CUSTOME*. Then the queue stops in SMQ2.

6. BAPI_CRM_SAVE: The qRFC calls function module BAPI_CRM_SAVE.

7. BUPA_MWX_BDOC_DOWNLOAD_R3A: The XML data is transferred to application. The bdoc is created here. This function module can be checked in tab “Mapping modules: R/3 to CRM” in Tcode R3AC1 for the corresponding object. After creation of the bdoc, it is handed over to MW flow again.

8. CRM_BUPA_BAPIMTCS_TO_MAIN / CRM_BUPA_BAPIMTCS_TO_REL: unpack the BAPIMTCS structure to the complex structure.

9. CRM_BUPA_MAIN_VAL/ CRM_BUPA_REL_VAL: validation function module. This can be checked in table SMW3BDOCIF of CRM system. The modules BUPA_MWX_BDOC_MAP_MAIN and BUPA_MWX_BDOC_MAP_REL are called for processing.

If you are facing the validation bdoc error, you could debug from here. Please read my blog "How to deal with the E04 bdoc errors?" for more details.

10. BUPA_INBOUND_MAP_MAIN/BUPA_INBOUND_MAP_REL: call the function module with event CRMIN in table CRMC_BUT_CALL_FU.

11. BAPI_TRANSACTION_COMMIT/BAPI_TRANSACTION_ROLLBACK: If no error occurred, the MW performs a commit work, otherwise a ROLLBACK.

12. Afterwards, the BP outbound processing creates a new BDoc (notification bdoc), triggered by BADIs that have been registered during the BAPI calls.

13. In the end, there are two bdocs (validation and notification) generated at the same time for the customer delta load.