SAP MPLAN_START_CYCLE Function Module for Maintenance Plan Schedluing - Start in Cycle









MPLAN_START_CYCLE is a standard mplan start cycle 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 Schedluing - Start in Cycle 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 start cycle FM, simply by entering the name MPLAN_START_CYCLE 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_START_CYCLE 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_START_CYCLE'"Maintenance Plan Schedluing - Start in Cycle
  EXPORTING
   WARPL =  "Maintenance Plan
*  NO_COMMIT = ' ' "
*  LRMDT =  "Date of Last Completion in Maintenance Plan
*  CONF_TIME =  "Completion Time of Call
*  ZYKLOFFSET =  "Offset with Start in Cycle
*  ZYKLUNIT =  "Unit for the Performance of Maintenance Tasks
*  RZAEH =  "Completion Counter Reading
*  CYCLESEQIND =  "Cycle Set Sequence
*  SETREPEATIND =  "Repeat Factor for Cycle Set Sequence
*  KEEP =  "Keep Calls on Hold (KEEP=X) or Delete Calls on Hold (KEEP=' ') Default Value

 IMPORTING
   RETURN =  "Table with BAPI Return Information
.



IMPORTING Parameters details for MPLAN_START_CYCLE

WARPL - Maintenance Plan

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

NO_COMMIT -

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

LRMDT - Date of Last Completion in Maintenance Plan

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

CONF_TIME - Completion Time of Call

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

ZYKLOFFSET - Offset with Start in Cycle

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

ZYKLUNIT - Unit for the Performance of Maintenance Tasks

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

RZAEH - Completion Counter Reading

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

CYCLESEQIND - Cycle Set Sequence

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

SETREPEATIND - Repeat Factor for Cycle Set Sequence

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

KEEP - Keep Calls on Hold (KEEP=X) or Delete Calls on Hold (KEEP=' ') Default Value

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

EXPORTING Parameters details for MPLAN_START_CYCLE

RETURN - Table with BAPI Return Information

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

Copy and paste ABAP code example for MPLAN_START_CYCLE 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_no_commit  TYPE XFLAG, "   ' '
lv_lrmdt  TYPE LRMDT, "   
lv_conf_time  TYPE CONFIRMATION_TIME, "   
lv_zykloffset  TYPE WOFFSET, "   
lv_zyklunit  TYPE DZEIEH, "   
lv_rzaeh  TYPE RZAEHC, "   
lv_cycleseqind  TYPE CYCLESETSEQ, "   
lv_setrepeatind  TYPE IND_SET_REPEAT, "   
lv_keep  TYPE BOOLEAN. "   

  CALL FUNCTION 'MPLAN_START_CYCLE'  "Maintenance Plan Schedluing - Start in Cycle
    EXPORTING
         WARPL = lv_warpl
         NO_COMMIT = lv_no_commit
         LRMDT = lv_lrmdt
         CONF_TIME = lv_conf_time
         ZYKLOFFSET = lv_zykloffset
         ZYKLUNIT = lv_zyklunit
         RZAEH = lv_rzaeh
         CYCLESEQIND = lv_cycleseqind
         SETREPEATIND = lv_setrepeatind
         KEEP = lv_keep
    IMPORTING
         RETURN = lv_return
. " MPLAN_START_CYCLE




ABAP code using 7.40 inline data declarations to call FM MPLAN_START_CYCLE

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



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!