SAP SLDAPI_CREATE_HTTP_DEST Function Module for









SLDAPI_CREATE_HTTP_DEST is a standard sldapi create http dest 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 sldapi create http dest FM, simply by entering the name SLDAPI_CREATE_HTTP_DEST into the relevant SAP transaction such as SE37 or SE38.

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



Function SLDAPI_CREATE_HTTP_DEST 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 'SLDAPI_CREATE_HTTP_DEST'"
EXPORTING
ACCESSDATA = "
* PATH_PREFIX = '/sld/cimom' "
* UPDATE = ABAP_FALSE "

IMPORTING
DEST_NAME = "

EXCEPTIONS
DUPLICATE_KEY = 1 INVALID_DATA = 2 DEST_API_FAILURE = 3
.



IMPORTING Parameters details for SLDAPI_CREATE_HTTP_DEST

ACCESSDATA -

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

PATH_PREFIX -

Data type: STRING
Default: '/sld/cimom'
Optional: Yes
Call by Reference: Yes

UPDATE -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for SLDAPI_CREATE_HTTP_DEST

DEST_NAME -

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

EXCEPTIONS details

DUPLICATE_KEY -

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

INVALID_DATA -

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

DEST_API_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SLDAPI_CREATE_HTTP_DEST 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_dest_name  TYPE RFCDEST, "   
lv_accessdata  TYPE SLD_S_ACCESSDATA_DISPLAY, "   
lv_duplicate_key  TYPE SLD_S_ACCESSDATA_DISPLAY, "   
lv_path_prefix  TYPE STRING, "   '/sld/cimom'
lv_invalid_data  TYPE STRING, "   
lv_update  TYPE ABAP_BOOL, "   ABAP_FALSE
lv_dest_api_failure  TYPE ABAP_BOOL. "   

  CALL FUNCTION 'SLDAPI_CREATE_HTTP_DEST'  "
    EXPORTING
         ACCESSDATA = lv_accessdata
         PATH_PREFIX = lv_path_prefix
         UPDATE = lv_update
    IMPORTING
         DEST_NAME = lv_dest_name
    EXCEPTIONS
        DUPLICATE_KEY = 1
        INVALID_DATA = 2
        DEST_API_FAILURE = 3
. " SLDAPI_CREATE_HTTP_DEST




ABAP code using 7.40 inline data declarations to call FM SLDAPI_CREATE_HTTP_DEST

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.

 
 
 
DATA(ld_path_prefix) = '/sld/cimom'.
 
 
DATA(ld_update) = ABAP_FALSE.
 
 


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!