EMMA_LOG_PROCESS_CHECK_ACTIVE SAP Function module

EMMA_LOG_PROCESS_CHECK_ACTIVE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name EMMA_LOG_PROCESS_CHECK_ACTIVE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: EMMA_BW
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM EMMA_LOG_PROCESS_CHECK_ACTIVE - EMMA LOG PROCESS CHECK ACTIVE

CALL FUNCTION 'EMMA_LOG_PROCESS_CHECK_ACTIVE' "
  EXPORTING
    iv_bpcode =                 " emma_bpcode   Business Process Code
  IMPORTING
    ev_bparea =                 " emma_bparea   Business Process Area
    ev_bpa_active =             " emma_bpa_active
    ev_extract_class =          " emma_bw_extrclass  Extract Class
    ev_kpi_msg =                " emma_kpi_msg
  EXCEPTIONS
    EXTRACT_CLASS_NOT_FOUND = 1  "
    BPCODE_NOT_FOUND = 2        "               Business Process Code Not Found
    BPAREA_NOT_FOUND = 3        "               Business process area not found
    .  "  EMMA_LOG_PROCESS_CHECK_ACTIVE

ABAP code example for Function Module EMMA_LOG_PROCESS_CHECK_ACTIVE

The ABAP code below is a full code listing to execute function module EMMA_LOG_PROCESS_CHECK_ACTIVE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_bparea  
 
 TYPE EMMA_BPAREA
,
ld_ev_bpa_active  
 
 TYPE EMMA_BPA_ACTIVE
,
ld_ev_extract_class  
 
 TYPE EMMA_BW_EXTRCLASS
,
ld_ev_kpi_msg  
 
 TYPE EMMA_KPI_MSG
.


DATA(ld_iv_bpcode) = 'Check type of data required'.
.

CALL FUNCTION 'EMMA_LOG_PROCESS_CHECK_ACTIVE'
  EXPORTING
    iv_bpcode =                  ld_iv_bpcode
  IMPORTING
    ev_bparea =                  ld_ev_bparea
    ev_bpa_active =              ld_ev_bpa_active
    ev_extract_class =           ld_ev_extract_class
    ev_kpi_msg =                 ld_ev_kpi_msg
  EXCEPTIONS
    EXTRACT_CLASS_NOT_FOUND =    1
    BPCODE_NOT_FOUND =           2
    BPAREA_NOT_FOUND =           3
    .  "  EMMA_LOG_PROCESS_CHECK_ACTIVE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ev_bparea
 
 TYPE EMMA_BPAREA ,
ld_iv_bpcode
 
 TYPE EMMA_BPCODE ,
ld_ev_bpa_active
 
 TYPE EMMA_BPA_ACTIVE ,
ld_ev_extract_class
 
 TYPE EMMA_BW_EXTRCLASS ,
ld_ev_kpi_msg
 
 TYPE EMMA_KPI_MSG .


ld_iv_bpcode = 'Check type of data required'.