SAP FTR_SL_BAPI_INIT Function Module for Init BAPI Call Module

Search SAP Function Modules

FTR_SL_BAPI_INIT is a standard ftr sl bapi init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Init BAPI Call Module 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 sl bapi init FM, simply by entering the name FTR_SL_BAPI_INIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: FTR_SL
Program Name: SAPLFTR_SL
Main Program: SAPLFTR_SL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTR_SL_BAPI_INIT 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_SL_BAPI_INIT'"Init BAPI Call Module
  EXPORTING
   I_BUKRS =  "Company Code
   I_RFHA =  "Financial Transaction
*  I_RFHAZU =  "Transaction activity

EXCEPTIONS
   DEAL_NOT_FOUND = 1    NO_AUTHORITY = 2    SETTLEMENT_NOT_POSSIBLE = 3    WRONG_PRODUCTTYPE = 4    WRONG_TRANSACTIONTYPE = 5    WRONG_FLOWTYPE = 6    ACTION_NOT_ALLOWED = 7    DEAL_LOCKED = 8    FAILED = 9 

.

IMPORTING Parameters details for FTR_SL_BAPI_INIT

I_BUKRS - Company Code

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

I_RFHA - Financial Transaction

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

I_RFHAZU - Transaction activity

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

EXCEPTIONS details

DEAL_NOT_FOUND - Geschäft nicht vorhanden

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY - No Authorization

Data type:
Optional: No
Call by Reference: Yes

SETTLEMENT_NOT_POSSIBLE - Keine Abrechnung möglich

Data type:
Optional: No
Call by Reference: Yes

WRONG_PRODUCTTYPE - falsche Produktart

Data type:
Optional: No
Call by Reference: Yes

WRONG_TRANSACTIONTYPE - falsche Geschaeftsart

Data type:
Optional: No
Call by Reference: Yes

WRONG_FLOWTYPE - Wrong movement type

Data type:
Optional: No
Call by Reference: Yes

ACTION_NOT_ALLOWED - Action cannot be executed

Data type:
Optional: No
Call by Reference: Yes

DEAL_LOCKED - Geschäft gesperrt

Data type:
Optional: No
Call by Reference: Yes

FAILED -

Data type:
Optional: No
Call by Reference: Yes

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

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