SAP IUUC_DELETE_SEQUENCES Function Module for delete all IUUC-related sequences
IUUC_DELETE_SEQUENCES is a standard iuuc delete sequences 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 all IUUC-related sequences 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 iuuc delete sequences FM, simply by entering the name IUUC_DELETE_SEQUENCES into the relevant SAP transaction such as SE37 or SE38.
Function Group: IUUC_SDB6
Program Name: SAPLIUUC_SDB6
Main Program: SAPLIUUC_SDB6
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function IUUC_DELETE_SEQUENCES 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 'IUUC_DELETE_SEQUENCES'"delete all IUUC-related sequences.
EXCEPTIONS
SEQUENCE_DROP_FAILED = 1 TRIGGERS_EXIST = 2
EXCEPTIONS details
SEQUENCE_DROP_FAILED - sequence drop failed
Data type:Optional: No
Call by Reference: Yes
TRIGGERS_EXIST - Triggers exist - Sequences must not be dropped
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IUUC_DELETE_SEQUENCES 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_sequence_drop_failed | TYPE STRING, " | |||
| lv_triggers_exist | TYPE STRING. " |
|   CALL FUNCTION 'IUUC_DELETE_SEQUENCES' "delete all IUUC-related sequences |
| EXCEPTIONS | ||
| SEQUENCE_DROP_FAILED = 1 | ||
| TRIGGERS_EXIST = 2 | ||
| . " IUUC_DELETE_SEQUENCES | ||
ABAP code using 7.40 inline data declarations to call FM IUUC_DELETE_SEQUENCES
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