SAP FTR_GET_FIXING_FLOWS Function Module for Read Flow for Fixing

Search SAP Function Modules

FTR_GET_FIXING_FLOWS is a standard ftr get fixing flows SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Flow for Fixing 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 get fixing flows FM, simply by entering the name FTR_GET_FIXING_FLOWS into the relevant SAP transaction such as SE37 or SE38.

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

Function FTR_GET_FIXING_FLOWS 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_GET_FIXING_FLOWS'"Read Flow for Fixing
  EXPORTING
   PI_BUKRS =  "Company Code
   PI_RFHA =  "Financial Transaction
   PI_RFHAZU =  "Transaction Activity
   PI_SANLF =  "Product Category
   PI_SFGZUSTT =  "Transaction Activity Category
   PI_RKONDGR =  "Direction of transaction
   PI_DFIX =  "Fixing Date

 IMPORTING
   PE_T_HAPO =  "

EXCEPTIONS
   TRANSACTION_INVALID = 1 

.

IMPORTING Parameters details for FTR_GET_FIXING_FLOWS

PI_BUKRS - Company Code

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

PI_RFHA - Financial Transaction

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

PI_RFHAZU - Transaction Activity

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

PI_SANLF - Product Category

Data type: VTBFHA-SANLF
Optional: No
Call by Reference: Yes

PI_SFGZUSTT - Transaction Activity Category

Data type: VTBFHAZU-SFGZUSTT
Optional: No
Call by Reference: Yes

PI_RKONDGR - Direction of transaction

Data type: VTBFHAZU-RKONDGR
Optional: No
Call by Reference: Yes

PI_DFIX - Fixing Date

Data type: VTBFHAZU-DFIX
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FTR_GET_FIXING_FLOWS

PE_T_HAPO -

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

EXCEPTIONS details

TRANSACTION_INVALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FTR_GET_FIXING_FLOWS 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_GET_FIXING_FLOWS

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