Middleware mandatory settings

R/3 OLTP

1. The CRMCONSUM table must contain the consumer application, which is

generally CRM. Use Transaction SM30 to enter the CRMCONSUM entry. The
message "Choose the key from the allowed name space" is normal. Confirm the
message and save the entry if it does not already exist.

CONSUMER: CRM

ACTIVE: X

TEXT: CRM

2. Table CRMRFCPAR must contain the RFC destination of the CRM server. Check
the following parameters in table CRMRFCPAR (example for CRM, other entries are
necessary for other applications-such as IPC):

CONSUMER: CRM

OBJNAME: *

RFCDEST: (customer-specific: destination CRM server)

DOWNLOAD: *

INACTIVE: blank

DISCARDDAT: blank

USE_IN_Q: X

XML SEND: X

HOLD_DATA: blank

USE_IN_Q: X

3. Make sure that the event control is active in the R/3 OLTP system, in the TBE11
table. Although the event control is delivered in the activated status, it may have been
deactivated in your system for test purposes. If this is the case, you must activate the
entry both for application indicator BC-MID and NDI. To do this, start Transaction
SE16 (Release 3.x) or Transaction SM30 (Release 4.x), with the TBE11 table. Set the
'Active' flag for BC-MID and NDI.
4. Table TBE31 contains the subscribed event modules for individual business
objects. You must carry out the check from the CRM server (see below).
 Note: For certain data objects, TBE31 entries are not required/entered because the
delta supply from the OLTP for these objects is carried out using BADIs. If you have
problems activating the delta data, refer to the respective application component.

5. The status of the outbound queue is WAITUPDA or the status text reads "Transaction
recorded (LUW with update records)": This problem can only occur if an update termination
occured previously. A solution for this problem can only be provided by the respective
application component in which the update terminated. If it is not clear in