LBPKOND SAP (Communication structure for conditions for layout area items) Structure details
Description: Communication structure for conditions for layout area items
Structure field list including key, data, relationships and ABAP select examples
LBPKOND 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 "Communication structure for conditions for layout area items" 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_LBPKOND TYPE LBPKOND.
The LBPKOND table consists of various fields, each holding specific information or linking keys about Communication structure for conditions for layout area items data available in SAP. These include MEINH (Unit of Measure for Display), WAERS (Currency key for product catalog variant), WAERS_EWU (Currency key for parallel currency), KSCHL (Condition Type).. 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 LBPKOND 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 |
MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
MEINH | Unit of Measure for Display | MEINH | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
WAERS | Currency key for product catalog variant | WMVWAERS | CUKY | 5 | Assigned to domain | WAERS | |||
WAERS_EWU | Currency key for parallel currency | WMVWAERS_EWU | CUKY | 5 | Assigned to domain | WAERS | |||
KSCHL | Condition Type | KSCHL | CHAR | 4 | Assigned to domain | KSCHL | VKS | ||
VBETR | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
VBETR_EWU | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
KBETR | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
KBETR_EWU | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
ABETR | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
ABETR_EWU | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
KFEHL | Price does not exist | KFEHL | CHAR | 1 | CHAR1 | ||||
KZWI2 | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
KZWI3 | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
KZWI4 | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
KZWI5 | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
KZWI6 | Rate (condition amount or percentage) | KBETR | CURR | 11(2) | WERTV6 | ||||
KFEHL_ZWI1 | Price does not exist | KFEHL | CHAR | 1 | CHAR1 | ||||
KFEHL_ZWI2 | Price does not exist | KFEHL | CHAR | 1 | CHAR1 | ||||
KFEHL_ZWI3 | Price does not exist | KFEHL | CHAR | 1 | CHAR1 | ||||
KFEHL_ZWI4 | Price does not exist | KFEHL | CHAR | 1 | CHAR1 | ||||
KFEHL_ZWI5 | Price does not exist | KFEHL | CHAR | 1 | CHAR1 | ||||
KFEHL_ZWI6 | Price does not exist | KFEHL | CHAR | 1 | CHAR1 | ||||
AKTNR | COUPON | WAKTION | CHAR | 10 | Assigned to domain | ALPHA | WAKTION | WAK |
Key field | Non-key field |
How do I retrieve data from SAP structure LBPKOND using ABAP code?
As LBPKOND 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 LBPKOND as there is no data to select.How to access SAP table LBPKOND
Within an ECC or HANA version of SAP you can also view further information about LBPKOND 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