SAP table VSKBKO_CN (Version: Capacity requirements header for an order)
SAP table VSKBKO_CN has 3 primary key fields being MANDT,VSNMR,BEDID.
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 | |||||||||||||||||||
VSNMR | Number or description of a version | CHAR | 12 | 0 | VSNMR | ||||||||||||||||||||
BEDID | ID of the Capacity Requirements Record | NUMC | 12 | 0 | BEDID | ||||||||||||||||||||
TYPKZ | Category of object causing the load (order category) | CHAR | 1 | 0 | TYPKZ |
|
|||||||||||||||||||
AUFPL | Routing number of operations in the order | NUMC | 10 | 0 | CO_AUFPL | ||||||||||||||||||||
PLNUM | Planned Order | CHAR | 10 | 0 | PLAF | PLNUM | |||||||||||||||||||
SAFNR | Sales Operations Planning Order | CHAR | 10 | 0 | SAFNR | ||||||||||||||||||||
PLNTY | Task List Type | CHAR | 1 | 0 | TCA01 | PLNTY | |||||||||||||||||||
PLNNR | Key for Task List Group | CHAR | 8 | 0 | PLNNR | ||||||||||||||||||||
PLNAL | Group Counter | CHAR | 2 | 0 | PLNAL | ||||||||||||||||||||
OBJNR | Object number | CHAR | 22 | 0 | ONR00 | J_OBJNR | |||||||||||||||||||
TRMDT | Date of the Last Scheduling | DATS | 8 | 0 | TRMDT | ||||||||||||||||||||
GLTRS | Scheduled finish | DATS | 8 | 0 | CO_GLTRS | ||||||||||||||||||||
GLUZS | Earliest finish of operation (time) | TIMS | 6 | 0 | FSEVZ | ||||||||||||||||||||
GSTRS | Scheduled start | DATS | 8 | 0 | CO_GSTRS | ||||||||||||||||||||
GSUZS | Earliest scheduled start: Execution (time) | TIMS | 6 | 0 | FSAVZ | ||||||||||||||||||||
TERKZ | Scheduling type | CHAR | 1 | 0 | T482 | TERMKZ | |||||||||||||||||||
BREAKS | Indicator: Scheduling allowing for breaks | CHAR | 1 | 0 | BREAKS | ||||||||||||||||||||
REDKZ | Reduction indicator for scheduling | CHAR | 1 | 0 | REDKZ |
|
|||||||||||||||||||
TRMER | Scheduling error | CHAR | 2 | 0 | TRMER |
|
|||||||||||||||||||
TRMHK | Scheduling source | CHAR | 1 | 0 | TRMHK |
|
|||||||||||||||||||
PLAUF | Date for Routing Explosion | DATS | 8 | 0 | CO_PLAUF | ||||||||||||||||||||
TL_VERSN | Routing Version | CHAR | 4 | 0 | PLNVERSN |
VSKBKO_CN foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 VSKBKO_CN | MANDT | T000 | Clients | MANDT |
1 VSKBKO_CN | OBJNR | ONR00 | General Object Number | MANDT |
0 VSKBKO_CN | PLNTY | TCA01 | Task list types | MANDT |
1 VSKBKO_CN | PLNUM | PLAF | Planned Order | MANDT |
0 VSKBKO_CN | TERKZ | T482 | Table of scheduling types | MANDT |
0 VSKBKO_CN | TERKZ | T482 | Table of scheduling types | TERMKZ |