SAP BAPI_FTR_CONDITION_CHANGE Function Module for RFC for Method Condition.Change

Search SAP Function Modules

BAPI_FTR_CONDITION_CHANGE is a standard bapi ftr condition change 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.Change 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 change FM, simply by entering the name BAPI_FTR_CONDITION_CHANGE 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_CHANGE 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_CHANGE'"RFC for Method Condition.Change
  EXPORTING
   COMPANYCODE =  "Company Code of Financial Transaction
   FINANCIALTRANSACTION =  "Financial Transaction Number
   CONDITIONKEY =  "Key which Identifies a Condition in the BAPI
   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
   RETURNCONDITIONKEY =  "Key which Identifies a Condition in the BAPI

TABLES
*  FORMULAVARIABLES =  "BAPI Structure: Formula Components
*  SINGLEDATES =  "BAPI Structure: Single Dates
*  RETURN =  "Return Parameters

.

IMPORTING Parameters details for BAPI_FTR_CONDITION_CHANGE

COMPANYCODE - Company Code of Financial Transaction

Data type: BAPI2042-COMPANY_CODE
Optional: No
Call by Reference: No ( called with pass by value option)

FINANCIALTRANSACTION - Financial Transaction Number

Data type: BAPI2042-TRANSACTION
Optional: No
Call by Reference: No ( called with pass by value option)

CONDITIONKEY - Key which Identifies a Condition in the BAPI

Data type: BAPI_FTR_COND_DETAIL-CONDITION_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

CONDITION - BAPI Structure: Change Condition Details

Data type: BAPI_FTR_COND_CHANGE
Optional: No
Call by Reference: No ( called with pass by value option)

CONDITIONX - BAPI Structure: Change Condition Details (Change Info)

Data type: BAPI_FTR_COND_CHANGEX
Optional: No
Call by Reference: No ( called with pass by value option)

SIDE - Direction of Transaction

Data type: BAPI_FTR_COND_DETAIL-DIRECTION
Optional: Yes
Call by Reference: No ( called with pass by value option)

TESTRUN - Switch to Simulation Mode for Write BAPIs

Data type: BAPI2042-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_FTR_CONDITION_CHANGE

RETURNCONDITIONKEY - Key which Identifies a Condition in the BAPI

Data type: BAPI_FTR_COND_DETAIL-CONDITION_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_FTR_CONDITION_CHANGE

FORMULAVARIABLES - BAPI Structure: Formula Components

Data type: BAPI_FTR_COND_FV_CHANGE
Optional: Yes
Call by Reference: Yes

SINGLEDATES - BAPI Structure: Single Dates

Data type: BAPI_FTR_COND_SD_CHANGE
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameters

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_FTR_CONDITION_CHANGE 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.

ABAP code using 7.40 inline data declarations to call FM BAPI_FTR_CONDITION_CHANGE

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