Skip to Content

     Sometimes we don’t want the delta download (replication from ECC to CRM) to happen, what should we do?

  

     The mechnism that the delta download happens with is by BTE event. Specifically, it’s ECC table TBE31. Then how to know which entries are the relevant ones concerning the object I’m going to stop? You can check the transaction R3AC4 in CRM.

     For example, if you want to stop delta download of SD customers, the object class, the object class is BUPA.

r3ac4-1.JPG

Select ‘BUPA’, then select ‘Event by object class’ folder, under which you can see all the relevant BTE event function modules.

r3ac4-2.JPG

These function modules are the ones that appear in ECC table TBE31. When an initial download of customers has been done successfully, these entries will be filled in TBE31 table automatically. When you create or change a SD customer in ECC, these function modules will be called to transfer the customer to CRM

     So, to stop delta download, you can delete these FMs from TBE31. But sometimes it is not safe as these FMs can be added back by some programs in ECC. So to make sure the delta download doesn’t happen for ever, the safest way is to add an entry in ECC table CRMRFCPAR:

User                        CRM (the consumer)

Object Name           CUSTOMER_MAIN(the adapter object)

Destination              (the RFC destination pointing to CRM)

Load Type                 D (‘D’ stands for delta download)

Discard Data            X

By setting ‘discard data’ to X, you can ensure the delta download of CUSTOMER_MAIN is stopped.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply