SAP ABAP Data Element VRZGT (Actual delay)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-CIC (Application Component) Interaction Center WinClient
⤷ CO (Package) R/3 Application development: PP Production orders
⤷ CRM-CIC (Application Component) Interaction Center WinClient
⤷ CO (Package) R/3 Application development: PP Production orders
Basic Data
Data Element | VRZGT |
Short Description | Actual delay |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | VRZGT | |
Data Type | QUAN | Quantity field, points to a unit field with format UNIT |
Length | 9 | |
Decimal Places | 3 | |
Output Length | 11 | |
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 | Act. delay |
Medium | 20 | Actual delay |
Long | 30 | Actual delay |
Heading | 11 | ActualDelay |
Documentation
Definition
The way in which the actual delay is calculated depends on the receipt element in question.
- Production order: The actual operation delay is calculated from the difference between the confirmed and planned operation ends of the last finally confirmed operation in the production order. The actual order delay is calculated from the difference between the current date and the scheduled end of the order. In the order progress report, the maximum from the actual operation delay and actual order delay is displayed. This is calculated dynamically.
- Planned order: The order start date lies in the past.
- Purchase requisition: The release date lies in the past.
- Purchase order: The latest confirmed date of a schedule line lies after the requested delivery date of the purchase order (header level).
History
Last changed by/on | SAP | 19990326 |
SAP Release Created in |