SAP WRF_PCTR_ACTIVITY_EXT Function Module for External API for Activities Controller
WRF_PCTR_ACTIVITY_EXT is a standard wrf pctr activity ext SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for External API for Activities Controller 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 wrf pctr activity ext FM, simply by entering the name WRF_PCTR_ACTIVITY_EXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: WRF_PCTR_ACTCTR
Program Name: SAPLWRF_PCTR_ACTCTR
Main Program: SAPLWRF_PCTR_ACTCTR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled + BasXML supported
Update:

Function WRF_PCTR_ACTIVITY_EXT 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 'WRF_PCTR_ACTIVITY_EXT'"External API for Activities Controller.
EXPORTING
IT_EXT_ACT = "External Interface Activities Controller
* IV_NO_COMMIT = "Should not commit
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for WRF_PCTR_ACTIVITY_EXT
IT_EXT_ACT - External Interface Activities Controller
Data type: WRF_PCTR_ACTCTR_EXT_TTYOptional: No
Call by Reference: No ( called with pass by value option)
IV_NO_COMMIT - Should not commit
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR - Errors occured during Dateline Processing
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for WRF_PCTR_ACTIVITY_EXT 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_error | TYPE STRING, " | |||
| lv_it_ext_act | TYPE WRF_PCTR_ACTCTR_EXT_TTY, " | |||
| lv_iv_no_commit | TYPE XFELD. " |
|   CALL FUNCTION 'WRF_PCTR_ACTIVITY_EXT' "External API for Activities Controller |
| EXPORTING | ||
| IT_EXT_ACT | = lv_it_ext_act | |
| IV_NO_COMMIT | = lv_iv_no_commit | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " WRF_PCTR_ACTIVITY_EXT | ||
ABAP code using 7.40 inline data declarations to call FM WRF_PCTR_ACTIVITY_EXT
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