BAPICONDHD SAP (BAPI Structure of KONH with English Field Names) Structure details
Description: BAPI Structure of KONH with English Field Names
Structure field list including key, data, relationships and ABAP select examples
BAPICONDHD 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 "BAPI Structure of KONH with English Field Names" 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_BAPICONDHD TYPE BAPICONDHD.
The BAPICONDHD table consists of various fields, each holding specific information or linking keys about BAPI Structure of KONH with English Field Names data available in SAP. These include SD_DOC (Sales and Distribution Document Number), ITM_NUMBER (Item number of the SD document), COND_NO (Condition record number), CREATED_BY (Name of Person who Created the Object).. 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 BAPICONDHD 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 |
| OPERATION | Function | MSGFN | CHAR | 3 | MSGFN | ||||
| SD_DOC | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| ITM_NUMBER | Item number of the SD document | POSNR | NUMC | 6 | Assigned to domain | POSNR | |||
| COND_NO | Condition record number | KNUMH | CHAR | 10 | KNUMB | ||||
| CREATED_BY | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| CREAT_DATE | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| COND_USAGE | Usage of the condition table | KVEWE | CHAR | 1 | T681V | KVEWE | KVW | ||
| TABLE_NO | Condition table | KOTABNR | NUMC | 3 | T681 | KOTABNR | KON | ||
| APPLICATIO | Application | KAPPL | CHAR | 2 | T681A | KAPPL | KAP | ||
| COND_TYPE | Condition type | KSCHA | CHAR | 4 | Assigned to domain | KSCHL | VKS | ||
| VARKEY | Character 100 | CHAR100 | CHAR | 100 | CHAR100 | ||||
| VALID_FROM | Valid-From Date | DATAB | DATS | 8 | DATUM | ||||
| VALID_TO | Valid To Date | DATBI | DATS | 8 | DATUM | ||||
| SEARCHTERM | Search term for conditions | KOSRT | CHAR | 10 | CHAR10 | ||||
| RESPONS | Responsibility in SD for condition/material | KZUST | CHAR | 3 | T686C | KZUST | |||
| PROMOT_NO | Promotion | KNUMA_PI | CHAR | 10 | KONA | ALPHA | KNUMA | VPI | VMBO |
| SALES_DEAL | Sales deal | KNUMA_AG | CHAR | 10 | KONA | ALPHA | KNUMA | VK1 | VMBO |
| SALESQUOTE | Sales quote | KNUMA_SQ | CHAR | 10 | KONA | ALPHA | KNUMA | VK3 | VMBO |
| STD_AGRMNT | Standard agreement | KNUMA_SD | CHAR | 10 | KONA | ALPHA | KNUMA | VK2 | VMBO |
| PROMOTION | COUPON | WAKTION | CHAR | 10 | Assigned to domain | ALPHA | WAKTION | WAK | |
| REBAGREEMT | Agreement (subsequent settlement) | KNUMA_BO | CHAR | 10 | KONA | ALPHA | KNUMA | VBO | VMBO |
| LIC_NO | Tax exemption license number | LICNO | CHAR | 20 | LICNO | ||||
| LIC_DATE | Date license granted | LICDT | DATS | 8 | DATUM | ||||
| VARDATE | Character 100 | CHAR100 | CHAR | 100 | CHAR100 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPICONDHD using ABAP code?
As BAPICONDHD 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 BAPICONDHD as there is no data to select.How to access SAP table BAPICONDHD
Within an ECC or HANA version of SAP you can also view further information about BAPICONDHD 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