cancel
Showing results for 
Search instead for 
Did you mean: 

Planner Group Mandatory Error in QM Notification

0 Kudos

Hello Gents,

I need a suggestion/approach to solve the below issue occured in my Testing.

We have PM Notifications with Planner group field (INGRP) as Mandatory input & I couldn't change this setting in SPRO (Screen Templates) as it's our business process from past 10 years (Business requirement).

Now As we are Implementing QM in our organization, Faced an issue with QM Notification "Planner Group error is appeared in QM Notification", and couldn't save any QM notification.

Could you suggest with any User exit details/approach to solve this issue.

Regards,

Vishal Singh R

Accepted Solutions (1)

Accepted Solutions (1)

busyaban7
Active Contributor
0 Kudos

Hi Vishal,

It seems, PLANNER GRP (INGRP) was mandatory for PM notification and you were only using PM in your plant. So you haven't had the need to change this screen template for influences. Till now there were no issues.

It seems your business has started using QM notifications newly along with PM notifications. Now if this planner Group is still coming as 'mandatory' field for QM notification, please can you check if any 'Influence' is created at PLANT level for planner group. If so, then there is a high chance that you will have an impact like this as it's a generalized influence.

If this observation is true - please remove the influence of 'planner group' at PLANT level and create new influences at NOTIFICATION TYPE level ONLY for PM notifications. If so, then this impact will not be translated to QM notifications created newly.

Thanks,

Arijit

0 Kudos

Hi Arijit,

Thanks for your Quick Reply !

I found an Influencing fields maintained for Notification Type, So i changed Planner group (VIQMEL-INGRP) as Mandatory here & Removed the same from Modifiable Fields.

Issue got solved & Now am able to Save QM Notifications.

Regards,

Vishal Singh R

Answers (1)

Answers (1)

subhrantbal
Participant
0 Kudos

Hi Vishal,

Please share the screen shot for better visibility on the issue.

Thanks

Subhrant