SAP EDI_PORT_DELETE_XML_HTTP Function Module for









EDI_PORT_DELETE_XML_HTTP is a standard edi port delete xml http 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 edi port delete xml http FM, simply by entering the name EDI_PORT_DELETE_XML_HTTP into the relevant SAP transaction such as SE37 or SE38.

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



Function EDI_PORT_DELETE_XML_HTTP 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 'EDI_PORT_DELETE_XML_HTTP'"
EXPORTING
PORTNAME = "

EXCEPTIONS
PORT_NOT_EXIST = 1 PORT_NOT_TYPE_XML_HTTP = 2 ERROR_IN_DELETE = 3
.



IMPORTING Parameters details for EDI_PORT_DELETE_XML_HTTP

PORTNAME -

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

EXCEPTIONS details

PORT_NOT_EXIST - Port does not exist

Data type:
Optional: No
Call by Reference: Yes

PORT_NOT_TYPE_XML_HTTP -

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_DELETE - Error while data was deleted from the database

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EDI_PORT_DELETE_XML_HTTP 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_portname  TYPE EDIPORT-PORT, "   
lv_port_not_exist  TYPE EDIPORT, "   
lv_port_not_type_xml_http  TYPE EDIPORT, "   
lv_error_in_delete  TYPE EDIPORT. "   

  CALL FUNCTION 'EDI_PORT_DELETE_XML_HTTP'  "
    EXPORTING
         PORTNAME = lv_portname
    EXCEPTIONS
        PORT_NOT_EXIST = 1
        PORT_NOT_TYPE_XML_HTTP = 2
        ERROR_IN_DELETE = 3
. " EDI_PORT_DELETE_XML_HTTP




ABAP code using 7.40 inline data declarations to call FM EDI_PORT_DELETE_XML_HTTP

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.

"SELECT single PORT FROM EDIPORT INTO @DATA(ld_portname).
 
 
 
 


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!