SAP ISHMED_GET_MATCHING_CASE Function Module for









ISHMED_GET_MATCHING_CASE is a standard ishmed get matching case 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 ishmed get matching case FM, simply by entering the name ISHMED_GET_MATCHING_CASE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISHMED_GET_MATCHING_CASE 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 'ISHMED_GET_MATCHING_CASE'"
EXPORTING
I_EINRI = "
I_FALNR = "
* I_ROLLE = '4' "

TABLES
* T_NFAL = "
* T_NDOC = "

EXCEPTIONS
READ_ERROR = 1
.



IMPORTING Parameters details for ISHMED_GET_MATCHING_CASE

I_EINRI -

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

I_FALNR -

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

I_ROLLE -

Data type: TN15B-REFTI
Default: '4'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ISHMED_GET_MATCHING_CASE

T_NFAL -

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

T_NDOC -

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

EXCEPTIONS details

READ_ERROR -

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

Copy and paste ABAP code example for ISHMED_GET_MATCHING_CASE 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:
lt_t_nfal  TYPE STANDARD TABLE OF NFAL, "   
lv_i_einri  TYPE NFAL-EINRI, "   
lv_read_error  TYPE NFAL, "   
lt_t_ndoc  TYPE STANDARD TABLE OF NDOC, "   
lv_i_falnr  TYPE NFAL-FALNR, "   
lv_i_rolle  TYPE TN15B-REFTI. "   '4'

  CALL FUNCTION 'ISHMED_GET_MATCHING_CASE'  "
    EXPORTING
         I_EINRI = lv_i_einri
         I_FALNR = lv_i_falnr
         I_ROLLE = lv_i_rolle
    TABLES
         T_NFAL = lt_t_nfal
         T_NDOC = lt_t_ndoc
    EXCEPTIONS
        READ_ERROR = 1
. " ISHMED_GET_MATCHING_CASE




ABAP code using 7.40 inline data declarations to call FM ISHMED_GET_MATCHING_CASE

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 EINRI FROM NFAL INTO @DATA(ld_i_einri).
 
 
 
"SELECT single FALNR FROM NFAL INTO @DATA(ld_i_falnr).
 
"SELECT single REFTI FROM TN15B INTO @DATA(ld_i_rolle).
DATA(ld_i_rolle) = '4'.
 


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!