SAP ABAP Data Element RUNTIMCORR (Runtime of collective processing exceeded)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ CA-GTF (Application Component) General Application Functions
⤷ BAM (Package) Technical Application Analysis
⤷ CA-GTF (Application Component) General Application Functions
⤷ BAM (Package) Technical Application Analysis
Basic Data
Data Element | RUNTIMCORR |
Short Description | Runtime of collective processing exceeded |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | INT1 | |
Data Type | INT1 | 1-byte integer, integer number <= 255 |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | RUNTIMCORR |
Medium | 20 | Runtime correlation |
Long | 40 | Coll. processing runtime correlation |
Heading | 11 | RUNTIMECORR |
Documentation
In the SD Monitor tool, the runtime of delivery coll. processing is determined via the difference between the start time of the collective processing and the time at which the last delivery is determined. The last delivery created has the highest document number of all the deliveries created during collective processing. The system takes into account the possibility that document numbers could originate in different number ranges and that some document numbers could contain non-numerical characters. Unusual number assignment in user exits (numbered correctly, but not entered chronologically) can lead to the runtime being miscalculated
Collective processing runs that create no document are always given a runtime of 0!
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |