SAP CLO0_DDB_VAL_DELETE Function Module for
CLO0_DDB_VAL_DELETE is a standard clo0 ddb val delete 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 clo0 ddb val delete FM, simply by entering the name CLO0_DDB_VAL_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CLO0
Program Name: SAPLCLO0
Main Program: SAPLCLO0
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CLO0_DDB_VAL_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 'CLO0_DDB_VAL_DELETE'".
EXPORTING
* CHANGE_NUMBER_IMP = "Change number
CLASSTYPE_IMP = "Class type
CLASS_IMP = "Class
* DATE_OF_CHANGE_IMP = "Change date
OBJECT_IMP = "Object
OBJ_STRUCTURE_IMP = "Database table of objects
EXCEPTIONS
ALLOCATION_NOT_EXIST = 1 FOREIGN_LOCK = 2 SYSTEM_FAILURE = 3 CHANGE_NR_NOT_EXIST = 4 OTHERS = 5
IMPORTING Parameters details for CLO0_DDB_VAL_DELETE
CHANGE_NUMBER_IMP - Change number
Data type: RMCLF-AENNR1Optional: Yes
Call by Reference: No ( called with pass by value option)
CLASSTYPE_IMP - Class type
Data type: KSSK-KLARTOptional: No
Call by Reference: No ( called with pass by value option)
CLASS_IMP - Class
Data type: KLAH-CLASSOptional: No
Call by Reference: No ( called with pass by value option)
DATE_OF_CHANGE_IMP - Change date
Data type: RMCLF-DATUV1Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_IMP - Object
Data type: KSSK-OBJEKOptional: No
Call by Reference: No ( called with pass by value option)
OBJ_STRUCTURE_IMP - Database table of objects
Data type: TCLA-OBTABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ALLOCATION_NOT_EXIST - Assignment does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FOREIGN_LOCK - Object locked
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE - System error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGE_NR_NOT_EXIST - Change number does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OTHERS - Other error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CLO0_DDB_VAL_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.| DATA: | ||||
| lv_change_number_imp | TYPE RMCLF-AENNR1, " | |||
| lv_allocation_not_exist | TYPE RMCLF, " | |||
| lv_foreign_lock | TYPE RMCLF, " | |||
| lv_classtype_imp | TYPE KSSK-KLART, " | |||
| lv_class_imp | TYPE KLAH-CLASS, " | |||
| lv_system_failure | TYPE KLAH, " | |||
| lv_date_of_change_imp | TYPE RMCLF-DATUV1, " | |||
| lv_change_nr_not_exist | TYPE RMCLF, " | |||
| lv_others | TYPE RMCLF, " | |||
| lv_object_imp | TYPE KSSK-OBJEK, " | |||
| lv_obj_structure_imp | TYPE TCLA-OBTAB. " |
|   CALL FUNCTION 'CLO0_DDB_VAL_DELETE' " |
| EXPORTING | ||
| CHANGE_NUMBER_IMP | = lv_change_number_imp | |
| CLASSTYPE_IMP | = lv_classtype_imp | |
| CLASS_IMP | = lv_class_imp | |
| DATE_OF_CHANGE_IMP | = lv_date_of_change_imp | |
| OBJECT_IMP | = lv_object_imp | |
| OBJ_STRUCTURE_IMP | = lv_obj_structure_imp | |
| EXCEPTIONS | ||
| ALLOCATION_NOT_EXIST = 1 | ||
| FOREIGN_LOCK = 2 | ||
| SYSTEM_FAILURE = 3 | ||
| CHANGE_NR_NOT_EXIST = 4 | ||
| OTHERS = 5 | ||
| . " CLO0_DDB_VAL_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM CLO0_DDB_VAL_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.| "SELECT single AENNR1 FROM RMCLF INTO @DATA(ld_change_number_imp). | ||||
| "SELECT single KLART FROM KSSK INTO @DATA(ld_classtype_imp). | ||||
| "SELECT single CLASS FROM KLAH INTO @DATA(ld_class_imp). | ||||
| "SELECT single DATUV1 FROM RMCLF INTO @DATA(ld_date_of_change_imp). | ||||
| "SELECT single OBJEK FROM KSSK INTO @DATA(ld_object_imp). | ||||
| "SELECT single OBTAB FROM TCLA INTO @DATA(ld_obj_structure_imp). | ||||
Search for further information about these or an SAP related objects