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

Replication from R3 to CRM

I want to pull master data(Customer ) from R3 to CRM

We are using CRM 4.0 .

I tried through IDoc but the Message type DEBCOR is not available in CRM .Is there any similar message type which we can use in place of DEBCOR or any other approach .

Awaiting for response .

Edited by: Sunil Nair on Jan 15, 2008 2:02 PM

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 15, 2008 at 04:26 PM

    Hi Sunil,

    I guess you are using the CRM Middleware component to realize master data replication from R/3 to CRM, correct?

    First of all you need to use transaction code PIDE in R/3 to define mapping between R/3 account groups and CRM BP classifications. Without defining this, your R/3 customer will not be ablel to come into CRM.

    Once the above step is done, log into CRM system and go to transaction code R3AS - Initial Load of data from R/3. You select object name BUPA_MAIN. This is how you load R/3 customer into CRM.

    Reward points if the tip helps.

    Regards,

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 16, 2008 at 12:05 AM

    C71:CRM connectivity is the best document to refer before replicating master data from ECC.

    You can find the Building Block Library [here|http://help.sap.com/bp_crmv340/CRM_DE/BBLibrary/html/BBLibrary.htm]

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 16, 2008 at 12:08 AM

    .

    Edited by: Praveen Rangineni on Jan 16, 2008 1:08 AM

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 16, 2008 at 06:04 AM

    Hello Sunil,

    In the R/3 side go to SM30, CRMCONSUM must be active CONSUMER: CRM ACTIVE: X TEXT: CRM

    2)The table CRMRFCPAR must contain RFC destination of CRM Server.

    3)Make sure that the event control is active in the R/3 OLTP system, in the TBE11 table.

    go to SM30.

    4)Table TBE31 contains the subscribed event modules for individual business objects. You must carry out the check from the CRM server

    5)The status of the outbound queue is WAITUPDA or the status text reads "Transaction recorded (LUW with update records)"

    6) If the status of the queue is 'NOSENDS', the sending of the data was blocked inadvertently. This should never be set during live operation.

    CRM Server.

    1)Set filters in R3AC1

    2)Check if the filter conditions entered in Transaction R3AC1 were transferred to the CRMFILTAB table in the R/3 Backend system correctly

    3)Check the ques for Delta Download(SMWP)

    4)You can use Transaction SMW01 to examine error messages of the CRM application

    5)Transaction SMWT: Middleware Trace with environment 'D': Display of additional information for transferred delta data

    6)Transaction R3AC4 (Object class activation): Check whether the event for the object is activated

    7)Make sure that the scheduler is registered in the CRM server for processing the R/3 OLTP queue .

    (tcode SMQR)

    Hope this helps.

    Please assign points.

    regards,

    Muralidhar Prasad Chatna

    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.