SAP EMMA_LOGMSG_PROCESS Function Module for

Search SAP Function Modules

EMMA_LOGMSG_PROCESS is a standard emma logmsg process SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 emma logmsg process FM, simply by entering the name EMMA_LOGMSG_PROCESS into the relevant SAP transaction such as SE37 or SE38.

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

Function EMMA_LOGMSG_PROCESS 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 'EMMA_LOGMSG_PROCESS'"
  EXPORTING
   IT_LOGINFO =  "EMMA: tab type for EMMA_LOG_INFO
   IT_LOG_HEADER =  "Application log: log header
   IT_MESSAGES =  "Table type for balm
*  IT_MESSAGE_PARAMS =  "Table type for balmp
*  IT_MESSAGE_CONTEXT =  "
   IV_TCODE =  "Transaction code

 IMPORTING
   ET_MESSAGES =  "Monitoring Mass Run: Log Summary According to Intervals
   ET_MESSAGES_PARAMS =  "table type for mesage parameter
   ET_MESSAGE_CONTEXT =  "

.

IMPORTING Parameters details for EMMA_LOGMSG_PROCESS

IT_LOGINFO - EMMA: tab type for EMMA_LOG_INFO

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

IT_LOG_HEADER - Application log: log header

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

IT_MESSAGES - Table type for balm

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

IT_MESSAGE_PARAMS - Table type for balmp

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

IT_MESSAGE_CONTEXT -

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

IV_TCODE - Transaction code

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

EXPORTING Parameters details for EMMA_LOGMSG_PROCESS

ET_MESSAGES - Monitoring Mass Run: Log Summary According to Intervals

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

ET_MESSAGES_PARAMS - table type for mesage parameter

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

ET_MESSAGE_CONTEXT -

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

Copy and paste ABAP code example for EMMA_LOGMSG_PROCESS 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.

ABAP code using 7.40 inline data declarations to call FM EMMA_LOGMSG_PROCESS

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.

Search for further information about these or an SAP related objects