SAP FMCA_EVENT_1232 Function Module for Sample: Account Balance (EBPP): Determination of Incoming Payment Method
FMCA_EVENT_1232 is a standard fmca event 1232 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sample: Account Balance (EBPP): Determination of Incoming Payment Method 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 1232 FM, simply by entering the name FMCA_EVENT_1232 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_EBPP
Program Name: SAPLFMCA_EBPP
Main Program: SAPLFMCA_EBPP
Appliation area: F
Release date: 27-Nov-2001
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMCA_EVENT_1232 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_1232'"Sample: Account Balance (EBPP): Determination of Incoming Payment Method.
EXPORTING
I_ITEM = "Account Balance (Workplace): Item Data
IMPORTING
E_AUTOPAY = "Items Intended for Automatic Payment
IMPORTING Parameters details for FMCA_EVENT_1232
I_ITEM - Account Balance (Workplace): Item Data
Data type: FKKL8_ITMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FMCA_EVENT_1232
E_AUTOPAY - Items Intended for Automatic Payment
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMCA_EVENT_1232 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_item | TYPE FKKL8_ITM, " | |||
| lv_e_autopay | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'FMCA_EVENT_1232' "Sample: Account Balance (EBPP): Determination of Incoming Payment Method |
| EXPORTING | ||
| I_ITEM | = lv_i_item | |
| IMPORTING | ||
| E_AUTOPAY | = lv_e_autopay | |
| . " FMCA_EVENT_1232 | ||
ABAP code using 7.40 inline data declarations to call FM FMCA_EVENT_1232
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 BOOLE FROM BOOLE INTO @DATA(ld_e_autopay). | ||||
Search for further information about these or an SAP related objects