Skip to Content
author's profile photo Former Member
Former Member

How to stop the replication of contact person from ECC to CRM

Hello,

I am facing one issue. I have download Customer (one particular group) from ECC. I have configure every thing and everything looks good and its working in Production. Now all the customer assigned to that group are replicated to CRM.

But in delta download, contact persons are also coming with a relation ship has contact person. But we don;t require these contact persons as we separately maintained the contact person.

For your reference, while doing the initial download I have downloaded the customizing objects,

DNL_CUST_TSAB

DNL_CUST_TPFK

COSTOMER_MAIN

But I didn't downloaded the relationship object CUSTOMER_REL. But still relationship are coming.

Is there any way to to stop the replication of relationship coming from ECC.

Thank you all in advance.

Regards

Subhankar

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Sep 13, 2011 at 12:04 PM

    Hi Subhankar

    Unles syou are using an IS system, you should normally use a filter on object CUSTOMER_REL rather than BUPA_REL.

    If you completely deactivate CUSTOMER_REL object in R3AC1 in CRM, no

    relationship will flow from R/3 to CRM (even other partner functions

    that you may need will not be replicated). You can also use the setting DISCARDDAT = X in ECCtable CRMRFCPAR to deactivate queue creation for the object, as described in note 482444. Thissettings will be client-specific.

    If it's only contacts you wish to stop, and not other relationships, I would recommend normally recommend using the fitler setting- ie KNVK-PARNR = 0. However, I worked on a recent issue where this filter didn't work.

    In htat case, development explained that KNVK-PARNR filter is not considered during the replication. So you can

    actually register the User Exit in the table TBE34 for the event DE_EIOUT. In this place you can check in LT_MAIN_EXTERN and LT_REL_EXTERN to find out whether the category BUR001 is transferred.

    If yes you can totally delete the Extern structure which will not be

    replicated further to the CRM system. You can check the sample coding

    for the same in note 638628. This note refers to data transfer from CRM to ECC.

    You would need to adapt the coding in your own user ext.

    You can create a User Exit which checks for the

    category and deletes the entire extern data. This should be present in

    ERP system.

    You have to maintain the product name and its description in the table

    TBE24 and you have to maintain same product name in TBE34. I am giving

    sample entries here:

    TBE24:

    PRDKT - CONREP

    TXT50 - Stop Contact person replication

    AKTIV - X

    TBE34:

    EVENT - DE_EIOUT

    PRDKT - CONREP

    LAND - FI (Country ISO Code)

    APPLK - BC-MID

    FUNCT - Z Function Module name.

    This the information you need to fill in. Once you have written

    your Z code to remove the information, register it here so that it is

    called in the outbound and the data is removed which is not sent to the

    CRM system. If you have issues with this, I could e-mail some sample coding that worked for another customer, but you would have to test this yourself in your testing/dev scenario.

    Hope this helps.

    Brian.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 13, 2011 at 05:06 AM

    In R3AC1 set filter for object BUPA_REL.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.