SAP MPLAN_READ_MULTIPLE Function Module for NOTRANSL: Massenlesen von Wartungsplänen









MPLAN_READ_MULTIPLE is a standard mplan read multiple SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Massenlesen von Wartungsplänen 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 mplan read multiple FM, simply by entering the name MPLAN_READ_MULTIPLE into the relevant SAP transaction such as SE37 or SE38.

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



Function MPLAN_READ_MULTIPLE 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 'MPLAN_READ_MULTIPLE'"NOTRANSL: Massenlesen von Wartungsplänen
EXPORTING
* WITH_HISTORY = ABAP_TRUE "X= Read History and Maintenance Call Data
* MAP_CONFIRMATION_DATE = ABAP_TRUE "

TABLES
WARPL_READ = "
HEADERS = "Maintenance Plan Header Data
* RETURN = "Notifications
.



IMPORTING Parameters details for MPLAN_READ_MULTIPLE

WITH_HISTORY - X= Read History and Maintenance Call Data

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

MAP_CONFIRMATION_DATE -

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

TABLES Parameters details for MPLAN_READ_MULTIPLE

WARPL_READ -

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

HEADERS - Maintenance Plan Header Data

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

RETURN - Notifications

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for MPLAN_READ_MULTIPLE 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_warpl_read  TYPE STANDARD TABLE OF MPLAN_WARPL, "   
lv_with_history  TYPE BOOLEAN, "   ABAP_TRUE
lt_headers  TYPE STANDARD TABLE OF MPLAN_MPLA, "   
lv_map_confirmation_date  TYPE BOOLEAN, "   ABAP_TRUE
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'MPLAN_READ_MULTIPLE'  "NOTRANSL: Massenlesen von Wartungsplänen
    EXPORTING
         WITH_HISTORY = lv_with_history
         MAP_CONFIRMATION_DATE = lv_map_confirmation_date
    TABLES
         WARPL_READ = lt_warpl_read
         HEADERS = lt_headers
         RETURN = lt_return
. " MPLAN_READ_MULTIPLE




ABAP code using 7.40 inline data declarations to call FM MPLAN_READ_MULTIPLE

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_with_history) = ABAP_TRUE.
 
 
DATA(ld_map_confirmation_date) = ABAP_TRUE.
 
 


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!