Maintenance package in strategy :...

Petr S 155 posts since Dec 10, 2008

Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 9, 2009 5:22 AM
Hello experts,

When creating a maintenance package :

'Initial' (Lead Float) and 'subsequent' (Follow-up float) : what those fields are for ? SAP help does not help me
much. Explanations with examples would be great.

Thanks in advance

S@P PM 156 posts since Feb 25, 2009

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 9, 2009 5:47 AM
Hi
Initial ---A tool that specifies the number of days before the due date of a maintenance package that you can
start to perform the package.

Subsequent due dates are not moved for maintenance packages that are performed within the preliminary
buffer.

here you can specify the no. of days in term of earlier start of order without affecting the schdeuled due
date of the order

Subsequent---The number of days, specifying how long after the due date the execution of a maintenance
package can be completed.

The subsequent due dates are not moved for maintenance packages that are performed within the follow-up
buffer.

if u specify here no. of days in term of late start of order and it does not affect the standards dates*

Jitender

Petr S 155 posts since Dec 10, 2008

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 9, 2009 8:12 AM
hi Jitender

Generated by Jive on 2015-05-25+02:00

1
Maintenance package in strategy :...

Could you give me an example to see the effects of field "subsequent" if filled with 4 days for example?

Thanks,

Sundar Desai 631 posts since Dec 11, 2008

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 9, 2009 12:18 PM
Hi Pete,

Initial & subsequent floats/buffers are used to set the maintenance order's start & end dates which are
generated from plan.

Example:

If we have created a maint plan with strategy & same scheduling data for both with & without floats.
Then scheduling is done (suppose for todays date i.e. 9/7/2009) & one call (order) generated.
Then order dates willl change as per following:

for withouts floats:

Basic start date of maint order will be = 09/07/2009
Basic end date of maint order will be = 09/07/2009

for with floats i.e. 4 days initial & subsequent)

Basic start date of maint order will be = 05/07/2009 ....shifted by 4 days as initial buffer is 4 days
mentioned in strategy.
Basic end date of maint order will be = 13/07/2009....shifted by 4 days as subsequent buffer is 4 days
mentioned in strategy.

Sundar

Petr S 155 posts since Dec 10, 2008

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 10, 2009 6:28 AM
Hello Sundar,

Thanks for the explanations and the example.

However , i tried and it seems that the subsequent field (when filled) is not taking into account.
I set 2 days as 'initial' and 4 days as 'subsequent' ; my example was run with today's date (June 10).
My order generated has :
-start date : June 8
-end date : June 8 ....

Generated by Jive on 2015-05-25+02:00

2
Maintenance package in strategy :...

I checked on OSS note but found nothing.

Thanks again

Pete

Sundar Desai 631 posts since Dec 11, 2008

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 10, 2009 6:50 AM
Hi Pete,

I also have checked for the same and its working fine for me.

Can you please try once again.

First you change the strategy with required float values and then use it in new maintenance plan, then check &
let us know.

Sundar

Sundar Desai 631 posts since Dec 11, 2008

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 10, 2009 7:14 AM
Hi Pete,

One curious thing.

Dont get confused with initial & subsequent float of 1st strategy & 2nd strategy.

If you have strategies like 1M, 3M & 12M.

Then you are always entering initial & subsequent float values for each package i.e.1M, 3M & 12M.

In first row i.e. for 1M package you have to enter both floats. Here you enter 2 days as initial & 4 days as
subsequent float (In a single row) and check

Also remember that order generated must be for that package (here in eg. 1M) only.

Sundar

Petr S 155 posts since Dec 10, 2008

Generated by Jive on 2015-05-25+02:00

3
Maintenance package in strategy :...

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 10, 2009 8:19 AM
Hi Sundar,

In my first test : my strategy was 1M and 3M but i had only entered initial and subsequent values for 1M (and
not for 3M).

In the second test , i updated my strategy : now 1M and 3M have inital (2days) and subsequent (4days) values.
Then I created another maintenance plan :
-call horizon :100%
-scheduling horizon : 1year
-start of cycle : 10 May 2009 , so 1rst call will be for today (10 June)

With
-General task list : duration of (only one) operation is 10 hours
-Work center capacity :
Start 10:00:00
Finish 18:00:00
Length of breaks 01:00:00
Operating time 7.00

After scheduling , the order generated shows:

Bsc start => 08.06.2009
Basic fin. => 09.06.2009
SchedStart 08.06.2009 10:00
Sched.Fin. 09.06.2009 13:25

Basic finish date is still on 9 june...any ideas?

Thanks,

Sundar Desai 631 posts since Dec 11, 2008

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 10, 2009 8:59 AM
Hi Pete,

Try following and check.

Run the transaction OPU7.

Select the your maintenance plant & PM Order type which is being generated by maintenance plan.

And inside, in adjust scheduling screen area, change the adjust dates to " Do not adjust basic dates, dep.
reqmts. to operation dates".

Generated by Jive on 2015-05-25+02:00

4
Maintenance package in strategy :...

Sundar

Edited by: Sundar Desai on Jun 10, 2009 12:29 PM

Petr S 155 posts since Dec 10, 2008

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 10, 2009 9:41 AM
Hi Sundar,

You are right : OPU7 was the reason !

Thanks a lot

Regards,

Pete

Pete Atkin 8,301 posts since Dec 8, 2005

Re: Maintenance package in strategy : 'initial' and 'subsequent' fields Jun 9, 2009 10:49 AM
[SAP Help|http://help.sap.com/saphelp_erp60_sp/helpdata/EN/3c/abb35d413911d1893d0000e8323c4f/
frameset.htm]

Generated by Jive on 2015-05-25+02:00

5