SAP BAPI_FTR_SECURITY_DEALCHANGE Function Module for Completely Change a Security Transaction









BAPI_FTR_SECURITY_DEALCHANGE is a standard bapi ftr security dealchange SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Completely Change 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 dealchange FM, simply by entering the name BAPI_FTR_SECURITY_DEALCHANGE 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: 31-Aug-2006
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_FTR_SECURITY_DEALCHANGE 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_DEALCHANGE'"Completely Change a Security Transaction
  EXPORTING
   COMPANYCODE =  "Company Code
   FINANCIALTRANSACTION =  "Financial Transaction
   SECURITY =  "Create Security Transaction per BAPI
   SECURITYX =  "Change Security Transaction per BAPI
   GENERALCONTRACTDATA =  "FTR: BAPI Structure for Changing Transactions (General)
   GENERALCONTRACTDATAX =  "FTR: BAPI Structure Change Information for Change Method
*  PAYDET_COMPLETE_INDICATOR = ' ' "Indicator if transferred data is complete
*  ADDFLOW_COMPLETE_INDICATOR = ' ' "Indicator if transferred data is complete
*  TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs

 IMPORTING
   RETURNCOMPANYCODE =  "Company Code
   RETURNFINANCIALTRANSACTION =  "Financial Transaction

TABLES
   PAYMENTDETAIL =  "FTR: BAPI Structure for Payment Details
   PAYMENTDETAILX =  "FTR: BAPI Structure Change Information for Payment Details
   ADDFLOW =  "FTR: BAPI Structure for Flows
   ADDFLOWX =  "FTR: BAPI Structure Change Information for Flows
*  EXTENSIONIN =  "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
*  RETURN =  "Return Parameter(s)
.



IMPORTING Parameters details for BAPI_FTR_SECURITY_DEALCHANGE

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)

SECURITY - Create Security Transaction per BAPI

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

SECURITYX - Change Security Transaction per BAPI

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

GENERALCONTRACTDATA - FTR: BAPI Structure for Changing Transactions (General)

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

GENERALCONTRACTDATAX - FTR: BAPI Structure Change Information for Change Method

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

PAYDET_COMPLETE_INDICATOR - Indicator if transferred data is complete

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

ADDFLOW_COMPLETE_INDICATOR - Indicator if transferred data is complete

Data type: BAPI2042-COMPLETE_INDICATOR
Default: SPACE
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_SECURITY_DEALCHANGE

RETURNCOMPANYCODE - Company Code

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

RETURNFINANCIALTRANSACTION - Financial Transaction

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

TABLES Parameters details for BAPI_FTR_SECURITY_DEALCHANGE

PAYMENTDETAIL - FTR: BAPI Structure for Payment Details

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

PAYMENTDETAILX - FTR: BAPI Structure Change Information for Payment Details

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

ADDFLOW - FTR: BAPI Structure for Flows

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

ADDFLOWX - FTR: BAPI Structure Change Information for Flows

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

EXTENSIONIN - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut

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

RETURN - Return Parameter(s)

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

Copy and paste ABAP code example for BAPI_FTR_SECURITY_DEALCHANGE 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:
lv_companycode  TYPE BAPI2042-COMPANY_CODE, "   
lt_paymentdetail  TYPE STANDARD TABLE OF BAPI_FTR_PAYDET, "   
lv_returncompanycode  TYPE BAPI2042-COMPANY_CODE, "   
lt_paymentdetailx  TYPE STANDARD TABLE OF BAPI_FTR_PAYDETX, "   
lv_financialtransaction  TYPE BAPI2042-TRANSACTION, "   
lv_returnfinancialtransaction  TYPE BAPI2042-TRANSACTION, "   
lt_addflow  TYPE STANDARD TABLE OF BAPI_FTR_FLOW, "   
lv_security  TYPE BAPI_FTR_CHANGE_SECURITY, "   
lt_addflowx  TYPE STANDARD TABLE OF BAPI_FTR_FLOWX, "   
lv_securityx  TYPE BAPI_FTR_CHANGE_SECURITYX, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_generalcontractdata  TYPE BAPI_FTR_CHANGE, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_generalcontractdatax  TYPE BAPI_FTR_CHANGEX, "   
lv_paydet_complete_indicator  TYPE BAPI2042-COMPLETE_INDICATOR, "   SPACE
lv_addflow_complete_indicator  TYPE BAPI2042-COMPLETE_INDICATOR, "   SPACE
lv_testrun  TYPE BAPI2042-TESTRUN. "   SPACE

  CALL FUNCTION 'BAPI_FTR_SECURITY_DEALCHANGE'  "Completely Change a Security Transaction
    EXPORTING
         COMPANYCODE = lv_companycode
         FINANCIALTRANSACTION = lv_financialtransaction
         SECURITY = lv_security
         SECURITYX = lv_securityx
         GENERALCONTRACTDATA = lv_generalcontractdata
         GENERALCONTRACTDATAX = lv_generalcontractdatax
         PAYDET_COMPLETE_INDICATOR = lv_paydet_complete_indicator
         ADDFLOW_COMPLETE_INDICATOR = lv_addflow_complete_indicator
         TESTRUN = lv_testrun
    IMPORTING
         RETURNCOMPANYCODE = lv_returncompanycode
         RETURNFINANCIALTRANSACTION = lv_returnfinancialtransaction
    TABLES
         PAYMENTDETAIL = lt_paymentdetail
         PAYMENTDETAILX = lt_paymentdetailx
         ADDFLOW = lt_addflow
         ADDFLOWX = lt_addflowx
         EXTENSIONIN = lt_extensionin
         RETURN = lt_return
. " BAPI_FTR_SECURITY_DEALCHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_FTR_SECURITY_DEALCHANGE

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 COMPANY_CODE FROM BAPI2042 INTO @DATA(ld_returncompanycode).
 
 
"SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_financialtransaction).
 
"SELECT single TRANSACTION FROM BAPI2042 INTO @DATA(ld_returnfinancialtransaction).
 
 
 
 
 
 
 
 
 
"SELECT single COMPLETE_INDICATOR FROM BAPI2042 INTO @DATA(ld_paydet_complete_indicator).
DATA(ld_paydet_complete_indicator) = ' '.
 
"SELECT single COMPLETE_INDICATOR FROM BAPI2042 INTO @DATA(ld_addflow_complete_indicator).
DATA(ld_addflow_complete_indicator) = ' '.
 
"SELECT single TESTRUN FROM BAPI2042 INTO @DATA(ld_testrun).
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!