Maintaining the CRMRFCPAR Table (SAP ECC) 
The parameters in this table indicate the RFC destinations which receive data. The required parameters include, for example: consumer, client, object name, and download type.
By making the appropriate specifications for the data exchange, you can send data to a certain consumer only in an initial download and not in a delta download.
Log on to the SAP ECC system.
Access the activity using one of the following navigation options:
Call transaction SM30.
In the SAP ERP menu, choose .
In the Table/view field, enter the table name CRMRFCPAR.
Choose Maintain.
Choose New Entries.
Note
If you choose New Entries and some of the fields are not maintainable, go back and choose Copy As….
Create the following parameter values:
Parameter name |
Description |
Recommended Parameter Value |
User |
User that uses the OLTP plug-in functions as data receivers |
CRM |
Object Name |
Object name |
* |
Destination |
Specifies the destination of the CRM server |
Erp_<SIDERP><CLIENTERP>_to_Crm_<SIDCRM><CLIENTCRM> (for example, Erp_ER1001_to_Crm_CR10)
The RFC destination name is case sensitive. End of the note. |
Load Type |
Restricts CRMRFCPAR entries to the initial (I) or delta (D) download. |
* All load types |
InQueue flag |
Controls whether qRFC inbound queues are used on the CRM server |
X |
Send XML |
XML supports (Should data be sent in XML format?) |
Mixed mode |
Stop data |
Causes the OLTP System to place data into the outbound queue. This field can be used to change the behavior of the queue. The HOLD_DATA field replaces the parameter RECORD_ASYNCHRONOUS_MESSAGE in the CRMPAROLTP table. Normally, the queue is processed automatically. If an X has been entered, the data is held in an outbound queue in the OLTP system. |
Save your entries.
Note
For some of the fields left blank here (for example, queue names, BAPI name, description), entries will be added automatically by the system when starting the download of objects at a later stage in the installation.
Note
Ensure that there is only one (the new) entry with Consumer CRM maintained in the CRMRFCPAR table. If not, delete other existing entries with CRM as Consumer. Otherwise, the download of sales documents ERP – CRM might not be successful.