SKBED SAP (Capacity requirements for sub-operation - log. DB) Structure details
Description: Capacity requirements for sub-operation - log. DB
Structure field list including key, data, relationships and ABAP select examples
SKBED is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Capacity requirements for sub-operation - log. DB" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_SKBED TYPE SKBED.
The SKBED table consists of various fields, each holding specific information or linking keys about Capacity requirements for sub-operation - log. DB data available in SAP. These include MANDT (Client), BEDID (ID of the capacity requirements record), BEDZL (Internal counter), CANUM (Counters for cap. rqmts. records (various caps. + indiv.caps).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP SKBED structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
BEDID | ID of the capacity requirements record | BEDID | NUMC | 12 | KBKO | BEDID | |||
BEDZL | Internal counter | CIM_COUNT | NUMC | 8 | CIM_COUNT | ||||
CANUM | Counters for cap. rqmts. records (various caps. + indiv.caps | CY_COUNT | NUMC | 4 | Assigned to domain | CY_COUNT | |||
ARBID | Work center ID | ARBPLATZ | NUMC | 8 | NUM08 | ||||
TYPKZ | Category of object causing the load (order category) | TYPKZ | CHAR | 1 | TYPKZ | ||||
OBJKZ | Indicator: Remaining split record | OBJKZ | CHAR | 1 | OBJKZ | ||||
KAPID | Capacity ID | KAPID | NUMC | 8 | KAKO | KAPID | |||
BEDKZ | Indicator: Remaining split record | BEDKZ | CHAR | 1 | X | ||||
KRUESOLL | Scheduled cap. requirements for the op. segment 'setup' | CY_KRUESOL | FLTP | 16(16) | KAPBED | ||||
KRUEREST | Remaining capacity rqmts. for operation segment 'Setup' | CY_KRUERES | FLTP | 16(16) | KAPBED | ||||
KBEASOLL | Scheduled cap. requirements for the op. segment 'processing' | CY_KBEASOL | FLTP | 16(16) | KAPBED | ||||
KBEAREST | Remaining capacity rqmts.for operation segment 'Processing' | CY_KBEARES | FLTP | 16(16) | KAPBED | ||||
KABRSOLL | Scheduled cap. requirements for the op. segment teardown | CY_KABRSOL | FLTP | 16(16) | KAPBED | ||||
KABRREST | Remaining capacity requirements for op. segment 'tear down' | CY_KABRRES | FLTP | 16(16) | KAPBED | ||||
KEINH | Unit of of measure for displaying capacity requirements | CY_KEINH | UNIT | 3 | T006 | CUNIT | MEINS | ||
FSTAD | Earliest start / date | FSTAD | DATS | 8 | DATUM | ||||
FSTAU | Earliest start / time | FSTAU | TIMS | 6 | T | ||||
FENDD | Earliest finish /date | FENDD | DATS | 8 | DATUM | ||||
FENDU | Earliest finish /time | FENDU | TIMS | 6 | T | ||||
SSTAD | Latest start / date | SSTAD | DATS | 8 | DATUM | ||||
SSTAU | Latest start / time | SSTAU | TIMS | 6 | T | ||||
SENDD | Latest finish / date | SENDD | DATS | 8 | DATUM | ||||
SENDU | Latest finish / time | SENDU | TIMS | 6 | T | ||||
ISTAD | Actual start / date | ISTAD | DATS | 8 | DATUM | ||||
ISTAU | Actual start / time | ISTAU | TIMS | 6 | T | ||||
IENDD | Actual finish / date | IENDD | DATS | 8 | DATUM | ||||
IENDU | Actual finish / time | IENDU | TIMS | 6 | T | ||||
PENDD | Forecast finish / date | PENDD | DATS | 8 | DATUM | ||||
PENDU | Forecast finish / time | PENDU | TIMS | 6 | T | ||||
ISPLI | Actual number of splits | ISPLI | DEC | 3 | SPLITTANZ | ||||
KPVER | Distribution of capacity requirements (Planned/prod.order) | CR_VERTL | CHAR | 8 | TC29 | CR_VERTL | |||
OBSTA | Object status (order status) | OBSTA | CHAR | 22 | ONR00 | J_OBJNR | |||
AUFPL | Routing number of operations in the order | CO_AUFPL | NUMC | 10 | AUFPL | ||||
APLZL | General counter for order | CO_APLZL | NUMC | 8 | AFVC | CO_APLZL | |||
PLNUM | Planned order number | PLNUM | CHAR | 10 | PLAF | ALPHA | PLNUM | PAF | |
PLNTY | Task List Type | PLNTY | CHAR | 1 | TCA01 | PLNTY | PTY | H_TCA01 | |
PLNNR | Key for Task List Group | PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | PLKS | |
PLNAL | Group Counter | PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
ZAEHL | Internal counter | CIM_COUNT | NUMC | 8 | CIM_COUNT | ||||
PLNFL | Sequence | PLNFOLGE | CHAR | 6 | ALPHA | PLNFOLGE | |||
ZAEHF | Internal counter | CIM_COUNT | NUMC | 8 | CIM_COUNT | ||||
PLNKN | Number of the task list node | PLNKN | NUMC | 8 | KNTNR | ||||
ZAEHP | Internal counter | CIM_COUNT | NUMC | 8 | CIM_COUNT | ||||
SPLKN | Number of the task list node of the sub-operation | SPLNKN | NUMC | 8 | KNTNR | ||||
SZAEHL | Internal counter | CIM_COUNT | NUMC | 8 | CIM_COUNT | ||||
SAFNR | SOP order number | SAFNR | CHAR | 10 | SAFNR | ||||
VORNR | Operation/Activity Number | VORNR | CHAR | 4 | NUMCV | VORNR | VGN | ||
OTYPE | Object Type | OTYPE | CHAR | 2 | T778O | OTYPE | POT | ||
PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
CANUMF | Counter for the main capacity requirements record | CANUMF | NUMC | 4 | NUM4 | ||||
SPLIT | Split number | CY_SPLIT | INT1 | 3 | INT1 | ||||
KBSTA | Status of a capacity requirements (object number) | CY_KBSTA | CHAR | 22 | ONR00 | J_OBJNR | |||
FSSBD | Earliest scheduled start: Processing (date) | FSSBD | DATS | 8 | DATUM | ||||
FSSBZ | Earliest scheduled start: Processing (time) | FSSBZ | TIMS | 6 | ATIME | ||||
FSSAD | Earliest scheduled start: Teardown (date) | FSSAD | DATS | 8 | DATUM | ||||
FSSAZ | Earliest scheduled start: Teardown (time) | FSSAZ | TIMS | 6 | ATIME | ||||
SSSBD | Latest scheduled start: Processing (date) | SSSBD | DATS | 8 | DATUM | ||||
SSSBZ | Latest scheduled start: Processing (time) | SSSBZ | TIMS | 6 | ATIME | ||||
SSSAD | Latest scheduled start: Teardown (date) | SSSAD | DATS | 8 | DATUM | ||||
SSSAZ | Latest scheduled start: Teardown (time) | SSSAZ | TIMS | 6 | ATIME | ||||
MGVRG | Operation Quantity | MGVRG | QUAN | 13(3) | MENG13 | ||||
MEINH | Unit of Measure for Activity/Operation | VORME | UNIT | 3 | T006 | CUNIT | MEINS | ||
RSTUF | Reduction level which reduces operation lead time | RSTUF | NUMC | 1 | REDST | ||||
PLSCN | Planning Scenario of Long-Term Planning | PLSCN | NUMC | 3 | PLSC | PLSCN | PLS | ||
BSTKZ | Indicator rqmts.record is confirmed (cap.availability check) | CY_BSTKZ | CHAR | 1 | CY_BSTKZ | ||||
BEDZLF | BEDZL of Main Operation (for Phases and Their Main Ops) | BEDZLF | NUMC | 8 | CIM_COUNT | ||||
PHASE_KZ | Indicator: Phase | PHASE_KZ | CHAR | 1 | PHASE_KZ | ||||
MAXBD_KZ | Indicator: Capacity fully committed | MAXBD_KZ | CHAR | 1 | XFELD | ||||
ANZMA | Number of employees | ANZMS | DEC | 5(2) | ANZMA |
Key field | Non-key field |
How do I retrieve data from SAP structure SKBED using ABAP code?
As SKBED is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on SKBED as there is no data to select.How to access SAP table SKBED
Within an ECC or HANA version of SAP you can also view further information about SKBED and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects