SAP CMS_UI_CAG_CR_PCN_ON_RELEASE Function Module for Release activity event handler
CMS_UI_CAG_CR_PCN_ON_RELEASE is a standard cms ui cag cr pcn on release SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Release activity event handler 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 cag cr pcn on release FM, simply by entering the name CMS_UI_CAG_CR_PCN_ON_RELEASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_UI_CAG_PCN
Program Name: SAPLCMS_UI_CAG_PCN
Main Program: SAPLCMS_UI_CAG_PCN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_UI_CAG_CR_PCN_ON_RELEASE 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_CAG_CR_PCN_ON_RELEASE'"Release activity event handler.
EXPORTING
I_REL_OBJECT_KEY = "Object Key (Chain of Object Key Fields)
* I_FLG_INUPDATETASK = 'X' "Indicator
EXCEPTIONS
NO_SUCCESS = 1
IMPORTING Parameters details for CMS_UI_CAG_CR_PCN_ON_RELEASE
I_REL_OBJECT_KEY - Object Key (Chain of Object Key Fields)
Data type: BCA_DTE_OBJECT_KEYOptional: No
Call by Reference: Yes
I_FLG_INUPDATETASK - Indicator
Data type: CMS_DTE_FLGDefault: 'X'
Optional: No
Call by Reference: Yes
EXCEPTIONS details
NO_SUCCESS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CMS_UI_CAG_CR_PCN_ON_RELEASE 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_no_success | TYPE STRING, " | |||
| lv_i_rel_object_key | TYPE BCA_DTE_OBJECT_KEY, " | |||
| lv_i_flg_inupdatetask | TYPE CMS_DTE_FLG. " 'X' |
|   CALL FUNCTION 'CMS_UI_CAG_CR_PCN_ON_RELEASE' "Release activity event handler |
| EXPORTING | ||
| I_REL_OBJECT_KEY | = lv_i_rel_object_key | |
| I_FLG_INUPDATETASK | = lv_i_flg_inupdatetask | |
| EXCEPTIONS | ||
| NO_SUCCESS = 1 | ||
| . " CMS_UI_CAG_CR_PCN_ON_RELEASE | ||
ABAP code using 7.40 inline data declarations to call FM CMS_UI_CAG_CR_PCN_ON_RELEASE
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_inupdatetask) | = 'X'. | |||
Search for further information about these or an SAP related objects