KOMKH SAP (Batch Determination Communication Block Header) Structure details
Description: Batch Determination Communication Block Header
Structure field list including key, data, relationships and ABAP select examples
KOMKH 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 "Batch Determination Communication Block Header" 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_KOMKH TYPE KOMKH.
The KOMKH table consists of various fields, each holding specific information or linking keys about Batch Determination Communication Block Header data available in SAP. These include KNDNR (Customer number), KNRZE (Payer), KUNRE (Bill-to party), KUNWE (Ship-to party).. 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)
SAP KOMKH 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 | |||
KNDNR | Customer number | KUNNR_V | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
KNRZE | Payer | KUNRG | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
KUNRE | Bill-to party | KUNRE | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
KUNWE | Ship-to party | KUNWE | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | C_KUNNR |
SPDNR | Forwarding agent | SPDNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
VRTNR | Sales employee | VRTNR | NUMC | 8 | PERNR | PREMV | |||
LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
VBELN | Sales and Distribution Document Number | VBELN | CHAR | 10 | VBUK | ALPHA | VBELN | AUN | |
POSNR | Item number of the SD document | POSNR | NUMC | 6 | VBUP | POSNR | |||
PSPNR | Work Breakdown Structure Element (WBS Element) | PS_PSP_PNR | NUMC | 8 | Assigned to domain | KONPR | PS_POSNR | ||
VKORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
VTWEG | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
SPART | Division in the order header | SPARK | CHAR | 2 | TSPA | SPART | |||
EKORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
VKBUR | Sales Office | VKBUR | CHAR | 4 | TVBUR | VKBUR | VKB | ||
VKGRP | Sales Group | VKGRP | CHAR | 3 | TVKGR | VKGRP | VKG | ||
KDGRP | Customer group | KDGRP | CHAR | 2 | T151 | KDGRP | VKD | ||
BZIRK | Sales district | BZIRK | CHAR | 6 | T171 | BZIRK | BZI | ||
ALAND | Departure country (country from which the goods are sent) | ALAND | CHAR | 3 | T005 | LAND1 | VAL | ||
WKREG | Region in which plant is located | WKREG | CHAR | 3 | T005S | REGIO | |||
WKCOU | County in which plant is located | WKCOU | CHAR | 3 | CHAR3 | ||||
WKCTY | City in which plant is located | WKCTY | CHAR | 4 | CHAR4 | ||||
INCO1 | Incoterms (Part 1) | INCO1 | CHAR | 3 | TINC | INCO1 | |||
INCO2 | Incoterms (Part 2) | INCO2 | CHAR | 28 | INCO2 | ||||
LAND1 | Country of Destination | LLAND | CHAR | 3 | T005 | LAND1 | VLL | ||
REGIO | STATE (State, Province, County) | REGIO | CHAR | 3 | T005S | REGIO | |||
COUNC | County Code | COUNC | CHAR | 3 | T005E | COUNC | |||
CITYC | City Code | CITYC | CHAR | 4 | T005G | CITYC | |||
AUART | Order Type | AUFART | CHAR | 4 | T003O | AUFART | AAT | ||
AUTYP | Order category | AUFTYP | NUMC | 2 | AUFTYP | ||||
VSBED | Shipping Conditions | VSBED | CHAR | 2 | TVSB | VSBED | |||
HIENR01 | Customer hierarchy 1 | HIENR01 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR02 | Customer hierarchy 2 | HIENR02 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR03 | Customer hierarchy 3 | HIENR03 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR04 | Customer hierarchy 4 | HIENR04 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR05 | Customer hierarchy 5 | HIENR05 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR06 | Customer hierarchy 6 | HIENR06 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR07 | Customer hierarchy 7 | HIENR07 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR08 | Customer hierarchy 8 | HIENR08 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR09 | Customer heirarchy 9 | HIENR09 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR10 | Customer hierarchy 10 | HIENR10 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR11 | Customer hierarchy 11 | HIENR11 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR12 | Customer hierarchy 12 | HIENR12 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR13 | Customer hierarchy 13 | HIENR13 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR14 | Customer hierarchy 14 | HIENR14 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIENR15 | Customer hierarchy 15 | HIENR15 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO01 | Customer hierarchy 1 | HIENR01 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO02 | Customer hierarchy 2 | HIENR02 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO03 | Customer hierarchy 3 | HIENR03 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO04 | Customer hierarchy 4 | HIENR04 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO05 | Customer hierarchy 5 | HIENR05 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO06 | Customer hierarchy 6 | HIENR06 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO07 | Customer hierarchy 7 | HIENR07 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO08 | Customer hierarchy 8 | HIENR08 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO09 | Customer heirarchy 9 | HIENR09 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO10 | Customer hierarchy 10 | HIENR10 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO11 | Customer hierarchy 11 | HIENR11 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO12 | Customer hierarchy 12 | HIENR12 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO13 | Customer hierarchy 13 | HIENR13 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO14 | Customer hierarchy 14 | HIENR14 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
HIEBO15 | Customer hierarchy 15 | HIENR15 | CHAR | 10 | KNA1 | ALPHA | KUNNR | ||
LGNUM | Warehouse Number / Warehouse Complex | LGNUM | CHAR | 3 | T300 | LGNUM | LGN | ||
BWLVS | Movement Type for Warehouse Management | BWLVS | NUMC | 3 | T333 | BWLVS | BWL | ||
AUART_SD | Sales Document Type | AUART | CHAR | 4 | TVAK | AUART | AUART | AAT | |
AUFNR | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
KDUMMY | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY |
Key field | Non-key field |
How do I retrieve data from SAP structure KOMKH using ABAP code?
As KOMKH 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 KOMKH as there is no data to select.How to access SAP table KOMKH
Within an ECC or HANA version of SAP you can also view further information about KOMKH 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