SAP SEO_CLASS_DELETE_COMPLETE Function Module for Klasse löschen
SEO_CLASS_DELETE_COMPLETE is a standard seo class delete complete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Klasse löschen 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 seo class delete complete FM, simply by entering the name SEO_CLASS_DELETE_COMPLETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEOQ
Program Name: SAPLSEOQ
Main Program: SAPLSEOQ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SEO_CLASS_DELETE_COMPLETE 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 'SEO_CLASS_DELETE_COMPLETE'"Klasse löschen.
EXPORTING
CLSKEY = "Class
* GENFLAG = ' ' "Generation Flag
* AUTHORITY_CHECK = SEOX_TRUE "Execute authority check (suppress possible only for GENFLAG = 'X')
* SUPPRESS_DOCU_DELETE = SEOX_FALSE "
* SUPPRESS_COMMIT = SEOX_FALSE "No DB_COMMIT will be executed
* SUPPRESS_CORR = SEOX_FALSE "Suppress Corr-Insert and Corr-Check
* LIFECYCLE_MANAGER = "Lifecycle manager
* LOCK_HANDLE = "Lock Handle
* SUPPRESS_DIALOG = SEOX_FALSE "X = no user interaction
CHANGING
* CORRNR = "Request/Task
EXCEPTIONS
NOT_EXISTING = 1 IS_INTERFACE = 2 DB_ERROR = 3 NO_ACCESS = 4 OTHER = 5
IMPORTING Parameters details for SEO_CLASS_DELETE_COMPLETE
CLSKEY - Class
Data type: SEOCLSKEYOptional: No
Call by Reference: No ( called with pass by value option)
GENFLAG - Generation Flag
Data type: GENFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
AUTHORITY_CHECK - Execute authority check (suppress possible only for GENFLAG = 'X')
Data type: SEOX_BOOLEANDefault: SEOX_TRUE
Optional: No
Call by Reference: No ( called with pass by value option)
SUPPRESS_DOCU_DELETE -
Data type: SEOX_BOOLEANDefault: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUPPRESS_COMMIT - No DB_COMMIT will be executed
Data type: SEOX_BOOLEANDefault: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUPPRESS_CORR - Suppress Corr-Insert and Corr-Check
Data type: SEOX_BOOLEANDefault: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LIFECYCLE_MANAGER - Lifecycle manager
Data type: IF_ADT_LIFECYCLE_MANAGEROptional: Yes
Call by Reference: Yes
LOCK_HANDLE - Lock Handle
Data type: IF_ADT_LOCK_HANDLEOptional: Yes
Call by Reference: Yes
SUPPRESS_DIALOG - X = no user interaction
Data type: SEOX_BOOLEANDefault: SEOX_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for SEO_CLASS_DELETE_COMPLETE
CORRNR - Request/Task
Data type: TRKORROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_EXISTING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IS_INTERFACE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DB_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ACCESS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OTHER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SEO_CLASS_DELETE_COMPLETE 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_clskey | TYPE SEOCLSKEY, " | |||
| lv_corrnr | TYPE TRKORR, " | |||
| lv_not_existing | TYPE TRKORR, " | |||
| lv_genflag | TYPE GENFLAG, " SPACE | |||
| lv_is_interface | TYPE GENFLAG, " | |||
| lv_db_error | TYPE GENFLAG, " | |||
| lv_authority_check | TYPE SEOX_BOOLEAN, " SEOX_TRUE | |||
| lv_no_access | TYPE SEOX_BOOLEAN, " | |||
| lv_suppress_docu_delete | TYPE SEOX_BOOLEAN, " SEOX_FALSE | |||
| lv_other | TYPE SEOX_BOOLEAN, " | |||
| lv_suppress_commit | TYPE SEOX_BOOLEAN, " SEOX_FALSE | |||
| lv_suppress_corr | TYPE SEOX_BOOLEAN, " SEOX_FALSE | |||
| lv_lifecycle_manager | TYPE IF_ADT_LIFECYCLE_MANAGER, " | |||
| lv_lock_handle | TYPE IF_ADT_LOCK_HANDLE, " | |||
| lv_suppress_dialog | TYPE SEOX_BOOLEAN. " SEOX_FALSE |
|   CALL FUNCTION 'SEO_CLASS_DELETE_COMPLETE' "Klasse löschen |
| EXPORTING | ||
| CLSKEY | = lv_clskey | |
| GENFLAG | = lv_genflag | |
| AUTHORITY_CHECK | = lv_authority_check | |
| SUPPRESS_DOCU_DELETE | = lv_suppress_docu_delete | |
| SUPPRESS_COMMIT | = lv_suppress_commit | |
| SUPPRESS_CORR | = lv_suppress_corr | |
| LIFECYCLE_MANAGER | = lv_lifecycle_manager | |
| LOCK_HANDLE | = lv_lock_handle | |
| SUPPRESS_DIALOG | = lv_suppress_dialog | |
| CHANGING | ||
| CORRNR | = lv_corrnr | |
| EXCEPTIONS | ||
| NOT_EXISTING = 1 | ||
| IS_INTERFACE = 2 | ||
| DB_ERROR = 3 | ||
| NO_ACCESS = 4 | ||
| OTHER = 5 | ||
| . " SEO_CLASS_DELETE_COMPLETE | ||
ABAP code using 7.40 inline data declarations to call FM SEO_CLASS_DELETE_COMPLETE
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_genflag) | = ' '. | |||
| DATA(ld_authority_check) | = SEOX_TRUE. | |||
| DATA(ld_suppress_docu_delete) | = SEOX_FALSE. | |||
| DATA(ld_suppress_commit) | = SEOX_FALSE. | |||
| DATA(ld_suppress_corr) | = SEOX_FALSE. | |||
| DATA(ld_suppress_dialog) | = SEOX_FALSE. | |||
Search for further information about these or an SAP related objects