RSDU_TABLE_SPLIT_PARTLIST SAP Function module - Determine the names and high values of new partitions for a maxvalue-spl

RSDU_TABLE_SPLIT_PARTLIST is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RSDU_TABLE_SPLIT_PARTLIST into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RSDU_PART
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RSDU_TABLE_SPLIT_PARTLIST - RSDU TABLE SPLIT PARTLIST

CALL FUNCTION 'RSDU_TABLE_SPLIT_PARTLIST' "Determine the names and high values of new partitions for a maxvalue-split
  EXPORTING
    i_tablnm =                  " rsd_tablnm    Table Name
    i_partition_val =           " rspartvl_to   Value until to split max partition
    i_increment =               " i             Increment to next partition max value
    i_part_iobjnm =             " rsd_iobjnm    Partitioning Infoobject
  IMPORTING
    e_ts_part_info =            " rsdu_ts_part_info  Partitioning information of NEW partitions
  EXCEPTIONS
    INVALID_INPUT = 1           "               Invalid input
    .  "  RSDU_TABLE_SPLIT_PARTLIST

ABAP code example for Function Module RSDU_TABLE_SPLIT_PARTLIST

The ABAP code below is a full code listing to execute function module RSDU_TABLE_SPLIT_PARTLIST including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_ts_part_info  
 
 TYPE RSDU_TS_PART_INFO
.


DATA(ld_i_tablnm) = 'Check type of data required'.

DATA(ld_i_partition_val) = 'Check type of data required'.

DATA(ld_i_increment) = 'Check type of data required'.

DATA(ld_i_part_iobjnm) = 'Check type of data required'.
.

CALL FUNCTION 'RSDU_TABLE_SPLIT_PARTLIST'
  EXPORTING
    i_tablnm =                   ld_i_tablnm
    i_partition_val =            ld_i_partition_val
    i_increment =                ld_i_increment
    i_part_iobjnm =              ld_i_part_iobjnm
  IMPORTING
    e_ts_part_info =             ld_e_ts_part_info
  EXCEPTIONS
    INVALID_INPUT =              1
    .  "  RSDU_TABLE_SPLIT_PARTLIST

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_ts_part_info
 
 TYPE RSDU_TS_PART_INFO ,
ld_i_tablnm
 
 TYPE RSD_TABLNM ,
ld_i_partition_val
 
 TYPE RSPARTVL_TO ,
ld_i_increment
 
 TYPE I ,
ld_i_part_iobjnm
 
 TYPE RSD_IOBJNM .


ld_i_tablnm = 'Check type of data required'.
ld_i_partition_val = 'Check type of data required'.
ld_i_increment = 'Check type of data required'.
ld_i_part_iobjnm = 'Check type of data required'.