Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO (Application Component) Workbench Tools: Editors, Painters, Modelers⤷
SWLT (Package) SQL Performance Tuning Worklist
Basic Data
| Data Element | SWLT_D_PBLOCK_EXECUTIONS |
| Short Description | Number of Processing Block Executions |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CVO_DEC20 | |
| Data Type | DEC | Counter or amount field with comma and sign |
| Length | 20 | |
| Decimal Places | 0 | |
| Output Length | 26 | |
| 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 | ProcBlkExe |
| Medium | 17 | ProcBlock Exec. |
| Long | 30 | Processing Block Executions |
| Heading | 30 | Processing Block Executions |
Documentation
Definition
Overall number of times the processing block has been executed after the Coverage Analyzer has been switched on
Note that the execution number is independent of the test groups that might have been defined in the Coverage Analyzer. If switched on, the Coverage Analyzer monitors all program executions, anyway.
If the execution number is zero, this is due to one of the following reasons:
- The type of the processing block is one of SYEX, PBO0 , EEDI or SEDI (for such processing blocks no coverage results are available at all)
- The processing block has never been executed while the Coverage Analyzer was active
- The processing block has been executed only on servers for which the collection of coverage data was not active at the moment of execution
- The Coverage Analyzer has been switched off after execution of the processing block (switching off the Coverage Analyzer implies deletion of all coverage data)
- The processing block has been modified, but has not been executed afterwards (by processing block modifications its coverage result is automatically reset)
- The coverage results for the program to which the processing block belongs have been explicitly reset in the Coverage Analyzer by someone having the authorization for Coverage Administration (this is possible, but not very likely, since this kind of activity is rather uncommon)
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20140117 |
| SAP Release Created in | 740 |
