SAP FMCA_BRFEVENT_SELECT Function Module for
FMCA_BRFEVENT_SELECT is a standard fmca brfevent select 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 fmca brfevent select FM, simply by entering the name FMCA_BRFEVENT_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_BRF_DB
Program Name: SAPLFMCA_BRF_DB
Main Program: SAPLFMCA_BRF_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_BRFEVENT_SELECT 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_BRFEVENT_SELECT'".
EXPORTING
I_ABTYP = "Revenue Type
I_PERSL = "Key for Period Assignment
TABLES
T_FMCA_BRFEVENT = "Assign Revenue Types to BRF Events
EXCEPTIONS
NOT_FOUND = 1 INVALID_INPUT = 2
IMPORTING Parameters details for FMCA_BRFEVENT_SELECT
I_ABTYP - Revenue Type
Data type: ABTYP_PSOptional: No
Call by Reference: Yes
I_PERSL - Key for Period Assignment
Data type: PERSL_KKOptional: No
Call by Reference: Yes
TABLES Parameters details for FMCA_BRFEVENT_SELECT
T_FMCA_BRFEVENT - Assign Revenue Types to BRF Events
Data type: TFMCA_BRFEVENTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Entry not found
Data type:Optional: No
Call by Reference: Yes
INVALID_INPUT - Insufficient Entry Parameters for Database Access
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_BRFEVENT_SELECT 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_abtyp | TYPE ABTYP_PS, " | |||
| lv_not_found | TYPE ABTYP_PS, " | |||
| lt_t_fmca_brfevent | TYPE STANDARD TABLE OF TFMCA_BRFEVENT, " | |||
| lv_i_persl | TYPE PERSL_KK, " | |||
| lv_invalid_input | TYPE PERSL_KK. " |
|   CALL FUNCTION 'FMCA_BRFEVENT_SELECT' " |
| EXPORTING | ||
| I_ABTYP | = lv_i_abtyp | |
| I_PERSL | = lv_i_persl | |
| TABLES | ||
| T_FMCA_BRFEVENT | = lt_t_fmca_brfevent | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| INVALID_INPUT = 2 | ||
| . " FMCA_BRFEVENT_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_BRFEVENT_SELECT
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