SAP CMS_UI_COM_PCN_MAINTAIN Function Module for Miantain Object in normal mode









CMS_UI_COM_PCN_MAINTAIN is a standard cms ui com 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 Miantain Object 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 com pcn maintain FM, simply by entering the name CMS_UI_COM_PCN_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.

Function Group: CMS_UI_COM_PCN
Program Name: SAPLCMS_UI_COM_PCN
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CMS_UI_COM_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_COM_PCN_MAINTAIN'"Miantain Object in normal mode
EXPORTING
I_PROC_OBJ = "Process object
* I_OBJECT_ID = "Object Identification number
* I_STR_RBL_SKY = "Semantic Key for CMS_RBL
* I_ACTIVITY = "Activity ID
* I_CR_TYPE = ' ' "Change Request Type
* I_FLG_UPDATETASK = 'X' "Indicator
* I_FLG_SAVE = 'X' "Indicator

IMPORTING
E_DYNNR = "ABAP program, number of current screen
E_PROGNAME = "ABAP program name
E_TITLE = "Screens, title text
E_TAB_RC = "Return Code and corresponding Message
.



IMPORTING Parameters details for CMS_UI_COM_PCN_MAINTAIN

I_PROC_OBJ - Process object

Data type: CMS_DTE_PCN_PROC_OBJ
Optional: No
Call by Reference: Yes

I_OBJECT_ID - Object Identification number

Data type: CMS_DTE_OBJECT_ID
Optional: Yes
Call by Reference: Yes

I_STR_RBL_SKY - Semantic Key for CMS_RBL

Data type: CMS_STR_RBL_SKY
Optional: Yes
Call by Reference: Yes

I_ACTIVITY - Activity ID

Data type: CMS_DTE_PCN_ACTVT
Optional: Yes
Call by Reference: Yes

I_CR_TYPE - Change Request Type

Data type: CMS_DTE_PCN_CR_TYP
Default: SPACE
Optional: Yes
Call by Reference: Yes

I_FLG_UPDATETASK - Indicator

Data type: CMS_DTE_FLG
Default: 'X'
Optional: Yes
Call by Reference: Yes

I_FLG_SAVE - Indicator

Data type: CMS_DTE_FLG
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CMS_UI_COM_PCN_MAINTAIN

E_DYNNR - ABAP program, number of current screen

Data type: SY-DYNNR
Optional: No
Call by Reference: Yes

E_PROGNAME - ABAP program name

Data type: PROGNAME
Optional: No
Call by Reference: Yes

E_TITLE - Screens, title text

Data type: SYTITLE
Optional: No
Call by Reference: Yes

E_TAB_RC - Return Code and corresponding Message

Data type: CMS_TAB_MSG_COL_MESSAGE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CMS_UI_COM_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_e_dynnr  TYPE SY-DYNNR, "   
lv_i_proc_obj  TYPE CMS_DTE_PCN_PROC_OBJ, "   
lv_e_progname  TYPE PROGNAME, "   
lv_i_object_id  TYPE CMS_DTE_OBJECT_ID, "   
lv_e_title  TYPE SYTITLE, "   
lv_i_str_rbl_sky  TYPE CMS_STR_RBL_SKY, "   
lv_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE, "   
lv_i_activity  TYPE CMS_DTE_PCN_ACTVT, "   
lv_i_cr_type  TYPE CMS_DTE_PCN_CR_TYP, "   SPACE
lv_i_flg_updatetask  TYPE CMS_DTE_FLG, "   'X'
lv_i_flg_save  TYPE CMS_DTE_FLG. "   'X'

  CALL FUNCTION 'CMS_UI_COM_PCN_MAINTAIN'  "Miantain Object in normal mode
    EXPORTING
         I_PROC_OBJ = lv_i_proc_obj
         I_OBJECT_ID = lv_i_object_id
         I_STR_RBL_SKY = lv_i_str_rbl_sky
         I_ACTIVITY = lv_i_activity
         I_CR_TYPE = lv_i_cr_type
         I_FLG_UPDATETASK = lv_i_flg_updatetask
         I_FLG_SAVE = lv_i_flg_save
    IMPORTING
         E_DYNNR = lv_e_dynnr
         E_PROGNAME = lv_e_progname
         E_TITLE = lv_e_title
         E_TAB_RC = lv_e_tab_rc
. " CMS_UI_COM_PCN_MAINTAIN




ABAP code using 7.40 inline data declarations to call FM CMS_UI_COM_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.

"SELECT single DYNNR FROM SY INTO @DATA(ld_e_dynnr).
 
 
 
 
 
 
 
 
DATA(ld_i_cr_type) = ' '.
 
DATA(ld_i_flg_updatetask) = 'X'.
 
DATA(ld_i_flg_save) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!