SAP SCSM_GET_DOWNTIME_MTE_TBL Function Module for









SCSM_GET_DOWNTIME_MTE_TBL is a standard scsm get downtime mte tbl 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 scsm get downtime mte tbl FM, simply by entering the name SCSM_GET_DOWNTIME_MTE_TBL into the relevant SAP transaction such as SE37 or SE38.

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



Function SCSM_GET_DOWNTIME_MTE_TBL 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 'SCSM_GET_DOWNTIME_MTE_TBL'"
TABLES
* MTE_LIST_NO_ALERTS = "
* MTE_LIST_NO_VALUES = "

EXCEPTIONS
WRONG_KERNEL_VERSION = 1 C_CALL_FAILED = 2
.



TABLES Parameters details for SCSM_GET_DOWNTIME_MTE_TBL

MTE_LIST_NO_ALERTS -

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

MTE_LIST_NO_VALUES -

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

EXCEPTIONS details

WRONG_KERNEL_VERSION -

Data type:
Optional: No
Call by Reference: Yes

C_CALL_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCSM_GET_DOWNTIME_MTE_TBL 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:
lt_mte_list_no_alerts  TYPE STANDARD TABLE OF ALMTFULLNMTBL, "   
lv_wrong_kernel_version  TYPE ALMTFULLNMTBL, "   
lv_c_call_failed  TYPE ALMTFULLNMTBL, "   
lt_mte_list_no_values  TYPE STANDARD TABLE OF ALMTFULLNMTBL. "   

  CALL FUNCTION 'SCSM_GET_DOWNTIME_MTE_TBL'  "
    TABLES
         MTE_LIST_NO_ALERTS = lt_mte_list_no_alerts
         MTE_LIST_NO_VALUES = lt_mte_list_no_values
    EXCEPTIONS
        WRONG_KERNEL_VERSION = 1
        C_CALL_FAILED = 2
. " SCSM_GET_DOWNTIME_MTE_TBL




ABAP code using 7.40 inline data declarations to call FM SCSM_GET_DOWNTIME_MTE_TBL

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



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!