SAP FTR_CORR_DETERMINE Function Module for Call FTR_CORR_PLANNED_RECORDS_CREATE and FTR_CORR_GET_ACTIVITY_STATE
FTR_CORR_DETERMINE is a standard ftr corr determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call FTR_CORR_PLANNED_RECORDS_CREATE and FTR_CORR_GET_ACTIVITY_STATE 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 corr determine FM, simply by entering the name FTR_CORR_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TB85
Program Name: SAPLTB85
Main Program: SAPLTB85
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_CORR_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 'FTR_CORR_DETERMINE'"Call FTR_CORR_PLANNED_RECORDS_CREATE and FTR_CORR_GET_ACTIVITY_STATE.
EXPORTING
* I_XDISPLAY = ' ' "Display Mode?
I_SFUNKTL = "
I_SFUNKTV = "
* I_CORTYP = "
* NO_POPUPS = ' ' "keine Popups bei Online-Datenübernahme
I_BUKRS = "Company Code
I_RFHA = "Transaction Number
I_SGSART = "
I_SFHAART = "
I_KONTRH = "
I_RFHAZU = "
I_ROFHAZU = "
I_SFGZUSTT = "
IMPORTING
E_TBCO_STATE_CON = "
E_TBCO_STATE_RECON = "
EXCEPTIONS
INVALID = 1
IMPORTING Parameters details for FTR_CORR_DETERMINE
I_XDISPLAY - Display Mode?
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SFUNKTL -
Data type: VTBFHAZU-SFUNKTLOptional: No
Call by Reference: No ( called with pass by value option)
I_SFUNKTV -
Data type: VTBFHAZU-SFUNKTVOptional: No
Call by Reference: No ( called with pass by value option)
I_CORTYP -
Data type: VTBKORES-CORTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
NO_POPUPS - keine Popups bei Online-Datenübernahme
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BUKRS - Company Code
Data type: VTBFHA-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_RFHA - Transaction Number
Data type: VTBFHA-RFHAOptional: No
Call by Reference: No ( called with pass by value option)
I_SGSART -
Data type: VTBFHA-SGSARTOptional: No
Call by Reference: No ( called with pass by value option)
I_SFHAART -
Data type: VTBFHA-SFHAARTOptional: No
Call by Reference: No ( called with pass by value option)
I_KONTRH -
Data type: VTBFHA-KONTRHOptional: No
Call by Reference: No ( called with pass by value option)
I_RFHAZU -
Data type: VTBFHAZU-RFHAZUOptional: No
Call by Reference: No ( called with pass by value option)
I_ROFHAZU -
Data type: VTBFHAZU-ROFHAZUOptional: No
Call by Reference: No ( called with pass by value option)
I_SFGZUSTT -
Data type: VTBFHAZU-SFGZUSTTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FTR_CORR_DETERMINE
E_TBCO_STATE_CON -
Data type: TBCO_STATE_CONOptional: No
Call by Reference: No ( called with pass by value option)
E_TBCO_STATE_RECON -
Data type: TBCO_STATE_RECONOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID - ungültiger Funktionsbausteinaufruf
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTR_CORR_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_invalid | TYPE STRING, " | |||
| lv_i_xdisplay | TYPE C, " SPACE | |||
| lv_e_tbco_state_con | TYPE TBCO_STATE_CON, " | |||
| lv_i_sfunktl | TYPE VTBFHAZU-SFUNKTL, " | |||
| lv_i_sfunktv | TYPE VTBFHAZU-SFUNKTV, " | |||
| lv_i_cortyp | TYPE VTBKORES-CORTYP, " | |||
| lv_no_popups | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_i_bukrs | TYPE VTBFHA-BUKRS, " | |||
| lv_e_tbco_state_recon | TYPE TBCO_STATE_RECON, " | |||
| lv_i_rfha | TYPE VTBFHA-RFHA, " | |||
| lv_i_sgsart | TYPE VTBFHA-SGSART, " | |||
| lv_i_sfhaart | TYPE VTBFHA-SFHAART, " | |||
| lv_i_kontrh | TYPE VTBFHA-KONTRH, " | |||
| lv_i_rfhazu | TYPE VTBFHAZU-RFHAZU, " | |||
| lv_i_rofhazu | TYPE VTBFHAZU-ROFHAZU, " | |||
| lv_i_sfgzustt | TYPE VTBFHAZU-SFGZUSTT. " |
|   CALL FUNCTION 'FTR_CORR_DETERMINE' "Call FTR_CORR_PLANNED_RECORDS_CREATE and FTR_CORR_GET_ACTIVITY_STATE |
| EXPORTING | ||
| I_XDISPLAY | = lv_i_xdisplay | |
| I_SFUNKTL | = lv_i_sfunktl | |
| I_SFUNKTV | = lv_i_sfunktv | |
| I_CORTYP | = lv_i_cortyp | |
| NO_POPUPS | = lv_no_popups | |
| I_BUKRS | = lv_i_bukrs | |
| I_RFHA | = lv_i_rfha | |
| I_SGSART | = lv_i_sgsart | |
| I_SFHAART | = lv_i_sfhaart | |
| I_KONTRH | = lv_i_kontrh | |
| I_RFHAZU | = lv_i_rfhazu | |
| I_ROFHAZU | = lv_i_rofhazu | |
| I_SFGZUSTT | = lv_i_sfgzustt | |
| IMPORTING | ||
| E_TBCO_STATE_CON | = lv_e_tbco_state_con | |
| E_TBCO_STATE_RECON | = lv_e_tbco_state_recon | |
| EXCEPTIONS | ||
| INVALID = 1 | ||
| . " FTR_CORR_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM FTR_CORR_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.| DATA(ld_i_xdisplay) | = ' '. | |||
| "SELECT single SFUNKTL FROM VTBFHAZU INTO @DATA(ld_i_sfunktl). | ||||
| "SELECT single SFUNKTV FROM VTBFHAZU INTO @DATA(ld_i_sfunktv). | ||||
| "SELECT single CORTYP FROM VTBKORES INTO @DATA(ld_i_cortyp). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_no_popups). | ||||
| DATA(ld_no_popups) | = ' '. | |||
| "SELECT single BUKRS FROM VTBFHA INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single RFHA FROM VTBFHA INTO @DATA(ld_i_rfha). | ||||
| "SELECT single SGSART FROM VTBFHA INTO @DATA(ld_i_sgsart). | ||||
| "SELECT single SFHAART FROM VTBFHA INTO @DATA(ld_i_sfhaart). | ||||
| "SELECT single KONTRH FROM VTBFHA INTO @DATA(ld_i_kontrh). | ||||
| "SELECT single RFHAZU FROM VTBFHAZU INTO @DATA(ld_i_rfhazu). | ||||
| "SELECT single ROFHAZU FROM VTBFHAZU INTO @DATA(ld_i_rofhazu). | ||||
| "SELECT single SFGZUSTT FROM VTBFHAZU INTO @DATA(ld_i_sfgzustt). | ||||
Search for further information about these or an SAP related objects