SXMSPHIST SAP (XML Message Broker: History) Table details
Dictionary Type: Table
Description: XML Message Broker: History
Description: XML Message Broker: History
Table field list including key, data, relationships and ABAP select examples
SXMSPHIST is a standard SAP Table which is used to store XML Message Broker: History data and is available within R/3 SAP systems depending on the version and release level.
The SXMSPHIST table consists of various fields, each holding specific information or linking keys about XML Message Broker: History data available in SAP. These include MSGGUID (XI: Message ID), PID (Integration Engine: Pipeline ID), MSGTYPE (Integration Engine: Message Type), SENDTST (UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)).. 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: L - Table for storing temporary data, is delivered emptyDisplay/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP SXMSPHIST table 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 | |||
MSGTYPE | Integration Engine: Message Type | SXMSPMTYPE | CHAR | 1 | SXMSPMTYPE | ||||
SENDTST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
EXESTRTTST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
EXEENDTST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
STATUSTST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
ADMINUSER | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
REORG | Reorganization Status | SXMSREORG | CHAR | 3 | SXMSREORG | ||||
MSGSTATE | Integration Engine: Message Status | SXMSPMSTAT | NUMC | 3 | Assigned to domain | SXMSPMSTAT | |||
MANUALSTAT | XMS: Flag (true/false) | SXMSFLAG | CHAR | 1 | SXMSFLAG | ||||
RESTART | XMS: Flag (true/false) | SXMSFLAG | CHAR | 1 | SXMSFLAG | ||||
RETRYCOUNT | Numc3, internal use | NUMC3 | NUMC | 3 | NUMC3 | ||||
ERROROCCUR | XMS: Flag (true/false) | SXMSFLAG | CHAR | 1 | SXMSFLAG | ||||
CLIENT | Client ID | SYMANDT | CLNT | 3 | Assigned to domain | MANDT |
Key field | Non-key field |
How do I retrieve data from SAP table SXMSPHIST using ABAP code
The following ABAP code Example will allow you to do a basic selection on SXMSPHIST to SELECT all data from the tableDATA: WA_SXMSPHIST TYPE SXMSPHIST.
SELECT SINGLE *
FROM SXMSPHIST
INTO CORRESPONDING FIELDS OF WA_SXMSPHIST
WHERE...
How to access SAP table SXMSPHIST
Within an ECC or HANA version of SAP you can also view further information about SXMSPHIST 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