SAP BAPI_FTR_MAINFLOW_CHANGE Function Module for Change Main Flow

Search SAP Function Modules

BAPI_FTR_MAINFLOW_CHANGE is a standard bapi ftr mainflow 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 Change Main Flow 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 mainflow change FM, simply by entering the name BAPI_FTR_MAINFLOW_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FTR_BAPI_MAINFLOW
Program Name: SAPLFTR_BAPI_MAINFLOW
Main Program: SAPLFTR_BAPI_MAINFLOW
Appliation area:
Release date: 21-Sep-2000
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_FTR_MAINFLOW_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_MAINFLOW_CHANGE'"Change Main Flow
  EXPORTING
   COMPANYCODE =  "Company Code of Financial Transaction
   FINANCIALTRANSACTION =  "Financial Transaction Number
   FLOWKEY =  "Key which Identifies a Flow in the BAPI
   MAINFLOW =  "FTR: BAPI Structure for Creating Payment Details
   MAINFLOWX =  "FTR: Change Structure for Changing Other Payment Details
*  SIDE = 0 "Direction of transaction
*  TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs

 IMPORTING
   RETURNFLOWKEY =  "Direction of Flow

TABLES
*  RETURN =  "Return Parameters

.

IMPORTING Parameters details for BAPI_FTR_MAINFLOW_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)

FLOWKEY - Key which Identifies a Flow in the BAPI

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

MAINFLOW - FTR: BAPI Structure for Creating Payment Details

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

MAINFLOWX - FTR: Change Structure for Changing Other Payment Details

Data type: BAPI_FTR_MAINFLOW_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_MAINFLOW_CHANGE

RETURNFLOWKEY - Direction of Flow

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

TABLES Parameters details for BAPI_FTR_MAINFLOW_CHANGE

RETURN - Return Parameters

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

Copy and paste ABAP code example for BAPI_FTR_MAINFLOW_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_MAINFLOW_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