MMPA SAP (Communication Structure: Partners in MM Area) Structure details
Description: Communication Structure: Partners in MM Area
Structure field list including key, data, relationships and ABAP select examples
MMPA 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: Partners in MM Area" 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_MMPA TYPE MMPA.
The MMPA table consists of various fields, each holding specific information or linking keys about Communication Structure: Partners in MM Area data available in SAP. These include EBELN (Purchasing Document Number), EBELP (Item Number of Purchasing Document), EKORG (Purchasing Organization), LTSNR (Vendor Subrange).. 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)
SAP MMPA 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 | Assigned to domain | MANDT | |||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| LTSNR | Vendor Subrange | LTSNR | CHAR | 6 | Assigned to domain | LTSNR | |||
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| KNUMA | Agreement (various conditions grouped together) | KNUMA | CHAR | 10 | Assigned to domain | ALPHA | KNUMA | VMBO | |
| PARVW | Partner Function | PARVW | CHAR | 2 | Assigned to domain | 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 | ||||
| LIFN2 | Reference to other vendor | LIFN2 | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
| DEFPA | Default Partner | DEFPA | CHAR | 1 | XFELD | ||||
| HITYP | Hierarchy category: vendor hierarchy | HITYP_LH | CHAR | 1 | Assigned to domain | HITYP_LH | HITYP_LH | ||
| PARNR | Number of contact person | PARNR | NUMC | 10 | PARNR | VPA | |||
| PERNR | Personnel Number | PERNR_D | NUMC | 8 | PERNR | PER | |||
| PRFRE | Indicator: 'relev. to price determination (vend. hierarchy) | PRFRE_LH | CHAR | 1 | XFELD | ||||
| BOLRE | Indicator: vendor subject to subseq. settlement accounting | BOLRE | CHAR | 1 | XFELD | ||||
| HISTUNR | Level number within hierarchy | HISTUNR | NUMC | 2 | NUM2 |
| Key field | Non-key field |
How do I retrieve data from SAP structure MMPA using ABAP code?
As MMPA 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 MMPA as there is no data to select.How to access SAP table MMPA
Within an ECC or HANA version of SAP you can also view further information about MMPA 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