SAP EMMA_LOG_PROCESS_V2 Function Module for Process Log









EMMA_LOG_PROCESS_V2 is a standard emma log process v2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Process 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 emma log process v2 FM, simply by entering the name EMMA_LOG_PROCESS_V2 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_LOG_PROCESS_V2 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_LOG_PROCESS_V2'"Process Log
  EXPORTING
   IT_LOGINFO =  "
   IV_RUNID =  "EMMA: Unique key system generated
   IV_VERSION =  "EMMA Release

 IMPORTING
   ES_OUTPUT_HDR =  "
   ET_RETURN =  "Table with BAPI Return Information
   ET_OUTPUT_INT =  "
   ET_EXPORTEO =  "
   ET_EXPORTWO =  "
   ET_EXPORTSO =  "
   ET_EXPORTIM =  "
   ET_EXPORTWM =  "
   ET_EXPORTEM =  "
   ET_MSGLONGTXTPAR =  "

EXCEPTIONS
   NOT_FOUND = 1    NO_MESSAGE_FOUND = 2
.



IMPORTING Parameters details for EMMA_LOG_PROCESS_V2

IT_LOGINFO -

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

IV_RUNID - EMMA: Unique key system generated

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

IV_VERSION - EMMA Release

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

EXPORTING Parameters details for EMMA_LOG_PROCESS_V2

ES_OUTPUT_HDR -

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

ET_RETURN - Table with BAPI Return Information

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

ET_OUTPUT_INT -

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

ET_EXPORTEO -

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

ET_EXPORTWO -

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

ET_EXPORTSO -

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

ET_EXPORTIM -

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

ET_EXPORTWM -

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

ET_EXPORTEM -

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

ET_MSGLONGTXTPAR -

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

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_MESSAGE_FOUND - No messages exist

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EMMA_LOG_PROCESS_V2 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_not_found  TYPE STRING, "   
lv_it_loginfo  TYPE EMMA_LOGINFO_OUT_TAB, "   
lv_es_output_hdr  TYPE EMMA_HDR, "   
lv_et_return  TYPE BAPIRETTAB, "   
lv_iv_runid  TYPE EMMA_RUNID, "   
lv_et_output_int  TYPE EMMA_INT_TAB, "   
lv_no_message_found  TYPE EMMA_INT_TAB, "   
lv_iv_version  TYPE EMMARELEASE, "   
lv_et_exporteo  TYPE EMMA_MSGSTOREDB_TAB_V2, "   
lv_et_exportwo  TYPE EMMA_MSGSTOREDB_TAB_V2, "   
lv_et_exportso  TYPE EMMA_MSGSTOREDB_TAB_V2, "   
lv_et_exportim  TYPE EMMA_MSGSTOREDB_TAB_V2, "   
lv_et_exportwm  TYPE EMMA_MSGSTOREDB_TAB_V2, "   
lv_et_exportem  TYPE EMMA_MSGSTOREDB_TAB_V2, "   
lv_et_msglongtxtpar  TYPE EMMA_MSGLONGTXTPAR_TAB. "   

  CALL FUNCTION 'EMMA_LOG_PROCESS_V2'  "Process Log
    EXPORTING
         IT_LOGINFO = lv_it_loginfo
         IV_RUNID = lv_iv_runid
         IV_VERSION = lv_iv_version
    IMPORTING
         ES_OUTPUT_HDR = lv_es_output_hdr
         ET_RETURN = lv_et_return
         ET_OUTPUT_INT = lv_et_output_int
         ET_EXPORTEO = lv_et_exporteo
         ET_EXPORTWO = lv_et_exportwo
         ET_EXPORTSO = lv_et_exportso
         ET_EXPORTIM = lv_et_exportim
         ET_EXPORTWM = lv_et_exportwm
         ET_EXPORTEM = lv_et_exportem
         ET_MSGLONGTXTPAR = lv_et_msglongtxtpar
    EXCEPTIONS
        NOT_FOUND = 1
        NO_MESSAGE_FOUND = 2
. " EMMA_LOG_PROCESS_V2




ABAP code using 7.40 inline data declarations to call FM EMMA_LOG_PROCESS_V2

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



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!