SAP PR_WF_PAYMENT_BLOCK_CHECK Function Module for Payment block check
PR_WF_PAYMENT_BLOCK_CHECK is a standard pr wf payment block check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Payment block check 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 pr wf payment block check FM, simply by entering the name PR_WF_PAYMENT_BLOCK_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: F051
Program Name: SAPLF051
Main Program: SAPLF051
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PR_WF_PAYMENT_BLOCK_CHECK 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 'PR_WF_PAYMENT_BLOCK_CHECK'"Payment block check.
EXPORTING
DMBTR = "
WFVAR = "
ZLSPR = "
BLART = "
* NOMSG = ' ' "
* FORBID_WFBLOCK = ' ' "
* CHECK_EMPTY = ' ' "
* BKPF = "
* BSEG = "
EXCEPTIONS
NOT_VALID = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLF051_001 User Exit: Check Whether Payment Release Necessary
EXIT_SAPLF051_002 Check Whether Document Parking Release is Necessary
EXIT_SAPLF051_003 Results of Changing Object FIPP
IMPORTING Parameters details for PR_WF_PAYMENT_BLOCK_CHECK
DMBTR -
Data type: BSEG-DMBTROptional: No
Call by Reference: No ( called with pass by value option)
WFVAR -
Data type: T001-WFVAROptional: No
Call by Reference: No ( called with pass by value option)
ZLSPR -
Data type: BSEG-ZLSPROptional: No
Call by Reference: No ( called with pass by value option)
BLART -
Data type: BKPF-BLARTOptional: No
Call by Reference: No ( called with pass by value option)
NOMSG -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FORBID_WFBLOCK -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHECK_EMPTY -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
BKPF -
Data type: BKPFOptional: Yes
Call by Reference: No ( called with pass by value option)
BSEG -
Data type: BSEGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PR_WF_PAYMENT_BLOCK_CHECK 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_dmbtr | TYPE BSEG-DMBTR, " | |||
| lv_not_valid | TYPE BSEG, " | |||
| lv_wfvar | TYPE T001-WFVAR, " | |||
| lv_zlspr | TYPE BSEG-ZLSPR, " | |||
| lv_blart | TYPE BKPF-BLART, " | |||
| lv_nomsg | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_forbid_wfblock | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_check_empty | TYPE XFELD, " SPACE | |||
| lv_bkpf | TYPE BKPF, " | |||
| lv_bseg | TYPE BSEG. " |
|   CALL FUNCTION 'PR_WF_PAYMENT_BLOCK_CHECK' "Payment block check |
| EXPORTING | ||
| DMBTR | = lv_dmbtr | |
| WFVAR | = lv_wfvar | |
| ZLSPR | = lv_zlspr | |
| BLART | = lv_blart | |
| NOMSG | = lv_nomsg | |
| FORBID_WFBLOCK | = lv_forbid_wfblock | |
| CHECK_EMPTY | = lv_check_empty | |
| BKPF | = lv_bkpf | |
| BSEG | = lv_bseg | |
| EXCEPTIONS | ||
| NOT_VALID = 1 | ||
| . " PR_WF_PAYMENT_BLOCK_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM PR_WF_PAYMENT_BLOCK_CHECK
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 DMBTR FROM BSEG INTO @DATA(ld_dmbtr). | ||||
| "SELECT single WFVAR FROM T001 INTO @DATA(ld_wfvar). | ||||
| "SELECT single ZLSPR FROM BSEG INTO @DATA(ld_zlspr). | ||||
| "SELECT single BLART FROM BKPF INTO @DATA(ld_blart). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_nomsg). | ||||
| DATA(ld_nomsg) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_forbid_wfblock). | ||||
| DATA(ld_forbid_wfblock) | = ' '. | |||
| DATA(ld_check_empty) | = ' '. | |||
Search for further information about these or an SAP related objects