EMMA_MSGSTOREDB SAP (Monitoring Mass Run: Messages from Application Log) Structure details
Description: Monitoring Mass Run: Messages from Application Log
Related tables to EMMA_MSGSTOREDB
Access table EMMA_MSGSTOREDB
Structure field list including key, data, relationships and ABAP select examples
EMMA_MSGSTOREDB 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 "Monitoring Mass Run: Messages from Application Log" 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_EMMA_MSGSTOREDB TYPE EMMA_MSGSTOREDB.
The EMMA_MSGSTOREDB table consists of various fields, each holding specific information or linking keys about Monitoring Mass Run: Messages from Application Log data available in SAP. These include OBJECTKEY (Object Key), INTNR (Number of interval within variant), MSGNUMBER (Application log: Internal message serial number), MSGTY (Message Type).. 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 EMMA_MSGSTOREDB 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 |
OBJECTTYPE | Object Type | SWO_OBJTYP | CHAR | 10 | Assigned to domain | OJ_NAME | OBJ | ||
OBJECTKEY | Object Key | EMMA_OBJKEY | CHAR | 50 | CHAR50 | ||||
INTNR | Number of interval within variant | INTNR_KK | INT4 | 10 | INT4 | ||||
MSGNUMBER | Application log: Internal message serial number | BALMNR | NUMC | 6 | Assigned to domain | BALMNR | |||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
MSGID | Application Log: Message class, message ID | BALMSGID | CHAR | 20 | T100A | ARBGB | |||
MSGNO | Application Log: Message number in message class | BALMSGNO | NUMC | 3 | SYMSGNO | ||||
MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
LOGDATE | Application log: date | BALDATE | DATS | 8 | DATUM | ||||
LOGTIME | Application log: time | BALTIME | TIMS | 6 | UZEIT | ||||
LONGTEXT | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
PARAMETERS | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
ALTEXT | Application log: Standard text | BALTEXT | CHAR | 28 | CHAR28 | ||||
TIME_STMP | Application Log: Message time stamp | BALTIMSTMP | DEC | 21(7) | TZNTSTMPL |
Key field | Non-key field |
How do I retrieve data from SAP structure EMMA_MSGSTOREDB using ABAP code?
As EMMA_MSGSTOREDB 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 EMMA_MSGSTOREDB as there is no data to select.How to access SAP table EMMA_MSGSTOREDB
Within an ECC or HANA version of SAP you can also view further information about EMMA_MSGSTOREDB 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