Call Date according to call horizon

[BIDOR]

Hi,

I would like to have a clearer understanding of Call Dates for Maintenance Plans.

Here is what I have:
Maintenance plan with packages for 4-months, 6 months and 12 months.

The Call Horizon is 88 % to have the call dates +/- 14 days before the planned date.
Shift Factors and Tolerances are 0% and we are using a Factory calendar.

Now the problem is that for most of the year the calls are in fact generated +/- 14 days in advance.

But for May and July, they are generated as the equivalent of +/- 7 days in advance.

In the present example, when I look at the call algorithm selecting planned date May 1st, I can see that the Planned cycle/offset = 60 days

The same occurs for planned date July 1st.

The next one is planned date November 1st and for this one Planned cycle/offset = 120 days.

I can see that from one planned date to another, the total amount of days would be 60 days or 120 days which seems to be the problem but since the call horizon is 88 % and the lowest package is 4-months, should'nt the call dates always be +/- 14 days in advance (120 days * 12%) ?

Thanks for your help !

[PJA]

- Are you using a factory calendar
- Are you using and BADIs/user-exits

PeteA

[BIDOR]

Yes for factory calendar - No for any BADIs or User Exits.

Thanks.

[PJA]

The system determines the call date based on the smallest package used in the plan.

In your case 4M is the smallest package, and 88% of 120 days equates to 14 days.

14 days is then used for the 4M, 6M and 1Y cycles.

[BIDOR]

That is exactly what I was expecting but it is not working this way. It is as if it sets the call date on the time interval between calls. (see my first post for May and July where the call is 7 days in advance and not 14 days)

[PJA]

Have a look at the calendar to see what the working days are to see if that's having an effect...

[BIDOR]

All the other maintenance plans (and there are quite a few...) don't have this problem but they also usually do not have this kind of sequence i.e. the others are either 1-month, 3-months, 4-months, 1-year, 1-month-1year, 3-months-1year, 6-months-1-year, 3-months-6-months-1-year etc.

It seems that between the 4-months and 6 months (in a sequence of packages of 4M-6M-1Y), the call horizon is calculated according to what is in the call algorithm which is 60 days. So would this be an SAP standard function ? If so I have had it wrong all along.

[PJA]

Could be a bug..

Have a look on OSS.

Otherwise, restart the plan and see if that helps, or re-create the plan

[BIDOR]

I have done a test to check if this is consistantly happening and it is.

I have created a task list with packages for 2-months, 3-months, 4-months and 6 months and a maintenance plan with call horizon at 77 % and as expected the call dates are:

14 days in advance for 2M
7 days in advance for 3M
7 days in advance for 4M
14 days in advance for 6M

The problem is not occuring for packages which are multiple of each other (ex 3M-6M-1Y) which still has me wondering...

If anyone could test on their side and see if the same is happening independantly of recent SAP versions, we could come to a conclusion about this (I don't have access to OSS...)

[PJA]

Works fine with my test using 2W, 4W, 6W and 8W and 77%

All have 3 days planned date lead times..

Also check you are not using any IPRM* user-exits via TCode SMOD

What system are you working on?

[BIDOR]

I believe your scenario would work fine for me also (since it is always a minimum of 2W interval and 2W is the lowest package) but if you have a chance try 2W, 3W, 4W and 6W. Then you might see that 3W and 4W will come up later than the other ones.

I appreciate you taking the time for this.

Thanks !

[BIDOR]

Forgot the system:

SAP ECC 6.0 and no User Exits are used.

[PJA]

I would raise an OSS Message to SAP

[BIDOR]

Did you or can you try with the sequence 2W, 3W, 4W and 6W ?

[PJA]

No, haven't got time..