SAP MI_PACKAGE_GETLIST Function Module for









MI_PACKAGE_GETLIST is a standard mi package getlist 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 mi package getlist FM, simply by entering the name MI_PACKAGE_GETLIST into the relevant SAP transaction such as SE37 or SE38.

Function Group: MI_PACKAGE_GEN
Program Name: SAPLMI_PACKAGE_GEN
Main Program: SAPLMI_PACKAGE_GEN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MI_PACKAGE_GETLIST 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 'MI_PACKAGE_GETLIST'"
  EXPORTING
   I_PACKAGENAME =  "
   I_MI_ENDDATE =  "
   I_MI_ENDTIME =  "
   I_CREATED_BY =  "
   I_DEVICENAME =  "
   I_PACKAGETYPE =  "
   I_DEVICEID =  "
   I_MIUSER =  "
   I_MIGROUP =  "
   I_MULTI_DEVINST =  "
   I_STATUS =  "
   I_MI_STARTDATE =  "
   I_MI_STARTTIME =  "

TABLES
   OT_PACKAGE_HEAD =  "
   OT_RETURN =  "
.



IMPORTING Parameters details for MI_PACKAGE_GETLIST

I_PACKAGENAME -

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

I_MI_ENDDATE -

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

I_MI_ENDTIME -

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

I_CREATED_BY -

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

I_DEVICENAME -

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

I_PACKAGETYPE -

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

I_DEVICEID -

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

I_MIUSER -

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

I_MIGROUP -

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

I_MULTI_DEVINST -

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

I_STATUS -

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

I_MI_STARTDATE -

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

I_MI_STARTTIME -

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

TABLES Parameters details for MI_PACKAGE_GETLIST

OT_PACKAGE_HEAD -

Data type: MIPACKAGE_HEAD_SE
Optional: No
Call by Reference: Yes

OT_RETURN -

Data type: BAPIRET2_T
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MI_PACKAGE_GETLIST 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_i_packagename  TYPE MI_PACKAGE_NAME, "   
lt_ot_package_head  TYPE STANDARD TABLE OF MIPACKAGE_HEAD_SE, "   
lv_i_mi_enddate  TYPE MI_END_DATE, "   
lv_i_mi_endtime  TYPE MI_END_TIME, "   
lv_i_created_by  TYPE UNAME, "   
lv_i_devicename  TYPE MEMGMT_DEVID_TXT, "   
lt_ot_return  TYPE STANDARD TABLE OF BAPIRET2_T, "   
lv_i_packagetype  TYPE MI_PACKAGE_TYPE, "   
lv_i_deviceid  TYPE MECONTGUID, "   
lv_i_miuser  TYPE UNAME, "   
lv_i_migroup  TYPE MI_GROUP, "   
lv_i_multi_devinst  TYPE MI_MULTIDEVINST, "   
lv_i_status  TYPE MI_PACKAGE_STATUS, "   
lv_i_mi_startdate  TYPE MI_START_DATE, "   
lv_i_mi_starttime  TYPE MI_START_TIME. "   

  CALL FUNCTION 'MI_PACKAGE_GETLIST'  "
    EXPORTING
         I_PACKAGENAME = lv_i_packagename
         I_MI_ENDDATE = lv_i_mi_enddate
         I_MI_ENDTIME = lv_i_mi_endtime
         I_CREATED_BY = lv_i_created_by
         I_DEVICENAME = lv_i_devicename
         I_PACKAGETYPE = lv_i_packagetype
         I_DEVICEID = lv_i_deviceid
         I_MIUSER = lv_i_miuser
         I_MIGROUP = lv_i_migroup
         I_MULTI_DEVINST = lv_i_multi_devinst
         I_STATUS = lv_i_status
         I_MI_STARTDATE = lv_i_mi_startdate
         I_MI_STARTTIME = lv_i_mi_starttime
    TABLES
         OT_PACKAGE_HEAD = lt_ot_package_head
         OT_RETURN = lt_ot_return
. " MI_PACKAGE_GETLIST




ABAP code using 7.40 inline data declarations to call FM MI_PACKAGE_GETLIST

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



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!