SAP FI_APAR_MANDATE_DOUBLECLICK Function Module for
FI_APAR_MANDATE_DOUBLECLICK is a standard fi apar mandate doubleclick 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 fi apar mandate doubleclick FM, simply by entering the name FI_APAR_MANDATE_DOUBLECLICK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FI_APAR_SEPA_MANDATES
Program Name: SAPLFI_APAR_SEPA_MANDATES
Main Program: SAPLFI_APAR_SEPA_MANDATES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FI_APAR_MANDATE_DOUBLECLICK 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 'FI_APAR_MANDATE_DOUBLECLICK'".
EXPORTING
* I_MANDATE = "
* I_USE = "
I_FIELDNAME = "Field Name
IMPORTING
E_MNDID = "
IMPORTING Parameters details for FI_APAR_MANDATE_DOUBLECLICK
I_MANDATE -
Data type: RFSEPA_WAOptional: Yes
Call by Reference: Yes
I_USE -
Data type: SEPA_MANDATE_USEOptional: Yes
Call by Reference: Yes
I_FIELDNAME - Field Name
Data type: FIELDNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FI_APAR_MANDATE_DOUBLECLICK
E_MNDID -
Data type: SEPA_MNDIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FI_APAR_MANDATE_DOUBLECLICK 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_e_mndid | TYPE SEPA_MNDID, " | |||
| lv_i_mandate | TYPE RFSEPA_WA, " | |||
| lv_i_use | TYPE SEPA_MANDATE_USE, " | |||
| lv_i_fieldname | TYPE FIELDNAME. " |
|   CALL FUNCTION 'FI_APAR_MANDATE_DOUBLECLICK' " |
| EXPORTING | ||
| I_MANDATE | = lv_i_mandate | |
| I_USE | = lv_i_use | |
| I_FIELDNAME | = lv_i_fieldname | |
| IMPORTING | ||
| E_MNDID | = lv_e_mndid | |
| . " FI_APAR_MANDATE_DOUBLECLICK | ||
ABAP code using 7.40 inline data declarations to call FM FI_APAR_MANDATE_DOUBLECLICK
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