KOMLFPA SAP (Communication structure, partner vendor billing document) Structure details
Description: Communication structure, partner vendor billing document
Structure field list including key, data, relationships and ABAP select examples
KOMLFPA 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, partner vendor billing document" 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_KOMLFPA TYPE KOMLFPA.
The KOMLFPA table consists of various fields, each holding specific information or linking keys about Communication structure, partner vendor billing document data available in SAP. These include MANDT (Client), WBELN (Agency Business: Document Number), POSNR (Agency business: Document item), PARVW (Partner Function).. 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 KOMLFPA 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 | |||
| WBELN | Agency Business: Document Number | WBELN_AG | CHAR | 10 | WBRK | ALPHA | WBELN | ||
| POSNR | Agency business: Document item | WPOSNR_LF | NUMC | 6 | WBRP | WPOSNR | |||
| PARVW | Partner Function | PARVW | CHAR | 2 | TPAR | PARVW | PARVW | PAR | |
| PARZA | Partner counter | PARZA | NUMC | 3 | PARZA | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| LIFNR | Reference to other vendor | LIFN2 | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
| KUNNR | Customer number of business partner | KUNN2 | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
| DEFPA | Default Partner | DEFPA | CHAR | 1 | XFELD | ||||
| PARNR | Number of contact person | PARNR | NUMC | 10 | KNVK | PARNR | VPA | ||
| PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
| ADRNR | Address | ADRNR | CHAR | 10 | Assigned to domain | ALPHA | ADRNR | ||
| XCPDK | Indicator: Is the account a one-time account? | XCPDK | CHAR | 1 | XFELD | ||||
| STCEG | VAT Registration Number | STCEG | CHAR | 20 | STCEG | ||||
| ADRDA | Address indicator | ADRDA | CHAR | 1 | ADRDA | ||||
| PLACE_HOLDER | Not Used | 0 | |||||||
| NAME1 | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| NRART | Type of partner number | NRART | CHAR | 2 | Assigned to domain | NRART | |||
| PARVW_TEXT | Name | VTXTK | CHAR | 20 | TEXT20 | ||||
| SORT | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| ICON_PARTNER | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
| ICON_ADDRESS | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
| UPDKZ | Update indicator | UPDKZ_D | CHAR | 1 | UPDKZ | ||||
| ENHANCED | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| PARTNER | Partner number (KUNNR, LIFNR, or PERNR) | KUNDE_D | CHAR | 10 | ALPHA | KUNDE |
| Key field | Non-key field |
How do I retrieve data from SAP structure KOMLFPA using ABAP code?
As KOMLFPA 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 KOMLFPA as there is no data to select.How to access SAP table KOMLFPA
Within an ECC or HANA version of SAP you can also view further information about KOMLFPA 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