SAP FTR_STAV_WORKFLOW_CHECK Function Module for Check if Object Is Processed in a Workflow
FTR_STAV_WORKFLOW_CHECK is a standard ftr stav workflow 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 Check if Object Is Processed in a Workflow 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 ftr stav workflow check FM, simply by entering the name FTR_STAV_WORKFLOW_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_STAV
Program Name: SAPLFTR_STAV
Main Program: SAPLFTR_STAV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_STAV_WORKFLOW_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 'FTR_STAV_WORKFLOW_CHECK'"Check if Object Is Processed in a Workflow.
EXPORTING
I_BUKRS = "Company Code
I_RFHA = "Financial Transaction
IMPORTING Parameters details for FTR_STAV_WORKFLOW_CHECK
I_BUKRS - Company Code
Data type: VTBFHA-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_RFHA - Financial Transaction
Data type: VTBFHA-RFHAOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FTR_STAV_WORKFLOW_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_i_bukrs | TYPE VTBFHA-BUKRS, " | |||
| lv_i_rfha | TYPE VTBFHA-RFHA. " |
|   CALL FUNCTION 'FTR_STAV_WORKFLOW_CHECK' "Check if Object Is Processed in a Workflow |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RFHA | = lv_i_rfha | |
| . " FTR_STAV_WORKFLOW_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FTR_STAV_WORKFLOW_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 BUKRS FROM VTBFHA INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single RFHA FROM VTBFHA INTO @DATA(ld_i_rfha). | ||||
Search for further information about these or an SAP related objects