SAP TB_GENERATED_FLOWS_DETERM_BFFR Function Module for Define Current SI Derived Flows

Search SAP Function Modules

TB_GENERATED_FLOWS_DETERM_BFFR is a standard tb generated flows determ bffr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Define Current SI Derived Flows 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 tb generated flows determ bffr FM, simply by entering the name TB_GENERATED_FLOWS_DETERM_BFFR into the relevant SAP transaction such as SE37 or SE38.

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

Function TB_GENERATED_FLOWS_DETERM_BFFR 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 'TB_GENERATED_FLOWS_DETERM_BFFR'"Define Current SI Derived Flows
  EXPORTING
   COMPANYCODE =  "Company Code
*  COUNTERPARTY =  "Partner (optional)
*  SFHAART = ' ' "Transaction Type
   SGSART =  "Product Type
*  I_ZGP =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

 IMPORTING
   GEN_FLOWS_ALLOCATION =  "Derived Flows

TABLES
*  PARTNER_R =  "Partnerrangestabelle als Rückgabe
*  GENERATED_FLOWS_ENTRY =  "Derived Flows

EXCEPTIONS
   ALLOCATION_NOT_FOUND = 1    SFHAART_NOT_FOUND = 2    SGSART_NOT_FOUND = 3 

.

IMPORTING Parameters details for TB_GENERATED_FLOWS_DETERM_BFFR

COMPANYCODE - Company Code

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

COUNTERPARTY - Partner (optional)

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

SFHAART - Transaction Type

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

SGSART - Product Type

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

I_ZGP - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for TB_GENERATED_FLOWS_DETERM_BFFR

GEN_FLOWS_ALLOCATION - Derived Flows

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

TABLES Parameters details for TB_GENERATED_FLOWS_DETERM_BFFR

PARTNER_R - Partnerrangestabelle als Rückgabe

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

GENERATED_FLOWS_ENTRY - Derived Flows

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

EXCEPTIONS details

ALLOCATION_NOT_FOUND - Keine Standing Instruction vorhanden

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

SFHAART_NOT_FOUND - Geschäftsart ist nicht vorgesehen

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

SGSART_NOT_FOUND - Produktart ist nicht vorgesehen

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

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

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