SMSKU SAP (Lock Table MSKU) Structure details
Description: Lock Table MSKU
Structure field list including key, data, relationships and ABAP select examples
SMSKU 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 "Lock Table MSKU" 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_SMSKU TYPE SMSKU.
The SMSKU table consists of various fields, each holding specific information or linking keys about Lock Table MSKU data available in SAP. These include WERKS (Plant), CHARG (Batch Number), SOBKZ (Special Stock Indicator), KUNNR (Customer Numbers).. 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 SMSKU 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 |
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| CHARG | Batch Number | CHARG_D | CHAR | 10 | Assigned to domain | CHARG | CHA | ||
| SOBKZ | Special Stock Indicator | SOBKZ | CHAR | 1 | Assigned to domain | SOBKZ | |||
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| RMSKU | Return code MSKU | RMSKU | CHAR | 1 | XFELD | ||||
| XDBUP | Database update | XDBUP | CHAR | 1 | XFELD | ||||
| LFGJA | Fiscal Year of Current Period | LFGJA | NUMC | 4 | GJAHR | GJAHR | |||
| LFMON | Current period (posting period) | LFMON | NUMC | 2 | MONAT | ||||
| KULAB | Valuated Unrestricted-Use Stock | LABST | QUAN | 13(3) | MENG13V | ||||
| KUINS | Stock in Quality Inspection | INSME | QUAN | 13(3) | MENG13V | ||||
| KUEIN | Total Stock of All Restricted Batches | EINME | QUAN | 13(3) | MENG13V | ||||
| KUVLA | Valuated unrestricted-use stock in previous period | VMLAB | QUAN | 13(3) | MENG13V | ||||
| KUVIN | Stock in Quality Inspection in Previous Period | VMINS | QUAN | 13(3) | MENG13V | ||||
| KUVEI | Restricted-Use Stock in Previous Period | VMEIN | QUAN | 13(3) | MENG13V | ||||
| KULAB_OLD | Valuated Unrestricted-Use Stock | LABST | QUAN | 13(3) | MENG13V | ||||
| KUINS_OLD | Stock in Quality Inspection | INSME | QUAN | 13(3) | MENG13V | ||||
| KUEIN_OLD | Total Stock of All Restricted Batches | EINME | QUAN | 13(3) | MENG13V | ||||
| KUVLA_OLD | Valuated unrestricted-use stock in previous period | VMLAB | QUAN | 13(3) | MENG13V | ||||
| KUVIN_OLD | Stock in Quality Inspection in Previous Period | VMINS | QUAN | 13(3) | MENG13V | ||||
| KUVEI_OLD | Restricted-Use Stock in Previous Period | VMEIN | QUAN | 13(3) | MENG13V | ||||
| RMSKUH | Data content X or blank | XWERT | CHAR | 1 | XFELD | ||||
| KULFM | Current period (posting period) | LFMON | NUMC | 2 | MONAT | ||||
| KUGJA | Fiscal Year of Current Period | LFGJA | NUMC | 4 | GJAHR | GJAHR | |||
| KURUE | MxxxH rec. already exists for per. before last of Mxxx per. | SBRUE | CHAR | 1 | XFELD | ||||
| KUUML | Stock in Transfer for Customer Consignment (Plant to Plant) | UMLME_W | QUAN | 13(3) | MENG13V | ||||
| KUUML_OLD | Stock in Transfer for Customer Consignment (Plant to Plant) | UMLME_W | QUAN | 13(3) | MENG13V | ||||
| KUVUM | Stock in Transfer in Previous Period | VMUML | QUAN | 13(3) | MENG13V | ||||
| KUVUM_OLD | Stock in Transfer in Previous Period | VMUML | QUAN | 13(3) | MENG13V |
| Key field | Non-key field |
How do I retrieve data from SAP structure SMSKU using ABAP code?
As SMSKU 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 SMSKU as there is no data to select.How to access SAP table SMSKU
Within an ECC or HANA version of SAP you can also view further information about SMSKU 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