MCKONACHK SAP (LIS Characteristics: Subsequent Settlement) Structure details
Description: LIS Characteristics: Subsequent Settlement
Structure field list including key, data, relationships and ABAP select examples
MCKONACHK 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 "LIS Characteristics: Subsequent Settlement" 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_MCKONACHK TYPE MCKONACHK.
The MCKONACHK table consists of various fields, each holding specific information or linking keys about LIS Characteristics: Subsequent Settlement data available in SAP. These include KNUMH (Condition record number), KOPOS (Sequential number of the condition), LIFNR (Vendor (PO, vendor billing document, settlement request)), MWSKZ (Tax on sales/purchases code).. 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 MCKONACHK 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 |
KNUMA | Agreement (subsequent settlement) | KNUMA_BO | CHAR | 10 | KONA | ALPHA | KNUMA | VBO | VMBO |
KNUMH | Condition record number | KNUMH | CHAR | 10 | KNUMB | ||||
KOPOS | Sequential number of the condition | KOPOS | NUMC | 2 | NUM02 | ||||
LIFNR | Vendor (PO, vendor billing document, settlement request) | BELIF | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
MWSKZ | Tax on sales/purchases code | MWSKZ | CHAR | 2 | Assigned to domain | MWSKZ | |||
WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
BOLIF | Settlement partner (vendor or customer) | BOPAR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
MATKL | Material Group | MATKL | CHAR | 9 | T023 | MATKL | MKL | S_WBWG | |
EKORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
EKGRP | Purchasing Group | EKGRP | CHAR | 3 | T024 | EKGRP | EKG | ||
DATBI | End date of validity period of an arrangement | MC_DATBI | DATS | 8 | DATUM | ||||
VKORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
VTWEG | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
SPART | Division | SPART | CHAR | 2 | TSPA | SPART | SPA | C_SPART | |
KUNRE | Bill-to party | KUNRE | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN |
Key field | Non-key field |
How do I retrieve data from SAP structure MCKONACHK using ABAP code?
As MCKONACHK 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 MCKONACHK as there is no data to select.How to access SAP table MCKONACHK
Within an ECC or HANA version of SAP you can also view further information about MCKONACHK 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