SAP PR_WF_SUBWF_DETERMINE Function Module for
PR_WF_SUBWF_DETERMINE is a standard pr wf subwf determine 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 pr wf subwf determine FM, simply by entering the name PR_WF_SUBWF_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: F040
Program Name: SAPLF040
Main Program: SAPLF040
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PR_WF_SUBWF_DETERMINE 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_SUBWF_DETERMINE'".
EXPORTING
BELNR = "Document Number
BUKRS = "Company Code
GJAHR = "Fiscal Year
BUZEI = "
IMPORTING
E_SUBNR = "
E_FRWEG = "
E_ANZDT = "
E_DMBTR = "
E_WFVAR = "
EXCEPTIONS
DOCUMENT_ITEM_NOT_FOUND = 1 NOT_FOUND = 2
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_SAPLF040_001 WF: Amount Release by Person with Release Authorization
EXIT_SAPLF040_002 WF: Account Assignment Approval by Person with Release Authorization
EXIT_SAPLF040_003 WF: Operater after Refusal of Release
EXIT_SAPLF040_004 User Exit: Payment Release by Person with Release Authorization
IMPORTING Parameters details for PR_WF_SUBWF_DETERMINE
BELNR - Document Number
Data type: VBKPF-BELNROptional: No
Call by Reference: No ( called with pass by value option)
BUKRS - Company Code
Data type: VBKPF-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
GJAHR - Fiscal Year
Data type: VBKPF-GJAHROptional: No
Call by Reference: No ( called with pass by value option)
BUZEI -
Data type: BSEG-BUZEIOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PR_WF_SUBWF_DETERMINE
E_SUBNR -
Data type: VBWF06-SUBNROptional: No
Call by Reference: No ( called with pass by value option)
E_FRWEG -
Data type: VBWF05-FRWEGOptional: No
Call by Reference: No ( called with pass by value option)
E_ANZDT -
Data type: RF05V-ANZDTOptional: No
Call by Reference: No ( called with pass by value option)
E_DMBTR -
Data type: BSEG-DMBTROptional: No
Call by Reference: No ( called with pass by value option)
E_WFVAR -
Data type: T001-WFVAROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DOCUMENT_ITEM_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PR_WF_SUBWF_DETERMINE 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_belnr | TYPE VBKPF-BELNR, " | |||
| lv_e_subnr | TYPE VBWF06-SUBNR, " | |||
| lv_document_item_not_found | TYPE VBWF06, " | |||
| lv_bukrs | TYPE VBKPF-BUKRS, " | |||
| lv_e_frweg | TYPE VBWF05-FRWEG, " | |||
| lv_not_found | TYPE VBWF05, " | |||
| lv_gjahr | TYPE VBKPF-GJAHR, " | |||
| lv_e_anzdt | TYPE RF05V-ANZDT, " | |||
| lv_buzei | TYPE BSEG-BUZEI, " | |||
| lv_e_dmbtr | TYPE BSEG-DMBTR, " | |||
| lv_e_wfvar | TYPE T001-WFVAR. " |
|   CALL FUNCTION 'PR_WF_SUBWF_DETERMINE' " |
| EXPORTING | ||
| BELNR | = lv_belnr | |
| BUKRS | = lv_bukrs | |
| GJAHR | = lv_gjahr | |
| BUZEI | = lv_buzei | |
| IMPORTING | ||
| E_SUBNR | = lv_e_subnr | |
| E_FRWEG | = lv_e_frweg | |
| E_ANZDT | = lv_e_anzdt | |
| E_DMBTR | = lv_e_dmbtr | |
| E_WFVAR | = lv_e_wfvar | |
| EXCEPTIONS | ||
| DOCUMENT_ITEM_NOT_FOUND = 1 | ||
| NOT_FOUND = 2 | ||
| . " PR_WF_SUBWF_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM PR_WF_SUBWF_DETERMINE
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_belnr). | ||||
| "SELECT single SUBNR FROM VBWF06 INTO @DATA(ld_e_subnr). | ||||
| "SELECT single BUKRS FROM VBKPF INTO @DATA(ld_bukrs). | ||||
| "SELECT single FRWEG FROM VBWF05 INTO @DATA(ld_e_frweg). | ||||
| "SELECT single GJAHR FROM VBKPF INTO @DATA(ld_gjahr). | ||||
| "SELECT single ANZDT FROM RF05V INTO @DATA(ld_e_anzdt). | ||||
| "SELECT single BUZEI FROM BSEG INTO @DATA(ld_buzei). | ||||
| "SELECT single DMBTR FROM BSEG INTO @DATA(ld_e_dmbtr). | ||||
| "SELECT single WFVAR FROM T001 INTO @DATA(ld_e_wfvar). | ||||
Search for further information about these or an SAP related objects