RH_ACTIVE_VERSION_UPDATE SAP Function module

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

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

Pattern for FM RH_ACTIVE_VERSION_UPDATE - RH ACTIVE VERSION UPDATE

CALL FUNCTION 'RH_ACTIVE_VERSION_UPDATE' "
  EXPORTING
    im_task =                   " swd_step_t
    im_wfdkey =                 " swd_wfdkey
    im_activat_on =             " sy-datum
    im_activat_at =             " sy-uzeit
    im_activat_by = SY-UNAME    " sy-uname
    im_activat_rl = SY-SAPRL    " sy-saprl
    im_client = SY-MANDT        " sy-mandt      R/3 System, Client Number from Logon
  IMPORTING
    ex_hri1205 =                " hri1205       Infotype 1205 Fields
    .  "  RH_ACTIVE_VERSION_UPDATE

ABAP code example for Function Module RH_ACTIVE_VERSION_UPDATE

The ABAP code below is a full code listing to execute function module RH_ACTIVE_VERSION_UPDATE 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_ex_hri1205  
 
 TYPE HRI1205
.


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

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

DATA(ld_im_activat_on) = '20210129'.

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

DATA(ld_im_activat_by) = 'some text here'.

DATA(ld_im_activat_rl) = 'some text here'.

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

CALL FUNCTION 'RH_ACTIVE_VERSION_UPDATE'
  EXPORTING
    im_task =                    ld_im_task
    im_wfdkey =                  ld_im_wfdkey
    im_activat_on =              ld_im_activat_on
    im_activat_at =              ld_im_activat_at
    im_activat_by =              ld_im_activat_by
    im_activat_rl =              ld_im_activat_rl
    im_client =                  ld_im_client
  IMPORTING
    ex_hri1205 =                 ld_ex_hri1205
    .  "  RH_ACTIVE_VERSION_UPDATE

IF SY-SUBRC EQ 0.
  "All OK
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_ex_hri1205
 
 TYPE HRI1205 ,
ld_im_task
 
 TYPE SWD_STEP_T ,
ld_im_wfdkey
 
 TYPE SWD_WFDKEY ,
ld_im_activat_on
 
 TYPE SY-DATUM ,
ld_im_activat_at
 
 TYPE SY-UZEIT ,
ld_im_activat_by
 
 TYPE SY-UNAME ,
ld_im_activat_rl
 
 TYPE SY-SAPRL ,
ld_im_client
 
 TYPE SY-MANDT .


ld_im_task = 'Check type of data required'.
ld_im_wfdkey = 'Check type of data required'.
ld_im_activat_on = '20210129'.
ld_im_activat_at = 'Check type of data required'.
ld_im_activat_by = 'some text here'.
ld_im_activat_rl = 'some text here'.
ld_im_client = 'Check type of data required'.