CRM server

7. Check the set filters for the corresponding object. You can check them in
Transaction R3AC1. Data which does not correspond to the filter conditions is not
transferred.
8. Check if the filter conditions entered in Transaction R3AC1 were transferred to the
CRMFILTAB table in the R/3 Backend system correctly. If this is not the case (for
example, because of a malfunction of the RFC connection to the R/3 Backend system
during the last change of the filter conditions), transfer the filter conditions again by
clicking the pushbutton for the filter synchronization.
9. You can check the queues for the delta download as follows: Basically you can use
Transaction SMWP (CRM Middleware Portal) in the CRM System to check the
queues for the delta data from the R/3 OLTP to the CRM System. Select menu option
'Middleware Portal' -> 'Runtime Information' -> 'R/3 Adapter Status Information' ->
'Delta Download and Upload Status'. Look at the following menu options there:
a) Menu option 'Outbound Queues in R/3 OLTP System': The queues named
R3AD* exist for several reasons:

o They have error status 'SYSFAIL'. This is only the case if there is a technical
problem with the receiving system (for example, a database problem on queue
tables QRFC*, ARFC*). The problem must be corrected on the CRM server,
and then you can restart the queue. Generally, a short dump is then displayed
on the target system, which provides more detailed information on the cause
of error.

o They have error status 'CPICERR': This is the case if there is no network link
to the target system. After you reestablish the link, the queues are started
automatically. It is also possible that you maintained the RFC connection
incorrectly in Transaction SM59 (for example, link does not exist, or incorrect
IP address, system number, user, password, client of the CRM target system).

o They have status 'STOP': In general, this is not an error. In this case, check
whether the initial load for the object or its child object is still running. During
this time, the delta queues are locked to prevent the transfer of newer delta
data until the completion of the initial load. In this case you must wait until the
initial load is complete, afterwards the system automatically removes the
STOP entries. For test purposes you can force the manual start of the delta
queues with a potential loss of the data consistency by deleting lock entries
R3AD_<object name>* in Transaction SMQ1 in the R/3 BACKEND System.
For the analysis of errors in the initial load, refer to Note 429423.