KARTE SAP (Kanban Data Structure) Structure details
Description: Kanban Data Structure
Structure field list including key, data, relationships and ABAP select examples
KARTE 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 "Kanban Data Structure" 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_KARTE TYPE KARTE.
The KARTE table consists of various fields, each holding specific information or linking keys about Kanban Data Structure data available in SAP. These include BARC1 (Bar code for setting to the status 'waiting'), BARCL (Set bar code to empty), BARC3 (Bar code for setting to the status 'In process'), BARCA (Bar code for setting to in process / in transit).. 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 KARTE 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 |
BARC0 | Bar code for status sequence | BARC0 | NUMC | 11 | BARC1 | ||||
BARC1 | Bar code for setting to the status 'waiting' | BARC1 | NUMC | 11 | BARC1 | ||||
BARCL | Set bar code to empty | BARCL | NUMC | 11 | BARC1 | ||||
BARC3 | Bar code for setting to the status 'In process' | BARC3 | NUMC | 11 | BARC1 | ||||
BARCA | Bar code for setting to in process / in transit | BARCA | NUMC | 11 | BARC1 | ||||
BARCV | Set bar code to full | BARCV | NUMC | 11 | BARC1 | ||||
BARC6 | Bar code for setting to the status 'In use' | BARC6 | NUMC | 11 | BARC1 | ||||
MAKTX | Material Description (Short Text) | MAKTX | CHAR | 40 | TEXT40 | ||||
PVBTX | Production supply area description | PVBTX | CHAR | 40 | TEXT40 | ||||
PKPOS | Kanban item number / control cycle item | PKPOS | NUMC | 3 | PKPOS | ||||
MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
PRVBE | Production Supply Area | PRVBE | CHAR | 10 | Assigned to domain | PRVBE | PVB | ||
BEHTX | Material Description (Short Text) | MAKTX | CHAR | 40 | TEXT40 | ||||
WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
BEHMG | Kanban Quantity | BEHMG | QUAN | 13(3) | MENG13 | ||||
MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
INHLT | Contents of a kanban container C10 | INHLT | CHAR | 10 | CHAR010 | ||||
RGVER | Person responsible for one or more supply areas | RGVER | CHAR | 3 | Assigned to domain | DISPO | DGR | ||
LGORT | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
NAME1 | Name 1 | NAME1_BAS | CHAR | 35 | NAME | ||||
NAME2 | Name 2 | NAME2_BAS | CHAR | 35 | NAME | ||||
NAME3 | Name 3 | NAME3_BAS | CHAR | 35 | NAME | ||||
NAME4 | Name 4 | NAME4_BAS | CHAR | 35 | NAME | ||||
ANZLT | Number of Load Carriers | ANZLT | NUMC | 3 | ANZLT | ||||
TAGIDHEX | Tag ID (Hexadecimal Format) | TAGIDHEX | RAW | 24 | TAGIDHEX | ||||
TAGIDTEXT | Tag ID (Text Format) | TAGIDTEXT | CHAR | 50 | TAGIDTEXT | ||||
.INCLU--AP | 0 | ||||||||
KANBAN_DUMMY | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 |
Key field | Non-key field |
How do I retrieve data from SAP structure KARTE using ABAP code?
As KARTE 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 KARTE as there is no data to select.How to access SAP table KARTE
Within an ECC or HANA version of SAP you can also view further information about KARTE 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