SAP ABAP Data Element SE30L1SRVT (Runtime Analysis Measurement Objects: RFC, Update)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-TOO-RTA (Application Component) Runtime Analysis
⤷
STRA (Package) Runtime Analysis
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO-RTA (Application Component) Runtime Analysis⤷
STRA (Package) Runtime Analysis
Basic Data
| Data Element | SE30L1SRVT |
| Short Description | Runtime Analysis Measurement Objects: RFC, Update |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | RFC, Upd. |
| Medium | 20 | RFC, Update |
| Long | 30 | RFC, Update |
| Heading | 20 | RFC, Update |
Documentation
Definition
With this option, RFC calls and updates are measured. The results are stored in seperate performance data files on the respective application sever. In the case of RFC, it may also be the server of a different SAP system. The evaluation of these files must be started on the relevant application server. No automatic conversion takes place in the Trace Container.
Use
Dependencies
The performance data files are stored under the user name SAPSYS. For the evaluation, the user filter must therefore be set properly.
The system (or the server side in the case of RFC calls) must be started using the profile parameter rstr/accept_remote_trace = true.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 630 |
