SAP FI_PAYMENT_REQUEST_CHECK_ALL Function Module for









FI_PAYMENT_REQUEST_CHECK_ALL is a standard fi payment request check all 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 check all FM, simply by entering the name FI_PAYMENT_REQUEST_CHECK_ALL into the relevant SAP transaction such as SE37 or SE38.

Function Group: F0PQ_EU
Program Name: SAPLF0PQ_EU
Main Program: SAPLF0PQ_EU
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FI_PAYMENT_REQUEST_CHECK_ALL 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_CHECK_ALL'"
EXPORTING
J_MODE = "(I)nsert or (U)pdate
* I_CHECK_ONLY = ' ' "
* I_TLANGU = ' ' "

IMPORTING
E_BELNR = "
E_GJAHR = "
E_BUKRS = "

CHANGING
* J_KBLK_USER = "Additional header data
J_IPRQH = "Header data of payment request
J_IPRQP = "Payment data for payment request

TABLES
J_IPRQI = "Payment request items
* J_FMUD_SMALL_RO = "
* J_PAYCT02 = "
* T_TLINE = "

EXCEPTIONS
CHECK_DYNP_ERROR = 1 PP_CHECK_ERROR = 2 PP_WRITE_ERROR = 3
.



IMPORTING Parameters details for FI_PAYMENT_REQUEST_CHECK_ALL

J_MODE - (I)nsert or (U)pdate

Data type: FIPRQ_MODIFY
Optional: No
Call by Reference: No ( called with pass by value option)

I_CHECK_ONLY -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TLANGU -

Data type: THEAD-TDSPRAS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FI_PAYMENT_REQUEST_CHECK_ALL

E_BELNR -

Data type: VBKPF-BELNR
Optional: No
Call by Reference: No ( called with pass by value option)

E_GJAHR -

Data type: VBKPF-GJAHR
Optional: No
Call by Reference: No ( called with pass by value option)

E_BUKRS -

Data type: VBKPF-BUKRS
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for FI_PAYMENT_REQUEST_CHECK_ALL

J_KBLK_USER - Additional header data

Data type: KBLK_USER
Optional: Yes
Call by Reference: No ( called with pass by value option)

J_IPRQH - Header data of payment request

Data type: IPRQH
Optional: No
Call by Reference: No ( called with pass by value option)

J_IPRQP - Payment data for payment request

Data type: IPRQP
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FI_PAYMENT_REQUEST_CHECK_ALL

J_IPRQI - Payment request items

Data type: IPRQI
Optional: No
Call by Reference: No ( called with pass by value option)

J_FMUD_SMALL_RO -

Data type: FMUD_T_SMALL_RO
Optional: Yes
Call by Reference: No ( called with pass by value option)

J_PAYCT02 -

Data type: PAYCT02
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_TLINE -

Data type: TLINE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

CHECK_DYNP_ERROR - Error in screen check module

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PP_CHECK_ERROR - Error in FI check

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PP_WRITE_ERROR - Write error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FI_PAYMENT_REQUEST_CHECK_ALL 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_j_mode  TYPE FIPRQ_MODIFY, "   
lv_e_belnr  TYPE VBKPF-BELNR, "   
lt_j_iprqi  TYPE STANDARD TABLE OF IPRQI, "   
lv_j_kblk_user  TYPE KBLK_USER, "   
lv_check_dynp_error  TYPE KBLK_USER, "   
lv_e_gjahr  TYPE VBKPF-GJAHR, "   
lv_j_iprqh  TYPE IPRQH, "   
lv_i_check_only  TYPE BOOLE-BOOLE, "   SPACE
lv_pp_check_error  TYPE BOOLE, "   
lt_j_fmud_small_ro  TYPE STANDARD TABLE OF FMUD_T_SMALL_RO, "   
lv_e_bukrs  TYPE VBKPF-BUKRS, "   
lv_j_iprqp  TYPE IPRQP, "   
lv_i_tlangu  TYPE THEAD-TDSPRAS, "   SPACE
lt_j_payct02  TYPE STANDARD TABLE OF PAYCT02, "   
lv_pp_write_error  TYPE PAYCT02, "   
lt_t_tline  TYPE STANDARD TABLE OF TLINE. "   

  CALL FUNCTION 'FI_PAYMENT_REQUEST_CHECK_ALL'  "
    EXPORTING
         J_MODE = lv_j_mode
         I_CHECK_ONLY = lv_i_check_only
         I_TLANGU = lv_i_tlangu
    IMPORTING
         E_BELNR = lv_e_belnr
         E_GJAHR = lv_e_gjahr
         E_BUKRS = lv_e_bukrs
    CHANGING
         J_KBLK_USER = lv_j_kblk_user
         J_IPRQH = lv_j_iprqh
         J_IPRQP = lv_j_iprqp
    TABLES
         J_IPRQI = lt_j_iprqi
         J_FMUD_SMALL_RO = lt_j_fmud_small_ro
         J_PAYCT02 = lt_j_payct02
         T_TLINE = lt_t_tline
    EXCEPTIONS
        CHECK_DYNP_ERROR = 1
        PP_CHECK_ERROR = 2
        PP_WRITE_ERROR = 3
. " FI_PAYMENT_REQUEST_CHECK_ALL




ABAP code using 7.40 inline data declarations to call FM FI_PAYMENT_REQUEST_CHECK_ALL

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 BELNR FROM VBKPF INTO @DATA(ld_e_belnr).
 
 
 
 
"SELECT single GJAHR FROM VBKPF INTO @DATA(ld_e_gjahr).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_check_only).
DATA(ld_i_check_only) = ' '.
 
 
 
"SELECT single BUKRS FROM VBKPF INTO @DATA(ld_e_bukrs).
 
 
"SELECT single TDSPRAS FROM THEAD INTO @DATA(ld_i_tlangu).
DATA(ld_i_tlangu) = ' '.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!