SAP FTR_FLOW_CHECK Function Module for flow type check
FTR_FLOW_CHECK is a standard ftr flow 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 flow type 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 ftr flow check FM, simply by entering the name FTR_FLOW_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_TLC
Program Name: SAPLFTR_TLC
Main Program: SAPLFTR_TLC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_FLOW_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_FLOW_CHECK'"flow type check.
EXPORTING
IV_SFHAZBA = "Flow Type
IV_SBKTYP = "Category of Flows and Conditions
EXCEPTIONS
NO_ALLOW = 1 INVALID = 2
IMPORTING Parameters details for FTR_FLOW_CHECK
IV_SFHAZBA - Flow Type
Data type: TB_SFHAZBAOptional: No
Call by Reference: Yes
IV_SBKTYP - Category of Flows and Conditions
Data type: TB_SBKTYPOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ALLOW - This flow type is not allowed
Data type:Optional: No
Call by Reference: Yes
INVALID - This flow type is invalid
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTR_FLOW_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_no_allow | TYPE STRING, " | |||
| lv_iv_sfhazba | TYPE TB_SFHAZBA, " | |||
| lv_invalid | TYPE TB_SFHAZBA, " | |||
| lv_iv_sbktyp | TYPE TB_SBKTYP. " |
|   CALL FUNCTION 'FTR_FLOW_CHECK' "flow type check |
| EXPORTING | ||
| IV_SFHAZBA | = lv_iv_sfhazba | |
| IV_SBKTYP | = lv_iv_sbktyp | |
| EXCEPTIONS | ||
| NO_ALLOW = 1 | ||
| INVALID = 2 | ||
| . " FTR_FLOW_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FTR_FLOW_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.Search for further information about these or an SAP related objects