SAP OO_INTERFACE_DELETE Function Module for Delete Interface

Search SAP Function Modules

OO_INTERFACE_DELETE is a standard oo interface delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete Interface 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 oo interface delete FM, simply by entering the name OO_INTERFACE_DELETE into the relevant SAP transaction such as SE37 or SE38.

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

Function OO_INTERFACE_DELETE 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 'OO_INTERFACE_DELETE'"Delete Interface
  EXPORTING
   INTERFACE =  "
*  COMMIT = SEOX_FALSE "
*  FORCE = SEOX_FALSE "
*  SUPPRESS_ACCESS_PERMISSION = SEOX_FALSE "
*  SUPPRESS_CORR = SEOX_FALSE "
*  NOTEASS_MODE = SEOX_FALSE "

CHANGING
*  CORRNR =  "Request/Task

EXCEPTIONS
   CANCELLED = 1    NOT_DELETED = 2 

.

IMPORTING Parameters details for OO_INTERFACE_DELETE

INTERFACE -

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

COMMIT -

Data type: SEOX_BOOLEAN
Default: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FORCE -

Data type: SEOX_BOOLEAN
Default: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUPPRESS_ACCESS_PERMISSION -

Data type: SEOX_BOOLEAN
Default: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUPPRESS_CORR -

Data type: SEOX_BOOLEAN
Default: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NOTEASS_MODE -

Data type: SEOX_BOOLEAN
Default: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for OO_INTERFACE_DELETE

CORRNR - Request/Task

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

EXCEPTIONS details

CANCELLED -

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

NOT_DELETED -

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

Copy and paste ABAP code example for OO_INTERFACE_DELETE 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.

ABAP code using 7.40 inline data declarations to call FM OO_INTERFACE_DELETE

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