Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-TWB-TST-P-GPA (Application Component) Global Performance Analysis (Transaction ST30)⤷
S_PERF_TRA (Package) New Performance Trace / Statistics with DB Connection
Basic Data
| Data Element | RFCL_STAT |
| Short Description | Performance Log for RFC Trace: Abbreviated Statement |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 210 | |
| Decimal Places | 0 | |
| Output Length | 210 | |
| 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 | Statement |
| Medium | 10 | Statement |
| Long | 15 | Statement |
| Heading | 10 | Statement |
Documentation
Definition
Depending on the trace type (SQL trace, enqueue trace, RFC trace, table buffer trace), a short form is displayed. If the short form ends with the symbol '...', it is incomplete. On account of the available output area, the short form had to be truncated.
1. SQL trace: In a logged SQL statement, an abbreviated SQL statement is displayed in which variables are replaced as far as this is possible (see below). When replacing variables in the abbreviated SQL statement, spaces at the end of variables are suppressed. If the variable contains only spaces, they are reduced to one single space.
2. Enqueue trace: In an enqueue trace, the granularities are displayed in this column. If there are multiple granularities, the symbol "l" is used as a separator. The number of granularities can be found in the column "Rec."
For each granularity, the following is displayed:
- Lock mode
- Table name for the lock object
- Lock argument
The following lock modes are possible:
- Excl(cum) Exclusive lock that can be cumulated
- Excl(non-cum) Exclusive lock that cannot be cumulated
- Shared Shared lock
If there is an exclusive lock, no other user can access the locked object. A shared lock enables other users to access the locked records in display mode.
3. RFC trace: In an RFC trace, the name of the local instance, the name of the remotely used instance, the characteristic client/server, and the name of the function module are displayed. Afterwards, the number of the sent and received bytes is displayed. If one of the names is not available, "?" is displayed at the relevant point.
4. Table buffer trace: When accessing buffered tables, "READ SI" and "OPEN" are displayed with the following operations.
- type of buffer
.P - Individual table records buffered
.R - Table completely buffered
.G - Key value area of the table buffered
.S - Import-/export buffering
- The length of the key that is used for access to the buffered table.
- (In round brackets) the number of key fields used for the area-orientated (generic) buffering of the table, if it is a generic table.
- The key value with which the buffered table is accessed.
In the operation 'FETCH', in the case of compressed display, the number of compressed fetches and the average duration of a fetch is displayed. If, for a fetch, the maximum set duration is exceeded, the pattern ">999999.9" is displayed. If the fetches are not displayed in compressed form, there is no additional information in this column.
In 'CLOSE' operations, no further information is displayed.
In export/import buffer traces that are characterized with the operations Load, Retrieve and Invalidate, the length of the object is also displayed.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 610 |
