SE30UREQ SAP (Runtime Analysis: Schedule for User/Service) Structure details
Description: Runtime Analysis: Schedule for User/Service
Structure field list including key, data, relationships and ABAP select examples
SE30UREQ 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 "Runtime Analysis: Schedule for User/Service" 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_SE30UREQ TYPE SE30UREQ.
The SE30UREQ table consists of various fields, each holding specific information or linking keys about Runtime Analysis: Schedule for User/Service data available in SAP. These include SUSER (User who starts the application to be measured), CLIENT (Client of the user who starts the application to be measured), EMODE (Number of External Session (see SM04)), EMODET (Runtime Analysis: External Session).. 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: Can be enhanced (character-type or numeric)
SAP SE30UREQ 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 |
| REQID | Runtime Analysis: ID of a Measurement for User/Service | SE30U_REQID | INT4 | 10 | |||||
| SUSER | User who starts the application to be measured | SE30U_SUSER | CHAR | 12 | UNAME | ||||
| CLIENT | Client of the user who starts the application to be measured | SE30U_CLIENT | CLNT | 3 | T000 | MANDT | |||
| EMODE | Number of External Session (see SM04) | SE30U_EMODE | INT4 | 10 | SE30U_EMODE | ||||
| EMODET | Runtime Analysis: External Session | SE30U_EMODET | CHAR | 10 | TEXT10 | ||||
| PTYPE | Runtime Analysis: Process Category | SE30U_PTYPE | INT4 | 10 | SE30U_PTYPE | ||||
| PTYPET | Runtime Analysis: Process Category | SE30U_PTYPET | CHAR | 20 | TEXT20 | ||||
| OTYPE | Runtime Analysis: Object Type | SE30U_OTYPE | CHAR | 1 | SE30U_OTYPE | ||||
| OTYPET | Runtime Analysis: Object Type | SE30U_OTYPET | CHAR | 24 | TEXT24 | ||||
| ONAME | Runtime Analyis: Object Name | SE30U_ONAME | CHAR | 255 | TEXT255 | ||||
| IRUNS | Runtime Analysis: Maximum Number of Scheduled Measurements | SE30U_IRUNS | INT4 | 10 | SE30U_IRUNS | ||||
| JRUNS | Runtime Analysis: Executed/Started Measurements | SE30U_JRUNS | INT4 | 10 | SE30U_IRUNS | ||||
| FRUNS | Runtime Analysis: Failed Measurements | SE30U_FRUNS | INT4 | 10 | |||||
| STATE | Runtime Analysis: Scheduling Active/Completed | SE30U_STATE | CHAR | 1 | SE30U_STATE | ||||
| STATET | Runtime Analysis: Scheduling Active/Completed | SE30U_STATET | CHAR | 20 | TEXT20 | ||||
| EDATE | Runtime Analysis: Expiration Date of a Scheduled Measurement | SE30U_EDATE | DATS | 8 | DATUM | ||||
| ETIME | Runtime Analysis: Expiration Time of a Scheduled Measurement | SE30U_ETIME | TIMS | 6 | SYTIME | ||||
| SERVER | Application Server Name | MSNAME2 | CHAR | 40 | MSNAME2 |
| Key field | Non-key field |
How do I retrieve data from SAP structure SE30UREQ using ABAP code?
As SE30UREQ 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 SE30UREQ as there is no data to select.How to access SAP table SE30UREQ
Within an ECC or HANA version of SAP you can also view further information about SE30UREQ 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