Messages

A unified extractor that accepts almost anything carrying SAP message data (single structures, internal tables, exception objects, BAL containers, BAPIRET tables, …) and returns a flat ty_t_msg.

Type Reference

TYPES: BEGIN OF ty_s_msg,
         text       TYPE string,
         id         TYPE string,
         no         TYPE string,
         type       TYPE string,
         v1         TYPE string,
         v2         TYPE string,
         v3         TYPE string,
         v4         TYPE string,
         timestampl TYPE timestampl,
       END OF ty_s_msg,
       ty_t_msg TYPE STANDARD TABLE OF ty_s_msg WITH EMPTY KEY.

msg_get

Extract a single message structure from any input.

DATA(ls_msg) = zabaputil_cl_util=>msg_get( ls_bapiret ).

msg_get_t

Extract all messages as a table. The most useful entry point — works for:

• structures with MSGID / MSGNO / MSGV1..4 (e.g. BAPIRET2)
• internal tables of such structures
• references to cx_root (any exception)
• references to if_bali_log (BAL log containers)
• references implementing ZIF_LOGGER (the popular logger interface)

DATA(lt_msg) = zabaputil_cl_util=>msg_get_t( lo_bali ).

msg_get_by_msg

Build one ty_s_msg from raw message components. Optional placeholders v1..v4 are passed through to MESSAGE so the text comes back resolved.

DATA(ls_msg) = zabaputil_cl_util=>msg_get_by_msg(
    id = '00'
    no = '398'
    v1 = 'Hello'
    v2 = 'World' ).

Companion class zabaputil_cl_util_msg

Lower-level helpers used by the façade. Useful when you need to extract messages from custom containers:

Method	Purpose
msg_get_text( val )	Returns the text of the first message in val
msg_map( name val is_msg )	Maps a single component into the right slot of ty_s_msg
msg_get( val )	Recursive extractor (called by the façade msg_get_t)
msg_get_by_sy( )	Build a ty_t_msg from the current sy-msg* fields

See also

• Logging — collect messages over time
• Errors & Exceptions — interplay with zabaputil_cx_util_error