SAP COPCA_ACTIVITY_CHECK Function Module for
COPCA_ACTIVITY_CHECK is a standard copca activity check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 copca activity check FM, simply by entering the name COPCA_ACTIVITY_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: PC04
Program Name: SAPLPC04
Main Program: SAPLPC04
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COPCA_ACTIVITY_CHECK 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 'COPCA_ACTIVITY_CHECK'".
EXPORTING
ACTIVITY = "
RLDNR = "
IMPORTING
RELEVANT = "
USER_EXIT = "
IMPORTING Parameters details for COPCA_ACTIVITY_CHECK
ACTIVITY -
Data type: T886PCA-ACTIVITYOptional: No
Call by Reference: No ( called with pass by value option)
RLDNR -
Data type: T886PCA-RLDNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for COPCA_ACTIVITY_CHECK
RELEVANT -
Data type: RKEC1-TESTOptional: No
Call by Reference: No ( called with pass by value option)
USER_EXIT -
Data type: RKEC1-TESTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for COPCA_ACTIVITY_CHECK 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_activity | TYPE T886PCA-ACTIVITY, " | |||
| lv_relevant | TYPE RKEC1-TEST, " | |||
| lv_rldnr | TYPE T886PCA-RLDNR, " | |||
| lv_user_exit | TYPE RKEC1-TEST. " |
|   CALL FUNCTION 'COPCA_ACTIVITY_CHECK' " |
| EXPORTING | ||
| ACTIVITY | = lv_activity | |
| RLDNR | = lv_rldnr | |
| IMPORTING | ||
| RELEVANT | = lv_relevant | |
| USER_EXIT | = lv_user_exit | |
| . " COPCA_ACTIVITY_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM COPCA_ACTIVITY_CHECK
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 ACTIVITY FROM T886PCA INTO @DATA(ld_activity). | ||||
| "SELECT single TEST FROM RKEC1 INTO @DATA(ld_relevant). | ||||
| "SELECT single RLDNR FROM T886PCA INTO @DATA(ld_rldnr). | ||||
| "SELECT single TEST FROM RKEC1 INTO @DATA(ld_user_exit). | ||||
Search for further information about these or an SAP related objects