SAP CNV_MBT_ADM_SERVER_VALID Function Module for Check if server is valid









CNV_MBT_ADM_SERVER_VALID is a standard cnv mbt adm server valid SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if server is valid 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 cnv mbt adm server valid FM, simply by entering the name CNV_MBT_ADM_SERVER_VALID into the relevant SAP transaction such as SE37 or SE38.

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



Function CNV_MBT_ADM_SERVER_VALID 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 'CNV_MBT_ADM_SERVER_VALID'"Check if server is valid
EXPORTING
IV_SERVER = "Server name

IMPORTING
EV_VALID = "Boolean Variable (X=True, -=False, Space=Unknown)
.



IMPORTING Parameters details for CNV_MBT_ADM_SERVER_VALID

IV_SERVER - Server name

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

EXPORTING Parameters details for CNV_MBT_ADM_SERVER_VALID

EV_VALID - Boolean Variable (X=True, -=False, Space=Unknown)

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

Copy and paste ABAP code example for CNV_MBT_ADM_SERVER_VALID 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_ev_valid  TYPE BOOLEAN, "   
lv_iv_server  TYPE BTCSRVNAME. "   

  CALL FUNCTION 'CNV_MBT_ADM_SERVER_VALID'  "Check if server is valid
    EXPORTING
         IV_SERVER = lv_iv_server
    IMPORTING
         EV_VALID = lv_ev_valid
. " CNV_MBT_ADM_SERVER_VALID




ABAP code using 7.40 inline data declarations to call FM CNV_MBT_ADM_SERVER_VALID

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!