SXMSVLST SAP (XML Message Broker: Message Version) Structure details
Description: XML Message Broker: Message Version
Structure field list including key, data, relationships and ABAP select examples
SXMSVLST 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 "XML Message Broker: Message Version" 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_SXMSVLST TYPE SXMSVLST.
The SXMSVLST table consists of various fields, each holding specific information or linking keys about XML Message Broker: Message Version data available in SAP. These include MSGGUID (XI: Message ID), PID (Integration Engine: Pipeline ID), VERSION (Sequence Number for a Message Log ID), MSGSTATE (Integration Engine: Message Status).. 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 SXMSVLST 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 ID | SYMANDT | CLNT | 3 | Assigned to domain | MANDT | |||
MSGGUID | XI: Message ID | SXMSMGUID | RAW | 16 | SYSUUID | ||||
PID | Integration Engine: Pipeline ID | SXMSPID | CHAR | 40 | Assigned to domain | SXMSPID | |||
VERSION | Sequence Number for a Message Log ID | SXMSLSQNBR | NUMC | 3 | |||||
MSGSTATE | Integration Engine: Message Status | SXMSPMSTAT | NUMC | 3 | Assigned to domain | SXMSPMSTAT | |||
TIMESTAMP | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
PELGUID | GUID of a Pipeline Element | SXMSPEGUID | CHAR | 32 | SYSUUID_C | ||||
CLIENT | Client ID | SYMANDT | CLNT | 3 | Assigned to domain | MANDT | |||
LOG_ENTRY | XMS: Flag (true/false) | SXMSFLAG | CHAR | 1 | SXMSFLAG | ||||
REST_VERS | Sequence Number for a Message Log ID | SXMSLSQNBR | NUMC | 3 | |||||
MAJOR | Protocol Version for Incompatible Changes | 0 | |||||||
MINOR | Protocol Version for Compatible Changes | 0 | |||||||
VERS_LINK | Sequence Number for a Message Log ID | SXMSLSQNBR | NUMC | 3 | |||||
SEQNBR | Sequence Number | SXMSNR | NUMC | 4 |
Key field | Non-key field |
How do I retrieve data from SAP structure SXMSVLST using ABAP code?
As SXMSVLST 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 SXMSVLST as there is no data to select.How to access SAP table SXMSVLST
Within an ECC or HANA version of SAP you can also view further information about SXMSVLST 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