MSG01 SAP (Display Outputs) Structure details
Description: Display Outputs
Structure field list including key, data, relationships and ABAP select examples
MSG01 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 "Display Outputs" 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_MSG01 TYPE MSG01.
The MSG01 table consists of various fields, each holding specific information or linking keys about Display Outputs data available in SAP. These include OBJECTKEY (Object key), TYPE (Output Type), LANGUAGE (Message language), PARTNER (Message partner).. 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 MSG01 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 |
| APPL | Application for output conditions | NA_KAPPL | CHAR | 2 | Assigned to domain | KAPPL | NA_KAPPL | ||
| OBJECTKEY | Object key | NA_OBJKEY | CHAR | 30 | NA_OBJKEY | ||||
| TYPE | Output Type | NA_KSCHL | CHAR | 4 | Assigned to domain | KSCHL | NAC | CSH_NA_KSCHL | |
| LANGUAGE | Message language | NA_SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
| PARTNER | Message partner | NA_PARNR | CHAR | 10 | ALPHA | NA_PARNR | |||
| FUNCTION | Partner Function | PARVW | CHAR | 2 | Assigned to domain | PARVW | PARVW | PAR | |
| DATE | Date on which status record was created | NA_ERDAT | DATS | 8 | DATUM | ||||
| TIME | Time at which status record was created | NA_ERUHR | TIMS | 6 | UZEIT | ||||
| MEDIUM | Message transmission medium | NA_NACHA | CHAR | 1 | NA_NACHA | ||||
| NUMBER | Number of messages (original + copies) | NA_ANZAL | DEC | 2 | DEC2 | ||||
| TIMEFLAG | Dispatch time | NA_VSZTP | CHAR | 1 | NA_VSZTP | ||||
| STATUS | Processing status of message | NA_VSTAT | CHAR | 1 | NA_VSTAT | ||||
| PRINTER | Spool: Output device | RSPOPNAME | CHAR | 4 | Assigned to domain | SPDEV | RSPOPNAME | ||
| SPOOL | Spool request: Name | RSPO0NAME | CHAR | 6 | CHAR6 | ||||
| SUFFIX1 | Spool request: Suffix 1 | RSPO1NAME | CHAR | 4 | CHAR4 | ||||
| SUFFIX2 | Spool request: Suffix 2 | RSPO2NAME | CHAR | 12 | CHAR12 | ||||
| DELETE | Release after output | TDDELETE | CHAR | 1 | TDBOOL | ||||
| IMMED | Print immediately | TDIMMED | CHAR | 1 | TDBOOL | ||||
| RECEIVER | Spool Recipient Name | SYPRREC | CHAR | 12 | SYCHAR12 | ||||
| DIVISION | Spool Department Name | SYPRABT | CHAR | 12 | SYCHAR12K | ||||
| COVER | Print: SAP cover page | SYPRSAP | CHAR | 1 | SYPRSAP | ||||
| COVERTITLE | Spool Description | SYPRTXT | CHAR | 68 | SYCHAR68K | ||||
| AUTHORITY | Print: Authorization | SYPRBER | CHAR | 12 | SYCHAR12 | SAU | |||
| TELEFAX | Fax Number | TELFX | CHAR | 31 | TEXT31 | ||||
| TELEX | Telex number | TELX1 | CHAR | 30 | TEXT30 | ||||
| TELETEX | Teletex number | TELTX | CHAR | 30 | TEXT30 | ||||
| SELFL | Selection flag | SELKZ | CHAR | 1 | SELKZ | ||||
| SORT | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
| TYPENAME | Output description | NA_MSGNA | CHAR | 30 | NA_MSGNA | ||||
| FUNCTEXT | Name | VTXTK | CHAR | 20 | TEXT20 | ||||
| PRINTERLOC | Spool: Location and naming of an output device | RSPOPLOCAT | CHAR | 64 | TEXT64 | ||||
| PARTNAME | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
| PARTCITY | City | ORT01_GP | CHAR | 35 | TEXT35 | ||||
| POINTER | Row Index of Internal Tables | SYTABIX | INT4 | 10 | SYST_LONG |
| Key field | Non-key field |
How do I retrieve data from SAP structure MSG01 using ABAP code?
As MSG01 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 MSG01 as there is no data to select.How to access SAP table MSG01
Within an ECC or HANA version of SAP you can also view further information about MSG01 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