Useful parameters to parallelize queue processing
Customers always have requirement to improve the performance for initial/request/delta load between ERP and CRM. In order to achieve this, you could set the following parameters to make the queues being processed parallel.
| Load type | Parameter | Note |
|---|---|---|
| Initial load |
Maintain the parameter in table CRMPAROLTP of ERP system via SM30: Parameter name: CRM_MAX_QUEUE_NUMBER_INITIAL Parameter name 2: <object name> Parameter name 3: Consumer/user: CRM, CDB or EXT (R/3 backend or external system) Parval1: <the number of the parallel processing queues> Parval2: |
Note 350176 |
| Request load |
Maintain the parameter in table CRMPAROLTP of ERP system via SM30: Parameter name: CRM_MAX_NO_QUEUES_PER_REQUEST Parameter name 2: <object name> Parameter name 3: Consumer/user: CRM, CDB or EXT (R/3 backend or external system) Parval1: <the number of the parallel processing queues> Parval2: |
Note 426159 |
| Delta load |
Maintain the following parameter and the parameter CRM_MAX_QUEUE_NUMBER_DELTA in table CRMPAROLTP simultaneously. Parameter name: CRM_IN_EQUAL_OUT_QUEUE Parameter name 2: <object name> Parameter name 3: Consumer/user: CRM, CDB or EXT (R/3 backend or external system) Parval1: X Parval2: For a serialization of the delta load of an R/3 back end to the CRM server, the parameter is entered in the R/3 back end. For a serialization of the delta load from the CRM server, the parameter is entered in the CRM server. |
Note 624436 |
| Dima |
Maintain the following parameter and the parameter CRM_MAX_QUEUE_NUMBER_DIMA in table CRMPAROLTP of ECC system simultaneously. Parameter name: CRM_IN_EQUAL_OUT_QUEUE Parameter name 2: <object name> Parameter name 3: Consumer/user: CRM, CDB or EXT (R/3 backend or external system) Parval1: X Parval2: |
Note 628949 |