STR_XO_MESSAGE SAP (Message) Structure details
Description: Message
Related tables to STR_XO_MESSAGE
Access table STR_XO_MESSAGE
Structure field list including key, data, relationships and ABAP select examples
STR_XO_MESSAGE 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 "Message" 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_STR_XO_MESSAGE TYPE STR_XO_MESSAGE.
The STR_XO_MESSAGE table consists of various fields, each holding specific information or linking keys about Message data available in SAP. These include TYPE (Message type: S Success, E Error, W Warning, I Info, A Abort), ID (Message Class), NUMBER (Message Number), MESSAGE (Message Text).. 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: Cannot Be Enhanced
SAP STR_XO_MESSAGE 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 |
TYPE | Message type: S Success, E Error, W Warning, I Info, A Abort | BAPI_MTYPE | CHAR | 1 | SYCHAR01 | ||||
ID | Message Class | SYMSGID | CHAR | 20 | T100A | ARBGB | |||
NUMBER | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
MESSAGE | Message Text | BAPI_MSG | CHAR | 220 | TEXT220 | ||||
LOG_NO | Application log: log number | BALOGNR | CHAR | 20 | BALHDR | BALOGNR | |||
LOG_MSG_NO | Application log: Internal message serial number | BALMNR | NUMC | 6 | BALM | BALMNR | |||
MESSAGE_V1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MESSAGE_V2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MESSAGE_V3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MESSAGE_V4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
PARAMETER | Parameter Name | BAPI_PARAM | CHAR | 32 | SWC_ELEM | ||||
ROW | Lines in parameter | BAPI_LINE | INT4 | 10 | INT4 | ||||
FIELD | Field in parameter | BAPI_FLD | CHAR | 30 | Assigned to domain | FDNAME | |||
SYSTEM | Logical system from which message originates | BAPILOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
TABLE | Table Name | XO_TABLE_NAME | CHAR | 30 | Assigned to domain | AS4TAB | |||
ECH_ERROR_CATEGORY | Error Category According to Error and Conflict Handler | XO_ECH_ERROR_CATEGORY | CHAR | 15 | XO_ECH_ERROR_CATEGORY |
Key field | Non-key field |
How do I retrieve data from SAP structure STR_XO_MESSAGE using ABAP code?
As STR_XO_MESSAGE 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 STR_XO_MESSAGE as there is no data to select.How to access SAP table STR_XO_MESSAGE
Within an ECC or HANA version of SAP you can also view further information about STR_XO_MESSAGE 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