cancel
Showing results for 
Search instead for 
Did you mean: 

Key date and completion requirement combination in Preventive process sap PM

0 Kudos

Dear All ,

i have a query with completion requirement check box. i knew that functionality is to check the preceeding object whether it is technically completed in order to call the next object even though it crossed many months.

current settings :

both the shift factor are 100 %

both tolerance is:10 %

completion req : X

call horizon :85%

strategy plan : 1M 1Y (same hierarchy)

Shcheduling indicaotr: time

Business requires plan date and call date to be exactly first of every month but completion requirement should be there.

changes needed in plan:

removing shift and tolerances and making 0.

completion req : X

call horizon :100% (so that there wont be early call date which might diff from first of every month)

strategy plan : 1M 1Y (same hierarchy)

Shcheduling indicaotr: time -key date

But even if above set up is done . only the plan date can be 1st of every month . call date will be called differently because if the order is january order is techod in feb 20th . the next order will be created on the 20th feb .which is call date = basic start date. .

is there any war for making the call date to be 1st of every month . inspite of keeping completion req ticked?

Accepted Solutions (0)

Answers (2)

Answers (2)

peter_atkin
Active Contributor

The Time - Key Date sewtting in the maintenance plan header will ensure that an order is created on the same date.

PeteA

0 Kudos

hi Pete .

Yes the planned date will be the same date. what i meant was the call date. it changes right based on the last completion date.

in that case the call data or basic start date wont be 1st of every month right.

thanks

peter_atkin
Active Contributor
0 Kudos

lucky me

That could be because you have set values in the shift factors. Try setting these values to zero and retest.

PeteA

BalaAP
Active Contributor

Hi, You may read the documentation of user exit IPRM0002 for some ideas. If you cannot achieve something in config or work-around then finally we need to land up into user-exit / badi approach...

You can also wait for some time for our PM experts (like Peter) may throw some light...For them it may be mid-night...