Hierarchy

⤷

⤷

⤷

Basic Data
Data Element | MSTDE |
Short Description | Date from which the cross-plant material status is valid |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATUM | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | PVALIDFROM | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Valid from |
Medium | 15 | Valid from |
Long | 20 | Valid from |
Heading | 10 | Valid from |
Documentation
Definition
Use
Procedure
Example
Dependencies
- Materials planning
The valid-from date of the material status is considered only if it precedes or is the same as the planning date; that is, if the valid-from date is later than the planning date, it is not considered, even if it is within the planning horizon.
Example
I<-------------Planning horizon------------->I
-----I--------------------I-----------------------I-->
Planning date Valid-from date TimeIn this case, the valid-from date is not considered in materials planning since it is later than the planning date.
- Purchasing
The valid-from date of the material status is checked against the current date.
Example
You block the material for purchasing from May 1, xxxx. A purchase order is created for the material on April 28, xxxx with a delivery date of May 10, xxxx. In this case, the valid-from date May 1, xxxx is checked against the purchase order date April 28, xxxx and the purchase order is allowed. Had you created the purchase order on May 3, xxxx, an error message would have been issued.
History
Last changed by/on | SAP | 19991108 |
SAP Release Created in |