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 | PROTIDTEXT |
| Short Description | Text for Performance Test |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TEXT128 | |
| Data Type | CHAR | Character String |
| Length | 128 | |
| Decimal Places | 0 | |
| Output Length | 128 | |
| 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 | Perf. Test |
| Medium | 13 | Perf. Test |
| Long | 16 | PerformanceTest |
| Heading | 16 | PerformanceTest |
Documentation
Definition
Here, you can enter and edit an explanation of a performance test for the global performance analysis.
Use
For each log ID, you can carry out as many performance tests as you want. Furthermore, you can hierarchically link several log IDs with each other in line with the logical structure that you want.
If, in the global performance analysis, you want to run test cases automatically, you must distinguish between two cases:
1. The whole flow of all test cases is carried out as a single performance test. In this case, the text for the performance test is adopted unchanged.
2. During the flow of the test cases, performance data per test data per test case is stored in a dedicated performance test on the database. In this case, the predefined text is taken as the prefix for the text of each performance test. For each performance test, the name of the currently used test case is attached to the text.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 50A |
