on 08-14-2012 11:50 AM
It migh be because of QCC0 -->QMplanning --->Baisc Data-->defect class type ,you might have selected " "Q-Notification"" in defect class.
This is reason why notification remains open.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes correct!!
Now if you click on, let say 01, you would get following screen. See what you have maintained there.
For your understanding, use F1 help for ' Activate Q-notification' which says below content,
If you set this indicator, the quality notification (already existing) is immediately activated, when the defect data record is created. This means, that the quality notification receives the status "Outstanding notification" (OSNO).
ntn
The question is usually how you set up your catalog codes for the defects. For each defect, you must specify the type of error. If you select Defect class 01 or 02 (in standard SAP), then any notification using those defect codes will automatically activate the notification and it will remain open.
Have you set up automatic defect recordings and/or inspection point valuation? And if you did are you using UD codes for each plant? (configured on in the QM plant settings).
Since this is only happening in one plant, I suspect you set up UD selected sets for each plant. When you did for the new plant, some one selected critical defect for the reject codes. This then causes the notification to remain open after UD.
Check your UD codes and see what defect is assigned. Then check that defects settings config to see if the "activate notification" radio button is selected.
Either change the config for the defect, or in the selected set, choose a different defect code.
Keep in mind the UD selected set codes are also used in the inspection point valuation and could be triggered by those codes.
Craig
Guys,
I tried to give UD manually via QA02 for that inspection lot. I am getting the following error message.
Actually the problem is with giving UD and not with notification. If UD happens, then automatically the notification may get updated correctly.
Inspection type what we are using is 8900.
Please guide me in simple steps to do the missing config.
Regards.
My guess is that for the new plant, in the QM plant config settings, under the lot completion tab, you have clicked on the setting "Selected set in own plant".
This means that you must create a selected set using your UD codes under the new plant code.
Create that selected set, or remove the setting from config and you should be ok.
(Note: A picture is worth a thousand words! )
Craig
You never indicated that you checked the config that Sujit referenced.
Craig
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I apologize for that. I have pasted the screenshot.
I could not see what Sujit had mentioned.
Regards.
Hi Arun,
Ref to above,kindly check the Notification task in QM02 tcode, the assigned responsible person in task item,who is having access to complete the task in IQS12 transaction,then you will get alert mail,after that you have to close the task & complete the same.
Regards,
M.Arunkumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If a notification has been activated before UD, it will not be completed even if UD done.
This is SAP standard process, not depend on version or support package.
Regards, DoWook KIM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Issue not yet resolved.
Our new plant is TPPC.
In QCC0 -> Basic Settings -> Maintain Settings at Plant level -> TPPC -> Results recording ->
Proposal for inspection point valuation is empty.
I guess this is the reason for the error.
For other plants, the data is available under that tab.
I am an ABAPer and not a functional guy. How to set this tab data?
Guide me.
Regards.
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.