RSDU_PSA_POST_ACTIVATION_ORA SAP Function module - Actions to perform after PSA table activation

RSDU_PSA_POST_ACTIVATION_ORA 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_PSA_POST_ACTIVATION_ORA into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM RSDU_PSA_POST_ACTIVATION_ORA - RSDU PSA POST ACTIVATION ORA

CALL FUNCTION 'RSDU_PSA_POST_ACTIVATION_ORA' "Actions to perform after PSA table activation
  EXPORTING
    i_tablnm =                  " rsd_tablnm    PSA Table Name
*   i_userapp =                 " rsuserapp
  IMPORTING
    e_repartitioned =           " rs_bool
  CHANGING
    c_processed =               " rs_bool       Boolean
  EXCEPTIONS
    PSA_POST_ACTIVATION_FAILED = 1  "           ANY ERROR DURING POST ACTIVATION
    .  "  RSDU_PSA_POST_ACTIVATION_ORA

ABAP code example for Function Module RSDU_PSA_POST_ACTIVATION_ORA

The ABAP code below is a full code listing to execute function module RSDU_PSA_POST_ACTIVATION_ORA 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_repartitioned  
 
 TYPE RS_BOOL
.


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

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

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

CALL FUNCTION 'RSDU_PSA_POST_ACTIVATION_ORA'
  EXPORTING
    i_tablnm =                   ld_i_tablnm
*   i_userapp =                  ld_i_userapp
  IMPORTING
    e_repartitioned =            ld_e_repartitioned
  CHANGING
    c_processed =                ld_c_processed
  EXCEPTIONS
    PSA_POST_ACTIVATION_FAILED =    1
    .  "  RSDU_PSA_POST_ACTIVATION_ORA

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_c_processed
 
 TYPE RS_BOOL ,
ld_e_repartitioned
 
 TYPE RS_BOOL ,
ld_i_tablnm
 
 TYPE RSD_TABLNM ,
ld_i_userapp
 
 TYPE RSUSERAPP .


ld_c_processed = 'Check type of data required'.
ld_i_tablnm = 'Check type of data required'.
ld_i_userapp = 'Check type of data required'.