Call object generation issue

[Former Member]

Hi,

I am having issue regarding call object generation by the system based on call horizon. details are as below:

maintenance plan: strategy based with two maintenance packages for 7 days and 1 month

Scheduling Parameters: call horizon= 60%; Scheduling period= 365 days; scheduling indicator= Time; Cycle modification factor=1

When I schedule this plan using IP10, and opted option as 'Start' to start the scheduling. Cycle start date= 14.01.2013

My call horizon working for 7 Days maintenance package, i.e. system generating the next call object after 4 days (60% of 7 days) of last planned date. But I wanted the same thing to happen with my monthly package as well.

How can I ensure the same call horizon to get applied on my all maintenance packages?

Please refer the attached screen shot and suggest as how to get the call objects on required dates.

Thanks.

[sebastian_lenartowicz · Accepted solution]

Greetings Lucky,

Do I understand correctly that you want the monthly package orders to be called at 12 days before due date (apply the 60% horizon to the 30 day cycle)?

TMM SAP determines the call horizon based off the shortest cycle in a Maintenance Plan. If you should want monthly Orders to be called at the horizon you wish, perhaps it is an option for you to schedule two separate concurrent Maintenance Plans.

BTW How is your strategy set up, what unit do you use - days? weeks?

[Former Member · Accepted solution]

Sebastian,

Thanks for your reply. Yes, You got it correct, but what do you mean by 'two concurrent maintenance plans' ?

In my strategy, I have used unit as 'Days'.

[sebastian_lenartowicz · Accepted solution]

Do you need this to be a Strategy plan?

One option I see is to create two identical single-cycle plans, one with a cycle of 7 days and other with 30 days. You can then assign the Task Lists with the appropriate operations, and schedule those plans from the same Start of Cycle. In that case, you would get the call horizon you wanted. But this option does not allow you to use a Strategy or Package Hierarchy.

[Former Member · Accepted solution]

Ya, that is what I was afraid of . anyways, that is one of good alternate to strategy based solution.

But, I was wondering if same thing could be achieved for strategy based maintenance plans. Is there any user exit or same thing available to achieve the same?

[peter_atkin · Accepted solution]

Lucky

This is one great limitation in SAP strategy-based planned maintenance in that the system uses the smallest package used in the plan as a basis for the call horizon/call date calculation.

You could use user-exits/BADI's to adjust the dates if required.

I believe EHP6 may also have some changes - can someone confirm please..

PeteA

[Former Member · Accepted solution]

Hey PeteA,

System consider smallest package sequence in EHP6 as well.

[Former Member]

lucky soni ,

You have option of Time- Key date. You define strategy base on time key date and system will generate order on specific date interval.

[Former Member]

Yogesh,

Checked, that Time-key date scheduling option becomes valid when in considering the maintenance packages in multiple of months and not for days or weeks or combination as above.

[Former Member]

Oh yes. you want in 7 days and 1 month. In that case you will have to create two plan (single cycle) with one cycle of 7 day and second of 30 day then only it will work as per your requirment.