You are on page 1of 1


Transaction SMWT: Middleware Trace with environment 'D': Display of additional

information for transferred delta data.
12. Transaction R3AC4 (Object class activation): Check whether the event for the
object is activated. If the event is not active (for example, because an initial load did
not occur for sales documents), you must manually activate the missing entry.
Usually, events are activated in table TBE31 in the R/3 BACKEND System by the
start of the initial downloads. If, however, events are not entered in the R/3
BACKEND System due to a system change, you can manually activate the entry by
switching to change mode in Transaction R3AC4 and saving again. Only those events
which are relevant for the respective application must be active, for example
MATERIAL for EBP. However, refer to the note in point 4 below.
13. Make sure that the scheduler is registered in the CRM server for processing the
R/3 OLTP queue (Transaction SMQR: An entry must exist for queue names R3A*).
In Transaction SMQR, more queues may be deregistered for test purposes (for
example R3AD* for delta queues) - this overrules the basic R3A* registration.
14. Check whether filter entries exist for the object. For this purpose, start Transaction
R3AC1 (business objects), R3AC3 (Customizing objects) or R3AC5 (condition
objects and condition Customizing) and select the corresponding object. In
Transaction R3AC1, choose 'Filter settings'. If necessary, delete unwanted filters
(when you save, the filter modules are automatically regenerated and the filters are
transferred to the OLTP system). Ensure that you enter filter criteria with leading
characters, for example 10-digit for customer number, 18-digit with leading zeros for
material number.
Note: Filters that are defined in the CRM System must be defined in the form in
which the data is stored in the source system in the database. For example, the filter
for date 20010215 corresponds to a filter for February 15, 2001 (profile