SAP MPLAN_RELEASE_CALL Function Module for Maintenance Plan Scheduling - Release Call
MPLAN_RELEASE_CALL is a standard mplan release call SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Maintenance Plan Scheduling - Release Call 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 release call FM, simply by entering the name MPLAN_RELEASE_CALL 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_RELEASE_CALL 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_RELEASE_CALL'"Maintenance Plan Scheduling - Release Call.
EXPORTING
WARPL = "Maintenance Plan
ABNUM = "Maintenance Plan Call Number
* NO_COMMIT = ' ' "
IMPORTING
RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for MPLAN_RELEASE_CALL
WARPL - Maintenance Plan
Data type: WARPLOptional: No
Call by Reference: No ( called with pass by value option)
ABNUM - Maintenance Plan Call Number
Data type: ABNUMOptional: No
Call by Reference: No ( called with pass by value option)
NO_COMMIT -
Data type: XFLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MPLAN_RELEASE_CALL
RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MPLAN_RELEASE_CALL 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_warpl | TYPE WARPL, " | |||
| lv_return | TYPE BAPIRETTAB, " | |||
| lv_abnum | TYPE ABNUM, " | |||
| lv_no_commit | TYPE XFLAG. " ' ' |
|   CALL FUNCTION 'MPLAN_RELEASE_CALL' "Maintenance Plan Scheduling - Release Call |
| EXPORTING | ||
| WARPL | = lv_warpl | |
| ABNUM | = lv_abnum | |
| NO_COMMIT | = lv_no_commit | |
| IMPORTING | ||
| RETURN | = lv_return | |
| . " MPLAN_RELEASE_CALL | ||
ABAP code using 7.40 inline data declarations to call FM MPLAN_RELEASE_CALL
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_no_commit) | = ' '. | |||
Search for further information about these or an SAP related objects