SAP SALP_SIMPLE_MON_GET_TID Function Module for get TID of an attribut

Search SAP Function Modules

SALP_SIMPLE_MON_GET_TID is a standard salp simple mon get tid SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for get TID of an attribut processing and below is the pattern details for this FM, 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 salp simple mon get tid FM, simply by entering the name SALP_SIMPLE_MON_GET_TID into the relevant SAP transaction such as SE37 or SE38.

Function Group: SALP_UTIL
Program Name: SAPLSALP_UTIL
Main Program: SAPLSALP_UTIL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SALP_SIMPLE_MON_GET_TID 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 'SALP_SIMPLE_MON_GET_TID'"get TID of  an attribut
  EXPORTING
   LONGNAME =  "Alert: monitoring type full name
*  OBJ_CLASS = '' "CCMS Monitoring Architecture: Name of MTE class
*  ATT_CLASS = '' "CCMS Monitoring Architecture: Name of MTE class
*  MTETYPE = '100' "Alert: monitoring type class (perf., single msg.,...)
*  PERF_UNIT = '' "Unit, only needed for MTETYPE = 100
*  OPTIONAL_PARAMETERS =  "Table with optional parameters

 IMPORTING
   TID =  "Alert: global monitoring type identifier

EXCEPTIONS
   ILLEGAL_NAME = 1    NAME_TOO_SHORT = 2    ONLY_LOCAL_SYSID_ALLOWED = 3    CREATE_CONTEXT_ERROR = 4    CREATE_PATH_ERROR = 5    CREATE_OBJECT_ERROR = 6    CREATE_ATTRIBUTE_ERROR = 7 

.

IMPORTING Parameters details for SALP_SIMPLE_MON_GET_TID

LONGNAME - Alert: monitoring type full name

Data type: ALMTNAME_L-ALMTFULLNM
Optional: No
Call by Reference: No ( called with pass by value option)

OBJ_CLASS - CCMS Monitoring Architecture: Name of MTE class

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

ATT_CLASS - CCMS Monitoring Architecture: Name of MTE class

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

MTETYPE - Alert: monitoring type class (perf., single msg.,...)

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

PERF_UNIT - Unit, only needed for MTETYPE = 100

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

OPTIONAL_PARAMETERS - Table with optional parameters

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

EXPORTING Parameters details for SALP_SIMPLE_MON_GET_TID

TID - Alert: global monitoring type identifier

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

EXCEPTIONS details

ILLEGAL_NAME -

Data type:
Optional: No
Call by Reference: Yes

NAME_TOO_SHORT -

Data type:
Optional: No
Call by Reference: Yes

ONLY_LOCAL_SYSID_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

CREATE_CONTEXT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CREATE_PATH_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CREATE_OBJECT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CREATE_ATTRIBUTE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SALP_SIMPLE_MON_GET_TID 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.

ABAP code using 7.40 inline data declarations to call FM SALP_SIMPLE_MON_GET_TID

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.

Search for further information about these or an SAP related objects