SAP BAPI_FTR_SECURITY_FIX_PRICE Function Module for Fix Price of a Security Transaction









BAPI_FTR_SECURITY_FIX_PRICE is a standard bapi ftr security fix price SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fix Price of a Security Transaction 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 security fix price FM, simply by entering the name BAPI_FTR_SECURITY_FIX_PRICE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FTR_BAPI_SECURITY
Program Name: SAPLFTR_BAPI_SECURITY
Main Program: SAPLFTR_BAPI_SECURITY
Appliation area:
Release date: 05-Mar-2021
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_FTR_SECURITY_FIX_PRICE 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_SECURITY_FIX_PRICE'"Fix Price of a Security Transaction
EXPORTING
COMPANYCODE = "Company Code
FINANCIALTRANSACTION = "Financial Transaction
NUMBER_UNITS = "No. of Units for Financial Instruments
PRICE = "Sec. Price Without Curr. Reference for Unit/Price Quotation
PRICE_UNIT = "Currency Unit of the Rate
* TESTRUN = "Switch to Simulation Session for Write BAPIs

IMPORTING
RETURNFINANCIALTRANSACTION = "Financial Transaction
RETURNCOMPANYCODE = "Company Code

TABLES
* RETURN = "Return Parameter
.



IMPORTING Parameters details for BAPI_FTR_SECURITY_FIX_PRICE

COMPANYCODE - Company Code

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

FINANCIALTRANSACTION - Financial Transaction

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

NUMBER_UNITS - No. of Units for Financial Instruments

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

PRICE - Sec. Price Without Curr. Reference for Unit/Price Quotation

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

PRICE_UNIT - Currency Unit of the Rate

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

TESTRUN - Switch to Simulation Session for Write BAPIs

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

EXPORTING Parameters details for BAPI_FTR_SECURITY_FIX_PRICE

RETURNFINANCIALTRANSACTION - Financial Transaction

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

RETURNCOMPANYCODE - Company Code

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

TABLES Parameters details for BAPI_FTR_SECURITY_FIX_PRICE

RETURN - Return Parameter

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

Copy and paste ABAP code example for BAPI_FTR_SECURITY_FIX_PRICE 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_companycode  TYPE BAPI2042-COMPANY_CODE, "   
lv_returnfinancialtransaction  TYPE BAPI2042-TRANSACTION, "   
lv_returncompanycode  TYPE BAPI2042-COMPANY_CODE, "   
lv_financialtransaction  TYPE BAPI2042-TRANSACTION, "   
lv_number_units  TYPE BAPI_FTR_CHANGE_SECURITY-NUMBER_UNITS, "   
lv_price  TYPE BAPI_FTR_CHANGE_SECURITY-PRICE, "   
lv_price_unit  TYPE BAPI_FTR_CHANGE_SECURITY-PRICE_UNIT, "   
lv_testrun  TYPE BAPI2042-TESTRUN. "   

  CALL FUNCTION 'BAPI_FTR_SECURITY_FIX_PRICE'  "Fix Price of a Security Transaction
    EXPORTING
         COMPANYCODE = lv_companycode
         FINANCIALTRANSACTION = lv_financialtransaction
         NUMBER_UNITS = lv_number_units
         PRICE = lv_price
         PRICE_UNIT = lv_price_unit
         TESTRUN = lv_testrun
    IMPORTING
         RETURNFINANCIALTRANSACTION = lv_returnfinancialtransaction
         RETURNCOMPANYCODE = lv_returncompanycode
    TABLES
         RETURN = lt_return
. " BAPI_FTR_SECURITY_FIX_PRICE




ABAP code using 7.40 inline data declarations to call FM BAPI_FTR_SECURITY_FIX_PRICE

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 COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_companycode).
 
"SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_returnfinancialtransaction).
 
"SELECT single COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_returncompanycode).
 
"SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_financialtransaction).
 
"SELECT single NUMBER_UNITS FROM BAPI_FTR_CHANGE_SECURITY INTO @DATA(ld_number_units).
 
"SELECT single PRICE FROM BAPI_FTR_CHANGE_SECURITY INTO @DATA(ld_price).
 
"SELECT single PRICE_UNIT FROM BAPI_FTR_CHANGE_SECURITY INTO @DATA(ld_price_unit).
 
"SELECT single TESTRUN FROM BAPI2042 INTO @DATA(ld_testrun).
 


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!