SAP IM_READ_REQUEST_MULTI Function Module for









IM_READ_REQUEST_MULTI is a standard im read request multi 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 im read request multi FM, simply by entering the name IM_READ_REQUEST_MULTI into the relevant SAP transaction such as SE37 or SE38.

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



Function IM_READ_REQUEST_MULTI 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 'IM_READ_REQUEST_MULTI'"
TABLES
*  T_IMAV =  "
*  T_IMAKPU =  "
*  T_IMAKA =  "
*  T_IMAKPS =  "
*  T_IMAKPW =  "
*  T_IMAKZS =  "
*  T_IMAVT =  "
*  T_IMAKT =  "
*  T_IMAVZ =  "
*  T_IMAKPA =  "
*  T_IMAK =  "
   T_IMAVZ_INPUT =  "
*  T_IMAKZ =  "
*  T_IMAKPI =  "

EXCEPTIONS
   NO_REQUEST_NUMBER = 1    WRONG_APP_REQUEST = 2
.



TABLES Parameters details for IM_READ_REQUEST_MULTI

T_IMAV -

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

T_IMAKPU -

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

T_IMAKA -

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

T_IMAKPS -

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

T_IMAKPW -

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

T_IMAKZS -

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

T_IMAVT -

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

T_IMAKT -

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

T_IMAVZ -

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

T_IMAKPA -

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

T_IMAK -

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

T_IMAVZ_INPUT -

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

T_IMAKZ -

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

T_IMAKPI -

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

EXCEPTIONS details

NO_REQUEST_NUMBER -

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

WRONG_APP_REQUEST -

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

Copy and paste ABAP code example for IM_READ_REQUEST_MULTI 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_imav  TYPE STANDARD TABLE OF RIMAV, "   
lv_no_request_number  TYPE RIMAV, "   
lt_t_imakpu  TYPE STANDARD TABLE OF RIMAKPU, "   
lt_t_imaka  TYPE STANDARD TABLE OF RIMAKA, "   
lt_t_imakps  TYPE STANDARD TABLE OF RIMAKPS, "   
lt_t_imakpw  TYPE STANDARD TABLE OF RIMAKPW, "   
lt_t_imakzs  TYPE STANDARD TABLE OF RIMAKZS, "   
lt_t_imavt  TYPE STANDARD TABLE OF RIMAVT, "   
lv_wrong_app_request  TYPE RIMAVT, "   
lt_t_imakt  TYPE STANDARD TABLE OF RIMAKT, "   
lt_t_imavz  TYPE STANDARD TABLE OF RIMAVZ, "   
lt_t_imakpa  TYPE STANDARD TABLE OF RIMAKPA, "   
lt_t_imak  TYPE STANDARD TABLE OF RIMAK, "   
lt_t_imavz_input  TYPE STANDARD TABLE OF RIMAVZ, "   
lt_t_imakz  TYPE STANDARD TABLE OF RIMAKZ, "   
lt_t_imakpi  TYPE STANDARD TABLE OF RIMAKPI. "   

  CALL FUNCTION 'IM_READ_REQUEST_MULTI'  "
    TABLES
         T_IMAV = lt_t_imav
         T_IMAKPU = lt_t_imakpu
         T_IMAKA = lt_t_imaka
         T_IMAKPS = lt_t_imakps
         T_IMAKPW = lt_t_imakpw
         T_IMAKZS = lt_t_imakzs
         T_IMAVT = lt_t_imavt
         T_IMAKT = lt_t_imakt
         T_IMAVZ = lt_t_imavz
         T_IMAKPA = lt_t_imakpa
         T_IMAK = lt_t_imak
         T_IMAVZ_INPUT = lt_t_imavz_input
         T_IMAKZ = lt_t_imakz
         T_IMAKPI = lt_t_imakpi
    EXCEPTIONS
        NO_REQUEST_NUMBER = 1
        WRONG_APP_REQUEST = 2
. " IM_READ_REQUEST_MULTI




ABAP code using 7.40 inline data declarations to call FM IM_READ_REQUEST_MULTI

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!