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

Function CMS_API_PCN_CR_CHECK_EXISTENCE 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_API_PCN_CR_CHECK_EXISTENCE'"Check Change Request Existence.
EXPORTING
I_CR_GUID = "Change Request Primary Key
IMPORTING
E_FLG_EXISTS = "Flag: Change Request Existence
IMPORTING Parameters details for CMS_API_PCN_CR_CHECK_EXISTENCE
I_CR_GUID - Change Request Primary Key
Data type: CMS_DTE_PCN_CR_GUIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CMS_API_PCN_CR_CHECK_EXISTENCE
E_FLG_EXISTS - Flag: Change Request Existence
Data type: CMS_DTE_FLGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_API_PCN_CR_CHECK_EXISTENCE 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_cr_guid | TYPE CMS_DTE_PCN_CR_GUID, " | |||
| lv_e_flg_exists | TYPE CMS_DTE_FLG. " |
|   CALL FUNCTION 'CMS_API_PCN_CR_CHECK_EXISTENCE' "Check Change Request Existence |
| EXPORTING | ||
| I_CR_GUID | = lv_i_cr_guid | |
| IMPORTING | ||
| E_FLG_EXISTS | = lv_e_flg_exists | |
| . " CMS_API_PCN_CR_CHECK_EXISTENCE | ||
ABAP code using 7.40 inline data declarations to call FM CMS_API_PCN_CR_CHECK_EXISTENCE
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.Search for further information about these or an SAP related objects