SAP ABAP Data Element TPM_TRG_PAR_RFC_GROUP (Logon/Server Group Name)
Hierarchy
☛
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
⤷
FIN-FSCM-TRM-TM (Application Component) Transaction Manager
⤷
FTR_GENERAL (Package) CFM TM: Application Basis / Global Objects

⤷

⤷

Basic Data
Data Element | TPM_TRG_PAR_RFC_GROUP |
Short Description | Logon/Server Group Name |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RZLLI_ACN | |
Data Type | CHAR | Character String |
Length | 20 | |
Decimal Places | 0 | |
Output Length | 20 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Lg/SrvGrp |
Medium | 19 | Logon/Server Group |
Long | 20 | Logon/Server Group |
Heading | 20 | Logon/Server Group |
Documentation
Definition
Transaction RZ12 lets you define logon/server groups and assign a quantity of instances. The logon/server groups are used to distribute volumes during parallel processing, ensuring that available resources are optimally used.
If an application server is used a part of an RFC server group for parallel processing, it must have at least three dialog work processes one of which is currently vacant. Other resources such as requests in queue, number of system messages and so on are also taken into account and cannot exceed certain limits.
Value Limits for Available Resources
All of the following criteria must be filled for resources to be made available for parallel processing.
- Number of vacant dialog work processes: 1
This standard value is 1 and can be defined by means of the profile parameter rdisp/rfc_min_wait_dia_wp. A specific number of dialog work processes must be reserved as stand-by instances for other purposes, for example, system messages or administrative programs. For this reason, more dialog processes must be vacant than the value indicated by profile parameter rdisp/rfc_min_wait_dia_wp. - Percentage of user-related dialog work processes: 75%
This default value can be changed by means of the rdisp/rfc_max_own_used_wp profile parameter. The number of dialog work processes is defined by the rdisp/wp_no_dia profile parameter. - Percentage of requests waiting in the dialog queue: 5%
This default value (5% of the total length of the dialog queue) can be changed with the rdisp/rfc_max_queue profile parameter. The length of dialog queues is defined by the rdisp/elem_per_queue profile parameter. - Percentage of system logons: 90%
If the portion of logged on users amounts to more, no resources are made available. The default value can be changed by means of the rdisp/rfc_max_login profile parameter. The maximum number of logons permitted in the server is set using the rdisp/tm_max_no profile parameter. - Percentage of your own logons in the system: 25%
This default value (25% of all logons) can be changed using the rdisp/rfc_max_own_login profile parameter. Each RFC causes a logon in the target system. - Percentage of communication entries. 90%
Each server has a limited number of communication channels. The default limit is 90%. This value can be changed using the rdisp/rfc_max_comm_entries profile parameter. The maximum number of communication channels is defined in the rdisp/wp_no_dia profile parameter. One entry is made for the client and one for the server for each connection.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20040819 |
SAP Release Created in | 500 |