Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA (Application Component) Cross-Application Components⤷
CFD (Package) IMG for APO Core Interface
IMG Activity
| ID | APOCIF_COMMKON | Configure qRFC Communication |
| Transaction Code | S_AX7_68000215 | (empty) |
| Created on | 20020828 | |
| Customizing Attributes | ATAPOCIF_COMMKON | Configure qRFC Communication |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | APOCIF_COMMKON |
Use
You can use the scheduler settings for inbound and outbound queues to configure communication using queued remote function call (qRFC) and therefore control the management and monitored processing of qRFCs.
qRFC communication allows asynchronous communication with transactional security and a serialization of calls. qRFC communication is used intensively in the SAP APO Core Interface to transfer logistical data online and thus retain the transactionality and sequence.
Inbound qRFCs are processed using the QIN scheduler, outbound ones by the QOUT scheduler.
The asynchronous transfer to SAP APO of logistical data relevant to planning is based on qRFC communication. If this is not configured correctly, processing does not take place. This means that planning data is not exchanged and consistent planning is no longer possible.
Requirements
To avoid problem situations, we recommend that you use the current qRFC version. For more information, see SAP Note 438015.
The qRFC is delivered as part of SAP Basis or implemented in Support Packages. An update is also possible using a special transport. For more information, see SAP Notes 481278 and 438015.
Activities
You make the settings for the necessary profile parameters in transaction RZ12.
- Call transaction RZ12.
- Double-click on a server group. A dialog window is displayed in which you can set the following parameters (as of SAP R/3 4.5B):
- Activated (0 or 1): 1
- Max. requests in queue: 5
- Max. number of logons: 90
- Max. number of own logons: 25
- Max. number of WPs (work processes) used: 75
- Min. number of free WPs: 1
- Max. number of comm. entries: 90
- Max. wait time : 10 (as of SAP R/3 4.6C)
Use SAP Note 74141 to fill the parameters for the system concerned. Note that all entries apart from Activated and Min. number of free WPs must be in percent.
The number of work processes (WPs), that may be used by qRFC is determined using the following formula:
- (Number of all dialog WPs - minimum number of free WPs) x maximum number of WPs used / 100.
If this figure is too small, it is not possible to use communication via qRFC.
Example 1:
- There are a total of 7 dialog WPs in a system, the minimum number of free WPs is 2, and the maximum number of WPs used is 6. The number of WPs that can be used is calculated as follows: (7-2) x 6/100 = 0.3. In this case, communication using qRFC is not possible.
Example 2:
- There are a total of 10 dialog WPs in a system, the minimum number of free WPs is 2, and the maximum number of WPs used is 75. The number of WPs that can be used is calculated as follows: (10-2) x 75/100 = 6. In this case, communication using qRFC is possible.
Other profile parameters
Note that qRFC calls are processed in work processes of the type DIALOG (exception: inbound queues). As a result, the DIALOG restriction for processing a dialog step (standard 300 seconds, system profile parameter rdisp/max_wprun_time) also applies to these RFC calls. On every sever that is available for processing parallel RFCs, more dialog work processes must be configured than non-dialog work processes. For more information, see SAP Note 74141.
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20020906 |
| SAP Release Created in |
