Skip to Content
0

Required Start Date in notification

Jul 14 at 09:13 AM

75

avatar image
Hi Friends
My query is with regards to the Required Start Date field in notification.
Scenario is like this: There is a maintenance plan with priority 1 (Very high). I am creating a notification through Maintenance Plan, that means the call object is a notification. When I schedule the maintenance plan, the cycle is 1 month. Current date is 13/07/2017. The first plan date is appearing as 12/08/2017 in IP10. But when I save the call, in the notification the Required Start Date is appearing as 10/08/2017. The call horizon is 0%. Tolerance is also 0%. Why the Reqd Start date is 10/08/2017? As per my understanding, it should be same as Plan date, i.e. 12/08/2017.
This is the SPRO setting for priority 1.

Prty Pr Pr type Rel str Rel end Priority text SDUn EDUn

SM 1 Service Priorities (Blank) 4 Very high H H


Thanks in Advance

Vikas

10 |10000 characters needed characters left characters exceeded

Hi Vikas,

Have a look at this note.

2341341 - EAM notification: Basic start date and basic finish date are not correct

Regards

Terence

0

Thanks Maria for your help.

I contacted SAP on this and they suggested to implement Note 2342788.

Regards

Vikas

1

Thanks for Sharing

0
* Please Login or Register to Answer, Follow or Comment.

5 Answers

shreyas shah Jul 14 at 07:38 PM
0

Hi Vikas,

What is the scheduling indicator on your maintenance plan?

Share
10 |10000 characters needed characters left characters exceeded
Vikas Gupta Jul 17 at 09:03 AM
0

Hello Shreyas

The Scheduling Indicator is "Time".

Regards

Vikas

Share
10 |10000 characters needed characters left characters exceeded
Vikas Gupta Jul 17 at 02:26 PM
0

Thanks Prashant for your help.

There is one more issue I am facing in another system.

When I am creating notification through scheduling of maintenance plan, it is taking Current date as Required Start Date (17.07.2017) in notification when the priority in Maint Plan is 0. But when Priority is 6, it takes the date calculated from last completion date (17.09.2014) as Required Start Date (17.09.2017). As per my understanding, the Reqd start date should be 17.09.2017. Why is this difference for priority 0 and 6. Below is SPRO setting:

Prty Pr Pr type Rel str Rel end Priority text SDUn EDUn

ZI 0 Service Priorities 0 4 High Blank MON

ZI 6 Service Priorities 0 0 Low Blank Blank

Share
10 |10000 characters needed characters left characters exceeded
Prashant Meshram Jul 17 at 10:41 AM
0

Hello Vikas ,

I also try to run same scenario and its working fine.

Notification type M1 ( Maintenance request ) is my call object and same has been assign to priority type (PM)

In my case ( as per today date )notification Required Start 16.08.2017 and Required End 17.08.2017

I am not sure it will helpful or not , but refer attached sheet.

Try for priority type :PM

Regards,

Prashant Meshram


Show 2 Share
10 |10000 characters needed characters left characters exceeded

Thanks Prashant for your help.

There is one more issue I am facing in another system.

When I am creating notification through scheduling of maintenance plan, it is taking Current date as Required Start Date (17.07.2017) in notification when the priority in Maint Plan is 0. But when Priority is 6, it takes the date calculated from last completion date (17.09.2014) as Required Start Date (17.09.2017). As per my understanding, the Reqd start date should be 17.09.2017. Why is this difference for priority 0 and 6. Below is SPRO setting:

Prty Pr Pr type Rel str Rel end Priority text SDUn EDUn

ZI 0 Service Priorities 0 4 High Blank MON

ZI 6 Service Priorities 0 0 Low Blank Blank

0

Hi Vikas,

Have you checked this note

2341341 - EAM notification: Basic start date and basic finish date are not correct

Regards

Terence

0
Vikas Gupta Aug 02 at 09:49 AM
0

Thanks all for your kind help.

The issue was coming because priority configuration was incomplete. SDUn was not maintained. After maintaining it, the issue was resolved.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Vikas,

Thanks, if you feel the issue is resolved, do close the thread.

Regards

Terence

0