SAP BAPI_FTR_ADDFLOW_CREATE Function Module for Create Ôther Flow









BAPI_FTR_ADDFLOW_CREATE is a standard bapi ftr addflow 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 Create Ôther 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 addflow create FM, simply by entering the name BAPI_FTR_ADDFLOW_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_FTR_ADDFLOW_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_ADDFLOW_CREATE'"Create Ôther Flow
EXPORTING
COMPANYCODEIN = "Company Code of Financial Transaction
FINANCIALTRANSACTIONIN = "Financial Transaction Number
ADDITIONALFLOW = "FTR: BAPI Structure for Creating Payment Details
* TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
* SIDE = 0 "Direction of transaction

IMPORTING
FLOWKEY = "Flow Type
FINANCIALTRANSACTION = "Company Code
COMPANYCODE = "Financial Transaction

TABLES
RETURN = "Return Parameters
.



IMPORTING Parameters details for BAPI_FTR_ADDFLOW_CREATE

COMPANYCODEIN - Company Code of Financial Transaction

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

FINANCIALTRANSACTIONIN - Financial Transaction Number

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

ADDITIONALFLOW - FTR: BAPI Structure for Creating Payment Details

Data type: BAPI_FTR_ADDFLOW_CREATE
Optional: No
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)

SIDE - Direction of transaction

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

EXPORTING Parameters details for BAPI_FTR_ADDFLOW_CREATE

FLOWKEY - Flow Type

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

FINANCIALTRANSACTION - Company Code

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

COMPANYCODE - Financial Transaction

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

TABLES Parameters details for BAPI_FTR_ADDFLOW_CREATE

RETURN - Return Parameters

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

Copy and paste ABAP code example for BAPI_FTR_ADDFLOW_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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_flowkey  TYPE BAPI_FTR_ADDFLOW_DETAIL-FLOW_KEY, "   
lv_companycodein  TYPE BAPI2042-COMPANY_CODE, "   
lv_financialtransaction  TYPE BAPI2042-TRANSACTION, "   
lv_financialtransactionin  TYPE BAPI2042-TRANSACTION, "   
lv_companycode  TYPE BAPI2042-COMPANY_CODE, "   
lv_additionalflow  TYPE BAPI_FTR_ADDFLOW_CREATE, "   
lv_testrun  TYPE BAPI2042-TESTRUN, "   SPACE
lv_side  TYPE BAPI_FTR_COND_DETAIL-DIRECTION. "   0

  CALL FUNCTION 'BAPI_FTR_ADDFLOW_CREATE'  "Create Ôther Flow
    EXPORTING
         COMPANYCODEIN = lv_companycodein
         FINANCIALTRANSACTIONIN = lv_financialtransactionin
         ADDITIONALFLOW = lv_additionalflow
         TESTRUN = lv_testrun
         SIDE = lv_side
    IMPORTING
         FLOWKEY = lv_flowkey
         FINANCIALTRANSACTION = lv_financialtransaction
         COMPANYCODE = lv_companycode
    TABLES
         RETURN = lt_return
. " BAPI_FTR_ADDFLOW_CREATE




ABAP code using 7.40 inline data declarations to call FM BAPI_FTR_ADDFLOW_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 FLOW_KEY FROM BAPI_FTR_ADDFLOW_DETAIL INTO @DATA(ld_flowkey).
 
"SELECT single COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_companycodein).
 
"SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_financialtransaction).
 
"SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_financialtransactionin).
 
"SELECT single COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_companycode).
 
 
"SELECT single TESTRUN FROM BAPI2042 INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 
"SELECT single DIRECTION FROM BAPI_FTR_COND_DETAIL INTO @DATA(ld_side).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!