SAP FTR_FLOW_LOCAL_AMOUNT_CHANGE Function Module for Change LC Amount/Exchange Rate for Foreign Exchange Flows (with Update)

Search SAP Function Modules

FTR_FLOW_LOCAL_AMOUNT_CHANGE is a standard ftr flow local amount change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change LC Amount/Exchange Rate for Foreign Exchange Flows (with Update) 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 flow local amount change FM, simply by entering the name FTR_FLOW_LOCAL_AMOUNT_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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

Function FTR_FLOW_LOCAL_AMOUNT_CHANGE 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_FLOW_LOCAL_AMOUNT_CHANGE'"Change LC Amount/Exchange Rate for Foreign Exchange Flows (with Update)
  EXPORTING
   I_FLOW =  "Financial Transaction Flow
   I_DATE =  "Date and Time, Current (Application Server) Date
   I_LOCAL_AMOUNT =  "Payment Amount in LC
   I_LOCAL_RATE =  "Local Currency Rate
*  I_LOCAL_FIX =  "Steuerung der Umrechnung in die Hauswährung

EXCEPTIONS
   ALREADY_POSTED_RELEASED = 1    AMOUNT_ALREADY_CALCULATED = 2    WRONG_FLOWKEY = 3    NO_FX_DEAL = 4 

.

IMPORTING Parameters details for FTR_FLOW_LOCAL_AMOUNT_CHANGE

I_FLOW - Financial Transaction Flow

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

I_DATE - Date and Time, Current (Application Server) Date

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

I_LOCAL_AMOUNT - Payment Amount in LC

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

I_LOCAL_RATE - Local Currency Rate

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

I_LOCAL_FIX - Steuerung der Umrechnung in die Hauswährung

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

EXCEPTIONS details

ALREADY_POSTED_RELEASED - Bewegung ist bereits freigegeben

Data type:
Optional: No
Call by Reference: Yes

AMOUNT_ALREADY_CALCULATED - HW-Betrag wurde bereits umgerechnet

Data type:
Optional: No
Call by Reference: Yes

WRONG_FLOWKEY - falscher Bewegungsschlüssel

Data type:
Optional: No
Call by Reference: Yes

NO_FX_DEAL - Kein Devisengeschaeft

Data type:
Optional: No
Call by Reference: Yes

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

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