Checking CRMRFCPAR

Use

The parameter file CRMRFCPAR is the RFC parameter file on the ERP back-end side.

The RFC destination is linked to an application.

To this end, the parameter file CRMRFCPAR contains the parameter CONSUMER. This parameter must be defined in table CRMCONSUM.

Procedure

To edit or check table CRMRFCPAR, choose Start of the navigation pathSystem Next navigation step Services Next navigation step Table Maintenance Next navigation step Extended Table MaintenanceEnd of the navigation path.

Table CRMRFCPAR contains the following parameters:

Parameter

Value

CONSUMER

Consumer that uses the CRM plug-in functions as a data recipient (for example, CRM)

OBJNAME

Object name, standard value: *

RFCDEST

Specifies the destination of the CRM server.

DOWNLOAD

Restricts CRMRFCPAR entries to the initial or delta load. Possible values include:

  • * generally valid entry

    I for initial data transfer only

  • D for delta data transfer only

With initial transfers, data can be sent to two destinations but with delta transfers, data can only be sent to one destination. Standard value: *

RFC_QUEUE

Standard value: "

RFC_IN_QUE

RFC inbound queue, standard value: "

BAPINAME

Standard value: "

INFO

Comment

INACTIVE

Data record inactive, standard value: "

DISCARDDAT

Prevents data from being transferred to specific RFC destinations. These entries are defined mainly only for specific objects and/or transfer types (initial/delta). The entries are taken into account when the RFC destinations are determined.

Standard value: "

USE_IN_Q

Controls whether qRFC inbound queues are used on the CRM server.

Standard value: X

SEND_XML

Supports XML. For information about how to improve performance during data exchange, refer to SAP Note 442277 Information published on SAP site.

Standard value: M (prior to support package 8: standard value X)

HOLD_DATA

Causes the ERP back-end 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 table CRMPAROLTP. Normally the queue is processed automatically. If X has been entered, the data is held in an outbound queue in the ERP back-end system.

For PI2000.2 taken from CRMPAROLTP (parameter RECORD_ASYNCHRONOUS_MESSAGE)

Standard value: "

Example

If you want to provide a CRM system with data, for example, you must create the following entries:

Parameter

Value

CONSUMER

CRM

OBJNAME

*

RFCDEST

<RFC destination>

DOWNLOAD

* (for initial data and delta data transfer)

USE_IN_Q

X

SEND_XML

M/X