SAP table KBKO (Header Record for Capacity Requirements)

SAP table KBKO has 2 primary key fields being MANDT,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
BEDID ID of the Capacity Requirements Record NUMC 12 0 BEDID
TYPKZ Category of object causing the load (order category) CHAR 1 0 TYPKZ
1 Work orders (detailed scheduling / routing...)
2 Planned orders (detailed scheduling / routing...)
3 SOP-Order (detailed scheduling / routing...)
A Maintenance task
B Maintenance messages
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
No reduction carried out
1 Reduction level 1
2 Reduction level 2
3 Reduction level 3
4 Reduction level 4
5 Reduction level 5
6 Reduction level 6
TRMER Scheduling error CHAR 2 0 TRMER
0 Scheduling carried out successfully
1 Scheduling parameters are not maintained in customizing
2 No capacity requirements determined, see customizing
3 Routing does not exist
4 No valid routing can be selected
5 Scheduling terminated, see log
6 Scheduling carried out, see log for error messages
7 Scheduling carried out, see log for information messages
8 Detailed scheduling and sequencing active at same time
TRMHK Scheduling source CHAR 1 0 TRMHK
1 Scheduling via material master
2 Scheduling via routing
PLAUF Date for Routing Explosion DATS 8 0 CO_PLAUF
TL_VERSN Routing Version CHAR 4 0 PLNVERSN

KBKO foreign key relationships

Table Field Check Table Check Field
0 KBKO MANDT T000 Clients MANDT
1 KBKO OBJNR ONR00 General Object Number MANDT
0 KBKO PLNTY TCA01 Task list types MANDT
1 KBKO PLNUM PLAF Planned Order MANDT
0 KBKO TERKZ T482 Table of scheduling types MANDT
0 KBKO TERKZ T482 Table of scheduling types TERMKZ