SAP CMS_OBJ_PCN_REL_END Function Module for Decides whether release process is trigggered
CMS_OBJ_PCN_REL_END is a standard cms obj pcn rel end SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Decides whether release process is trigggered 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 obj pcn rel end FM, simply by entering the name CMS_OBJ_PCN_REL_END into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_OBJ_PCN_REL
Program Name: SAPLCMS_OBJ_PCN_REL
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_OBJ_PCN_REL_END 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_OBJ_PCN_REL_END'"Decides whether release process is trigggered.
EXPORTING
I_PROC_OBJ = "Process Object
I_PROC_AREA = "Process Control Area
I_PROC_CKY = "Process Control Key
I_CR_TYPE = "Change Request Type
I_ACTIVITY = "Activity ID
I_OBJECT_ID = "Object Identification Number
I_STR_REL_CRITERIA = "
* I_FLG_UPDATETASK = 'X' "Indicator
IMPORTING
E_FLG_RELEASE = "Indicator
E_REL_STATUS = "Change Request Release Status
E_REL_ACTVT = "Activity ID
E_TAB_RC = "Return Code and corresponding Message
IMPORTING Parameters details for CMS_OBJ_PCN_REL_END
I_PROC_OBJ - Process Object
Data type: CMS_DTE_PCN_PROC_OBJOptional: 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_PROC_CKY - Process Control Key
Data type: CMS_DTE_PCN_PROC_CKYOptional: No
Call by Reference: No ( called with pass by value option)
I_CR_TYPE - Change Request Type
Data type: CMS_DTE_PCN_CR_TYPOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTIVITY - Activity ID
Data type: CMS_DTE_PCN_ACTVTOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJECT_ID - Object Identification Number
Data type: CMS_DTE_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_STR_REL_CRITERIA -
Data type: ANYOptional: No
Call by Reference: No ( called with pass by value option)
I_FLG_UPDATETASK - Indicator
Data type: CMS_DTE_FLGDefault: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CMS_OBJ_PCN_REL_END
E_FLG_RELEASE - Indicator
Data type: CMS_DTE_FLGOptional: No
Call by Reference: No ( called with pass by value option)
E_REL_STATUS - Change Request Release Status
Data type: CMS_DTE_PCN_CR_REL_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
E_REL_ACTVT - Activity ID
Data type: CMS_DTE_PCN_ACTVTOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_RC - Return Code and corresponding Message
Data type: CMS_TAB_MSG_COL_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CMS_OBJ_PCN_REL_END 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_flg_release | TYPE CMS_DTE_FLG, " | |||
| lv_i_proc_area | TYPE CMS_DTE_PCN_AREA, " | |||
| lv_e_rel_status | TYPE CMS_DTE_PCN_CR_REL_STATUS, " | |||
| lv_i_proc_cky | TYPE CMS_DTE_PCN_PROC_CKY, " | |||
| lv_e_rel_actvt | TYPE CMS_DTE_PCN_ACTVT, " | |||
| lv_e_tab_rc | TYPE CMS_TAB_MSG_COL_MESSAGE, " | |||
| lv_i_cr_type | TYPE CMS_DTE_PCN_CR_TYP, " | |||
| lv_i_activity | TYPE CMS_DTE_PCN_ACTVT, " | |||
| lv_i_object_id | TYPE CMS_DTE_OBJECT_ID, " | |||
| lv_i_str_rel_criteria | TYPE ANY, " | |||
| lv_i_flg_updatetask | TYPE CMS_DTE_FLG. " 'X' |
|   CALL FUNCTION 'CMS_OBJ_PCN_REL_END' "Decides whether release process is trigggered |
| EXPORTING | ||
| I_PROC_OBJ | = lv_i_proc_obj | |
| I_PROC_AREA | = lv_i_proc_area | |
| I_PROC_CKY | = lv_i_proc_cky | |
| I_CR_TYPE | = lv_i_cr_type | |
| I_ACTIVITY | = lv_i_activity | |
| I_OBJECT_ID | = lv_i_object_id | |
| I_STR_REL_CRITERIA | = lv_i_str_rel_criteria | |
| I_FLG_UPDATETASK | = lv_i_flg_updatetask | |
| IMPORTING | ||
| E_FLG_RELEASE | = lv_e_flg_release | |
| E_REL_STATUS | = lv_e_rel_status | |
| E_REL_ACTVT | = lv_e_rel_actvt | |
| E_TAB_RC | = lv_e_tab_rc | |
| . " CMS_OBJ_PCN_REL_END | ||
ABAP code using 7.40 inline data declarations to call FM CMS_OBJ_PCN_REL_END
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_updatetask) | = 'X'. | |||
Search for further information about these or an SAP related objects