Problem with initial download from R/3 to CRM

Question

Hello All,
Initial we were able to download & replicate all object from CRM to R/3  & vice versa such as product ,BP, sales documents & conditions etc. After that <<removed>> R/3 system was refreshed by Client itself. After refresh, connectivity between R/3 & CRM is disturbed.We have observed that while initial download we are facing problem in SMQ1 & SMQ2. After debugging we found that table entry  i.e. table :- CRMMLSGUID from CRM & CRMPRLS from R/3 have Logical system guid values different( which  should be identical). Because of this no replication is happening between CRM & R/3. How to rectify this?
Regards
Priyanka
Edited by: Rob Burbank on Dec 9, 2011 4:37 PM

Answer 1

Hello,
see note 588701:
"The queues are deliberately halted since the change of the logical       
system name in the R/3 backend or the linking of new R/3 backend clients 
to a client of the EBP/CRM Server with the same logical system name as a 
client already linked to the R/3 backend would lead to severe data       
inconsistencies in various CRM applications.                             
For this reason, such changes are not allowed on principle. The halting  
of the queues prevents such data inconsistencies. The following          
situations may lead to the queues being halted:                                                                               
o  The logical system of a client of an R/3 Backend system linked to 
       the EBP/CRM server was changed in current operation.                                                                               
o  A new client of an R/3 Backend system or a client of a new R/3    
       Backend system was linked to an existing client of the EBP/CRM    
       server where the logical system name was already assigned to a    
       client of an R/3 Backend system linked to the CRM server before.  
There are different cases in which different forms of processing are      
required or where several options exist:                                                                               
-  The logical system name of an R/3 Backend client was changed    
          in current operation. In this case, the data hangs in the       
          outbound queues of the R/3 Backend system as specified under    
          point 1 of the symptom. In this case, the logical system name   
                                                                 Seite 2                                                                               
must be changed back to the original value. Then the outbound   
          queues can be reactivated. If no data was transferred to the    
          EBP/CRM server before the change, also a correctioin of the     
          check table is possible.                                                                               
-  The same logical system name was used again in a new client of  
          an R/3 Backend system that was linked to the EBP/CRM server.    
          In this case, the data is in the inbound queue of the EBP/CRM   
          server with the exception GUID_FOR_LOGSYS_CHANGED. In this      
          case, the queue entries which have status SYSFAIL must be       
          rejected, however, not the entire queues. If the new client of  
          the R/3 Backend system you have linked has exactly the same     
          data as the old client and if it is meant to replace the old    
          client (that is, this was deactivated), also a correction of    
          the check tables is possible. In this case, the inbound queues  
          can be reactivated after the correction.                        
The correction of the corresponding check tables or the correct           
procecure in individual cases is to be agreed upon with the support of    
SAP or SAP consultants at the customer site. In justified cases, SAP can  
carry out the correction of the check tables.           "