SAP RSDU_TABLE_SPLIT_MAXVALUE_DB6 Function Module for Merge all partitions up to the specified partitioning column value









RSDU_TABLE_SPLIT_MAXVALUE_DB6 is a standard rsdu table split maxvalue db6 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Merge all partitions up to the specified partitioning column value 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 table split maxvalue db6 FM, simply by entering the name RSDU_TABLE_SPLIT_MAXVALUE_DB6 into the relevant SAP transaction such as SE37 or SE38.

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



Function RSDU_TABLE_SPLIT_MAXVALUE_DB6 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_TABLE_SPLIT_MAXVALUE_DB6'"Merge all partitions up to the specified partitioning column value
  EXPORTING
   I_TABLNM =  "Table Name
   I_PARTITION_VAL =  "First value for split max partition
   I_INCREMENT =  "Increment to next partition max value
   I_NUM_PARTITIONS =  "Number resulting partitions
   I_PART_IOBJNM =  "Partitioning Infoobject

 IMPORTING
   E_T_MESSAGE =  "Protocol on the operations performed

CHANGING
   C_PROCESSED =  "Boolean

EXCEPTIONS
   SPLIT_FAILED = 1    INVALID_INPUT = 2    SPLIT_FAILED_BAD_STATUS = 3
.



IMPORTING Parameters details for RSDU_TABLE_SPLIT_MAXVALUE_DB6

I_TABLNM - Table Name

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

I_PARTITION_VAL - First value for split max partition

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

I_INCREMENT - Increment to next partition max value

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

I_NUM_PARTITIONS - Number resulting partitions

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

I_PART_IOBJNM - Partitioning Infoobject

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

EXPORTING Parameters details for RSDU_TABLE_SPLIT_MAXVALUE_DB6

E_T_MESSAGE - Protocol on the operations performed

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

CHANGING Parameters details for RSDU_TABLE_SPLIT_MAXVALUE_DB6

C_PROCESSED - Boolean

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

EXCEPTIONS details

SPLIT_FAILED - Split failed

Data type:
Optional: No
Call by Reference: Yes

INVALID_INPUT - Invalid input parameter

Data type:
Optional: No
Call by Reference: Yes

SPLIT_FAILED_BAD_STATUS - Split failed, table is now inconsistent

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSDU_TABLE_SPLIT_MAXVALUE_DB6 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_i_tablnm  TYPE RSD_TABLNM, "   
lv_c_processed  TYPE RS_BOOL, "   
lv_e_t_message  TYPE RSDU_T_MESSAGE, "   
lv_split_failed  TYPE RSDU_T_MESSAGE, "   
lv_invalid_input  TYPE RSDU_T_MESSAGE, "   
lv_i_partition_val  TYPE RSPARTVL_TO, "   
lv_i_increment  TYPE I, "   
lv_split_failed_bad_status  TYPE I, "   
lv_i_num_partitions  TYPE I, "   
lv_i_part_iobjnm  TYPE RSD_IOBJNM. "   

  CALL FUNCTION 'RSDU_TABLE_SPLIT_MAXVALUE_DB6'  "Merge all partitions up to the specified partitioning column value
    EXPORTING
         I_TABLNM = lv_i_tablnm
         I_PARTITION_VAL = lv_i_partition_val
         I_INCREMENT = lv_i_increment
         I_NUM_PARTITIONS = lv_i_num_partitions
         I_PART_IOBJNM = lv_i_part_iobjnm
    IMPORTING
         E_T_MESSAGE = lv_e_t_message
    CHANGING
         C_PROCESSED = lv_c_processed
    EXCEPTIONS
        SPLIT_FAILED = 1
        INVALID_INPUT = 2
        SPLIT_FAILED_BAD_STATUS = 3
. " RSDU_TABLE_SPLIT_MAXVALUE_DB6




ABAP code using 7.40 inline data declarations to call FM RSDU_TABLE_SPLIT_MAXVALUE_DB6

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!