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 | GET_ADD_STAT |
| Short Description | Read Additional Statistics Data from Manually Created Dests |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Add.Stats |
| Medium | 20 | Addnl Stats Data |
| Long | 24 | Addnl Statistics Data |
| Heading | 29 | Additional Statistics Data |
Documentation
Definition
You define here whether, in addition to the distributed statistics records (DSRs) automatically collected by the specified central monitoring system, additional statistics data is to be collected from destinations entered manually before the test run on the "Manual Test 1" or "Manual Test 2" screen. Important: the correct RFC user for which the statistics data is to be collected must be used in the destination. This also applies for th eserver, which must be correctly specifed there.
Background:
Assuming that an eCATT test configuration is run, that works, for example on another system with Web Dynpro and a J2EE. In this case, another ABAP system is used as a backend system. Since it is not absolutely certain, that systems of this type are registered on the central monitoring system, you can query their statistics data here by entering the required destinations. This is then displayed on the statistics data screen in addition to the displaying of the DSRs.
Note:
If ABAP destinations are also used in the eCATT test configuration used, you should not also enter these manually in the list of destinations. You should always use a separate destination created for the purpose, even if a suitable destination already exists, if this is used in the eCATT test configuration.
Reason: if you manually enter a destination used in the eCATT, the associated statistics data is not displayed separately later. If you use a separate (but identically-defined) destination, the statistics data for it is displayed separately. The situation described here only occurs rarely in practice.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
