SAP IDALV_STATS_MSG_ADD Function Module for Structured Application Log









IDALV_STATS_MSG_ADD is a standard idalv stats msg add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Structured Application Log processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for idalv stats msg add FM, simply by entering the name IDALV_STATS_MSG_ADD into the relevant SAP transaction such as SE37 or SE38.

Function Group: IDALV
Program Name: SAPLIDALV
Main Program: SAPLIDALV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function IDALV_STATS_MSG_ADD pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'IDALV_STATS_MSG_ADD'"Structured Application Log
  EXPORTING
*  I_NODE_KEY =  "Structured Application Log
*  I_MSGV3 =  "Message Variable
*  I_MSGV4 =  "Message Variable
*  I_STCNT =  "Application Log: Cumulated message count
*  I_NODID =  "Structured Application Log
*  I_NODPA =  "Structured Application Log
   I_MSGID =  "Message Class
*  I_MSGTY = 'S' "Message Type
   I_MSGNO =  "Message Number
*  I_MSGV1 =  "Message Variable
*  I_MSGV2 =  "Message Variable

 IMPORTING
   E_STATS_NODE_KEY =  "HR Application Log

EXCEPTIONS
   PROGRAM_ERROR = 1
.



IMPORTING Parameters details for IDALV_STATS_MSG_ADD

I_NODE_KEY - Structured Application Log

Data type: BALS_NODE_KEY
Optional: Yes
Call by Reference: Yes

I_MSGV3 - Message Variable

Data type: SYMSGV
Optional: Yes
Call by Reference: Yes

I_MSGV4 - Message Variable

Data type: SYMSGV
Optional: Yes
Call by Reference: Yes

I_STCNT - Application Log: Cumulated message count

Data type: BALS_S_STATS-STCNT
Optional: Yes
Call by Reference: Yes

I_NODID - Structured Application Log

Data type: BALS_NODE_KEY
Optional: Yes
Call by Reference: Yes

I_NODPA - Structured Application Log

Data type: BALS_NODE_KEY
Optional: Yes
Call by Reference: Yes

I_MSGID - Message Class

Data type: SYMSGID
Optional: No
Call by Reference: Yes

I_MSGTY - Message Type

Data type: SYMSGTY
Default: 'S'
Optional: Yes
Call by Reference: Yes

I_MSGNO - Message Number

Data type: SYMSGNO
Optional: No
Call by Reference: Yes

I_MSGV1 - Message Variable

Data type: SYMSGV
Optional: Yes
Call by Reference: Yes

I_MSGV2 - Message Variable

Data type: SYMSGV
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for IDALV_STATS_MSG_ADD

E_STATS_NODE_KEY - HR Application Log

Data type: BALS_NODE_KEY
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PROGRAM_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IDALV_STATS_MSG_ADD Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_i_node_key  TYPE BALS_NODE_KEY, "   
lv_program_error  TYPE BALS_NODE_KEY, "   
lv_e_stats_node_key  TYPE BALS_NODE_KEY, "   
lv_i_msgv3  TYPE SYMSGV, "   
lv_i_msgv4  TYPE SYMSGV, "   
lv_i_stcnt  TYPE BALS_S_STATS-STCNT, "   
lv_i_nodid  TYPE BALS_NODE_KEY, "   
lv_i_nodpa  TYPE BALS_NODE_KEY, "   
lv_i_msgid  TYPE SYMSGID, "   
lv_i_msgty  TYPE SYMSGTY, "   'S'
lv_i_msgno  TYPE SYMSGNO, "   
lv_i_msgv1  TYPE SYMSGV, "   
lv_i_msgv2  TYPE SYMSGV. "   

  CALL FUNCTION 'IDALV_STATS_MSG_ADD'  "Structured Application Log
    EXPORTING
         I_NODE_KEY = lv_i_node_key
         I_MSGV3 = lv_i_msgv3
         I_MSGV4 = lv_i_msgv4
         I_STCNT = lv_i_stcnt
         I_NODID = lv_i_nodid
         I_NODPA = lv_i_nodpa
         I_MSGID = lv_i_msgid
         I_MSGTY = lv_i_msgty
         I_MSGNO = lv_i_msgno
         I_MSGV1 = lv_i_msgv1
         I_MSGV2 = lv_i_msgv2
    IMPORTING
         E_STATS_NODE_KEY = lv_e_stats_node_key
    EXCEPTIONS
        PROGRAM_ERROR = 1
. " IDALV_STATS_MSG_ADD




ABAP code using 7.40 inline data declarations to call FM IDALV_STATS_MSG_ADD

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
"SELECT single STCNT FROM BALS_S_STATS INTO @DATA(ld_i_stcnt).
 
 
 
 
DATA(ld_i_msgty) = 'S'.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!