FC_USER_CHECK_MONITOR SAP Function module

FC_USER_CHECK_MONITOR 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 FC_USER_CHECK_MONITOR into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM FC_USER_CHECK_MONITOR - FC USER CHECK MONITOR

CALL FUNCTION 'FC_USER_CHECK_MONITOR' "
  EXPORTING
    e_dimen =                   " fc_dimen      Dimension
    e_rvers =                   " fc_rvers      Version
    e_ryear =                   " fc_ryear      Fiscal Year
    e_perid =                   " fc_perid      Period
    e_cacti =                   " fc_cacti
  IMPORTING
    i_cm_flag =                 " fc_flg
  EXCEPTIONS
    CACTI_NOT_FOUND = 1         "
    CACTI_NOT_USER_DEFINED = 2  "
    .  "  FC_USER_CHECK_MONITOR

ABAP code example for Function Module FC_USER_CHECK_MONITOR

The ABAP code below is a full code listing to execute function module FC_USER_CHECK_MONITOR 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_i_cm_flag  
 
 TYPE FC_FLG
.


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

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

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

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

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

CALL FUNCTION 'FC_USER_CHECK_MONITOR'
  EXPORTING
    e_dimen =                    ld_e_dimen
    e_rvers =                    ld_e_rvers
    e_ryear =                    ld_e_ryear
    e_perid =                    ld_e_perid
    e_cacti =                    ld_e_cacti
  IMPORTING
    i_cm_flag =                  ld_i_cm_flag
  EXCEPTIONS
    CACTI_NOT_FOUND =            1
    CACTI_NOT_USER_DEFINED =     2
    .  "  FC_USER_CHECK_MONITOR

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
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_i_cm_flag
 
 TYPE FC_FLG ,
ld_e_dimen
 
 TYPE FC_DIMEN ,
ld_e_rvers
 
 TYPE FC_RVERS ,
ld_e_ryear
 
 TYPE FC_RYEAR ,
ld_e_perid
 
 TYPE FC_PERID ,
ld_e_cacti
 
 TYPE FC_CACTI .


ld_e_dimen = 'Check type of data required'.
ld_e_rvers = 'Check type of data required'.
ld_e_ryear = 'Check type of data required'.
ld_e_perid = 'Check type of data required'.
ld_e_cacti = 'Check type of data required'.