SAP FTR_API_CONDITION_SET Function Module for Condition Details: Set Data
FTR_API_CONDITION_SET is a standard ftr api condition set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Condition Details: Set Data 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 api condition set FM, simply by entering the name FTR_API_CONDITION_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_API
Program Name: SAPLFTR_API
Main Program: SAPLFTR_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_API_CONDITION_SET 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_API_CONDITION_SET'"Condition Details: Set Data.
EXPORTING
MODE = "Single-Character Indicator
CONDITION = "FTR: BAPI Structure for Condition Details
CONDITIONX = "Change Structure of Condition by BAPI
IMPORTING
CONDITIONKEY = "Key which Identifies a Condition in the BAPI
TABLES
* FORMULAVARIABLES = "FTR: BAPI Structure for Condition Details Formula Variables
* SINGLEDATES = "FTR: BAPI Structure for Condition Details Single Dates
* RETURN = "Return Parameter
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for FTR_API_CONDITION_SET
MODE - Single-Character Indicator
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
CONDITION - FTR: BAPI Structure for Condition Details
Data type: BAPI_FTR_CONDITIONOptional: No
Call by Reference: No ( called with pass by value option)
CONDITIONX - Change Structure of Condition by BAPI
Data type: BAPI_FTR_CONDITIONXOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FTR_API_CONDITION_SET
CONDITIONKEY - Key which Identifies a Condition in the BAPI
Data type: TB_BAPI_COND_KEYOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FTR_API_CONDITION_SET
FORMULAVARIABLES - FTR: BAPI Structure for Condition Details Formula Variables
Data type: BAPI_FTR_CONDITION_FORMULAOptional: Yes
Call by Reference: Yes
SINGLEDATES - FTR: BAPI Structure for Condition Details Single Dates
Data type: BAPI_FTR_CONDITION_SINGLEDATOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR - Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTR_API_CONDITION_SET 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_mode | TYPE CHAR1, " | |||
| lv_error | TYPE CHAR1, " | |||
| lv_conditionkey | TYPE TB_BAPI_COND_KEY, " | |||
| lt_formulavariables | TYPE STANDARD TABLE OF BAPI_FTR_CONDITION_FORMULA, " | |||
| lv_condition | TYPE BAPI_FTR_CONDITION, " | |||
| lt_singledates | TYPE STANDARD TABLE OF BAPI_FTR_CONDITION_SINGLEDAT, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_conditionx | TYPE BAPI_FTR_CONDITIONX. " |
|   CALL FUNCTION 'FTR_API_CONDITION_SET' "Condition Details: Set Data |
| EXPORTING | ||
| MODE | = lv_mode | |
| CONDITION | = lv_condition | |
| CONDITIONX | = lv_conditionx | |
| IMPORTING | ||
| CONDITIONKEY | = lv_conditionkey | |
| TABLES | ||
| FORMULAVARIABLES | = lt_formulavariables | |
| SINGLEDATES | = lt_singledates | |
| RETURN | = lt_return | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " FTR_API_CONDITION_SET | ||
ABAP code using 7.40 inline data declarations to call FM FTR_API_CONDITION_SET
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