SAP SP_CHECK_ENTERED_EXT_SERVER Function Module for









SP_CHECK_ENTERED_EXT_SERVER is a standard sp check entered ext server 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 sp check entered ext server FM, simply by entering the name SP_CHECK_ENTERED_EXT_SERVER into the relevant SAP transaction such as SE37 or SE38.

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



Function SP_CHECK_ENTERED_EXT_SERVER 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 'SP_CHECK_ENTERED_EXT_SERVER'"
  EXPORTING
   EXT_USER =  "
   EXTENSION =  "
   SERVER =  "

 IMPORTING
   ALLOWED =  "

EXCEPTIONS
   NOT_ALLOWED = 1    SERVER_NOT_EXIST = 2
.



IMPORTING Parameters details for SP_CHECK_ENTERED_EXT_SERVER

EXT_USER -

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

EXTENSION -

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

SERVER -

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

EXPORTING Parameters details for SP_CHECK_ENTERED_EXT_SERVER

ALLOWED -

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

EXCEPTIONS details

NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

SERVER_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SP_CHECK_ENTERED_EXT_SERVER 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_allowed  TYPE SP_BOOLEAN, "   
lv_ext_user  TYPE SP_USER, "   
lv_not_allowed  TYPE SP_USER, "   
lv_extension  TYPE SP_OWNTEL, "   
lv_server_not_exist  TYPE SP_OWNTEL, "   
lv_server  TYPE SX_NODE_ID. "   

  CALL FUNCTION 'SP_CHECK_ENTERED_EXT_SERVER'  "
    EXPORTING
         EXT_USER = lv_ext_user
         EXTENSION = lv_extension
         SERVER = lv_server
    IMPORTING
         ALLOWED = lv_allowed
    EXCEPTIONS
        NOT_ALLOWED = 1
        SERVER_NOT_EXIST = 2
. " SP_CHECK_ENTERED_EXT_SERVER




ABAP code using 7.40 inline data declarations to call FM SP_CHECK_ENTERED_EXT_SERVER

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!