SAP BAPI_FTR_CONDITION_CREATE Function Module for RFC for Method Condition Creation
BAPI_FTR_CONDITION_CREATE is a standard bapi ftr condition create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RFC for Method Condition Creation 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 bapi ftr condition create FM, simply by entering the name BAPI_FTR_CONDITION_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_BAPI_CONDITION
Program Name: SAPLFTR_BAPI_CONDITION
Main Program: SAPLFTR_BAPI_CONDITION
Appliation area:
Release date: 21-Sep-2000
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_FTR_CONDITION_CREATE 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 'BAPI_FTR_CONDITION_CREATE'"RFC for Method Condition Creation.
EXPORTING
COMPANYCODEIN = "Company Code of Financial Transaction
FINANCIALTRANSACTIONIN = "Financial Transaction Number
REFERENCECONDITIONKEY = "Key which Identifies a Condition in the BAPI
EFFECTIVEFROM = "Validity of condition
CONDITION = "BAPI Structure: Change Condition Details
CONDITIONX = "BAPI Structure: Change Condition Details (Change Info)
* SIDE = 0 "Direction of transaction
* TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
IMPORTING
CONDITIONKEY = "Key which Identifies a Condition in the BAPI
COMPANYCODE = "Company Code
FINANCIALTRANSACTION = "Financial Transaction
TABLES
* FORMULAVARIABLES = "BAPI Structure: Formula Components
* SINGLEDATES = "BAPI Structure: Single Dates
RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_FTR_CONDITION_CREATE
COMPANYCODEIN - Company Code of Financial Transaction
Data type: BAPI2042-COMPANY_CODEOptional: No
Call by Reference: No ( called with pass by value option)
FINANCIALTRANSACTIONIN - Financial Transaction Number
Data type: BAPI2042-TRANSACTIONOptional: No
Call by Reference: No ( called with pass by value option)
REFERENCECONDITIONKEY - Key which Identifies a Condition in the BAPI
Data type: BAPI_FTR_COND_DETAIL-CONDITION_KEYOptional: No
Call by Reference: No ( called with pass by value option)
EFFECTIVEFROM - Validity of condition
Data type: BAPI_FTR_COND_DETAIL-EFFECTIVE_FROMOptional: No
Call by Reference: No ( called with pass by value option)
CONDITION - BAPI Structure: Change Condition Details
Data type: BAPI_FTR_COND_CHANGEOptional: No
Call by Reference: No ( called with pass by value option)
CONDITIONX - BAPI Structure: Change Condition Details (Change Info)
Data type: BAPI_FTR_COND_CHANGEXOptional: No
Call by Reference: No ( called with pass by value option)
SIDE - Direction of transaction
Data type: BAPI_FTR_COND_DETAIL-DIRECTIONOptional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: BAPI2042-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_FTR_CONDITION_CREATE
CONDITIONKEY - Key which Identifies a Condition in the BAPI
Data type: BAPI_FTR_COND_DETAIL-CONDITION_KEYOptional: No
Call by Reference: No ( called with pass by value option)
COMPANYCODE - Company Code
Data type: BAPI2042-COMPANY_CODEOptional: No
Call by Reference: No ( called with pass by value option)
FINANCIALTRANSACTION - Financial Transaction
Data type: BAPI2042-TRANSACTIONOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_FTR_CONDITION_CREATE
FORMULAVARIABLES - BAPI Structure: Formula Components
Data type: BAPI_FTR_COND_FV_CHANGEOptional: Yes
Call by Reference: Yes
SINGLEDATES - BAPI Structure: Single Dates
Data type: BAPI_FTR_COND_SD_CHANGEOptional: Yes
Call by Reference: Yes
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_FTR_CONDITION_CREATE 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_conditionkey | TYPE BAPI_FTR_COND_DETAIL-CONDITION_KEY, " | |||
| lv_companycodein | TYPE BAPI2042-COMPANY_CODE, " | |||
| lt_formulavariables | TYPE STANDARD TABLE OF BAPI_FTR_COND_FV_CHANGE, " | |||
| lv_companycode | TYPE BAPI2042-COMPANY_CODE, " | |||
| lt_singledates | TYPE STANDARD TABLE OF BAPI_FTR_COND_SD_CHANGE, " | |||
| lv_financialtransactionin | TYPE BAPI2042-TRANSACTION, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_financialtransaction | TYPE BAPI2042-TRANSACTION, " | |||
| lv_referenceconditionkey | TYPE BAPI_FTR_COND_DETAIL-CONDITION_KEY, " | |||
| lv_effectivefrom | TYPE BAPI_FTR_COND_DETAIL-EFFECTIVE_FROM, " | |||
| lv_condition | TYPE BAPI_FTR_COND_CHANGE, " | |||
| lv_conditionx | TYPE BAPI_FTR_COND_CHANGEX, " | |||
| lv_side | TYPE BAPI_FTR_COND_DETAIL-DIRECTION, " 0 | |||
| lv_testrun | TYPE BAPI2042-TESTRUN. " SPACE |
|   CALL FUNCTION 'BAPI_FTR_CONDITION_CREATE' "RFC for Method Condition Creation |
| EXPORTING | ||
| COMPANYCODEIN | = lv_companycodein | |
| FINANCIALTRANSACTIONIN | = lv_financialtransactionin | |
| REFERENCECONDITIONKEY | = lv_referenceconditionkey | |
| EFFECTIVEFROM | = lv_effectivefrom | |
| CONDITION | = lv_condition | |
| CONDITIONX | = lv_conditionx | |
| SIDE | = lv_side | |
| TESTRUN | = lv_testrun | |
| IMPORTING | ||
| CONDITIONKEY | = lv_conditionkey | |
| COMPANYCODE | = lv_companycode | |
| FINANCIALTRANSACTION | = lv_financialtransaction | |
| TABLES | ||
| FORMULAVARIABLES | = lt_formulavariables | |
| SINGLEDATES | = lt_singledates | |
| RETURN | = lt_return | |
| . " BAPI_FTR_CONDITION_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_FTR_CONDITION_CREATE
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 CONDITION_KEY FROM BAPI_FTR_COND_DETAIL INTO @DATA(ld_conditionkey). | ||||
| "SELECT single COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_companycodein). | ||||
| "SELECT single COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_companycode). | ||||
| "SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_financialtransactionin). | ||||
| "SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_financialtransaction). | ||||
| "SELECT single CONDITION_KEY FROM BAPI_FTR_COND_DETAIL INTO @DATA(ld_referenceconditionkey). | ||||
| "SELECT single EFFECTIVE_FROM FROM BAPI_FTR_COND_DETAIL INTO @DATA(ld_effectivefrom). | ||||
| "SELECT single DIRECTION FROM BAPI_FTR_COND_DETAIL INTO @DATA(ld_side). | ||||
| "SELECT single TESTRUN FROM BAPI2042 INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
Search for further information about these or an SAP related objects