Start cycle date in maintenance plan

Hello Every one,
In my project i have uploaded all the plans in production server with start cycle date. Now when i am going in change mode i cant see the start cycle date even thoug i can see the scheduling overview in plan as correct date but i m not able to see the start cycle date. Kindly help me in this.
Regards
Abhishek Sinha

Hi,
In Maintenance Plan, once you have mentioned the start of the cycle. Again it wont appear in Change Maintenance Plan, you will have to restart or reschedule the Plan.
Regards,

Similar Messages

  • Change start of cycle date in maintenance plan

    Dear Experts,
    We would like to change start of cycle date in maintenance plan. Iwe have rescheduled the plan but the start of cycle date remains the same.
    could you please confirm, whether it can be changed. The requirement is because of some Mt plan created with future start date in production (Year-2020) and we want to correct the same.
    Thanks

    Don,
    To determine the next maintenance call date you need to tell the system when the last maintenance call occured
    Example:
    You want the next call date on the 1 June based on a six month cycle. Therefore the last maintenance date would have been 1 January (assuming key date scheduling).
    In your case you need to RESTART your single-cycle plan on the 1 January and the system then calculates the next maintenance calls.
    PeteA

  • Mass Change of Start Cycle Date of Plans

    Hi All,
    Does any know of any standard Program or Transaction available for changing the Start Cycle date for Single Cycle Plans in Mass.
    Regards,
    Manish

    Hi Manish,
    Theres a standard T-Code available: MCH01.
    Please refer to [Changing Maintenance Plans With the Mass Maintenance Function|http://help.sap.com/saphelp_dimp50/helpdata/en/95/83833cb67a8955e10000000a114084/frameset.htm].
    Thanks,
    Amit.
    Edited by: Amit Saxena on Nov 5, 2008 2:27 PM

  • Mass Re-start / Re-schedule of Maintenance Plan

    Dear Sirs,
    I have created a BDC which runs in the background at the end of every month.
    This BDC creates a Strategy Maintenance Plan (IP42), the moment a new equipment is installed in the system & it automatically gets scheduled (IP10) as per the installed date.
    After a while we came to know that the BDC was not taking the proper start cycle date & hence the Maintenance Plans which were created were scheduled on the wrong date. We have already solved the problem & have corrected the coding.
    But we need to re-schedule all the earlier wrongly scheduled maintenance plans & delete the previous history.
    When we tried to re-start the cycle manually through IP10 it was allowing us to delete the earlier records as well as to re-start the cycle.
    But as there were thousands of Maintenance plan to be re-started, we planned to create a LSMW or BDC to do the same.
    But while running the LSMW / BDC recording we are not able to delete the earlier records & those are showing as skipped.
    We want the earlier records to be deleted & to re-start the new cycle.
    Can you please tell me something that can be done through any std transaction like IP30 etc.
    Regards,
    YVK.
    Edited by: Yogesh Khamkar on Mar 5, 2010 1:13 PM

    Hi Goswami,
    I am facing the same problem while creating recording for restarting scheduling maintenance plan in IP10 with  LSMW , I am not getting the option screen as given below to delete or skip the call
    as result I am not getting any field in  " Maintain Field mapping and conversion rule"
    Please help me for same. As I have scheduled 1000s of plan one month ago but client need to reshedule all with new start of cycle.
    regards,
    Raj

  • Change/restart start of cycle for strategy maintenance plan MPLA- STADT

    Dear experts,
    is it possible to change the start of cycle date in strategy maintenance plan (MPLA- STADT).
    The start of cycle was entered incorrectly into the strategy maintenance plan (IP42)
    Maint. plan was already started
    ...and called: Service orders are already created
    The existing maint. plan should be used with a new cycle start date.
    By using u201Crestartu201D in IP10, a new start of cycle date is entered and the orders are called correctly.
    But the cycle start date is not updated in the data base: MPLA- STADT
    Why?
    Regards,
    Philipp

    Dear all,
    I opened a OSS message. SAP replied that this is not covered by SAP standard. so system works as designed.
    SAP:
    The described behaviour is the SAP/R3 standard and works as designed.
    IP16 only shows this field if it's updated in MPLA-STADT.
    The 'Cycle start' resulting of scheduling (IP10) is kept in the table
    MHIS (field STADT).
    Transaction IP16 takes data from MPLA and does not read the entries
    in MHIS. The only value that can therefore be shown as 'cycle start'
    is the original value as recorded in MPLA.
    Well, this explains why system behaves like it does.
    But in my eyes this is not the correct system behavior.
    If a maint. plan is restarted, future calls will be calculated based on
    the new cycle date - what is ok.
    But IP16 indicates the old cycle date!
    In my eyes this is not correct because the list will show an incorrect
    cycle date.
    I was told to take a look at note 11:
    Sehr geehrte Kundin, sehr geehrter Kunde,
    die von Ihnen benötigte Funktionalität ist leider nicht im SAP-Standardsystem enthalten.
    Wenn Sie mit SAP an zukünftiger Produktfunktionalität arbeiten möchten, empfehlen wir Ihnen, dies entweder über die Mitarbeit in einer SAP Anwendergruppe oder über die Mitarbeit in einer der SAP Communities of Innovation zu tun. Eine Liste aller SAP Anwendergruppen finden Sie unter http://www.sapusergroups.org.
    Eine Beschreibung der SAP Communities of Innovation können Sie unter http://www.sap.com/ecosystem/communities/index.epx einsehen.
    Alternativ können Sie spezielle, von Ihnen gewünschte Funktionalität von SAP Custom Development entwickeln lassen (http://www.sap.com/services/bysubject/customdev).
    Weiterführende Informationen finden Sie unter http://service.sap.com/rollin.
    Mit freundlichen Grüßen
    Ihr SAP Active Global Support
    How can I trigger such an improvement?
    Regards,
    Philipp

  • Change or Add Cycles in a Maintenance Plan (IP02)

    good afternoon all,
    we have an issue with a number of maintenance plans that were setup as 1 year cycles, and now we want to run them as monthly. Is there a way to either change the yearly cycle to monthly, or add a new monthly cycle?
    SAP ECC6
    Release 731 sp level 0007.
    Thanks.

    Greetings Santosh,
    You are correct, the key word here is "approximately", as the Cycle Modification Factor has only two decimals of precision, you will need to input 0,08 to reflect the appropriate factor of 1/12=0,08(3) - so that will mean your cycle is 360*0,08=28,8 and not 30 days, which is why I did not propose this route. But if it's not an issue, then yes, that's another way to do this
    EDIT: Which reminds me, after switching the cycle to monthly, consider if you require Time or Key Date scheduling on the Maintenance Plan scheduling parameters, as for SAP 1 Month = 30 Days with the former, but with the latter the scheduling is always for the same day of each month.

  • Start of cycle date is not taking while scheduling

    Hi
    I have created a maintainance plan with scheduling indicator TIME and scheduling period 365 days . I am giving start of cycle date as 04-02-2011 but while scheduling the plan it is taking 19-02-2011 as first plan date . my maintainance plan cycle is 15 days.
    I want that date as 04-02-2011 . how can I get that.
    Regards
    Kumar

    The system is working fine. Once you decide the start cycle date then first plan /Order will come only after the cycle duration from the start cycle date. You can put 15 day before date from 4-2-2011. then you will get first call on desired date.
    Raj

  • Work order dates calculated by priority when created by maintenance plan

    Can anyone tell me how to get the dates on a work order created via a maintenance plan to be calculated from the priority?  I know how to get the notification dates to calculate from the priority when created via a maintenance plan but I can't seem to get the order dates to do the same. 
    Any info would be most appreciated.

    Check these links
    Influence Order basic start/end dates from maintenance plan
    Scheduled Maintenance basic start and finish date

  • Table for maintenance plan and maintenance cycle and Unit

    Hello,
    I need to know the table where the values are stored for maintenance plan, maintenance cycle and Unit.
    I know that we can get the maintenance cycle and unit from MMPT table.
    Question 1
    If the maintenance plan has only a single cycle then the data is stored in above table MMPT, but if a maintenance plan has mutiple cycles like 1 maintenance plan has maintenance cycle as 364 Days and 1092 days then the data is not stored in MMPt table.
    Question 2
    Requirement is I need to develop a report where in I need maintenance order, maintenance plan and the relevant maintenance cycle and unit. Supose an maintenance order is created for the above maintenance plan which has 2 maintenance cycle how can I identify for which maintenance cycle the order is created.
    Regards,
    Narendra

    Hi,
    Please review PM tables
    PM/SM/SD Tables
    MPOS                       Maintenance Items
    AFAB     Network - Relationships
    PLKO     Task list
    PLAS
    AFFH     Operations
    PRT assignment data for the work order
    AFFL     Work order sequence
    AFFT     Order process instructions
    AFFV     Order process instruction values
    AFFW     Goods movements with errors from confirmations
    AFIH     Maintenance order header
    AFKO     Order header data PP orders
    AFPO     Order item
    AFRC     Table of planned changes to conf.: Automatic goods receipt
    AFRD     Default values for collective confirmation
    AFRH     Header information for confirmation pool
    AFRU     Order completion confirmations
    AFRV     Pool of confirmations
    AFVC     Operation within an order
    AFVU     DB structure of the user fields of the operation
    AFVV     DB structure of the quantities/dates/values in the operation
    MPOS     Maintenance ITEM
    AFWI     Subsequently posted goods movements for confirmations
    AUFK     Order master data
    AUFM     Goods movement for order
    MPLA     Maintenance Plans
    BGMK     Master warranty header
    BGMP     Master warranty item
    BGMS     Text item master warranty
    BGMT     Master warranty text
    BGMZ     Warranty counter information
    CRHD     Work Center Header
    CRTX     Text for the Work Center or Production Resource/Tool
    EQKT     Equipment short texts
    EQST     Equipment link to BOM
    EQUI     Equipment master data
    EQUZ     Equipment time segment
    HIKO     Order master data history
    IFLO     Functional Location (View)
    IFLOT     Functional location (TABLE)
    IFLOTX     Functional location: Short texts
    IHGNS     Plant maintenance permit segment
    IHPA     Plant Maintenance: Partners
    IHSG     Object-related permits in Plant Maintenance
    ILOA     PM object location and account assignment
    IMPTT     Measuring point (table)
    IMRG     Measurement document
    KAKO     Capacity Header Segment
    KONP     Conditions (Item)
    KONV     Conditions (Procedure Data)
    OBJK     Plant Maintenance Object List
    QMEL     Quality notification
    QMFE     Quality notification - items
    QMIH     Quality message - maintenance data excerpt
    QMMA     Quality notification - activities
    QMSM     Notification - Tasks
    QMUR     Quality notification - causes
    STPOA     Name is does not have an A at the end; BOM items
    T001     Company Codes
    T001L     Storage Locations
    T001W     Plants
    T077D     Customer account groups
    T003O     Order Types
    T352R     Maintenance revisions
    T353I_T     Maintenance activity type description
    T356     Priorities
    T357G     Permits
    T357G_T     Table 357G texts
    T370A     Activity category for PM lists
    TINCT     Customers: Incoterms: Texts
    TVKO     Organizational Unit: Sales Organizations
    TVKOS     Organizational Unit: Divisions per Sales Organization
    TVKOV     Org. Unit: Distribution Channels per Sales Organization
    TVTA     Organizational Unit: Sales Area(s)
    VIAUFKST     Order selection view
    MMPT Cycle detail
    Regards
    Carlos

  • Problem regarding scheduling of maintenance plan

    Dear Sap Gurus,
    I am facing the problem during the scheduling of maintenancepan thruough IP10 follwing error is coming
    "Planned date for maintenance plan 124 was scheduled for 00.00.0000"
    Planned date for maintenance plan 124 was scheduled for 00.00.0000
    Message no. IP889
    Diagnosis
    During scheduling of the maintenance plan, the planned date was set to 00.00.0000.
    This error can occur, if, for example, the cycle for the planned schedule is too big (offset) means that the planned date is actually after the 31.12.9999.
    Procedure
    Check the master data of the maintenance plan to ensure that no date is calculated after the 31.12.9999.
    If necessary, check the counters used and the annual performance.
    I explore all the things in SPRO also also check the setting parameter for the plan but i didnt get any breakthrough for my above problem.Plz guide me whats the exactly problem with scheduling of of maintenance plan.
    points are sure
    Regards
    Rakesh

    Summary
    Symptom:
    In the scheduling of a multiple counter plan, the system
    1. generates message IP889 "Planned date for maintenance plan &1 was scheduled for 00.00.0000" or
    2. terminates with CONVT_NO_NUMBER.
    Other terms
    Scheduling, IP10, IP30, maintenance plan scheduling, maintenance plan, multiple counter, BADI IPRM_MCP_SCHE_CHANGE, CONVT_NO_NUMBER, SAPLIWP2, LIWP2F19, MCP_PREPARE_RESCH_CALLED_CALLS, LV_ABNUM
    Reason and Prerequisites
    This problem is caused by a program error.
    Solution:
    Implement the attached source code corrections.

  • Restarting maintenance plan after closing notification

    Hello all,
    We want to implement scheduled maintenance plans based on time criteria. That is, for example, that every 2 months an equipment should be revised by a technician.
    But sometimes this equipment is visited by a technician, out of the scheduled date, creating a notification and closing it, in that case the maintenance plan shoud be restarted after closing notification of that equipment,
    I guess we could achive it using some notification EXIT , for example EXIT_SAPMIWO0_020, but we do not know if there is a function module or anything to restart the plan,
    any help would be really apreciated,
    Thank you,
    Xavi

    Hello all,
    thank you very much by your answers,
    The problem is that we need in some cases to restart the cycle of the maintenance plan.
    Let's say we have scheduled notifications every 3 months in an equipment located 40 Km from the factory, for example a fridger. The BackOffice receives an alarm telling that the equipment does not work at all, and a technician goes there in order to solve the problem.
    The tech solves the issue, and he decides to make a sanitization of the equipment, which is out of the scheduled plan (for example it was supposed to be done in 20 days, but the technician decides to do it now, in order to spare the Km)
    The decision is right, but the plan says that in 20 days the tech should go again to the equipment, which is false, he should be there in 3 months, that is, restart the cycle.
    Anyone knows a function module the restart the cycle, used from an Exit of notifications (when closing the sanitizacion done by the tech?)
    thank you,

  • Workflow for maintenance plan

    Hi .
    I need to start/ deactivate / stop a maintenance plan depending upon few conditions.
    Is there any workflow for above mentioned scenario

    Hi,
       You can give the conditions in your workflow bulider. Check the link for more details.
    Work Flow Triggering when purchase order is released
    Cherck the posts of Raja Sekhar and Rob Dielemans.
    Thank you,
    Ramu N.
    Message was edited by: Ramu Nemurgommula
    Message was edited by: Ramu Nemurgommula

  • Difference in Maintenance Plan date to Order basic start date

    If i creat a strategy plan and schedule, i am getting difference in PLan date in Maint plan to Basic start date. What is making this difference. How to overcome this. I need Order start date same as PLan date.
    Plz help me frnds.
    Guruprasad

    hi
    can you explain in details with your maintenance plan with the dates.Normally your call date and plan date will be different becase of call horizon ,but the order basic start date and plan date will be equal only
    kindly revert back
    regards
    thyagarajan
    your order basic date will be when you have maintenance call is generated.kindly check
    Edited by: thyagarajan krishnamurthy on Feb 25, 2009 9:46 AM

  • How to compute Maintenance Plan's Plan Date

    Dear Gurus,
    I would like to request help from you.  I have a problem wherein I would like to know how is the Maintenance Plan's Plan Date is computed.
    Below is the parameters of the Maintenance Plan:
    cycle = 1500
    offset = 1478
    annual estimate = 5070
    first meas reading = 22.5
    Start of cycle is = Jun 16, 2011
    The plan date computed is = Sept 7, 2011
    Please let me know if there are other information needed.
    I hope you can share your knowledge on my problem.  Thank you.

    Hi,
        Please note that for Plant date calculate in Counter Based Plans system takes the below into preference for calculation :-
    1. Start of Counter reading value
    2. Date of Last counter reading udpate ..
    If you maintain offset then system first plans the offset then starts the cycle
    If ur annual estimate is  5070  , if scheduling is done by time then daily activity is 5070/365 = 13.89  round to 14
    Now if your start of counter reading value is 0KM
    And if your date of last counter reading is :- 2/3/2012
    Then your first planned date would be based on the offset :- 1478 -22.5 = 1455.5 /daily activity =1455.5/14 =104days
    So counting 104days from 2/3/2012 you would getting your First Plan date ..
    If u put call horizon as 100% then it will be in HOLD status
    regards
    giri

  • Maintenance plan package change resulting in incorrect call dates

    When we change a maintenance package on an existing maintenance plan to a package whose frequency is not an exact multiple of the previous package (for example, changing from a 6M 180-day package to a 1Y 365-day package) and then restart the plan, the call horizon of the plan seems to be ignored and the new call dates are always a day or so before the plan date regardles
    Why is the call horizon being ignored in this situation?

    Hello
    Please check the Option Start in Cycle while scheduling the Plan.
    Also refer the below thread too
    http://scn.sap.com/thread/1788240
    Br
    Rakesh
    Message was edited by: RAKESH MANE

Maybe you are looking for