Required automatic QM notification generation when result recorded for an MIC is failure

[former_member473962]

Hello experts,

In my project, we are doing equipment calibration in SAP PM and the process is such that when PM plan is scheduled, a PM order and an inspection lot gets generated automatically.The next step is to record the result for the MIC in QE17 and go on to record the usage decision in QA11.

So far, it is working.

Now, the requirement is that if the result is 'fail', i.e. the inspection lot (the equipment) is rejected, then a QM notification should be automatically generated.

Since, I am new to QM , I need detailed instructions for the configurations and master data required  to accomplish this.

I created the MIC w.r.t a characteristic.

Once I changed my MIC (created w.r.t a characteristic) to check 'defect recording' in the control indicators. I was able to proceed upto QE17 and select my result 'fail' but when I tried to save, system gave the error that 'report 0000002 is missing".

Another thing I tried in my MIC but could not proceed much was when  I clicked on the button 'catalog' and tried to enter 'Defect codes for rejection'.

The characteristic which I used in my MIC, I had created by using the following option in the tab 'values' of transaction code CT04.

Then I entered plant # and a selected set from the drop down list.

Am I on the right track?

I have looked at some related discussions but getting confused.Please guide me on this.

Regards

PR

[busyaban7 · Accepted solution]

Hi PR,

You can go through my detailed feedback on 4th May, 2016 in the below discussion thread: https://scn.sap.com/thread/3899275

Please take care of point 4 and 5 (Define Report Type) for further using it.

Thanks,

Arijit

[former_member473962 · Accepted solution]

Hello Arijit,

Thanks for the inputs.

Your solution worked for me. I am now able to do defect recording and create QM notification in dialog form , from transaction code QE17, when the result is 'fail' instead of 'pass'.

However, I have a question. In the screenshot below, you can see that the check box for 'Quality notification' is unchecked. Why is it so? Have I missed something in config or is this how it is supposed to be?

Related questions :-

• Generation of QM notification from result recording is a standard process in SAP. Is it possible to maintain a PM notification type, under the configuration for Inspection types, instead and get a PM notification generated automatically? My client has expressed such a wish and I would like to try for the same.

• Secondly in the confirmation profile, all the entries were 'optional'. Not a single was 'required'. Then why did system create the QM notification in dialog form instead of generating it in the background on its own? In the dialog, I had to enter certain defect code related information. See the screenshot below.

Thanks and regards

PR

[busyaban7 · Accepted solution]

Hi PR,

Below are my understanding:

a) Activate Notification checkbox with inspection lot: Well, while doing defect recording, if you have selected the 'Activate" pencil icon, then this check you are currently missing in your system, will come up automatically. The activate Icon looks like below -

Alternatively, you can either revisit the recorded defect to use the above indicator, or form UD screen select the recorded defect and select this indicator, then this notification checkbox will be activated for your inspection lot.

NOTE: You need to also take care of a few points, before you do it. Please note that as soon as you have got this link as Active, means notification which got created at background is also in active state with initial system status like OSNO (Outstanding Notification). With this status being active, you will not be able to do UD as it will force you to do the notification processing to get system status NOCO (Notification Completed). Only after that you will be able to do UD for your inspection lot, against which you have recorded defects. On the other hand, if you have not use this "Activate" indicator, then though the notification got created at background, will allow you to UD, and in turn, will automatically set the system status NOCO for the linked notification.

b) Activating PM notification type for Inspection type: My understanding is - YES, this is possible!! But as per best practice we don't do it. For example, if we are using inspection form Purchase order Goods receipt (01), then we test to use the notification type Q2 (Complaint against Vendor). With that, the process adopted remains streamlined. But this is not a hard and fast rule though, and you can still give it a try by adding PM notification for logistic inspection types, test it thoroughly and only after successful testing, you can advice your clients. The configuration to maintain the link between Inspection type and notification type is below -

SPRO -----> Quality Management => Quality Inspection => Inspection Lot Creation => Maintain Inspection Types => Select the inspection type => Inspection result block => Notification Type => Add the new notification type here.

c) Query on Confirmation Profile: If these values are 'Optional" means, you can save the notification at background without manual intervention in foreground. If you wish to add details for defect details in foreground, then you need to select any one of these entries as "Required". Please check if 'Defect Recording" for MIC is active. If so, you can try removing it and the try.

Please go through the shared thread once again for more clarity.

Thanks,

Arijit

[former_member473962 · Accepted solution]

Hello Arijit,

First I want to say that under Inspection type 14, I experimented with both PM and QM notification types and it worked.

I was able to generate both types.

However, now I am facing 2 very strange problems.

First problem is that under the defects tab, two entries, same in every sense, are getting created, as you can see below. There should be only 1 defect. Why 2?

Secondly, I changed my confirmation profile to make one of the entries 'required', as you can see here. Still it is getting generated automatically only.

Hence, I could not test your suggestion about checking the 'Q notification' checkbox.

For your reference, here is the catalogs info about my MIC.

Please advise as what might be missing.

[busyaban7 · Accepted solution]

Hi PR,

You might have looked into the 'Item' record number, as the 1st line is flagged as "1" and 2nd line has been marked as "2". This definitely means, you must have added defects two times, hence two records were created against the same inspection lot. You can do one more test yourself to confirm this understanding. Go to result recording tab, you will see Red Color Defects flag like below -

Once you add another record for defects using code group/codes, etc then you can see that 3rd record in your list for QA11. You could also add defects form QA11 screen, and this is not a problem at all. Please can you check the previously shared config to check if the check for One Q-notification lot is active or not?

Related to your second question - As I already suggested before, defect code for rejection is active. So, you must have been doing defects recording manually, and notification should have been getting created in the BACKGROUND, isn't it? If you remove that form MIC, and then make one of the parameter as required for confirmation profile (like what you did now), will force you to keep adding the defects in foreground in dialog mode, only then the notification will be created in background.

I will again suggest you to READ through the previous thread very carefully to get these details clarified.

Many thanks,

Arijit

[former_member473962 · Accepted solution]

Hello Arijit,

I followed your advice and removed the defect code that I had maintained in my MIC master data, under the catalogs button.

Then I ran a full cycle. In QE17, after mentioning the result as 'Fail', system prompted me to record the defects. I created as many no. of defects as I wanted. So, it worked.

Then I selected all the rows for the entered defects and clicked on the button 'Activate notification'. I got the message that defects have been activated.

Next when I came to QA11, I saw that each of the defect lines had the 'Q. notif.' checked.

So far so good.

However when I tried to record my usage decision, I was very much able to do so and save my changes. After that, on checking my QM notification generated, I saw that the status is still 'OSNO NOTI'.

Earlier, when I had not gone for this activation thing, I could still go ahead and record my usage decision but on doing so, the status of the generated QM notification used to getting updated to NOCO, just like you said it would.

What I am trying to say is that activation action did not stop me from completing my usage decision about the status of the notification remain OSNO only.

I have not tested this entire behaviour when the generated notification is a PM type.

[busyaban7 · Accepted solution]

Hi PR,

Check the SAP note KBA: 2285138 - Defect record notification is closed during usage decision (NOCO)

Thanks,

Arijit

[former_member473962 · Accepted solution]

Hello Arijit,

I think the activation functionality is working now.

I checked the similar functionality for the automatic PM notification generation also.

After recording the defects if I activate them, then I am still able to go ahead and record the UD but the notification generated remains active (OSNO).

If I do not activate the defects, then also system lets me record the UD but in that case, the notification gets completed (NOCO) when the UD gets saved.

I will still check out the OSS note mentioned by you.

Appreciate all your inputs very much.

[former_member42743 · Accepted solution]

When a notification is activated, (either manually by user or by cataloging the defect as a critical defect), a UD is still allowed to be made.  If Arjit is seeing in his system, this is not possible, I would believe that they have implemented some user exit to accomplish that.

Normally, in standard SAP, at least as I know it, activating a notiication means it will not be closed automatically.  Someone has to manually address the notification, i.e. investigate and close. If only minor defects are detected, the notification is created but not activated. Then when the UD is made  the notification is automatically closed by the system.  In these cases, the notification is simply serving as a collector of minor defects that can then be monitored and evaluated in the QMIS module. 

Craig

[former_member473962 · Accepted solution]

Thanks, Craig for clarifying this point about the activation.