SAP F4_MATCHCODE_USER_EXIT Function Module for Bridge functions for the K-matchcodes









F4_MATCHCODE_USER_EXIT is a standard f4 matchcode user exit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Bridge functions for the K-matchcodes 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 f4 matchcode user exit FM, simply by entering the name F4_MATCHCODE_USER_EXIT into the relevant SAP transaction such as SE37 or SE38.

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



Function F4_MATCHCODE_USER_EXIT 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 'F4_MATCHCODE_USER_EXIT'"Bridge functions for the K-matchcodes
EXPORTING
* FUNCNAME = ' ' "

CHANGING
SHLP = "
CALLCONTROL = "

TABLES
SHLP_TAB = "
RECORD_TAB = "

EXCEPTIONS
INVALID_OBJECT = 1
.



IMPORTING Parameters details for F4_MATCHCODE_USER_EXIT

FUNCNAME -

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

CHANGING Parameters details for F4_MATCHCODE_USER_EXIT

SHLP -

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

CALLCONTROL -

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

TABLES Parameters details for F4_MATCHCODE_USER_EXIT

SHLP_TAB -

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

RECORD_TAB -

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

EXCEPTIONS details

INVALID_OBJECT -

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

Copy and paste ABAP code example for F4_MATCHCODE_USER_EXIT 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_shlp  TYPE SHLP_DESCR_T, "   
lv_funcname  TYPE MCFUNCNAME, "   ' '
lt_shlp_tab  TYPE STANDARD TABLE OF SHLP_DESCR_TAB_T, "   
lv_invalid_object  TYPE SHLP_DESCR_TAB_T, "   
lt_record_tab  TYPE STANDARD TABLE OF SEAHLPRES, "   
lv_callcontrol  TYPE DDSHF4CTRL. "   

  CALL FUNCTION 'F4_MATCHCODE_USER_EXIT'  "Bridge functions for the K-matchcodes
    EXPORTING
         FUNCNAME = lv_funcname
    CHANGING
         SHLP = lv_shlp
         CALLCONTROL = lv_callcontrol
    TABLES
         SHLP_TAB = lt_shlp_tab
         RECORD_TAB = lt_record_tab
    EXCEPTIONS
        INVALID_OBJECT = 1
. " F4_MATCHCODE_USER_EXIT




ABAP code using 7.40 inline data declarations to call FM F4_MATCHCODE_USER_EXIT

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.

 
DATA(ld_funcname) = ' '.
 
 
 
 
 


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!