MCKENNZVB SAP (Key Figure Information for Update Routine) Structure details
Description: Key Figure Information for Update Routine
Structure field list including key, data, relationships and ABAP select examples
MCKENNZVB 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 "Key Figure Information for Update Routine" 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_MCKENNZVB TYPE MCKENNZVB.
The MCKENNZVB table consists of various fields, each holding specific information or linking keys about Key Figure Information for Update Routine data available in SAP. These include KENNI (Key figure in the Logistics Information Library (LIL)), LRTAB (Reference table in Logistics Information System), LRNAM (Reference field in the Logistics Information System (LIS)), RTART (Execution type (transaction, program, and so on)).. 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: Cannot Be Enhanced
SAP MCKENNZVB 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 |
| KENNI | Key figure in the Logistics Information Library (LIL) | KENNZ | CHAR | 8 | Assigned to domain | ALPHA | KENNZ | KNZ | |
| LRTAB | Reference table in Logistics Information System | LRTAB | CHAR | 30 | Assigned to domain | AS4TAB | |||
| LRNAM | Reference field in the Logistics Information System (LIS) | LRNAM | CHAR | 30 | Assigned to domain | FDNAME | |||
| RTART | Execution type (transaction, program, and so on) | RTART | CHAR | 1 | RTART | ||||
| RTNAM | ABAP Program Name | PROGRAMM | CHAR | 40 | Assigned to domain | PROGRAMM | RID | ||
| TBNAM | Table Name | TABNAME | CHAR | 30 | Assigned to domain | AS4TAB | DTB | ||
| TCODE | Transaction Code | TCODE | CHAR | 20 | Assigned to domain | TCODE | TCD | ||
| SELSC | Access program w/o selection screen | SLSCR | CHAR | 1 | SELSC | ||||
| VARNA | ABAP variant name | VARNA | CHAR | 14 | CHAR14 | ||||
| KLA01 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA02 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA03 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA04 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA05 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA06 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA07 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA08 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA09 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| KLA10 | Classifying byte | KLASB | RAW | 1 | KLASB | ||||
| APPLI | Number of application | MCAPP | CHAR | 2 | Assigned to domain | MCAPP | MCC | ||
| ZAEHL | Counter of the calls in the Logistics Information Library | DZAEH1 | CHAR | 8 | CHAR8 | ||||
| AENDP | Last person to change the key figure/information item | LAEND | CHAR | 12 | CHAR12 | ||||
| AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| TEXTZ | Description of key figure | KENNT | CHAR | 60 | TEXT60 | ||||
| MCANA | Number of standard analysis | MCANA | CHAR | 4 | Assigned to domain | MCANALYSE | MCG | ||
| MCAPPL | Number of application | MCAPP | CHAR | 2 | Assigned to domain | MCAPP | MCC | ||
| ACTYP | Activity Type for Transactions | ACTYP | CHAR | 1 | CHAR1 | ||||
| LANGU | Language Key | LANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS |
| Key field | Non-key field |
How do I retrieve data from SAP structure MCKENNZVB using ABAP code?
As MCKENNZVB 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 MCKENNZVB as there is no data to select.How to access SAP table MCKENNZVB
Within an ECC or HANA version of SAP you can also view further information about MCKENNZVB 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