SAP TABCONTROL_SH_PREPARE_DIALOGS Function Module for Generating the (internal) tables used for the search help









TABCONTROL_SH_PREPARE_DIALOGS is a standard tabcontrol sh prepare dialogs SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Generating the (internal) tables used for the search help 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 tabcontrol sh prepare dialogs FM, simply by entering the name TABCONTROL_SH_PREPARE_DIALOGS into the relevant SAP transaction such as SE37 or SE38.

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



Function TABCONTROL_SH_PREPARE_DIALOGS 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 'TABCONTROL_SH_PREPARE_DIALOGS'"Generating the (internal) tables used for the search help
EXPORTING
FIELDNAME = "
* MATCHCODE = "
TAB_CTRL = "
* N_MATCHCODE = "
* SHLP_CURR = "
* MAXRECORDS = "
* MAXRECORDTITLE = "

IMPORTING
WIDTH = "

TABLES
DIALOGITEM = "
DIALOGPAGE = "
* DESCR_TAB = "
* SELECTION_FIELDS = "
* SHLP_TAB = "
.



IMPORTING Parameters details for TABCONTROL_SH_PREPARE_DIALOGS

FIELDNAME -

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

MATCHCODE -

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

TAB_CTRL -

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

N_MATCHCODE -

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

SHLP_CURR -

Data type: SHLP_DESCR_T
Optional: Yes
Call by Reference: Yes

MAXRECORDS -

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

MAXRECORDTITLE -

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

EXPORTING Parameters details for TABCONTROL_SH_PREPARE_DIALOGS

WIDTH -

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

TABLES Parameters details for TABCONTROL_SH_PREPARE_DIALOGS

DIALOGITEM -

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

DIALOGPAGE -

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

DESCR_TAB -

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

SELECTION_FIELDS -

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

SHLP_TAB -

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

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

DATA:
lv_width  TYPE I, "   
lv_fieldname  TYPE C, "   
lt_dialogitem  TYPE STANDARD TABLE OF MCTBC_DI, "   
lv_matchcode  TYPE PHELP-MCOBJ, "   
lt_dialogpage  TYPE STANDARD TABLE OF MCTBC_DP, "   
lv_tab_ctrl  TYPE I, "   
lt_descr_tab  TYPE STANDARD TABLE OF DDSHDESCR, "   
lv_n_matchcode  TYPE DD30V-SHLPNAME, "   
lt_selection_fields  TYPE STANDARD TABLE OF DFIES, "   
lt_shlp_tab  TYPE STANDARD TABLE OF SHLP_DESCR_TAB_T, "   
lv_shlp_curr  TYPE SHLP_DESCR_T, "   
lv_maxrecords  TYPE C, "   
lv_maxrecordtitle  TYPE C. "   

  CALL FUNCTION 'TABCONTROL_SH_PREPARE_DIALOGS'  "Generating the (internal) tables used for the search help
    EXPORTING
         FIELDNAME = lv_fieldname
         MATCHCODE = lv_matchcode
         TAB_CTRL = lv_tab_ctrl
         N_MATCHCODE = lv_n_matchcode
         SHLP_CURR = lv_shlp_curr
         MAXRECORDS = lv_maxrecords
         MAXRECORDTITLE = lv_maxrecordtitle
    IMPORTING
         WIDTH = lv_width
    TABLES
         DIALOGITEM = lt_dialogitem
         DIALOGPAGE = lt_dialogpage
         DESCR_TAB = lt_descr_tab
         SELECTION_FIELDS = lt_selection_fields
         SHLP_TAB = lt_shlp_tab
. " TABCONTROL_SH_PREPARE_DIALOGS




ABAP code using 7.40 inline data declarations to call FM TABCONTROL_SH_PREPARE_DIALOGS

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.

 
 
 
"SELECT single MCOBJ FROM PHELP INTO @DATA(ld_matchcode).
 
 
 
 
"SELECT single SHLPNAME FROM DD30V INTO @DATA(ld_n_matchcode).
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!