SAP table TCK16 (Date Control)
SAP table TCK16 has 2 primary key fields being MANDT,TERID.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
| Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |
|---|---|---|---|---|---|---|---|
| MANDT | Client | CLNT | 3 | 0 | T000 | MANDT | |
| TERID | Date Control | CHAR | 4 | 0 | CK_TERID | ||
| EINVO | Costing Date From Is Ready for Input (Date Control) | CHAR | 1 | 0 | CK_EINVO | ||
| VORVO | Default for Costing Date From | CHAR | 1 | 0 | CK_VORVO | ||
| EINVE | Costing Date To Is Ready for Input | CHAR | 1 | 0 | CK_EINVE | ||
| VORVE | Default for Costing Date To | CHAR | 1 | 0 | CK_VORVE | ||
| EINBR | Quantity Structure Date Is Ready for Input | CHAR | 1 | 0 | CK_EINBR | ||
| VORBR | Default Quantity Structure Date | CHAR | 1 | 0 | CK_VORBR | ||
| EINBE | Requirements Date Ready for Input | CHAR | 1 | 0 | CK_EINBE | ||
| VORBE | Default Requirements Date | CHAR | 1 | 0 | CK_VORBE | ||
| STABE | Statistical Requirements Date for Costing | CHAR | 1 | 0 | CK_STABE | ||
| EINBW | Valuation Date Is Ready for Input | CHAR | 1 | 0 | CK_EINBW | ||
| VORBW | Default Valuation Date | CHAR | 1 | 0 | CK_VORBW | ||
| STABW | Static Valuation Date for Materials | CHAR | 1 | 0 | CK_STABW | ||
| VETBW | Valuation Dates from Material Master Replenishment Lead Time | CHAR | 1 | 0 | CK_VETBW |