SAP F4TOOL_F4FUNCTION_BRIDGE Function Module for

Search SAP Function Modules

F4TOOL_F4FUNCTION_BRIDGE is a standard f4tool f4function bridge SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 f4tool f4function bridge FM, simply by entering the name F4TOOL_F4FUNCTION_BRIDGE into the relevant SAP transaction such as SE37 or SE38.

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

Function F4TOOL_F4FUNCTION_BRIDGE 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 'F4TOOL_F4FUNCTION_BRIDGE'"
  EXPORTING
*  CUCOL = 0 "
*  CUROW = 0 "
   TABNAME =  "
   FIELDNAME =  "
   DISPLAY_ONLY =  "
*  NO_CONVERSION = ' ' "
*  WINDOW_TITLE =  "
*  TABDISPLAY = ' ' "

 IMPORTING
   SELECTED_VALUE =  "
   SELECTED_INDEX =  "

TABLES
*  SHVALUE_TAB =  "
*  SHSTRUC_TAB =  "
*  VALUE_TAB =  "
*  FIELDS_TAB =  "
*  VALUES_OUT =  "
*  COLTITLE_TAB =  "
*  SEL_OPT =  "

.

IMPORTING Parameters details for F4TOOL_F4FUNCTION_BRIDGE

CUCOL -

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

CUROW -

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

TABNAME -

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

FIELDNAME -

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

DISPLAY_ONLY -

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

NO_CONVERSION -

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

WINDOW_TITLE -

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

TABDISPLAY -

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

EXPORTING Parameters details for F4TOOL_F4FUNCTION_BRIDGE

SELECTED_VALUE -

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

SELECTED_INDEX -

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

TABLES Parameters details for F4TOOL_F4FUNCTION_BRIDGE

SHVALUE_TAB -

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

SHSTRUC_TAB -

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

VALUE_TAB -

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

FIELDS_TAB -

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

VALUES_OUT -

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

COLTITLE_TAB -

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

SEL_OPT -

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

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

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