Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-UPG-NA (Application Component) SAP Note Assistant⤷
SANST (Package) Automated Notes Search Tool
Basic Data
| Data Element | ANSTSE30L1DOWN |
| Short Description | ABAP Runtime Analysis: Measure Called Functionality |
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 | Called |
| Medium | 20 | Called Functionality |
| Long | 30 | Measure Called Functionality |
| Heading | 40 | Measure Called Functionality Too |
Documentation
Definition
When this option is selected, the runtimes are measured of all the program components within and on any level below one of the specified program components or hotspots called.
Without this option, only the specified program components and hotspots and the program components called directly by these program components/hotspots are measured.
Use
To keep ABAP trace files small, this option should only be used if an exact analysis is required of a program component to be measured.
Example
A class CL1 has four methods: M1, M2, M3, M4.
The method M1 is specified as a program component to be measured or defined as a hotspot.
M1 calls M2,
M2 calls M3,
M3 calls M4.
If the option is selected, all calls M1, M2, M3, M4 are measured.
if the option is not selected, only M1 and M2 are measured because M1 is specified as program component or hotspot and M2 is called directly within M1.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 740 |
