Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
CA-GTF (Application Component) General Application Functions⤷
BAM (Package) Technical Application Analysis
Basic Data
| Data Element | PERIODTIME |
| Short Description | Mean time interval (h) between calling a variant |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | INT4 | |
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Interv.(h) |
| Medium | 20 | Mean interval (h) |
| Long | 40 | Mean interval (h) between 2 variants |
| Heading | 12 | Interval (h) |
Documentation
Mean time interval (in hours) between 2 collective processing runs of the variant during statististical analysis of the collective delivery processing run.
If this statistic is only slightly dispersed, then a periodically started variant is involved. First of all a check must be carried out to determine whether the parameters for the delivery creation date or goods issue date cover a larger area than the period duration. This is because continuous reprocessing of the documents, that may be marked as not relevant for delivery until the end of the process, causes a drop in performance levels.
If the the average period is long and the number of processed documents is high, you should consider reducing the period duration, as the cost to resources of the collective delivery processing run will grow disproportionately with the number of newly processed documents.
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
