SRT_UTIL_MESSAGE SAP (SRTUTIL: Message Relationship) Structure details
Description: SRTUTIL: Message Relationship
Related tables to SRT_UTIL_MESSAGE
Access table SRT_UTIL_MESSAGE
Structure field list including key, data, relationships and ABAP select examples
SRT_UTIL_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 "SRTUTIL: Message Relationship" 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_SRT_UTIL_MESSAGE TYPE SRT_UTIL_MESSAGE.
The SRT_UTIL_MESSAGE table consists of various fields, each holding specific information or linking keys about SRTUTIL: Message Relationship data available in SAP. These include MANDT (Client ID), USERID (User Name), INI_DATE (Creation Date), INI_TIME (Creation Time).. 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 SRT_UTIL_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 |
| SNUMBER | Order Number | 0 | |||||||
| MANDT | Client ID | SYMANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| USERID | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
| INI_DATE | Creation Date | 0 | |||||||
| INI_TIME | Creation Time | 0 | |||||||
| EXE_DATE | Execution Date | 0 | |||||||
| EXE_TIME | Execution Time | 0 | |||||||
| ROLE | Service Role | 0 | |||||||
| PIPELINE_ID | Pipeline ID | 0 | |||||||
| STATE_CODE | Processing State Code | 0 | |||||||
| PROCESSING_STATE | Processing State | 0 | |||||||
| SEQUENCE_STATE | Sequence State | 0 | |||||||
| QUEUE_STATE | Queue State | 0 | |||||||
| MESSAGE_STATE | Message State | 0 | |||||||
| TW_STATE | Task Watcher State | 0 | |||||||
| PAF_STATE | PAF State | 0 | |||||||
| LOGICAL_SID | Logical Sequence ID | 0 | |||||||
| QUEUE_NAME | Queue Name for Background RFC | QRFC_QUEUE_NAME | CHAR | 40 | QRFC_QUEUE_NAME | ||||
| UNIT_ID | Queue Unit ID | 0 | |||||||
| PERSIST_ID | Persistency ID | 0 | |||||||
| TECHNICAL_SID | Any URI | ANYURI | SSTR | 255 | ANYURI | ||||
| MESSAGE_ID | Message ID | 0 | |||||||
| WSRM_VERSION | WS RM version | 0 | |||||||
| CHECK_RESULT | Check Result Text | 0 | |||||||
| TECHNICAL_SID | Any URI | ANYURI | SSTR | 255 | ANYURI | ||||
| T100_AREA | Application Area | ARBGB | CHAR | 20 | Assigned to domain | ARBGB | MAG | ||
| WSRM_VERSION | WS RM version | 0 | |||||||
| T100_MSGNO | System Message Number | MSGNO | CHAR | 3 | Assigned to domain | MSGNR | |||
| CHECK_RESULT | Check Result Text | 0 | |||||||
| INFO_ICON | Tree Control: Icon / Image | TV_IMAGE | CHAR | 46 | TV_IMAGE | ||||
| T100_AREA | Application Area | ARBGB | CHAR | 20 | Assigned to domain | ARBGB | MAG | ||
| T100_MSGNO | System Message Number | MSGNO | CHAR | 3 | Assigned to domain | MSGNR | |||
| TW_TASK_ID | Task Watcher Task ID | 0 | |||||||
| N_UNITS | Number of bgRFC Units | 0 | |||||||
| INFO_ICON | Tree Control: Icon / Image | TV_IMAGE | CHAR | 46 | TV_IMAGE | ||||
| TW_TASK_ID | Task Watcher Task ID | 0 | |||||||
| N_INCOMPLETE | Number of Incomplete Messages | 0 | |||||||
| N_UNITS | Number of bgRFC Units | 0 | |||||||
| SENDER_IF_SPACE | Sender Interface Namespace | 0 | |||||||
| N_INCOMPLETE | Number of Incomplete Messages | 0 | |||||||
| SENDER_IF_NAME | Sender Interface Name | 0 | |||||||
| SENDER_IF_SPACE | Sender Interface Namespace | 0 | |||||||
| RECEIVER_IF_SPACE | Receiver Interface Namespace | 0 | |||||||
| SENDER_IF_NAME | Sender Interface Name | 0 | |||||||
| RECEIVER_IF_NAME | Receiver Interface Name | 0 | |||||||
| RECEIVER_IF_SPACE | Receiver Interface Namespace | 0 | |||||||
| RECEIVER_IF_NAME | Receiver Interface Name | 0 | |||||||
| SENDER_COMPONENT | Sender Component | 0 | |||||||
| SENDER_PARTY | Sender Party | 0 | |||||||
| RECEIVER_COMPONENT | Receiver Component | 0 | |||||||
| RECEIVER_PARTY | Receiver Party | 0 | |||||||
| SENDER_OPERATION | Sender Operation | 0 | |||||||
| RECEIVER_OPERATION | Receiver Operation | 0 | |||||||
| COMMTYPE | Communication Type Name | SRT_UTIL_COMMTYPE | CHAR | 18 | SRT_UTIL_COMMTYPE | ||||
| REF_MESSAGE_ID | Reference Message ID | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure SRT_UTIL_MESSAGE using ABAP code?
As SRT_UTIL_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 SRT_UTIL_MESSAGE as there is no data to select.How to access SAP table SRT_UTIL_MESSAGE
Within an ECC or HANA version of SAP you can also view further information about SRT_UTIL_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