Problem with Business partner flow from R/3 to CRM

Question

Hi,
We are setting up a process to flow of Business Partners from R/3 to CRM. 
We have configured PIDE correctly but the problem is when I am creating any customer in R/3 we are getting DUMP.  
Kindly help me in this regards.
Thanks

Answer 1

Hi,
Check out the following Middleware Configuration :
     <b>CRM Middleware configurations</b>     
1.     Source client for Client copy
     Using t-code SCC3 in both CRM and ISU to get the source client used for client copy.      Get source client for profile SAP_ALL.
2.     RFC Destinations
     Use t-code SM59 and check if the following RFC destinations have been created:
•     CRM
o     R/3 Destination for CRM e.g. CRTCLNT240
o     R/3 Destination for ISU e.g. ISTCLNT240
o     Logical Destination for Middleware R&R queues – one for current client and one for client 000.                                                                            e.g. SAPCRM_MW_RR_240, SAPCRM_MW_RR_000     
o     TCP/IP Destination for IPC dispatcher e.g. IPC_RFC_DISPATCHER
o     TCP/IP Destination for IPC server e.g. IPC_RFC_SERVER
•     ISU
o     R/3 Destination for CRM e.g. CRTCLNT240
o     R/3 Destination for ISU e.g. ISTCLNT240
3.     Logical Systems
     Using t-code SALE check if the following logical systems have been created:
•     CRM
o     Own logical system – e.g. CRTCLNT240
o     Logical system for ISU – e.g. ISTCLNT240
o     Logical system for source client used in client copy – e.g. CRTCLNT200
•     ISU
o     Own logical system – e.g. ISTCLNT240
o     Logical system for CRM – e.g. CRTCLNT240
o     Logical system for source client used in client copy – e.g. ISTCLNT200
     Check if own logical system is assigned to the client.
     Path: Sending and Receiving systems -> Logical Systems -> Assign Client to Logical      System.
     Convert Logical System name in application tables
     Use t-code BDLS to convert logical system names in the application system.     
1.     Enter old logical system name retrieved in step 1. e.g. CRTCLNT200
2.     Enter new logical system name e.g. CRTCLNT240.
3.     Select radio button Conversion of Client-Dependent Tables and execute the transaction.
This process needs to be carried out 4 times: twice in CRM and twice in ISU.
•     CRM
o     Old CRM logical system -> New CRM logical system. e.g. CRTCLNT200 -> CRTCLNT240.
o     Old ISU logical system -> New ISU logical system. e.g. ISTCLNT200 -> ISTCLNT240.
•     ISU
o     Old CRM logical system -> New CRM logical system. e.g. CRTCLNT200 -> CRTCLNT240.
o     Old ISU logical system -> New ISU logical system. e.g. ISTCLNT200 -> ISTCLNT240.
4.     Middleware Parameter tables
     Use t-code SM30 to maintain middleware parameters in following tables
•     CRM
o     Table SMOFPARSFA:
     Change value for following parameter entry:
     Key - R3A_COMMON
     Para name - CRM_DEFAULT_DESTINATION
     Value - Old ISU logical system -> new ISU logical system
          E.g. ISTCLNT200 -> ISTCLNT240     
•     ISU
o     Table CRMRFCPAR:
     Delete the previous entry for the following key:
     User - CRM
     Object name - *
     RFC Destination - Old RFC destination for CRM e.g. CRTCLNT200.
     Load types - All Load Types
     Create new entry with following data:
     User - CRM
     Object name - *
     RFC Destination - New RFC destination for CRM e.g. CRTCLNT240.
     Load types - All Load Types
     In Queue flag - X
     Send XML – No XML
o     Table CRMPAROLTP:
     Change value for following parameter entry:
     Para name - CRM_DEFAULT_DESTINATION
     User - CRM
     Value - Old CRM logical system -> new CRM logical system
          E.g. CRTCLNT200 -> CRTCLNT240
5.     Admin Console (Sites and subscriptions)
     Using t-code SMOEAC in CRM change attributes for the following sites.
•     CRM site
o     Name: Change name from old CRM logical system -> new CRM logical system e.g. CRTCLNT200 -> CRTCLNT240
o     Description: Change description from old CRM logical system -> new CRM logical system e.g. CRTCLNT200 -> CRTCLNT240
o     Site attributes: Change RFC destination from old CRM RFC destination to new CRM RFC destination e.g. CRTCLNT200 -> CRTCLNT240
o     Click on get values button to refresh logical system details.
•     ISU site
o     Name: Change name from old ISU logical system -> new ISU logical system e.g. ISTCLNT200 -> ISTCLNT240
o     Description: Change description from old ISU logical system -> new ISU logical system e.g. ISTCLNT200 -> ISTCLNT240
o     Site attributes: Change RFC destination from old ISU RFC destination to new ISU RFC destination e.g. ISTCLNT200 -> ISTCLNT240
o     Click on get values button to refresh logical system details.
     Check if ISU site is assigned to following subscriptions.          
•     All Business Agreements (MESG)
•     All Business Partner Relationship (MESG)
•     All Business Partners (MESG)
•     All Business Transactions
•     IS-U Connection Objects (MESG)
•     IS-U Contracts (MESG)
•     IS-U Points of Delivery (MESG)
•     Product Materials (MESG)
6.     CRM Middleware Queues
     Inbound Queues:
I.     Execute transaction SMQR.
II.     Change AS group from ‘DEFAULT’ to ‘parallel generators’.                Path: Edit -> Change AS Group
III.     Register following queues:
•     CRM     
o     CSA*
o     R3A*
•     ISU
o     R3A*     
Outbound Queues:
I.     Execute transaction SMQS.
II.     Change AS group from ‘DEFAULT’ to ‘parallel generators’.                Path: Edit -> Change AS Group
III.     Register following queues:
•     CRM     
o     CSA*
o     R3A*
•     ISU
o     R3A*     
R&R Queues:
I.     Execute transaction SMOHQUEUE in CRM.
II.     Check if all queues have status ‘Released’.
III.     Start Queue Demon by clicking on ‘Start Queue Demon’.
<b>Please reward points if it helps.</b>
Regards,
Amit Mishra