BAPI_FTR_CHANGE SAP Function module - Change financial transaction

BAPI_FTR_CHANGE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BAPI_FTR_CHANGE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FTR_BUS2042
Released Date: 30.04.1998
Processing type: Remote-Enabled

Pattern for FM BAPI_FTR_CHANGE - BAPI FTR CHANGE

CALL FUNCTION 'BAPI_FTR_CHANGE' "Change financial transaction
  EXPORTING
    companycode =               " bapi2042-company_code  Company Code
    transaction =               " bapi2042-transaction  Transaction Number
*   moneymarket =               " bapi2042_maintain_mm  Structure: Money Market
*   moneymarketx =              " bapi2042_maintain_mm  Structure: Money Market (Comparison)
*   foreignexchange =           " bapi2042_maintain_fx  Structure: Foreign Exchange
*   foreignexchangex =          " bapi2042_maintain_fx  Structure: Foreign Exchange (Comparison)
  IMPORTING
    return =                    " bapiret2      Confirmations
    .  "  BAPI_FTR_CHANGE

ABAP code example for Function Module BAPI_FTR_CHANGE

The ABAP code below is a full code listing to execute function module BAPI_FTR_CHANGE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_return  
 
 TYPE BAPIRET2
.



DATA(ld_companycode) = some text here


DATA(ld_transaction) = some text here

DATA(ld_moneymarket) = 'Check type of data required'.

DATA(ld_moneymarketx) = 'Check type of data required'.

DATA(ld_foreignexchange) = 'Check type of data required'.

DATA(ld_foreignexchangex) = 'Check type of data required'.
.

CALL FUNCTION 'BAPI_FTR_CHANGE'
  EXPORTING
    companycode =                ld_companycode
    transaction =                ld_transaction
*   moneymarket =                ld_moneymarket
*   moneymarketx =               ld_moneymarketx
*   foreignexchange =            ld_foreignexchange
*   foreignexchangex =           ld_foreignexchangex
  IMPORTING
    return =                     ld_return
    .  "  BAPI_FTR_CHANGE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_return
 
 TYPE BAPIRET2 ,
ld_companycode
 
 TYPE BAPI2042-COMPANY_CODE ,
ld_transaction
 
 TYPE BAPI2042-TRANSACTION ,
ld_moneymarket
 
 TYPE BAPI2042_MAINTAIN_MM ,
ld_moneymarketx
 
 TYPE BAPI2042_MAINTAIN_MM ,
ld_foreignexchange
 
 TYPE BAPI2042_MAINTAIN_FX ,
ld_foreignexchangex
 
 TYPE BAPI2042_MAINTAIN_FX .



ld_companycode = some text here

ld_transaction = some text here
ld_moneymarket = 'Check type of data required'.
ld_moneymarketx = 'Check type of data required'.
ld_foreignexchange = 'Check type of data required'.
ld_foreignexchangex = 'Check type of data required'.

SAP Documentation for FM BAPI_FTR_CHANGE