KOMEXP SAP (Trading Contract: IO Structure of Planned Costs) Structure details
Description: Trading Contract: IO Structure of Planned Costs
Structure field list including key, data, relationships and ABAP select examples
KOMEXP 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 "Trading Contract: IO Structure of Planned Costs" 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_KOMEXP TYPE KOMEXP.
The KOMEXP table consists of various fields, each holding specific information or linking keys about Trading Contract: IO Structure of Planned Costs data available in SAP. These include KOTABNR (Condition table), KOPOS (Sequential number of the condition), TKONN (Trading Contract: Trading Contract Number), EPOSN (Condition counter).. 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 KOMEXP 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 |
KNUMH | Condition record number | KNUMH | CHAR | 10 | KNUMB | ||||
KOTABNR | Condition table | KOTABNR | NUMC | 3 | Assigned to domain | KOTABNR | KON | ||
KOPOS | Sequential number of the condition | KOPOS | NUMC | 2 | NUM02 | ||||
TKONN | Trading Contract: Trading Contract Number | TKONN | CHAR | 10 | Assigned to domain | ALPHA | TKONN | WKN | WBHK |
EPOSN | Condition counter | DZAEHK | NUMC | 2 | ZAEHK | ||||
KOBOG | Condition type/table group for agreements | KOBOG | CHAR | 4 | T6B2 | KOBOG | |||
WEXTYP | Trading Contract: Expense Type | WEXTYP | CHAR | 1 | WEXTYP | WEX | |||
KAPPL | Application | KAPPL | CHAR | 2 | Assigned to domain | KAPPL | KAP | ||
KSCHL | Condition type | KSCHA | CHAR | 4 | T685 | KSCHL | VKS | ||
LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
ZTERM | Terms of Payment Key | DZTERM | CHAR | 4 | ZTERM | ||||
VALDT | Fixed value date | VALDT | DATS | 8 | DATUM | ||||
KDATU | Condition pricing date | KDATU | DATS | 8 | DATUM | ||||
KRECH | Calculation type for condition | KRECH | CHAR | 1 | KRECH | ||||
KBETR | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
WAERS | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
KKURS | Condition exchange rate for conversion to local currency | KKURS | DEC | 9(5) | KKURS | ||||
KPEIN | Condition pricing unit | KPEIN | DEC | 5 | KPEIN | ||||
KMEIN | Condition unit in the document | KVMEI | UNIT | 3 | T006 | CUNIT | MEINS | ||
KUMZA | Numerator for converting condition units to base units | KUMZA | DEC | 5 | UMBSZ | ||||
KUMNE | Denominator for converting condition units to base units | KUMNE | DEC | 5 | UMBSN | ||||
KNTYP | Condition category (examples: tax, freight, price, cost) | KNTYP | CHAR | 1 | KNTYP | ||||
KSTAT | Condition is used for statistics | KSTAT | CHAR | 1 | XFELD | ||||
KNPRS | Scale Type | STFKZ | CHAR | 1 | STFKZ | ||||
UPDKZ | Update indicator | UPDKZ_D | CHAR | 1 | UPDKZ | ||||
CREAT | General Flag | FLAG | CHAR | 1 | FLAG | ||||
LOEVM_KO | Deletion Indicator for Condition Item | LOEVM_KO | CHAR | 1 | XFELD | ||||
ZAEHK | Condition counter | DZAEHK | NUMC | 2 | ZAEHK | ||||
LIEF_NAME1 | Name 1 | AD_NAME1 | CHAR | 40 | TEXT40 | ||||
DISP_TKWAERS | Trading Contract: Currency of Trading Contract | TKWAERS | CUKY | 5 | Assigned to domain | WAERS | |||
DISP_MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
DISP_VTEXT | Name | VTXTK | CHAR | 20 | TEXT20 | ||||
BEZ_WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
BEZ_KEY | Description | BEZEI100 | CHAR | 100 | TEXT100 | ||||
VAKEY | Variable key 100 bytes | VAKEY | CHAR | 100 | VAKEY | ||||
BEZ_EXP_CL_GROUP | Description | BEZEI20 | CHAR | 20 | TEXT20 | ||||
BEZ_EXP_CLASS | Description | BEZEI20 | CHAR | 20 | TEXT20 | ||||
BEZ_ACC_TYPE | Description | BEZEI20 | CHAR | 20 | TEXT20 | ||||
BEZ_POSTTYPE | Description | BEZEI20 | CHAR | 20 | TEXT20 | ||||
.INCLU--AP | 0 | ||||||||
TEW_TYPE | Trading Execution Workbench Type | WB2_TEW_TYPE | CHAR | 4 | TEWTYPE | WB2_TEW_TYPE | TEW_TYPE2 | S_TEWTYPE | |
EXP_CLASS | GT Expenses: Expense Class | WB2_EXPENSE_CLASS | CHAR | 3 | TWBEXCLASS | WB2_EXPENSE_CLASS | EXP_CLASS | ||
ACCOUNT_TYPE | GT Expenses: Accounting Type for Expenses | WB2_EXPENSES_ACCOUNT_TYPE | CHAR | 1 | TWBACCTYPE | WB2_EXPENSES_ACCOUNT_TYPE | |||
POST_TYPE | GT Expenses: Posting Type of Expenses | WB2_EXPENSE_POSTING_TYPE | CHAR | 1 | TWBPOSTTYPE | WB2_EXPENSE_POSTING_TYPE | |||
TCTYP | Trading Contract: Trading Contract Type | TCTYP | CHAR | 4 | Assigned to domain | TCTYP | WKA | ||
UASTA | Status of business volume comparison for a condition | UASTA | CHAR | 1 | UASTA | ||||
PARTNER | Partner number | PARTNER_EXP | CHAR | 10 | ALPHA | PARTNER_EXP | |||
BOMAT | Material for rebate settlement | BOMAT | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | |
EXP_CLASS_GROUP | Expense Class Group | WB2_EXPENSE_CLASS_GROUP | CHAR | 2 | Assigned to domain | WB2_EXPENSE_CLASS_GROUP | S_TWBEXCLASSGROUP | ||
PO_TYPE_GROUP | GT Expenses: Posting Type Group | WB2_EXPENSE_POST_TYPE_GROUP | CHAR | 1 | Assigned to domain | WB2_EXPENSE_POST_TYPE_GROUP | |||
TEXT | Text, 40 Characters Long | TEXT40 | CHAR | 40 | TEXT40 | ||||
BEZEI_PARTNER | Address line | LINES | CHAR | 80 | LINES | ||||
REFERENCE_ID | BusinessTransactionDocumentID | WLF_REF_ID | CHAR | 35 |
Key field | Non-key field |
How do I retrieve data from SAP structure KOMEXP using ABAP code?
As KOMEXP 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 KOMEXP as there is no data to select.How to access SAP table KOMEXP
Within an ECC or HANA version of SAP you can also view further information about KOMEXP 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