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

Similar Messages

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

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,

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

How to look for New start Called call for a Maintenance plan

Hi,
I need to find out all calls for a maintenance plan of scheduling type- 'New Start' and Status- 'Called'. How to find this using tables.
For 'New Start' scheduling type probably table field and value is MHIS-TERMA = 'N'. There are different statuse in this table but I am not able to identify the status 'called'. Also what is the field MHIS-ZAEHL(Maintenance package number) for?
Thanks,
Vimal

Taken from the standard IP10 program:
* possible status combinations
* TSABR - Scheduling status: planned date called
* TSVBT - Scheduling status: call outstanding
* TSENQ - Scheduling status: call horizon not reached
* TSENM - Scheduling status: stopped manually
* TSTAT - Sceduling status
* TSABR   TSVBT   TSENQ   TSENM   TSTAT
*   X       -       -       -       A     called with order
*   X       -       -       -       -     called without order
*   -       X       X       -       -     on hold (TSENQ), due (TSVBT)
*   -       X       X       -       F     on hold, due and fixed
*   X       -       -       -       X     skipped
*   -       X       X       X       -     blocked
*   -       X       X       X       F     blocked
*   X       -       -       -       -     LRMDT <> 0, completed

How to set start of cycle/next planned date at the Maintenance Item level??

Hi All,
We are uploading a bulk of Strategy Maintenance Plans into the system. Each plan has multiple maintenance items and each maintenance item in a plan having different next due dates. Now if we set the Start of cycle at the Maintenance Plan level, then the next due dates of the maintenance items in that plan would be calculated on the basis on Start of Cycle (Common for all) and frequency as set in MPackages in an item Task list. Since each Maintenance item may have different Frequency and next due date, generating a call object while scheduling the plan correctly to satisfy at the Maintenance item level is not seeming possible.
Can someone please suggest as to how do I set the Start of cycle or say Next Planned Date or Last Scheduled date at the Maintenance Item level either through configuration or programmatically.We are working on an SAP 4.6C version.It is urgent!!!

hi
i think specifying start of the cycle for each maintenance level is not possible ,since start of the cycle refers to maintenance plan only .
for SAP standard kindly refer the following [link|http://help.sap.com/saphelp_46c/helpdata/en/94/43a968abc011d395bd00a0c93029cf/content.htm]
it is better to create one maintenance item per maintenance plan,if you want to control each maintenance item independently
regards
thyagarajan

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

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

SNP Planned order start and end dates are not calculated correctly

Hello SNP Guru's
The SNP planned orders generated after the Heuristics run, have a start and end date based on the Activity Duration (Fixed), while the resource consumption is based on the Bucket Consumption (Variable), which is correct.
The Activity Duration (Fixed) is based on the BOM Base Quantity. So if the Activity Duration = 1 day, and if the order quantity is more than a day, the start and end dates, still shows as 1 day. So no matter what is the order quantity, the start and end dates is always = 1 day.
Does anyone have any experience in implementing any code to change the start and end dates on SNP Planned Order?
Seems like it should work as standard.
Am i missing something?
Thanks,
Mangesh

Dear Mangesh,
SNP is a infinite planning tool. If you have defined fixed duration to be 1 DAY in the activity, no matter how many quantity you input for your planned order, the order will last for one day. If the resourced is overloaded, you then run capacity levelling to
banlance the capacity. What your expected beahavior happens in PPDS planning.
Claire

FIX: Change your Billing Cycle and Due Date!

There are many people angry about the change in billing due dates that have been set by AT&T recently. There is a way to get your due date back to where you want it but does require a little work on your part. NOTE: I am not an AT&T Employee, this is just advice from someone doing a little research! How the change works:First you will need to contact AT&T customer support (as this is just a customer to customer support forum so nobody here can make changes to your account). Let them know you want to change your billing cycle and due date. First month - you must complete your current billing cycleSecond month - you will have a prorated "short" cycle anywhere from 0-29 daysThird month - you will start with the billing cycle on the new date you select. There are a couple of other requirements below just so you are completely informed when talking to AT&T support.
Billing Cycle Change Requirements:
Changing your billing cycle is NOT an option in all service areas so contact support at 800-331-0500 to find out if this option is available in your service area.
Your billing cycle cannot be changed during the five days before or after the close of your current cycle. Your billing cycle cannot be changed if your account is in a delinquent status, or if the account will fall delinquent before the requested change date. If you have a payment arrangement set up, the payment arrangement must be made before the billing cycle is changed. If you have Autopay, you may see two Autopay drafts in one month due to the billing cycle change. Please keep in mind that when a billing cycle is changed you will see prorated charges to get all of the billing back on track with the new dates. Understanding that this does create an inconvenience for many people for the first 2 months you will be where you need to be after and back on track. If anyone has anything to add please do so and I will update my post.

Hi there
This is a great guide that will be very helpful to any of our customers who wish to change their bill cycle dates! I’d just like to thank you for posting this and add some further expectations.
The balance on the prorated second invoice shows as Past Due on the customer's third invoice, even if it is not. The cycle change process does not impact their account status and corrects itself on subsequent bills. With regards to prorated charges, the customer is provided a video bill with their next statement to help explain the charges.
Thanks!
Charise

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

How to change the main work center and work center of each operation when generating work order by maintenance plan

Dear experts,
I face a problem that system get main work center from equipment master data as a default main work center in maintenance plan when creating maintenance plan. however, if main work center in equipment is changed later, the change will not synchronize to related maintenance plan. if work order is generated from maintenance plan, main work order in order is defaulted from maintenance plan instead of updated work center in equipment.
another problem is that, for those orders generated by maintenance plan, the work centers in operations is defaulted from task list in maintenance plan. in most case, work center in task list is dummy. Actually the work is done by work center in equipment master data.
My expectation is how to auto replace the main work center and work center of operations in work order with the one in equipment master data if order is generated by maintenance plan? is there any standard configuration or enhancement/BADi that can help with this requirement?
thanks！
Wesley

Wesley,
Sorry - development is the only way.
Another option is to create a batch program that runs before your IP30 run(s) and updates any maintenance items and task lists with the correct work centres.
PeteA

Offset and Start in Cycle

How do offset and start in cycle differ? What is basic difference between them?
what is the necessity of having both function in SAP PM?

Maintenance package offset
The offset of a maintenance package or maintenance cycle determines the
    time after which a maintenance package first becomes due.
You must enter an offset when the first time a maintenance package is to be performed does not correspond with the cycle length.
In the case of multiple counter plans or maintenance cyles,you can use the offset to perform a maintenanc pckage once only, by maintaining the offset
Example
Cycle length of maintenance package:every two years
First time due (offset): after three years
Logically we can say
Start of cycle is Start date of Maintenance plan,
Offset is time after which a maintenance package first becomes due.
Logically you can get detailed help be pressing F1 at the Offset field.Logic behind my answer was F1.
Reward points if it helps!!

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.

Change start of cycle date in maintenance plan

Similar Messages

Maybe you are looking for