SAP SALC_CACHE_RELEVANT_MTECLASSES Function Module for









SALC_CACHE_RELEVANT_MTECLASSES is a standard salc cache relevant mteclasses SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 salc cache relevant mteclasses FM, simply by entering the name SALC_CACHE_RELEVANT_MTECLASSES into the relevant SAP transaction such as SE37 or SE38.

Function Group: SAL_CACHE_RECEIVE
Program Name: SAPLSAL_CACHE_RECEIVE
Main Program: SAPLSAL_CACHE_RECEIVE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SALC_CACHE_RELEVANT_MTECLASSES 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 'SALC_CACHE_RELEVANT_MTECLASSES'"
  EXPORTING
   SYSID =  "Name of SAP R/3 System
*  GET_MTE_CLASSES = 'X' "Alerts: Indicator ('X' or ' ' )
*  PERFDB_RES_FLAG = ' ' "

 IMPORTING
   CACHE_NOT_CONFIGURED =  "Alerts: Indicator ('X' or ' ' )

TABLES
*  MTECLASSES =  "Table Containing MTE Classes
*  MTECLASSES_IN_PERFDB =  "
*  CONTEXTS =  "
*  TID =  "Alert: Global Monitoring Type Identifier
*  TID_IN_PERFDB =  "Alert: Global Monitoring Type Identifier
*  TID_VISI_MAXLEVEL =  "Alert: TID + MaxLevel + VisibleOnUserLevel
.



IMPORTING Parameters details for SALC_CACHE_RELEVANT_MTECLASSES

SYSID - Name of SAP R/3 System

Data type: SYSYSID
Optional: No
Call by Reference: No ( called with pass by value option)

GET_MTE_CLASSES - Alerts: Indicator ('X' or SPACE )

Data type: ALFLAG
Default: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)

PERFDB_RES_FLAG -

Data type: ALPDBRTYP1
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SALC_CACHE_RELEVANT_MTECLASSES

CACHE_NOT_CONFIGURED - Alerts: Indicator ('X' or SPACE )

Data type: ALFLAG
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SALC_CACHE_RELEVANT_MTECLASSES

MTECLASSES - Table Containing MTE Classes

Data type: ALMTECLS
Optional: Yes
Call by Reference: Yes

MTECLASSES_IN_PERFDB -

Data type: ALMTECLS
Optional: Yes
Call by Reference: Yes

CONTEXTS -

Data type: ALMTECLS
Optional: Yes
Call by Reference: Yes

TID - Alert: Global Monitoring Type Identifier

Data type: ALGLOBTID
Optional: Yes
Call by Reference: Yes

TID_IN_PERFDB - Alert: Global Monitoring Type Identifier

Data type: ALGLOBTID
Optional: Yes
Call by Reference: Yes

TID_VISI_MAXLEVEL - Alert: TID + MaxLevel + VisibleOnUserLevel

Data type: ALTIDMAXLV
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SALC_CACHE_RELEVANT_MTECLASSES 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_sysid  TYPE SYSYSID, "   
lt_mteclasses  TYPE STANDARD TABLE OF ALMTECLS, "   
lv_cache_not_configured  TYPE ALFLAG, "   
lv_get_mte_classes  TYPE ALFLAG, "   'X'
lt_mteclasses_in_perfdb  TYPE STANDARD TABLE OF ALMTECLS, "   
lt_contexts  TYPE STANDARD TABLE OF ALMTECLS, "   
lv_perfdb_res_flag  TYPE ALPDBRTYP1, "   ' '
lt_tid  TYPE STANDARD TABLE OF ALGLOBTID, "   
lt_tid_in_perfdb  TYPE STANDARD TABLE OF ALGLOBTID, "   
lt_tid_visi_maxlevel  TYPE STANDARD TABLE OF ALTIDMAXLV. "   

  CALL FUNCTION 'SALC_CACHE_RELEVANT_MTECLASSES'  "
    EXPORTING
         SYSID = lv_sysid
         GET_MTE_CLASSES = lv_get_mte_classes
         PERFDB_RES_FLAG = lv_perfdb_res_flag
    IMPORTING
         CACHE_NOT_CONFIGURED = lv_cache_not_configured
    TABLES
         MTECLASSES = lt_mteclasses
         MTECLASSES_IN_PERFDB = lt_mteclasses_in_perfdb
         CONTEXTS = lt_contexts
         TID = lt_tid
         TID_IN_PERFDB = lt_tid_in_perfdb
         TID_VISI_MAXLEVEL = lt_tid_visi_maxlevel
. " SALC_CACHE_RELEVANT_MTECLASSES




ABAP code using 7.40 inline data declarations to call FM SALC_CACHE_RELEVANT_MTECLASSES

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_get_mte_classes) = 'X'.
 
 
 
DATA(ld_perfdb_res_flag) = ' '.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!