SAP BAPI_FTR_CTYFWD_DEALCHANGE Function Module for Completely Change a Forex Transaction
BAPI_FTR_CTYFWD_DEALCHANGE is a standard bapi ftr ctyfwd 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 Forex 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 ctyfwd dealchange FM, simply by entering the name BAPI_FTR_CTYFWD_DEALCHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTR_BAPI_CTY_OTC
Program Name: SAPLFTR_BAPI_CTY_OTC
Main Program: SAPLFTR_BAPI_CTY_OTC
Appliation area:
Release date: 07-Aug-2007
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_FTR_CTYFWD_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_CTYFWD_DEALCHANGE'"Completely Change a Forex Transaction.
EXPORTING
COMPANYCODE = "Company Code
* AVERAGE_COMPLETE_INDICATOR = "Indicator if Transferred Data Is Complete
FINANCIALTRANSACTION = "Financial Transaction
COMMODITY = "Change Product-Specific Data of a Commodity Forward
COMMODITYX = "Product-Specific Change Information
GENERALCONTRACTDATA = "Change General Data of a Forex Transaction
GENERALCONTRACTDATAX = "General Change Information
* PAYDET_COMPLETE_INDICATOR = ' ' "Indicator whether Entries in Table PAYMENTDETAIL Are Complete
* ADDFLOW_COMPLETE_INDICATOR = ' ' "Indicator whether Entries in Table ADDFLOW Are Complete
* TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
IMPORTING
RETURNCOMPANYCODE = "Company Code
RETURNFINANCIALTRANSACTION = "Financial Transaction
TABLES
PAYMENTDETAIL = "Change Payment Details
PAYMENTDETAILX = "Change Information for Payment Details
ADDFLOW = "Change Other Flows
ADDFLOWX = "Change Information for Other Flows
* RETURN = "Return Parameter(s)
* EXTENSIONIN = "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
* AVERAGE = "Change Average for Commodity Forward Flow per BAPI
* AVERAGEX = "Change Structure of Average for Commodity Forw. Flow by BAPI
IMPORTING Parameters details for BAPI_FTR_CTYFWD_DEALCHANGE
COMPANYCODE - Company Code
Data type: BAPI2042-COMPANY_CODEOptional: No
Call by Reference: No ( called with pass by value option)
AVERAGE_COMPLETE_INDICATOR - Indicator if Transferred Data Is Complete
Data type: BAPI2042-COMPLETE_INDICATOROptional: Yes
Call by Reference: No ( called with pass by value option)
FINANCIALTRANSACTION - Financial Transaction
Data type: BAPI2042-TRANSACTIONOptional: No
Call by Reference: No ( called with pass by value option)
COMMODITY - Change Product-Specific Data of a Commodity Forward
Data type: BAPI_FTR_CHANGE_CTYOptional: No
Call by Reference: No ( called with pass by value option)
COMMODITYX - Product-Specific Change Information
Data type: BAPI_FTR_CHANGE_CTYXOptional: No
Call by Reference: No ( called with pass by value option)
GENERALCONTRACTDATA - Change General Data of a Forex Transaction
Data type: BAPI_FTR_CHANGEOptional: No
Call by Reference: No ( called with pass by value option)
GENERALCONTRACTDATAX - General Change Information
Data type: BAPI_FTR_CHANGEXOptional: No
Call by Reference: No ( called with pass by value option)
PAYDET_COMPLETE_INDICATOR - Indicator whether Entries in Table PAYMENTDETAIL Are Complete
Data type: BAPI2042-COMPLETE_INDICATORDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ADDFLOW_COMPLETE_INDICATOR - Indicator whether Entries in Table ADDFLOW Are Complete
Data type: BAPI2042-COMPLETE_INDICATORDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: BAPI2042-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_FTR_CTYFWD_DEALCHANGE
RETURNCOMPANYCODE - Company Code
Data type: BAPI2042-COMPANY_CODEOptional: No
Call by Reference: No ( called with pass by value option)
RETURNFINANCIALTRANSACTION - Financial Transaction
Data type: BAPI2042-TRANSACTIONOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_FTR_CTYFWD_DEALCHANGE
PAYMENTDETAIL - Change Payment Details
Data type: BAPI_FTR_PAYDETOptional: No
Call by Reference: No ( called with pass by value option)
PAYMENTDETAILX - Change Information for Payment Details
Data type: BAPI_FTR_PAYDETXOptional: No
Call by Reference: No ( called with pass by value option)
ADDFLOW - Change Other Flows
Data type: BAPI_FTR_FLOWOptional: No
Call by Reference: No ( called with pass by value option)
ADDFLOWX - Change Information for Other Flows
Data type: BAPI_FTR_FLOWXOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONIN - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
AVERAGE - Change Average for Commodity Forward Flow per BAPI
Data type: BAPI_FTR_CHANGE_CTYAVGOptional: Yes
Call by Reference: Yes
AVERAGEX - Change Structure of Average for Commodity Forw. Flow by BAPI
Data type: BAPI_FTR_CHANGE_CTYAVGXOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_FTR_CTYFWD_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, " | |||
| lv_average_complete_indicator | TYPE BAPI2042-COMPLETE_INDICATOR, " | |||
| 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_commodity | TYPE BAPI_FTR_CHANGE_CTY, " | |||
| lt_addflowx | TYPE STANDARD TABLE OF BAPI_FTR_FLOWX, " | |||
| lv_commodityx | TYPE BAPI_FTR_CHANGE_CTYX, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_generalcontractdata | TYPE BAPI_FTR_CHANGE, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_generalcontractdatax | TYPE BAPI_FTR_CHANGEX, " | |||
| lt_average | TYPE STANDARD TABLE OF BAPI_FTR_CHANGE_CTYAVG, " | |||
| lv_paydet_complete_indicator | TYPE BAPI2042-COMPLETE_INDICATOR, " SPACE | |||
| lt_averagex | TYPE STANDARD TABLE OF BAPI_FTR_CHANGE_CTYAVGX, " | |||
| lv_addflow_complete_indicator | TYPE BAPI2042-COMPLETE_INDICATOR, " SPACE | |||
| lv_testrun | TYPE BAPI2042-TESTRUN. " SPACE |
|   CALL FUNCTION 'BAPI_FTR_CTYFWD_DEALCHANGE' "Completely Change a Forex Transaction |
| EXPORTING | ||
| COMPANYCODE | = lv_companycode | |
| AVERAGE_COMPLETE_INDICATOR | = lv_average_complete_indicator | |
| FINANCIALTRANSACTION | = lv_financialtransaction | |
| COMMODITY | = lv_commodity | |
| COMMODITYX | = lv_commodityx | |
| 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 | |
| RETURN | = lt_return | |
| EXTENSIONIN | = lt_extensionin | |
| AVERAGE | = lt_average | |
| AVERAGEX | = lt_averagex | |
| . " BAPI_FTR_CTYFWD_DEALCHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_FTR_CTYFWD_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 COMPLETE_INDICATOR FROM BAPI2042 INTO @DATA(ld_average_complete_indicator). | ||||
| "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