VSCAN_CCMS_MONITOR SAP Function module

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

Associated Function Group: VSCAN_CCMS
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM VSCAN_CCMS_MONITOR - VSCAN CCMS MONITOR

CALL FUNCTION 'VSCAN_CCMS_MONITOR' "
  EXPORTING
    dialog_mode =               " altypes-char1  Dialog Box Yes / No
*   bypass_buffer =             " char1
*   if_name =                   " vscan_server_name
  TABLES
    mt_tool_info =              " altlexdesc
  EXCEPTIONS
    INVALID_DIALOG_MODE = 1     "
    MT_TOOL_INFO_MISSING = 2    "
    TOOL_INTENTIONALLY_ABORTED = 3  "
    DONT_START_TOOL_AGAIN = 4   "
    .  "  VSCAN_CCMS_MONITOR

ABAP code example for Function Module VSCAN_CCMS_MONITOR

The ABAP code below is a full code listing to execute function module VSCAN_CCMS_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:
it_mt_tool_info  
 
 TYPE STANDARD TABLE OF ALTLEXDESC,"TABLES PARAM
wa_mt_tool_info
 
 LIKE LINE OF it_mt_tool_info
.



DATA(ld_dialog_mode) = some text here

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

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

"populate fields of struture and append to itab
append wa_mt_tool_info to it_mt_tool_info.
.

CALL FUNCTION 'VSCAN_CCMS_MONITOR'
  EXPORTING
    dialog_mode =                ld_dialog_mode
*   bypass_buffer =              ld_bypass_buffer
*   if_name =                    ld_if_name
  TABLES
    mt_tool_info =               it_mt_tool_info
  EXCEPTIONS
    INVALID_DIALOG_MODE =        1
    MT_TOOL_INFO_MISSING =       2
    TOOL_INTENTIONALLY_ABORTED =    3
    DONT_START_TOOL_AGAIN =      4
    .  "  VSCAN_CCMS_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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_dialog_mode
 
 TYPE ALTYPES-CHAR1 ,
it_mt_tool_info
 
 TYPE STANDARD TABLE OF ALTLEXDESC ,
wa_mt_tool_info
 
 LIKE LINE OF it_mt_tool_info,
ld_bypass_buffer
 
 TYPE CHAR1 ,
ld_if_name
 
 TYPE VSCAN_SERVER_NAME .



ld_dialog_mode = some text here 

"populate fields of struture and append to itab
append wa_mt_tool_info to it_mt_tool_info.
ld_bypass_buffer = 'Check type of data required'.
ld_if_name = 'Check type of data required'.