MSGPA SAP (Output partner) Structure details
Description: Output partner
Structure field list including key, data, relationships and ABAP select examples
MSGPA 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 "Output partner" 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_MSGPA TYPE MSGPA.
The MSGPA table consists of various fields, each holding specific information or linking keys about Output partner data available in SAP. These include PARVW (Partner Function), PARNO (Partner number (KUNNR, LIFNR, or PERNR)), NAME1 (Name 1 of a partner), TELFX (Fax Number).. 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 MSGPA 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 |
| PARVW | Partner Function | PARVW | CHAR | 2 | TPAR | PARVW | PARVW | PAR | |
| PARNO | Partner number (KUNNR, LIFNR, or PERNR) | KUNDE_D | CHAR | 10 | ALPHA | KUNDE | |||
| NAME1 | Name 1 of a partner | NAME1_VP | CHAR | 35 | NAME | ||||
| TELFX | Fax Number | TELFX | CHAR | 31 | TEXT31 | ||||
| TELTX | Teletex number | TELTX | CHAR | 30 | TEXT30 | ||||
| TELX1 | Telex number | TELX1 | CHAR | 30 | TEXT30 | ||||
| SPRAS | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| ED_APPLID | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| ED_ORGID | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| ED_PARTART | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| LAND1 | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| ADDRTYPE | Address type (1=Organization, 2=Person, 3=Contact person) | AD_ADRTYPE | CHAR | 1 | AD_ADRTYPE | ||||
| ADDRNUMBER | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| PERSNUMBER | Person number | AD_PERSNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_PERSNUM | CDT | ADDRESS |
| Key field | Non-key field |
How do I retrieve data from SAP structure MSGPA using ABAP code?
As MSGPA 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 MSGPA as there is no data to select.How to access SAP table MSGPA
Within an ECC or HANA version of SAP you can also view further information about MSGPA 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