SAP CMSC_CRC_EVENT_GET Function Module for Change Request Common: GET Method
CMSC_CRC_EVENT_GET is a standard cmsc crc event get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Request Common: GET Method 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 cmsc crc event get FM, simply by entering the name CMSC_CRC_EVENT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_UI_PCN_CR_BDT
Program Name: SAPLCMS_UI_PCN_CR_BDT
Main Program: SAPLCMS_UI_PCN_CR_BDT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMSC_CRC_EVENT_GET 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 'CMSC_CRC_EVENT_GET'"Change Request Common: GET Method.
IMPORTING
E_STR_CR = "Change Requests
E_DATA = "BP: Data Container of Length 15000
E_STR_PCN = "Process control key behaviour
E_STR_BDT_PARAMS = "BDT Parameters (Activity, Update Task, etc.)
EXPORTING Parameters details for CMSC_CRC_EVENT_GET
E_STR_CR - Change Requests
Data type: CMS_STR_PCN_CR_DBOptional: No
Call by Reference: No ( called with pass by value option)
E_DATA - BP: Data Container of Length 15000
Data type: BUSSDI3-DATAOptional: No
Call by Reference: No ( called with pass by value option)
E_STR_PCN - Process control key behaviour
Data type: CMS_STR_PCN_CKY_BOptional: No
Call by Reference: No ( called with pass by value option)
E_STR_BDT_PARAMS - BDT Parameters (Activity, Update Task, etc.)
Data type: CMS_STR_BDT_PARAMSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CMSC_CRC_EVENT_GET 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_str_cr | TYPE CMS_STR_PCN_CR_DB, " | |||
| lv_e_data | TYPE BUSSDI3-DATA, " | |||
| lv_e_str_pcn | TYPE CMS_STR_PCN_CKY_B, " | |||
| lv_e_str_bdt_params | TYPE CMS_STR_BDT_PARAMS. " |
|   CALL FUNCTION 'CMSC_CRC_EVENT_GET' "Change Request Common: GET Method |
| IMPORTING | ||
| E_STR_CR | = lv_e_str_cr | |
| E_DATA | = lv_e_data | |
| E_STR_PCN | = lv_e_str_pcn | |
| E_STR_BDT_PARAMS | = lv_e_str_bdt_params | |
| . " CMSC_CRC_EVENT_GET | ||
ABAP code using 7.40 inline data declarations to call FM CMSC_CRC_EVENT_GET
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 DATA FROM BUSSDI3 INTO @DATA(ld_e_data). | ||||
Search for further information about these or an SAP related objects