CMS_UI_CAG_PCN_MAINTAIN SAP Function module - Maintain CAG in normal mode

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

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

Pattern for FM CMS_UI_CAG_PCN_MAINTAIN - CMS UI CAG PCN MAINTAIN

CALL FUNCTION 'CMS_UI_CAG_PCN_MAINTAIN' "Maintain CAG in normal mode
* EXPORTING
*   i_cag_guid =                " cms_dte_cag_guid  Guid for table CMS_CAG
*   i_activity =                " cms_dte_pcn_actvt  Activity ID
*   i_cr_type = SPACE           " cms_dte_pcn_cr_typ  Table of field values
*   i_flg_update_task = 'X'     " cms_dte_flg   Indicator
*   i_flg_save = 'X'            " cms_dte_flg   Indicator
  IMPORTING
    e_save_state =              " cms_dte_flg_state  Flag to indicate whether data has been changed or not
    e_tab_rc =                  " cms_tab_msg_col_message  Return Code and corresponding Message
    .  "  CMS_UI_CAG_PCN_MAINTAIN

ABAP code example for Function Module CMS_UI_CAG_PCN_MAINTAIN

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


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

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

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

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

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

CALL FUNCTION 'CMS_UI_CAG_PCN_MAINTAIN'
* EXPORTING
*   i_cag_guid =                 ld_i_cag_guid
*   i_activity =                 ld_i_activity
*   i_cr_type =                  ld_i_cr_type
*   i_flg_update_task =          ld_i_flg_update_task
*   i_flg_save =                 ld_i_flg_save
  IMPORTING
    e_save_state =               ld_e_save_state
    e_tab_rc =                   ld_e_tab_rc
    .  "  CMS_UI_CAG_PCN_MAINTAIN

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_save_state
 
 TYPE CMS_DTE_FLG_STATE ,
ld_i_cag_guid
 
 TYPE CMS_DTE_CAG_GUID ,
ld_e_tab_rc
 
 TYPE CMS_TAB_MSG_COL_MESSAGE ,
ld_i_activity
 
 TYPE CMS_DTE_PCN_ACTVT ,
ld_i_cr_type
 
 TYPE CMS_DTE_PCN_CR_TYP ,
ld_i_flg_update_task
 
 TYPE CMS_DTE_FLG ,
ld_i_flg_save
 
 TYPE CMS_DTE_FLG .


ld_i_cag_guid = 'Check type of data required'.
ld_i_activity = 'Check type of data required'.
ld_i_cr_type = 'Check type of data required'.
ld_i_flg_update_task = 'Check type of data required'.
ld_i_flg_save = 'Check type of data required'.