SAP CPE_CHECK_VMC_DEST_TRIGGER Function Module for Checks the IPC VMC Destination
CPE_CHECK_VMC_DEST_TRIGGER is a standard cpe check vmc dest trigger SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks the IPC VMC Destination 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 cpe check vmc dest trigger FM, simply by entering the name CPE_CHECK_VMC_DEST_TRIGGER into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPE_FORMULA_TRIGGER
Program Name: SAPLCPE_FORMULA_TRIGGER
Main Program: SAPLCPE_FORMULA_TRIGGER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CPE_CHECK_VMC_DEST_TRIGGER 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 'CPE_CHECK_VMC_DEST_TRIGGER'"Checks the IPC VMC Destination.
EXPORTING
IV_APPLICATION = "Character Field Length = 10
IMPORTING
EV_RFC_DESTINATION = "Logical Destination (Specified in Function Call)
IMPORTING Parameters details for CPE_CHECK_VMC_DEST_TRIGGER
IV_APPLICATION - Character Field Length = 10
Data type: CHAR10Optional: No
Call by Reference: Yes
EXPORTING Parameters details for CPE_CHECK_VMC_DEST_TRIGGER
EV_RFC_DESTINATION - Logical Destination (Specified in Function Call)
Data type: RFCDESTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CPE_CHECK_VMC_DEST_TRIGGER 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_iv_application | TYPE CHAR10, " | |||
| lv_ev_rfc_destination | TYPE RFCDEST. " |
|   CALL FUNCTION 'CPE_CHECK_VMC_DEST_TRIGGER' "Checks the IPC VMC Destination |
| EXPORTING | ||
| IV_APPLICATION | = lv_iv_application | |
| IMPORTING | ||
| EV_RFC_DESTINATION | = lv_ev_rfc_destination | |
| . " CPE_CHECK_VMC_DEST_TRIGGER | ||
ABAP code using 7.40 inline data declarations to call FM CPE_CHECK_VMC_DEST_TRIGGER
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