SAP ISHMED_MMINT_HANDLER Function Module for

Search SAP Function Modules

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

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

Function ISHMED_MMINT_HANDLER 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_MMINT_HANDLER'"
  EXPORTING
   EINRI =  "Institution
   ORGID =  "Organizational Unit
   LNRLS =  "
   SAVKZ =  "
   SELKZ =  "
   VARKZ =  "
   DEPTH =  "
*  I_TCODE =  "
*  I_TITLE = ' 1' "

 IMPORTING
   SAVEL =  "

TABLES
   INLEI =  "
   OMATV =  "
*  N1MATKL =  "
*  N1MTART =  "

EXCEPTIONS
   NO_OP_OE = 1    NO_INPUT = 2    NO_FOUND = 3 

.

IMPORTING Parameters details for ISHMED_MMINT_HANDLER

EINRI - Institution

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

ORGID - Organizational Unit

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

LNRLS -

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

SAVKZ -

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

SELKZ -

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

VARKZ -

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

DEPTH -

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

I_TCODE -

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

I_TITLE -

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

EXPORTING Parameters details for ISHMED_MMINT_HANDLER

SAVEL -

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

TABLES Parameters details for ISHMED_MMINT_HANDLER

INLEI -

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

OMATV -

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

N1MATKL -

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

N1MTART -

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

EXCEPTIONS details

NO_OP_OE -

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

NO_INPUT -

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

NO_FOUND -

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

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

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