RPLM_S_MESSAGELOG SAP (Structure of Message Log) Structure details
Description: Structure of Message Log
Related tables to RPLM_S_MESSAGELOG
Access table RPLM_S_MESSAGELOG
Structure field list including key, data, relationships and ABAP select examples
RPLM_S_MESSAGELOG 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 "Structure of Message 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_RPLM_S_MESSAGELOG TYPE RPLM_S_MESSAGELOG.
The RPLM_S_MESSAGELOG table consists of various fields, each holding specific information or linking keys about Structure of Message Log data available in SAP. These include LOG_HANDLE (Application Log: Log Handle), MSGNUMBER (Application log: Internal message serial number), EXC_HANDLE (), LOG_HANDLE (Application Log: Log Handle).. 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 RPLM_S_MESSAGELOG 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 |
MSG_HANDLE | 0 | ||||||||
LOG_HANDLE | Application Log: Log Handle | BALLOGHNDL | CHAR | 22 | SYSUUID_22 | ||||
MSGNUMBER | Application log: Internal message serial number | BALMNR | NUMC | 6 | BALMNR | ||||
EXC_HANDLE | 0 | ||||||||
LOG_HANDLE | Application Log: Log Handle | BALLOGHNDL | CHAR | 22 | SYSUUID_22 | ||||
MSGNUMBER | Application log: Internal message serial number | BALMNR | NUMC | 6 | BALMNR | ||||
CLASS | 0 | ||||||||
TEXT | 0 | ||||||||
TYPE | 0 | ||||||||
ID | 0 | ||||||||
LONGTEXT | 0 | ||||||||
LANGUAGE | Language Key | SYLANGU | LANG | 1 | ISOLA | SYLANGU | |||
LEVEL_VALUE | 0 | ||||||||
EXC_DATA | 0 | ||||||||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
EXCLSNAME | Application Log: Exception Class | BALEXCLS | CHAR | 30 | CLASSNAME | ||||
TXT_EXCID | Application Log: Label for Exception Text (Exception ID) | BALTXT | CHAR | 30 | CHAR30 | ||||
DETLEVEL | Application Log: Level of detail | BALLEVEL | CHAR | 1 | BALLEVEL | ||||
PROBCLASS | Application log: Message problem class | BALPROBCL | CHAR | 1 | BALPROBCL | ||||
ALSORT | Application log: Sort criterion/grouping | BALSORT | CHAR | 3 | CHAR3 | ||||
MSG_COUNT | Application Log: Cumulated message count | BALDBCNTCU | NUMC | 6 | |||||
TIME_STMP | Application Log: Message time stamp | BALTIMSTMP | DEC | 21(7) | TZNTSTMPL | ||||
MSG_DATA | 0 | ||||||||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
MSGID | Message Class | SYMSGID | CHAR | 20 | ARBGB | ||||
MSGNO | Message Number | SYMSGNO | 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 | ||||
MSGV1_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
MSGV2_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
MSGV3_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
MSGV4_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
DETLEVEL | Application Log: Level of detail | BALLEVEL | CHAR | 1 | BALLEVEL | ||||
PROBCLASS | Application log: Message problem class | BALPROBCL | CHAR | 1 | BALPROBCL | ||||
ALSORT | Application log: Sort criterion/grouping | BALSORT | CHAR | 3 | CHAR3 | ||||
TIME_STMP | Application Log: Message time stamp | BALTIMSTMP | DEC | 21(7) | TZNTSTMPL | ||||
MSG_COUNT | Application Log: Cumulated message count | BALCNTCUM | INT4 | 10 | BALCOUNT | ||||
CONTEXT | 0 | ||||||||
TABNAME | Application Log: Context: DDIC structure name | BALTABNAME | CHAR | 30 | AS4TAB | DTB | |||
VALUE | Application Log: Context data | BALCVAL | CHAR | 256 | BALCVAL | ||||
PARAMS | 0 | ||||||||
T_PAR | 0 | ||||||||
CALLBACK | 0 | ||||||||
USEREXITP | Application Log: Callback: Program name | BALUEP | CHAR | 40 | PROGNAME | ||||
USEREXITF | Application Log: Callback: Routine name | BALUEF | CHAR | 30 | CHAR30 | ||||
USEREXITT | Application Log: Callback: Type (Ext. Perform, FM, etc.) | BALUET | CHAR | 1 | BALUET | ||||
ALTEXT | Application log: Standard text | BALTEXT | CHAR | 28 | CHAR28 | ||||
PROTOCOL_HANDLE | Application Log: Log Handle | BALLOGHNDL | CHAR | 22 | SYSUUID_22 | ||||
STANDARD_RETURN | 0 | ||||||||
TYPE | Message type: S Success, E Error, W Warning, I Info, A Abort | BAPI_MTYPE | CHAR | 1 | SYCHAR01 | ||||
ID | Message Class | SYMSGID | CHAR | 20 | ARBGB | ||||
NUMBER | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
MESSAGE | Message Text | BAPI_MSG | CHAR | 220 | TEXT220 | ||||
LOG_NO | Application log: log number | BALOGNR | CHAR | 20 | BALOGNR | ||||
LOG_MSG_NO | Application log: Internal message serial number | BALMNR | NUMC | 6 | BALMNR | ||||
MESSAGE_V1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MESSAGE_V2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MESSAGE_V3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MESSAGE_V4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
PARAMETER | Parameter Name | BAPI_PARAM | CHAR | 32 | SWC_ELEM | ||||
ROW | Lines in parameter | BAPI_LINE | INT4 | 10 | INT4 | ||||
FIELD | Field in parameter | BAPI_FLD | CHAR | 30 | FDNAME | ||||
SYSTEM | Logical system from which message originates | BAPILOGSYS | CHAR | 10 | ALPHA | LOGSYS | |||
EXC_REF | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure RPLM_S_MESSAGELOG using ABAP code?
As RPLM_S_MESSAGELOG 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 RPLM_S_MESSAGELOG as there is no data to select.How to access SAP table RPLM_S_MESSAGELOG
Within an ECC or HANA version of SAP you can also view further information about RPLM_S_MESSAGELOG 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