RSM_PROCESS_ACTIONS SAP Function module

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

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

Pattern for FM RSM_PROCESS_ACTIONS - RSM PROCESS ACTIONS

CALL FUNCTION 'RSM_PROCESS_ACTIONS' "
  EXPORTING
    number =                    " hrsm_head-hrsm_seqnr
    integration_active =        " char1
  IMPORTING
    return1 =                   " bapireturn1
  TABLES
    t_proposed_values =         " pprop
  CHANGING
    l_head =                    " rsm_head
    error_message =             " rsm_ermsg
  EXCEPTIONS
    NUMBER_RANGE_ERROR = 1      "
    .  "  RSM_PROCESS_ACTIONS

ABAP code example for Function Module RSM_PROCESS_ACTIONS

The ABAP code below is a full code listing to execute function module RSM_PROCESS_ACTIONS 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_return1  
 
 TYPE BAPIRETURN1
,
it_t_proposed_values  
 
 TYPE STANDARD TABLE OF PPROP,"TABLES PARAM
wa_t_proposed_values
 
 LIKE LINE OF it_t_proposed_values
.


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

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

SELECT single HRSM_SEQNR 
  FROM HRSM_HEAD 
  INTO @DATA(ld_number).


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

"populate fields of struture and append to itab
append wa_t_proposed_values to it_t_proposed_values.
.

CALL FUNCTION 'RSM_PROCESS_ACTIONS'
  EXPORTING
    number =                     ld_number
    integration_active =         ld_integration_active
  IMPORTING
    return1 =                    ld_return1
  TABLES
    t_proposed_values =          it_t_proposed_values
  CHANGING
    l_head =                     ld_l_head
    error_message =              ld_error_message
  EXCEPTIONS
    NUMBER_RANGE_ERROR =         1
    .  "  RSM_PROCESS_ACTIONS

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_l_head
 
 TYPE RSM_HEAD ,
ld_return1
 
 TYPE BAPIRETURN1 ,
ld_number
 
 TYPE HRSM_HEAD-HRSM_SEQNR ,
it_t_proposed_values
 
 TYPE STANDARD TABLE OF PPROP ,
wa_t_proposed_values
 
 LIKE LINE OF it_t_proposed_values,
ld_error_message
 
 TYPE RSM_ERMSG ,
ld_integration_active
 
 TYPE CHAR1 .


ld_l_head = 'Check type of data required'.

SELECT single HRSM_SEQNR 
  FROM HRSM_HEAD 
  INTO ld_number.
 

"populate fields of struture and append to itab
append wa_t_proposed_values to it_t_proposed_values.
ld_error_message = 'Check type of data required'.
ld_integration_active = 'Check type of data required'.