SAP EMMA_LOG_PROCESS_START Function Module for Note start of process
EMMA_LOG_PROCESS_START is a standard emma log process start SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Note start of process 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 start FM, simply by entering the name EMMA_LOG_PROCESS_START into the relevant SAP transaction such as SE37 or SE38.
Function Group: EMMA_BW
Program Name: SAPLEMMA_BW
Main Program: SAPLEMMA_BW
Appliation area:
Release date: 03-Feb-2006
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EMMA_LOG_PROCESS_START 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_START'"Note start of process.
EXPORTING
IV_BPAREA = "Business Process Area
* IV_RUNMODE = ' ' "Execution Mode
* IV_MASSPROCESS = ' ' "Process Is Mass Process
* IV_DB_UPDATE = 'X' "Update Application Log and Job Header on Database
* IV_NEWPROCESS = "New Process for CIC0
* IV_START_TIMESTAMPL = "UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)
IV_BPCODE = "Business Process Code
IV_TCODE = "Transaction Code
IV_MAIN_BUS_OBJTYPE = "Object Type
* IV_MAIN_BUS_OBJKEY = "Object Key
IS_LOG_INFO = "Information for Opening Process Log
* IV_START_TIMESTAMP = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
* IV_NO_TIME_MEAS = "No Time Measurement
* IS_BUSOBJECTS = "Business Objects in Process
IMPORTING
EV_LOG_HANDLE = "Handle of log used
EV_BPGUID_C = "GUID of Transaction/Process
EXCEPTIONS
BPAREA_NOT_FOUND = 1 BPAREA_MEAS_INACTIVE = 2 BPCODE_NOT_FOUND = 3 LOGOBJECT_SUBOBJECT_NOT_SPECIF = 4 SYSTEM_ERROR = 5
IMPORTING Parameters details for EMMA_LOG_PROCESS_START
IV_BPAREA - Business Process Area
Data type: EMMA_BPAREAOptional: No
Call by Reference: No ( called with pass by value option)
IV_RUNMODE - Execution Mode
Data type: EMMA_XPRUNDefault: ' '
Optional: Yes
Call by Reference: Yes
IV_MASSPROCESS - Process Is Mass Process
Data type: BOOLE_DDefault: ' '
Optional: Yes
Call by Reference: Yes
IV_DB_UPDATE - Update Application Log and Job Header on Database
Data type: BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_NEWPROCESS - New Process for CIC0
Data type: BOOLE_DOptional: Yes
Call by Reference: Yes
IV_START_TIMESTAMPL - UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)
Data type: TIMESTAMPLOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_BPCODE - Business Process Code
Data type: EMMA_BPCODEOptional: No
Call by Reference: No ( called with pass by value option)
IV_TCODE - Transaction Code
Data type: TCODEOptional: No
Call by Reference: No ( called with pass by value option)
IV_MAIN_BUS_OBJTYPE - Object Type
Data type: SWO_OBJTYPOptional: No
Call by Reference: No ( called with pass by value option)
IV_MAIN_BUS_OBJKEY - Object Key
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_LOG_INFO - Information for Opening Process Log
Data type: EMMA_PROC_LOG_OPENOptional: No
Call by Reference: No ( called with pass by value option)
IV_START_TIMESTAMP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
Data type: TIMESTAMPOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NO_TIME_MEAS - No Time Measurement
Data type: EMMA_PROC_NO_TIME_MEASOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_BUSOBJECTS - Business Objects in Process
Data type: EMMA_PROC_BUSOBJECTSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EMMA_LOG_PROCESS_START
EV_LOG_HANDLE - Handle of log used
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
EV_BPGUID_C - GUID of Transaction/Process
Data type: EMMA_BPGUID_COptional: No
Call by Reference: Yes
EXCEPTIONS details
BPAREA_NOT_FOUND - Business process area not found
Data type:Optional: No
Call by Reference: Yes
BPAREA_MEAS_INACTIVE - Measurement of Processes of this Process Area Not Active
Data type:Optional: No
Call by Reference: Yes
BPCODE_NOT_FOUND - Process code for process area not found
Data type:Optional: No
Call by Reference: Yes
LOGOBJECT_SUBOBJECT_NOT_SPECIF - Log object and subobject not specified
Data type:Optional: No
Call by Reference: Yes
SYSTEM_ERROR - System Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EMMA_LOG_PROCESS_START 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_iv_bparea | TYPE EMMA_BPAREA, " | |||
lv_ev_log_handle | TYPE BALLOGHNDL, " | |||
lv_bparea_not_found | TYPE BALLOGHNDL, " | |||
lv_iv_runmode | TYPE EMMA_XPRUN, " ' ' | |||
lv_iv_massprocess | TYPE BOOLE_D, " ' ' | |||
lv_iv_db_update | TYPE BOOLE_D, " 'X' | |||
lv_iv_newprocess | TYPE BOOLE_D, " | |||
lv_iv_start_timestampl | TYPE TIMESTAMPL, " | |||
lv_iv_bpcode | TYPE EMMA_BPCODE, " | |||
lv_ev_bpguid_c | TYPE EMMA_BPGUID_C, " | |||
lv_bparea_meas_inactive | TYPE EMMA_BPGUID_C, " | |||
lv_iv_tcode | TYPE TCODE, " | |||
lv_bpcode_not_found | TYPE TCODE, " | |||
lv_iv_main_bus_objtype | TYPE SWO_OBJTYP, " | |||
lv_logobject_subobject_not_specif | TYPE SWO_OBJTYP, " | |||
lv_system_error | TYPE SWO_OBJTYP, " | |||
lv_iv_main_bus_objkey | TYPE SWO_OBJTYP, " | |||
lv_is_log_info | TYPE EMMA_PROC_LOG_OPEN, " | |||
lv_iv_start_timestamp | TYPE TIMESTAMP, " | |||
lv_iv_no_time_meas | TYPE EMMA_PROC_NO_TIME_MEAS, " | |||
lv_is_busobjects | TYPE EMMA_PROC_BUSOBJECTS. " |
  CALL FUNCTION 'EMMA_LOG_PROCESS_START' "Note start of process |
EXPORTING | ||
IV_BPAREA | = lv_iv_bparea | |
IV_RUNMODE | = lv_iv_runmode | |
IV_MASSPROCESS | = lv_iv_massprocess | |
IV_DB_UPDATE | = lv_iv_db_update | |
IV_NEWPROCESS | = lv_iv_newprocess | |
IV_START_TIMESTAMPL | = lv_iv_start_timestampl | |
IV_BPCODE | = lv_iv_bpcode | |
IV_TCODE | = lv_iv_tcode | |
IV_MAIN_BUS_OBJTYPE | = lv_iv_main_bus_objtype | |
IV_MAIN_BUS_OBJKEY | = lv_iv_main_bus_objkey | |
IS_LOG_INFO | = lv_is_log_info | |
IV_START_TIMESTAMP | = lv_iv_start_timestamp | |
IV_NO_TIME_MEAS | = lv_iv_no_time_meas | |
IS_BUSOBJECTS | = lv_is_busobjects | |
IMPORTING | ||
EV_LOG_HANDLE | = lv_ev_log_handle | |
EV_BPGUID_C | = lv_ev_bpguid_c | |
EXCEPTIONS | ||
BPAREA_NOT_FOUND = 1 | ||
BPAREA_MEAS_INACTIVE = 2 | ||
BPCODE_NOT_FOUND = 3 | ||
LOGOBJECT_SUBOBJECT_NOT_SPECIF = 4 | ||
SYSTEM_ERROR = 5 | ||
. " EMMA_LOG_PROCESS_START |
ABAP code using 7.40 inline data declarations to call FM EMMA_LOG_PROCESS_START
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.DATA(ld_iv_runmode) | = ' '. | |||
DATA(ld_iv_massprocess) | = ' '. | |||
DATA(ld_iv_db_update) | = 'X'. | |||
Search for further information about these or an SAP related objects