SAP MSS_MON_OBJECT_TYPE Function Module for Find the type of an object

Search SAP Function Modules

MSS_MON_OBJECT_TYPE is a standard mss mon object type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find the type of an object 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 mss mon object type FM, simply by entering the name MSS_MON_OBJECT_TYPE into the relevant SAP transaction such as SE37 or SE38.

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

Function MSS_MON_OBJECT_TYPE 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 'MSS_MON_OBJECT_TYPE'"Find the type of an object
  EXPORTING
*  CON_NAME = 'DEFAULT' "DBCON name
*  SCHEMA = ' ' "Target Schema
   OBJECT_NAME =  "Object name
*  SCHEMA_NAME =  "Schema name
*  DB_NAME =  "Database name

 IMPORTING
   OBJECT_TYPE =  "Object type

EXCEPTIONS
   NOT_RUNNING_ON_MSSQL = 1    DB_ERROR = 2    INTERNAL_ERROR = 3    DB_NOT_FOUND = 4    NO_DB_ACCESS = 5    SCHEMA_NOT_FOUND = 6    INVALID_INPUT = 7    OBJECT_NOT_FOUND = 8    CONNECT_ERROR = 9 

.

IMPORTING Parameters details for MSS_MON_OBJECT_TYPE

CON_NAME - DBCON name

Data type: DBCON-CON_NAME
Default: 'DEFAULT'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SCHEMA - Target Schema

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

OBJECT_NAME - Object name

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

SCHEMA_NAME - Schema name

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

DB_NAME - Database name

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

EXPORTING Parameters details for MSS_MON_OBJECT_TYPE

OBJECT_TYPE - Object type

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

EXCEPTIONS details

NOT_RUNNING_ON_MSSQL -

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

DB_ERROR -

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

INTERNAL_ERROR -

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

DB_NOT_FOUND -

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

NO_DB_ACCESS -

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

SCHEMA_NOT_FOUND -

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

INVALID_INPUT -

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

OBJECT_NOT_FOUND -

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

CONNECT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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

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