Hierarchy
⤷ BC-CCM-MON (Application Component) Monitoring
⤷ SAPWL_FRONTEND (Package) SAP: Workload Display, Enjoy & OO Version - ST03N
Basic Data
Data Element | SAPWLSPRFC |
Short Description | SAP Workload: Online Parameter: Number of RFC Subrecords |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SAPWLINT4 | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | 0 | |
Medium | 15 | stat/rfcrec |
Long | 30 | stat/rfcrec - RFC Subrecords |
Heading | 40 | stat/rfcrec - Number of RFC Subrecords |
Documentation
Definition
With the profile parameter stat/rfcrec, you can determine whether and how many RFC calls are recorded in the statistics files. The RFC calls are broken down for each transaction step by RFC server, RFC client, and RFC destination (again broken down for client and server) and the <stat/rfcrec> records with the longestexecution time for each of the criteria are logged in the statistics files.
By default, stat/rfcrec has the value 5, which means that for each transaction step, the five RFC calls with the longest execution time are logged. We recommend that you do not use a higher value in production operation due to the higher load on the statistics collector.
A change to an online parameter is valid immediately. After a restart of the instance, the change is automatically reset. If you want to change an online parameter permanently, change the corresponding value in transaction RZ11 (Profile Parameter Maintenance).
See also:
Display RFC Profile
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 46D |