SAP ABAP Data Element EXP_TOV_ORDERS (Number of Overdue Purchase Orders)
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
PS-PRG-TRC (Application Component) Progress Tracking
⤷
EXPD (Package) Expediting for Order
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
PS-PRG-TRC (Application Component) Progress Tracking⤷
EXPD (Package) Expediting for Order
Basic Data
| Data Element | EXP_TOV_ORDERS |
| Short Description | Number of Overdue Purchase Orders |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMC5 | |
| Data Type | NUMC | Character string with only digits |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| 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 | OvrduePO |
| Medium | 15 | Overdue POrders |
| Long | 20 | Overdue Pur. Orders |
| Heading | 8 | OvrduePO |
Documentation
Definition
Number of overdue purchase orders in an evaluation for Progress Tracking.
A purchase order is considered as being overdue if at least one schedule line, item or subitem has an event for which a plan or baseline date is maintained and for which there is no actual date.
Here, the plan or baseline date is in the past, and there is no subsequent event with a higher rank for which an actual date exists.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in | 461 |
