SAP CMS_UI_PCN_MAINTAIN Function Module for Ui call in normal mode
CMS_UI_PCN_MAINTAIN is a standard cms ui pcn maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ui call in normal mode processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for cms ui pcn maintain FM, simply by entering the name CMS_UI_PCN_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_UI_PCN
Program Name: SAPLCMS_UI_PCN
Main Program: SAPLCMS_UI_PCN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_UI_PCN_MAINTAIN pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CMS_UI_PCN_MAINTAIN'"Ui call in normal mode.
EXPORTING
I_PROC_OBJ = "Process object
* I_FLG_SAVE = 'X' "Indicator
I_PROC_CKY = "Process control key
I_PROC_AREA = "Process Control Area
* I_CR_TYPE = ' ' "Change Request Type
* I_ACTIVITY = "Activity ID
* I_UI_VAR = "Object Screen (Field Status Variant)
* I_OBJECT_ID = "Object Identification number
* I_TAB_FLD_VAL = "Table of field values
* I_FLG_UPDATE_TASK = 'X' "Indicator
IMPORTING
E_SAVE_STATE = "Flag to indicate whether data has been changed or not
E_TAB_RC = "Return Code and corresponding Message
IMPORTING Parameters details for CMS_UI_PCN_MAINTAIN
I_PROC_OBJ - Process object
Data type: CMS_DTE_PCN_PROC_OBJOptional: No
Call by Reference: No ( called with pass by value option)
I_FLG_SAVE - Indicator
Data type: CMS_DTE_FLGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PROC_CKY - Process control key
Data type: CMS_DTE_PCN_PROC_CKYOptional: No
Call by Reference: No ( called with pass by value option)
I_PROC_AREA - Process Control Area
Data type: CMS_DTE_PCN_AREAOptional: No
Call by Reference: No ( called with pass by value option)
I_CR_TYPE - Change Request Type
Data type: CMS_DTE_PCN_CR_TYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTIVITY - Activity ID
Data type: CMS_DTE_PCN_ACTVTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_UI_VAR - Object Screen (Field Status Variant)
Data type: CMS_DTE_FSTAT_VAROptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJECT_ID - Object Identification number
Data type: CMS_DTE_OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TAB_FLD_VAL - Table of field values
Data type: CMS_TAB_FLDVALOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_UPDATE_TASK - Indicator
Data type: CMS_DTE_FLGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CMS_UI_PCN_MAINTAIN
E_SAVE_STATE - Flag to indicate whether data has been changed or not
Data type: CMS_DTE_FLG_STATEOptional: No
Call by Reference: Yes
E_TAB_RC - Return Code and corresponding Message
Data type: CMS_TAB_MSG_COL_MESSAGEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_UI_PCN_MAINTAIN Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_i_proc_obj | TYPE CMS_DTE_PCN_PROC_OBJ, " | |||
| lv_e_save_state | TYPE CMS_DTE_FLG_STATE, " | |||
| lv_i_flg_save | TYPE CMS_DTE_FLG, " 'X' | |||
| lv_e_tab_rc | TYPE CMS_TAB_MSG_COL_MESSAGE, " | |||
| lv_i_proc_cky | TYPE CMS_DTE_PCN_PROC_CKY, " | |||
| lv_i_proc_area | TYPE CMS_DTE_PCN_AREA, " | |||
| lv_i_cr_type | TYPE CMS_DTE_PCN_CR_TYP, " SPACE | |||
| lv_i_activity | TYPE CMS_DTE_PCN_ACTVT, " | |||
| lv_i_ui_var | TYPE CMS_DTE_FSTAT_VAR, " | |||
| lv_i_object_id | TYPE CMS_DTE_OBJECT_ID, " | |||
| lv_i_tab_fld_val | TYPE CMS_TAB_FLDVAL, " | |||
| lv_i_flg_update_task | TYPE CMS_DTE_FLG. " 'X' |
|   CALL FUNCTION 'CMS_UI_PCN_MAINTAIN' "Ui call in normal mode |
| EXPORTING | ||
| I_PROC_OBJ | = lv_i_proc_obj | |
| I_FLG_SAVE | = lv_i_flg_save | |
| I_PROC_CKY | = lv_i_proc_cky | |
| I_PROC_AREA | = lv_i_proc_area | |
| I_CR_TYPE | = lv_i_cr_type | |
| I_ACTIVITY | = lv_i_activity | |
| I_UI_VAR | = lv_i_ui_var | |
| I_OBJECT_ID | = lv_i_object_id | |
| I_TAB_FLD_VAL | = lv_i_tab_fld_val | |
| I_FLG_UPDATE_TASK | = lv_i_flg_update_task | |
| IMPORTING | ||
| E_SAVE_STATE | = lv_e_save_state | |
| E_TAB_RC | = lv_e_tab_rc | |
| . " CMS_UI_PCN_MAINTAIN | ||
ABAP code using 7.40 inline data declarations to call FM CMS_UI_PCN_MAINTAIN
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| DATA(ld_i_flg_save) | = 'X'. | |||
| DATA(ld_i_cr_type) | = ' '. | |||
| DATA(ld_i_flg_update_task) | = 'X'. | |||
Search for further information about these or an SAP related objects