CKI_MLBE SAP (Record for Table MLBE) Structure details
Description: Record for Table MLBE
Structure field list including key, data, relationships and ABAP select examples
CKI_MLBE 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 "Record for Table MLBE" 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_CKI_MLBE TYPE CKI_MLBE.
The CKI_MLBE table consists of various fields, each holding specific information or linking keys about Record for Table MLBE data available in SAP. These include MANDT (Client), MLVNR (Material ledger transaction number), VGABE (Type of Transaction in the Object History), GJAHR (Material Document Year).. 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: Not classified
SAP CKI_MLBE 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 | Assigned to domain | MANDT | |||
| MLVNR | Material ledger transaction number | CK_MLVNR | CHAR | 12 | CK_MLVNR | ||||
| VGABE | Type of Transaction in the Object History | CKI_VGABE | CHAR | 1 | CKI_VGABE | ||||
| GJAHR | Material Document Year | MJAHR | NUMC | 4 | GJAHR | GJAHR | MJA | ||
| BELNR | Number of Material Document | MBLNR | CHAR | 10 | ALPHA | BELNR | MBN | ||
| BUZEI | Item in Material Document | MBLPO | NUMC | 4 | MBLPO | POS | |||
| BEWTP | PO history category | BEWTP | CHAR | 1 | Assigned to domain | BEWTP | |||
| BUDAT | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| MENGE | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
| ZEKKN | Sequential Number of Account Assignment | DZEKKN | NUMC | 2 | NUM02 | ||||
| KALNR | Cost Estimate Number for Cost Est. w/o Qty Structure | CK_KALNR | NUMC | 12 | Assigned to domain | CK_KALNR | KNR | ||
| POPER | Posting period | POPER | NUMC | 3 | POPER | POPR | |||
| BDATJ | Posting Date YYYY | BDATJ | NUMC | 4 | GJAHR | GJAHR | BDTJ | ||
| XWOFF | Calculation of val. open | XWOFF | CHAR | 1 | XFELD | ||||
| HRKFT | Origin Group as Subdivision of Cost Element | HRKFT | CHAR | 4 | Assigned to domain | HRKFT | |||
| KSTAR | Cost Element | KSTAR | CHAR | 10 | Assigned to domain | ALPHA | KSTAR | KAT | |
| BWART | Movement Type (Inventory Management) | BWART | CHAR | 3 | Assigned to domain | BWART | BWA | ||
| CPUDT | Day On Which Accounting Document Was Entered | CPUDT | DATS | 8 | DATUM | ||||
| CPUTM | Time of Entry | CPUTM | TIMS | 6 | UZEIT |
| Key field | Non-key field |
How do I retrieve data from SAP structure CKI_MLBE using ABAP code?
As CKI_MLBE 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 CKI_MLBE as there is no data to select.How to access SAP table CKI_MLBE
Within an ECC or HANA version of SAP you can also view further information about CKI_MLBE 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