SALP_SM_PERF_RUNTIME SAP Function module

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

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

Pattern for FM SALP_SM_PERF_RUNTIME - SALP SM PERF RUNTIME

CALL FUNCTION 'SALP_SM_PERF_RUNTIME' "
  EXPORTING
    sm_object =                 " char2
*   sysid_or_applsrv =          " char40
    parent_tid =                " alglobtid     Alert: Global Monitoring Type Identifier
    runtime_value =             " int4
  EXCEPTIONS
    NO_ATTRIB = 1               "
    EMPTY_INPUT = 2             "
    ILLEGAL_INPUT = 3           "
    ERROR_REPORTING_VALUE = 4   "
    .  "  SALP_SM_PERF_RUNTIME

ABAP code example for Function Module SALP_SM_PERF_RUNTIME

The ABAP code below is a full code listing to execute function module SALP_SM_PERF_RUNTIME 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_sm_object) = 'Check type of data required'.

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

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

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

CALL FUNCTION 'SALP_SM_PERF_RUNTIME'
  EXPORTING
    sm_object =                  ld_sm_object
*   sysid_or_applsrv =           ld_sysid_or_applsrv
    parent_tid =                 ld_parent_tid
    runtime_value =              ld_runtime_value
  EXCEPTIONS
    NO_ATTRIB =                  1
    EMPTY_INPUT =                2
    ILLEGAL_INPUT =              3
    ERROR_REPORTING_VALUE =      4
    .  "  SALP_SM_PERF_RUNTIME

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_sm_object
 
 TYPE CHAR2 ,
ld_sysid_or_applsrv
 
 TYPE CHAR40 ,
ld_parent_tid
 
 TYPE ALGLOBTID ,
ld_runtime_value
 
 TYPE INT4 .


ld_sm_object = 'Check type of data required'.
ld_sysid_or_applsrv = 'Check type of data required'.
ld_parent_tid = 'Check type of data required'.
ld_runtime_value = 'Check type of data required'.