Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | SDMSELSET3 |
| Short Description | Variant of a coll. delivery proc.compared to another variant |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SELSET | |
| Data Type | CHAR | Character String |
| Length | 14 | |
| Decimal Places | 0 | |
| Output Length | 14 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 0 |
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!
Variant of the collective delivery processing run that is compared with another variant with regards to runtimes and parameters.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
