SAP FMCA_EVENT_0202 Function Module for PSCD: Search Help Exit GPART/VKONT/VTREF
FMCA_EVENT_0202 is a standard fmca event 0202 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PSCD: Search Help Exit GPART/VKONT/VTREF 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 fmca event 0202 FM, simply by entering the name FMCA_EVENT_0202 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_PSOB_EVENTS
Program Name: SAPLFMCA_PSOB_EVENTS
Main Program: SAPLFMCA_PSOB_EVENTS
Appliation area:
Release date: 02-Dec-2003
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_EVENT_0202 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 'FMCA_EVENT_0202'"PSCD: Search Help Exit GPART/VKONT/VTREF.
EXPORTING
I_GPART = "Business Partner
I_VKONT = "Contract Account
I_VTREF = "Contract Object
* I_SUBAP = ' ' "Subapplication in Contract Accounting
* I_N = 250 "Maximum No.of Hits
TABLES
T_STR_SHLP_VTREF = "Hit List
* R_GPART = "Business Partner Ranges Table
* R_VKONT = "Contract Account Ranges Table
* R_VTREF = "Contract Object Ranges-Table
* R_SUBAP = "Ranges Table Sub-Application
IMPORTING Parameters details for FMCA_EVENT_0202
I_GPART - Business Partner
Data type: DFKKOP-GPARTOptional: No
Call by Reference: No ( called with pass by value option)
I_VKONT - Contract Account
Data type: DFKKOP-VKONTOptional: No
Call by Reference: No ( called with pass by value option)
I_VTREF - Contract Object
Data type: DFKKOP-VTREFOptional: No
Call by Reference: No ( called with pass by value option)
I_SUBAP - Subapplication in Contract Accounting
Data type: DFKKOP-SUBAPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_N - Maximum No.of Hits
Data type: SY-INDEXDefault: 250
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FMCA_EVENT_0202
T_STR_SHLP_VTREF - Hit List
Data type: STR_SHLP_VTREFOptional: No
Call by Reference: No ( called with pass by value option)
R_GPART - Business Partner Ranges Table
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
R_VKONT - Contract Account Ranges Table
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
R_VTREF - Contract Object Ranges-Table
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
R_SUBAP - Ranges Table Sub-Application
Data type:Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_EVENT_0202 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_gpart | TYPE DFKKOP-GPART, " | |||
| lt_t_str_shlp_vtref | TYPE STANDARD TABLE OF STR_SHLP_VTREF, " | |||
| lv_i_vkont | TYPE DFKKOP-VKONT, " | |||
| lt_r_gpart | TYPE STANDARD TABLE OF DFKKOP, " | |||
| lv_i_vtref | TYPE DFKKOP-VTREF, " | |||
| lt_r_vkont | TYPE STANDARD TABLE OF DFKKOP, " | |||
| lv_i_subap | TYPE DFKKOP-SUBAP, " SPACE | |||
| lt_r_vtref | TYPE STANDARD TABLE OF DFKKOP, " | |||
| lv_i_n | TYPE SY-INDEX, " 250 | |||
| lt_r_subap | TYPE STANDARD TABLE OF SY. " |
|   CALL FUNCTION 'FMCA_EVENT_0202' "PSCD: Search Help Exit GPART/VKONT/VTREF |
| EXPORTING | ||
| I_GPART | = lv_i_gpart | |
| I_VKONT | = lv_i_vkont | |
| I_VTREF | = lv_i_vtref | |
| I_SUBAP | = lv_i_subap | |
| I_N | = lv_i_n | |
| TABLES | ||
| T_STR_SHLP_VTREF | = lt_t_str_shlp_vtref | |
| R_GPART | = lt_r_gpart | |
| R_VKONT | = lt_r_vkont | |
| R_VTREF | = lt_r_vtref | |
| R_SUBAP | = lt_r_subap | |
| . " FMCA_EVENT_0202 | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_EVENT_0202
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 GPART FROM DFKKOP INTO @DATA(ld_i_gpart). | ||||
| "SELECT single VKONT FROM DFKKOP INTO @DATA(ld_i_vkont). | ||||
| "SELECT single VTREF FROM DFKKOP INTO @DATA(ld_i_vtref). | ||||
| "SELECT single SUBAP FROM DFKKOP INTO @DATA(ld_i_subap). | ||||
| DATA(ld_i_subap) | = ' '. | |||
| "SELECT single INDEX FROM SY INTO @DATA(ld_i_n). | ||||
| DATA(ld_i_n) | = 250. | |||
Search for further information about these or an SAP related objects