Hierarchy

⤷

⤷

Basic Data
Data Element | UAINV_WIP_CLEARING_DATE |
Short Description | Status Date |
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 | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | WIP Clear |
Medium | 20 | WIP Clearing Date |
Long | 20 | WIP Clearing Date |
Heading | 50 | WIP Clearing Date |
Documentation
Definition
Indicates when the status technically completed or delivered was set for a manufacturing order. If both statuses were set, the status date shows when the first status was set.
Use
The date determines whether work in process (WIP) is cleared for the order or whether a previous WIP clearing is reversed.
Dependencies
Example
An order is technically completed on October 15 (= status date). WIP clearing is then executed for period 10. The key date for WIP clearing is the last day of the period (October 31). Since the status date of technical completion is before the key date of WIP clearing, the system clears the WIP on the order.
On November 10, the status technically completed on the order is removed and the status delivered is set (with a status date of November 10). WIP clearing is then repeated for period 10. Since now the date of final delivery applies (November 10) which is after the key date of WIP clearing for period 10 (October 31), the WIP cleared in period 10 is posted back to the order.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20041006 |
SAP Release Created in | 350 |