SAP RSDU_PART_GENERIC_DROP_HDB Function Module for Add a partition to a partitioned table in a generic way
RSDU_PART_GENERIC_DROP_HDB is a standard rsdu part generic drop hdb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Add a partition to a partitioned table in a generic way 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 rsdu part generic drop hdb FM, simply by entering the name RSDU_PART_GENERIC_DROP_HDB into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDU_PART_HDB
Program Name: SAPLRSDU_PART_HDB
Main Program: SAPLRSDU_PART_HDB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSDU_PART_GENERIC_DROP_HDB 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 'RSDU_PART_GENERIC_DROP_HDB'"Add a partition to a partitioned table in a generic way.
EXPORTING
I_TABLNM = "
I_TS_DROP = "
I_TRUNCATE = "
I_SIMULATE = "
* I_CONNECTION = 'R/3*' "
IMPORTING
E_T_PROT = "
EXCEPTIONS
TABLE_NOT_EXISTS = 1 TABLE_NOT_PARTITIONED = 2 PARTITION_NOT_EXISTS = 3 DROP_PARTITION_FAILED = 4 WRONG_IMPORT_PARAMETERS = 5 NOT_IMPLEMENTED = 6 WRONG_PARTITION_NAME = 7 INHERITED_ERROR = 8 INITIAL_PARTITION = 9
IMPORTING Parameters details for RSDU_PART_GENERIC_DROP_HDB
I_TABLNM -
Data type: RSD_TABLNMOptional: No
Call by Reference: Yes
I_TS_DROP -
Data type: RSDU_TS_GENPART_INFOOptional: No
Call by Reference: Yes
I_TRUNCATE -
Data type: RS_BOOLOptional: No
Call by Reference: Yes
I_SIMULATE -
Data type: RS_BOOLOptional: No
Call by Reference: Yes
I_CONNECTION -
Data type: DBCON_NAMEDefault: 'R/3*'
Optional: No
Call by Reference: Yes
EXPORTING Parameters details for RSDU_PART_GENERIC_DROP_HDB
E_T_PROT -
Data type: RSDU_T_GENPART_PROTOptional: No
Call by Reference: Yes
EXCEPTIONS details
TABLE_NOT_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLE_NOT_PARTITIONED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTITION_NOT_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DROP_PARTITION_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_IMPORT_PARAMETERS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_IMPLEMENTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_PARTITION_NAME -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INHERITED_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INITIAL_PARTITION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSDU_PART_GENERIC_DROP_HDB 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_e_t_prot | TYPE RSDU_T_GENPART_PROT, " | |||
| lv_i_tablnm | TYPE RSD_TABLNM, " | |||
| lv_table_not_exists | TYPE RSD_TABLNM, " | |||
| lv_i_ts_drop | TYPE RSDU_TS_GENPART_INFO, " | |||
| lv_table_not_partitioned | TYPE RSDU_TS_GENPART_INFO, " | |||
| lv_i_truncate | TYPE RS_BOOL, " | |||
| lv_partition_not_exists | TYPE RS_BOOL, " | |||
| lv_i_simulate | TYPE RS_BOOL, " | |||
| lv_drop_partition_failed | TYPE RS_BOOL, " | |||
| lv_i_connection | TYPE DBCON_NAME, " 'R/3*' | |||
| lv_wrong_import_parameters | TYPE DBCON_NAME, " | |||
| lv_not_implemented | TYPE DBCON_NAME, " | |||
| lv_wrong_partition_name | TYPE DBCON_NAME, " | |||
| lv_inherited_error | TYPE DBCON_NAME, " | |||
| lv_initial_partition | TYPE DBCON_NAME. " |
|   CALL FUNCTION 'RSDU_PART_GENERIC_DROP_HDB' "Add a partition to a partitioned table in a generic way |
| EXPORTING | ||
| I_TABLNM | = lv_i_tablnm | |
| I_TS_DROP | = lv_i_ts_drop | |
| I_TRUNCATE | = lv_i_truncate | |
| I_SIMULATE | = lv_i_simulate | |
| I_CONNECTION | = lv_i_connection | |
| IMPORTING | ||
| E_T_PROT | = lv_e_t_prot | |
| EXCEPTIONS | ||
| TABLE_NOT_EXISTS = 1 | ||
| TABLE_NOT_PARTITIONED = 2 | ||
| PARTITION_NOT_EXISTS = 3 | ||
| DROP_PARTITION_FAILED = 4 | ||
| WRONG_IMPORT_PARAMETERS = 5 | ||
| NOT_IMPLEMENTED = 6 | ||
| WRONG_PARTITION_NAME = 7 | ||
| INHERITED_ERROR = 8 | ||
| INITIAL_PARTITION = 9 | ||
| . " RSDU_PART_GENERIC_DROP_HDB | ||
ABAP code using 7.40 inline data declarations to call FM RSDU_PART_GENERIC_DROP_HDB
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_i_connection) | = 'R/3*'. | |||
Search for further information about these or an SAP related objects