CMS_API_RIG_SAVE_MLT SAP Function module - Save Rights - Multiple

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

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

Pattern for FM CMS_API_RIG_SAVE_MLT - CMS API RIG SAVE MLT

CALL FUNCTION 'CMS_API_RIG_SAVE_MLT' "Save Rights - Multiple
  EXPORTING
    i_tab_rig_pky =             " cms_tab_rig_pky  Movables Primary key
*   i_ast_objsysid =            " cms_dte_obj_sysid  Object System Reference ID
*   i_flg_update_task = SPACE   " cms_dte_flg_update_task  Flag: Use update task to save data
*   i_flg_planned_changes = SPACE  " cms_dte_flg_planned_changes  Flag: Planned Changes
  IMPORTING
    e_tab_rig_pky_sky_map =     " cms_tab_rig_pky_sky_map  Rights PKy SKy mapping
    e_tab_rc =                  " cms_tab_msg_col_message  Return Code and corresponding Message
    .  "  CMS_API_RIG_SAVE_MLT

ABAP code example for Function Module CMS_API_RIG_SAVE_MLT

The ABAP code below is a full code listing to execute function module CMS_API_RIG_SAVE_MLT 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_tab_rig_pky_sky_map  
 
 TYPE CMS_TAB_RIG_PKY_SKY_MAP
,
ld_e_tab_rc  
 
 TYPE CMS_TAB_MSG_COL_MESSAGE
.


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

DATA(ld_i_ast_objsysid) = 'some text here'.

DATA(ld_i_flg_update_task) = 'some text here'.

DATA(ld_i_flg_planned_changes) = 'some text here'.
.

CALL FUNCTION 'CMS_API_RIG_SAVE_MLT'
  EXPORTING
    i_tab_rig_pky =              ld_i_tab_rig_pky
*   i_ast_objsysid =             ld_i_ast_objsysid
*   i_flg_update_task =          ld_i_flg_update_task
*   i_flg_planned_changes =      ld_i_flg_planned_changes
  IMPORTING
    e_tab_rig_pky_sky_map =      ld_e_tab_rig_pky_sky_map
    e_tab_rc =                   ld_e_tab_rc
    .  "  CMS_API_RIG_SAVE_MLT

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_e_tab_rig_pky_sky_map
 
 TYPE CMS_TAB_RIG_PKY_SKY_MAP ,
ld_i_tab_rig_pky
 
 TYPE CMS_TAB_RIG_PKY ,
ld_e_tab_rc
 
 TYPE CMS_TAB_MSG_COL_MESSAGE ,
ld_i_ast_objsysid
 
 TYPE CMS_DTE_OBJ_SYSID ,
ld_i_flg_update_task
 
 TYPE CMS_DTE_FLG_UPDATE_TASK ,
ld_i_flg_planned_changes
 
 TYPE CMS_DTE_FLG_PLANNED_CHANGES .


ld_i_tab_rig_pky = 'some text here'.
ld_i_ast_objsysid = 'some text here'.
ld_i_flg_update_task = 'some text here'.
ld_i_flg_planned_changes = 'some text here'.