Skip to Content
0

Automated Notification creation in QM

Jan 22 at 09:23 PM

98

avatar image

Experts,

I see that we can automate notification creation provided spro config to maintain default notification type for inspection type is done. I have SPRO config in place.

Once i enter results in QE51N, i would expect that notification should be automatically created.

Question: Where can i see this auto created notification to confirm that this happened as expected? Is there a Tcode where this gets displayed?

BR,

Aspire

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

8 Answers

Stylianos Pan. Jan 23 at 10:00 AM
0

You can review the notifications created through tcode QM10 . From your original email i understand that you just did the assignment of the Notification type in the inspection type, you should be aware that additional config + setup steps are required for this to work.

Few of these steps below:

- Defects recording setup for your characteristics (control indicators / defect catalogs)

- Config the Report Type

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

Hi Stylianos,

Can you please help me with instructions or screenshots to maintain the suggested steps. For step 1, i see that we need to maintain catalog tab in QS22 Tcode for MIC. Unfortunately, i see that for 3000 plus MICs in our system, this has not been maintained yet! Is there a way to mass maintain this tab?

Config report type - Can you please help me understand how this can be done.

BR,

Aspire

0
Aspire WF Jan 23 at 03:03 PM
0

Hi Stylianos,

Thanks a lot for your reply. I was not aware that more config is required. It's very helpful that you have listed the steps. Can you please help let me know how i can set up the same.

BR,

Aspire

Share
10 |10000 characters needed characters left characters exceeded
Yogini Thorat Jan 24 at 12:19 PM
0

Hello Aspire WF,

Notification can be created automatically if defects is recorded for inspection lot, char, operation.

As u said in above thread, u have recorded result and want to see notification, this is only possible if defect is recorded for that char automatically on valuation of char as rejected.

following settings are required

1. in task list defect recording control indicator is set

2. defect code is mentioned in catalog tab of inspection char (i.e. if char is rejected this defect code will be selected by default on valuation of char as rejected.

hope this will help

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

Hi Yogini,

Even though i am not going down the path of maintaining catalog tab for MIC in QS22, I have 2 doubts as below just for my own understanding:

1) I see that we can maintain upto 4 catalog types. In my case, catalog type '9' stands for defects. There are 8 code groups against this catalog type. Is it legit scenario to map a MIC possibly to multiple code groups under same catalog type? If yes, how can customers map more than 4 records as there is no option to add a new row in this popup?

2) Defect Code Group for General Rejection - Pressing F1 on this field shows that if no alternative codes for a rejection with reference to an upper or lower specification limit are maintained, code group and code maintained in this field will be used. Is it possible to maintain separate codes - One for upper limit and one more for lower limit? If so, where can this be done.

0
Aspire WF Jan 24 at 06:24 PM
0

Hi Yogini,

Thanks a lot for your reply. Let me confirm if the points you have mentioned are in place.

BR,

Aspire

Share
10 |10000 characters needed characters left characters exceeded
Aspire WF Jan 29 at 08:57 AM
0

Hi Yogini,

I am a novice QM user. I could not locate defect recording control ind. in task list. I checked in QP01 Tcode where inspection plan is created and task list is mapped to insp. plan. I believe this is the place to check tasklist.

In QS23, i see catalog tab for MIC. I have around 3000 MICs in system. I randomly checked couple of frequently used MICs and see that none of them have catalog tab maintained. Only Classification and Other languages tab have been maintained. Do i have to maintain defect code for all MICs in system to achieve auto QM notification? Is there a way to mass maintain this tab for 3000 MICs.

BR,

Aspire

Share
10 |10000 characters needed characters left characters exceeded
Yogini Thorat Jan 29 at 09:12 AM
0

Hello,

for Defect recording control indicator - select inspection char , click on control indicators button above inspection char table. pop up will come, at the lefthand side end u will get a check box for defect recording field.

Yes u need to maintain defect code for auto notification creation for rejected chars. in MIC/Inspection plan.

Another way is record defects manually for rejected char, notification will be created automatically in background- pre requiste is in config 'Activate Q notification' is marked for the defect class of that defect

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

Hi Yogini,

Thanks a ton for your valuable quick reply. I found defects recording checkbox based on your directions. Thanks.

I will go with the option to maintain defect code at inspec. plan level. I think it's better not to edit MIC Master data from QS22 and instead set appropriate defect values in plan level.

Currently we enter results for MICs in QE51N Tcode. When you say there is another way to manually record defects for reject characteristics - Can you please tell me the Tcode from which this can be done.

BR,

Aspire

0
Yogini Thorat Jan 29 at 09:40 AM
0

Hello Aspire,

Can you please tell me the Tcode from which this can be done - this can be done in result recording screen itself- same screen u will find a button 'Defect' on lefthand side top or else goto menu bar Edit-->defect--> char defect--> select insp char --> record defects.

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

Thanks a bunch Yogini! Let me try this option - Run an end to end cycle and will let you know the feedback.

0

Hi Yogini,

With your inputs, I am able to understand how user can manually record defects from QE51N screen. As you mentioned, i can see defects button(Create) on top left corner clicking which pops up a screen for entering defect details.

I have few doubts as below:
1) Where can i do config for Activate Q notification checkbox

2) Approach wise: Is it better to manually record defects for rejected char or is it better to maintain this in plan level? Is there a benefit to one versus other and is there a commonly practiced approach that is preferred over other one. It would be helpful for me to get this clarity before deciding on final approach for business team.

BR,

Aspire

0

Hi Yogini,

From this LINK I could spot the path for Activate Q Notification checkbox in SPRO.

BR,

Aspire

0

Hi Yogini,

It will be extremely helpful if you can shed some light on benefits of 2 different approaches you suggested.

BR,

Aspire

0

Hello

Option 1- Add defect in plan for rejected char- This option is useful if u are sure that only particular defect/defect codes will be the reason for rejection of char. Benefit is Automation, reduces effort of manually entrying defect

Option 2 - record defects manually whenever char is rejected- Benefit is user can select defects as required.

I would refer option 2 as it totally depends on user whether to create defect or not, and which defect to select.

0

Hi Yogini,

Thanks a lot for your helpful reply. I just figured out that the person creation inspection plan is different from the person recording results. Since i am new to the department and module, i was not aware that these are 2 separate activities performed by 2 separate individuals.

I agree with you that option 2 will work for my scenario as plan creator might not know the particular defect codes that will be appropriate right at the time of creating inspec. plan.

0
Aspire WF Jan 31 at 04:32 PM
0

Hi Yogini,

Based on your inputs, I am able to create notification from QE51N by clicking Defects button. Thank you so much for all your valuable inputs and directions.
Assume I have 5 MICs mapped to a sample inside an inspection lot. Say for MIC1, i enter defects by manually clicking Defects button. I click on Activate notification and its good so far. For MIC2, if i have enter defects again, i see that i am allowed to enter more defects from the popup, but only 1 notification gets created for multiple defects. Is there a way we can create separate notifications for each defect entered in the popup?

BR,

Aspire

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

Hello Aspire,

I would like to ask, why u want to create different notifications for each defect when the remaining data like inspection lot is same for all the defects. If the reason is u want to analyse, document root cause, activity for each defect separately, that can be done in single notification also by selecting defect and documenting it in causes, activity tab below item tab.

Thanks

0

Hi Yogini,

Without your help in this thread, i would not have the little understanding that i have now about automating notifications. Thanks a lot for your reply.

We are capturing the complaint quantity for every defective MIC that we find during our sample test. Assume a lot has 1 sample which in-turn has 3 MICs inside it. Say MIC1 is defect free. MIC 2 and 3 are defective. MIC2 can have complaint quantity as 2 and MIC3 can have complaint quantity as 10. I believe complaint quantity is the no of items that are defective.

I could not find activity tab below item. My screen looks as below,

BR,

Aspire

mic.png (42.9 kB)
0

Hello Aspire,

R U using standard Notification type? Generally u will get item tab as following

item.png (6.7 kB)
0