/BOFU/S_BAL_MESSAGE_K SAP (Application Log Message) Structure details
Description: Application Log Message
Related tables to /BOFU/S_BAL_MESSAGE_K
Access table /BOFU/S_BAL_MESSAGE_K
Structure field list including key, data, relationships and ABAP select examples
/BOFU/S_BAL_MESSAGE_K 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 "Application Log Message" 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_/BOFU/S_BAL_MESSAGE_K TYPE /BOFU/S_BAL_MESSAGE_K.
The /BOFU/S_BAL_MESSAGE_K table consists of various fields, each holding specific information or linking keys about Application Log Message data available in SAP. These include KEY (NodeID), PARENT_KEY (NodeID), ROOT_KEY (NodeID), 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: Can be enhanced (character-type or numeric)
SAP /BOFU/S_BAL_MESSAGE_K 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 |
KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY | ||||
PARENT_KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY | ||||
ROOT_KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY | ||||
LOG_HANDLE | Application Log: Log Handle | BALLOGHNDL | CHAR | 22 | SYSUUID_22 | ||||
MSGNUMBER | Application log: Internal message serial number | BALMNR | NUMC | 6 | Assigned to domain | BALMNR | |||
MSGTY | Application Log: Message type (A,E,W,I,S) | BALMSGTY | CHAR | 1 | BALMSGTY | ||||
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 | Application Log: Message variable 1 | BALMSGV1 | CHAR | 50 | SYCHAR50 | ||||
MSGV2 | Application Log: Message variable 2 | BALMSGV2 | CHAR | 50 | SYCHAR50 | ||||
MSGV3 | Application Log: Message variable 3 | BALMSGV3 | CHAR | 50 | SYCHAR50 | ||||
MSGV4 | Application Log: Message variable 4 | BALMSGV4 | CHAR | 50 | SYCHAR50 | ||||
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 | ||||
.INCLU-CTX | 0 | ||||||||
TABNAMECTX | Application Log: Context: DDIC structure name | BALTABNAME | CHAR | 30 | Assigned to domain | AS4TAB | DTB | ||
VALUECTX | Application Log: Context data | BALCVAL | CHAR | 256 | BALCVAL | ||||
MSG_EXISTS_ON_DB | Message Exists on DB | /BOFU/BAL_MSG_EXISTS_ON_DB | CHAR | 1 | BOOLE | ||||
SEQ_NO | Application Log: Chronological message serial number | BALSEQNO | NUMC | 6 | Assigned to domain | BALMNR | |||
MSG_COUNT | Application Log: Cumulated message count | BALCNTCUM | INT4 | 10 | BALCOUNT | ||||
TIME_STMP | Application Log: Message time stamp | BALTIMSTMP | DEC | 21(7) | TZNTSTMPL | ||||
MSG_DATE | Anpplication Log: Message creation date | BALMSGDAT | DATS | 8 | DATUM | ||||
MSG_TIME | Application Log: Message creation time | BALMSGTIM | TIMS | 6 | UZEIT | ||||
MSG_STMP | Application Log: Message date/time | BALMSGSTM | CHAR | 20 | CHAR20 | ||||
ICON_MSGTYPE | Icon in text fields (substitute display, alias) | ICON_D | CHAR | 4 | Assigned to domain | ICON | |||
ICON_NAME_MSGTYPE | Name of an Icon | ICONNAME | CHAR | 30 | ICONNAME | ||||
ICON_MSGTY | Application Log: Message Type Visualization | BALIMSGTY | CHAR | 30 | TEXT30 | ||||
ICON_PAR | Application Log: Detail data icon | BALIPARM | CHAR | 30 | TEXT30 | ||||
ICON_LNG | Application Log: Message long text icon | BALILONGT | CHAR | 30 | TEXT30 | ||||
T_MSG | Application Log: Formatted message text | BALTMSG | CHAR | 255 | BALTMSG | ||||
T_MSGTY | Application Log: Seriousness of a message (A,E,W,I,S) | BALTMSGTY | CHAR | 20 | TEXT20 | ||||
T_MSGID | Application Log: Message area | BALTMSGID | CHAR | 60 | AS4TEXT | ||||
T_DETLEVEL | Application Log: Level of detail | BALTDETLVL | CHAR | 60 | AS4TEXT | ||||
T_PROBCLSS | Application Log: Problem class | BALTPROBCL | CHAR | 60 | AS4TEXT | ||||
STATUS_MSG_TEXT | Status Icon teext | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure /BOFU/S_BAL_MESSAGE_K using ABAP code?
As /BOFU/S_BAL_MESSAGE_K 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 /BOFU/S_BAL_MESSAGE_K as there is no data to select.How to access SAP table /BOFU/S_BAL_MESSAGE_K
Within an ECC or HANA version of SAP you can also view further information about /BOFU/S_BAL_MESSAGE_K 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