SAP FTR_WORKFLOW_RELEASE_DEALCHECK Function Module for Transaction Release: Check if Transaction Can Be Changed
FTR_WORKFLOW_RELEASE_DEALCHECK is a standard ftr workflow release dealcheck SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Transaction Release: Check if Transaction Can Be Changed 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 workflow release dealcheck FM, simply by entering the name FTR_WORKFLOW_RELEASE_DEALCHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_WF1
Program Name: SAPLFTR_WF1
Main Program: SAPLFTR_WF1
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_WORKFLOW_RELEASE_DEALCHECK 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_WORKFLOW_RELEASE_DEALCHECK'"Transaction Release: Check if Transaction Can Be Changed.
EXPORTING
I_VTBFHA = "Company Code
I_SFGZUSTT = "Transaction Activity Category
I_ACTVT = "Activity
* I_SILENTMESSAGE = ' ' "Ausnahmen statt Fehlernachricht auslösen
EXCEPTIONS
NOT_AUTHORIZED = 1 IN_WORKFLOW = 2
IMPORTING Parameters details for FTR_WORKFLOW_RELEASE_DEALCHECK
I_VTBFHA - Company Code
Data type: VTBFHAOptional: No
Call by Reference: No ( called with pass by value option)
I_SFGZUSTT - Transaction Activity Category
Data type: VTBFHAZU-SFGZUSTTOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTVT - Activity
Data type: ATRELE2-ACTVTOptional: No
Call by Reference: No ( called with pass by value option)
I_SILENTMESSAGE - Ausnahmen statt Fehlernachricht auslösen
Data type: BOOLE-BOOLEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_AUTHORIZED - Keine Berechtigung für den Zugriff
Data type:Optional: No
Call by Reference: Yes
IN_WORKFLOW - Geschäft ist im Workflow
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTR_WORKFLOW_RELEASE_DEALCHECK 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_vtbfha | TYPE VTBFHA, " | |||
| lv_not_authorized | TYPE VTBFHA, " | |||
| lv_i_sfgzustt | TYPE VTBFHAZU-SFGZUSTT, " | |||
| lv_in_workflow | TYPE VTBFHAZU, " | |||
| lv_i_actvt | TYPE ATRELE2-ACTVT, " | |||
| lv_i_silentmessage | TYPE BOOLE-BOOLE. " ' ' |
|   CALL FUNCTION 'FTR_WORKFLOW_RELEASE_DEALCHECK' "Transaction Release: Check if Transaction Can Be Changed |
| EXPORTING | ||
| I_VTBFHA | = lv_i_vtbfha | |
| I_SFGZUSTT | = lv_i_sfgzustt | |
| I_ACTVT | = lv_i_actvt | |
| I_SILENTMESSAGE | = lv_i_silentmessage | |
| EXCEPTIONS | ||
| NOT_AUTHORIZED = 1 | ||
| IN_WORKFLOW = 2 | ||
| . " FTR_WORKFLOW_RELEASE_DEALCHECK | ||
ABAP code using 7.40 inline data declarations to call FM FTR_WORKFLOW_RELEASE_DEALCHECK
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 SFGZUSTT FROM VTBFHAZU INTO @DATA(ld_i_sfgzustt). | ||||
| "SELECT single ACTVT FROM ATRELE2 INTO @DATA(ld_i_actvt). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_silentmessage). | ||||
| DATA(ld_i_silentmessage) | = ' '. | |||
Search for further information about these or an SAP related objects