SAP FI_PAYMENT_REQUEST_OPEN_GET Function Module for
FI_PAYMENT_REQUEST_OPEN_GET is a standard fi payment request open get 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 payment request open get FM, simply by entering the name FI_PAYMENT_REQUEST_OPEN_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPRQ
Program Name: SAPLFPRQ
Main Program: SAPLFPRQ
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FI_PAYMENT_REQUEST_OPEN_GET 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_PAYMENT_REQUEST_OPEN_GET'".
IMPORTING
E_ALL_CLEARED = "
TABLES
T_RNG_KEYNO = "
T_PAYRQ = "
EXCEPTIONS
IMPORT_PARAMETER = 1
EXPORTING Parameters details for FI_PAYMENT_REQUEST_OPEN_GET
E_ALL_CLEARED -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
TABLES Parameters details for FI_PAYMENT_REQUEST_OPEN_GET
T_RNG_KEYNO -
Data type: FIPRQ_SEL10TABOptional: No
Call by Reference: No ( called with pass by value option)
T_PAYRQ -
Data type: PAYRQOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
IMPORT_PARAMETER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FI_PAYMENT_REQUEST_OPEN_GET 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: | ||||
| lt_t_rng_keyno | TYPE STANDARD TABLE OF FIPRQ_SEL10TAB, " | |||
| lv_e_all_cleared | TYPE BOOLE-BOOLE, " | |||
| lv_import_parameter | TYPE BOOLE, " | |||
| lt_t_payrq | TYPE STANDARD TABLE OF PAYRQ. " |
|   CALL FUNCTION 'FI_PAYMENT_REQUEST_OPEN_GET' " |
| IMPORTING | ||
| E_ALL_CLEARED | = lv_e_all_cleared | |
| TABLES | ||
| T_RNG_KEYNO | = lt_t_rng_keyno | |
| T_PAYRQ | = lt_t_payrq | |
| EXCEPTIONS | ||
| IMPORT_PARAMETER = 1 | ||
| . " FI_PAYMENT_REQUEST_OPEN_GET | ||
ABAP code using 7.40 inline data declarations to call FM FI_PAYMENT_REQUEST_OPEN_GET
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_all_cleared). | ||||
Search for further information about these or an SAP related objects