Defective quantity in Notification

Hi,
pls advice.
Scenerio : PO 100 , GR 100 , QI 100 , Sample QTY to be inspected 5 .
While creating Notification , i m getting complaint qty and ref qty as 100.
But i want to restrict my defective quantity which should not be more than sample quantity(5).
Also existing Defective qty (Int) , Defective qty ( ext) is taking values upto Gr qty.
How to restrict my defective qty w. r. to sample qty as i m doing physically defects recording for sample qty only.
Number of defects is also for only for defetcs and not for defect quantity.
Thanz.
Mangal.

Dear Mangal
Just adding my views
See normally when you take a sample out of a lot it is understood that it is representing the whole lot. The company may chose to completely reject the material which in that case the complaint quantity is also same as GR quantity. That is the reason why the entire GR quantity is automatically populated as reference quantity & complaint quantity. chaning the reference quantity to sample quantity may not give a correct picture , you may enter the defective quantity as No of defects in the item view and as the inspection lot is already getting copied to the notification sample quantity can be derived from the same.
Regards
Gajesh

Similar Messages

Notification quantity fields

Hi,
Please clarify me on the actual purposes of quantity fields in notification like Complaint quantity, Refernce quantity, Defect quantity internal, Defect quantity external and Return Delivery quantity.
Please throw some light with actual use of these fields based on your experience. F1 help says something meaningless. Actually there is no check in Return delivery quantity field in notification and Quantity returned through 122 movement type.
How can we capture operation wise defect quantity (internal and external) for in-process inspections.
Is it possible to assign a reason code while we scrap a material like we assign during return material to vendor.
Thanks
Jessy Jason

Hi,
Following are the meaning of there fileds:
1) Complaint Quantity : This is the quantity against with you want to raise the complaint to vendor. ex if the lot is of say 1000 kgs and you have defects with 10 samples then your complaint quantity would be entire 1000. But for urgency you segregated the lot and found the defective quantity as 200 then your complaint quantity will be 200 nos.
2) Ref Quantity : This is the basic supplied quantity of lot, above case it will be 1000 kgs.
3) Return delivery quantity : Even the defect is in 10 samples you can return entire quantity of 1000 nos, however if you segregated and found 200 defects then in that case return delivery quantity is 200 nos. One can raise debit note for segregation activity.
Best Regards,
Shekhar

Notification set in process again at defect recording

Hi all,
In customizing, my inspection type is defined as "one Q-notification by inspection lot". The linked notification type is A1.
I created an inspection lot. I created a notification of type B1 with QM01 link to this inspection lot (QMEL-PRUEFLOS). This B1 notification is already closed.
When I record an defect in QE51N for this inspection lot, a new A1 notification is created BUT the closed B1 notification is set in process again.
Is there a way to avoid this kind of behavior ? I just want to create a new A1 notification without reopening the closed one. Eventually just reopen existing A1 which are already closed but not other type of notifications.
Thanks in advance

Hello Sebastien,
"one Q-notification by inspection lot" applies to Inspection lot only irrespective of Notification type and it will set other notifications in-process if you record new defects.
In your case i guess both A1 and B1 are customized notification types. And in B1 notification you have incorporated "inspection lot" field by using some Exit.
When you create manual notification B1 using QM01, you enter Inspection lot number and it hits Table QMEL. Now when you record defects and create notification A1 system gets another Notification with the same inspection lot number and puts it In-Process.
Now if you consider standard notification types F2, Q2; When you go for QM01, you can not maintain Inspection lot number in Q2 notification, but for F2 (Automatically) system copies inspection lot number into notification. And as it does not get any other entry in QMEL there is no effect on Q2 notification created earlier.
Experiment on user Exit QQMA0030 Check validity of status change; and see if you can restrict putting notification in-process if Notification type is Not Same.
Amol.

Multiple 'F3' Quality Notifications for defects from single Service Order

Those of you working w/ the QM module no doubt know that if a failure is recorded against an inspection characteristic linked to a Production Order (Order category 10), that SAP standard functionality creates a Defect document (Quality Notification type 'F3'). Any subsequent failures recorded that are linked to that same Production Order (as well as the material & serial number) are recorded, as additional line item defectes, on that same 'F3' Quality Notification.
HOWEVER, I have found when failures are recorded against inspection characteristics for a Maintenance Order (Order Category 30), a new Defect document (Quality Notification type 'F3') is created for each failure that is recorded. Why is this?
My client wants only a single 'F3' Quality Notification to be created for any and all failures that are recorded against a single Maintenance Order. I do not see any way to accomplish this w/o a core mod. Understanding WHY SAP treats these two order categories differently will go a long way to assisting me in designing an adequate solution.
Thanks for your help.

A couple more pieces of information....
1. We are currently running SAP Enterprise (4.7).
2. If I go to SPRO -> 'Quality Management' -> 'Inspection Lot Creation' -> 'Maintain Inspection Types', and display the details for Inspection Type 14 (which we use for Service Orders) the check box for 'One Q-notification per insp. lot' is active. Clearly the system is not processing a single Quality Notification per inspection lot on service orders.
Your assistance is greatly appreciated. Happy New Year

How to create a new field for Q3 - QM notification in Header and item level

Dear All,
l
Sub: How to create a new field for Q3 - QM notification in Header and item level
Ref. the link --> Quality Notification
We want to create a new field in header level and item level.
As per the thread the solution is given below.
In the IMG Config: Quality Management -> Quality Notification -> Notification Types -> Define screen areas for notification types Then Choose 'Define screen areas' Then Click on 'New entries' button Now, select the relevant Notification Type and click in 'Enter'. Select the 'Iten Cases' register and remember to setup the Tabstrip Header, Icon, etc. Set the 'Tabstrip active' flag. Then Save.
Quality Notification -> Notification Types -> Define screen areas for notification types
WE ARE UNABLE TO FIND IN CUSTOMIZATION PATH --> DEFINE SCREEN AREAS FOR NOTIFICATION TYPES.
Please help.
Question No. 2 :
THE REQUIREMENT IS GIVEN BELOW.
We want to hide the field in Q3 - QM Notification
In header --> Reference tab --> Item (sub heading) --> "DEFECT LOCATION" FIELD TO BE ELIMINATED (HIDE)
Ref the link --> Quality notification
The solutiion is given below.
Hi Sami,
We can hide the collumns using the Transaction OQM1 and Program Name SAPLIQS0.
Lets say Defect location need to be hidden, the field TXTCDOT need to have the radio button HIDE.
Hope this will suffice your requirement.
Kindly ask me if you need any other details.
Thanks & Regards,
Srinivas.D
Hi Sami,
We can hide the collumns using the Transaction OQM1 and Program Name SAPLIQS0.
Lets say Defect location need to be hidden, the field TXTCDOT need to have the radio button HIDE.
Hope this will suffice your requirement.
Kindly ask me if you need any other details.
Thanks & Regards,
Srinivas.D
By double clicking the "DEFECTIVE QUANTITY (EXTERNAL), WE COULD NOT GET --> field TXTCDOT .
Plese do the needful.
We are using ECC6.0 Ehp3 and Ehp4.
With Best Regards,
Raghu Sharma

Dear Pushpa,
Transaction Code :SHD0 is working fine.
Please accept my sincere thanks for your sharing your Knowledge.
I am able to fulfill my
Regarding the enhancement, I have not tried.
Once I will complete, I will award the fulll marks to you.
With Best Regards,
Raghu Sharma

Quality Notification

Hi sap gurus,
In standard Notification report, Defective quantity, Reference quantity and plant is not printing. How can i get plant wise notification report.Can anybody suggest me how to do this.
Krishna

Hi,
Are you refering to reports QM10 / QM11. Both of them will print plant and reference qty.
To get plant wise notification, add plant as a selection from the dynamic selection screen.
Cheers !

122 through notification

Hi,
I want to use notification for 122.I have the lot of type 01 and wen i do result recording and reject the char.notification(F2) is getting created.
Now i want to return stock to vendor through notification.
i can do 122 through UD screen but then notification will not be used.
What steps are to be followed after result recording if i want to return to vendor through this notification?

Dear Shreya
If the material is lying in the 01 inspection stock then you cannot do 122 through notification. You have to do throughUD stock posting itself.
It is mentioned in the sap help also
At the goods receipt inspection or at the subsequent storage and processing of goods, defects can be identified that can be traced back to the vendor or manufacturer. As a first step, you create a quality notification that documents the problem and forms the basis for the appropriate corrective tasks. To prevent the damaged goods from being used, the department responsible can post the stock available in the warehouse from unrestricted-use stock to blocked stock or to inspection stock.
You have several options for further processing. If necessary, the partial quantity that can still be used can be sorted and the defective partial quantity sent for rework or scrapped. The defective quantity can also be returned to the vendor with a request for a replacement quantity.
If you decide to return the goods, you can do so either with or without reference to the original purchase order or goods receipt. If you reference the original document, the system reduces the delivered quantity contained in the original purchase order. If you do not use a reference, the system creates a separate return delivery purchase order, which then forms the basis for the actual return delivery.
In both scenarios a delivery is created, the accompanying papers (such as delivery note, complaint against a vendor with defect data, 8D report) are printed, the goods issue is posted and the vendor is sent an invoice. The return delivery purchase order and credit memo request or debit display reference the quality notification from which they were triggered. You can trace the document flow in the notification.
Regards
gajesh

Automatic Creation of Quality Notification

Dear All,
In standard SAP whenever defects recording is done for an inspection lot and saved,automatically a quality notification is also created.In my business scenario they will record defects for almost all the inspection lots hence resulting in a huge number of unwanted quality notification which then later wont be processed at all.
Hence i wanted to know whether anything can be done to stop auto creation of notification.Is there anything which i could in IMG or any setting to avoid that???
Expecting your valuable comments
Regards
JR

Hi
i wanted to know whether anything can be done to stop auto creation of notification.Is there anything which i could in IMG or any setting to avoid that???
1.This is very much possible through SPRO setting.
QCC0>Quality planning>catalogs>select defect calss->
like for Minor defect-->remove Raido button & make it No active function
Just a suggetion ...what you can do for all Critical & major type of defect keep "Active Notification"
for Minor type of defects keep "No Act fuction"
this will reduce unnecessory notification.
2.If you permanently want to remove all notification after defect recording then
Go to Inspection type setting in SPRO & remove notification against inspection type.
QCC0>Qul insp>Insp lot creation-->maintain inspec type.
Regards
Sujit

Creation of Quality notification

Hi,
I need to create quality notification using BAPI_QUALNOT_CREATE.
I have to create cause text too for the notification.
Can someone guide me to fill the necessary data for header and text.
Moderator message: please do some research before asking.
Edited by: Thomas Zloch on Mar 7, 2011 4:37 PM

Hi
i wanted to know whether anything can be done to stop auto creation of notification.Is there anything which i could in IMG or any setting to avoid that???
1.This is very much possible through SPRO setting.
QCC0>Quality planning>catalogs>select defect calss->
like for Minor defect-->remove Raido button & make it No active function
Just a suggetion ...what you can do for all Critical & major type of defect keep "Active Notification"
for Minor type of defects keep "No Act fuction"
this will reduce unnecessory notification.
2.If you permanently want to remove all notification after defect recording then
Go to Inspection type setting in SPRO & remove notification against inspection type.
QCC0>Qul insp>Insp lot creation-->maintain inspec type.
Regards
Sujit

CS Report- defect Type-wise components consumed

Hi Experts,
I am trying to figure out if there is any standard report available that can cull out information on defect type (from notification) and components consumed (from service order). What's the best possible solution?
Please advise!
Thanks

You will probably need a customer-specific report..
Will this report be used regularly?
PeteA

Notification origin

Hi,
When I close the notification, I get a popup to choose if its internal or external origin. I need to get more detail as to who is reponsible for the defect. For eg if its external then it could be the distributor, the manufacturer, the transport agency and if its internal it could be someone at receiving, someone in the warehouse. How do I record that ? Ideally I would like to assign the actual vendor, manufacturer, transport agency's ID or the internal person's ID who caused the actual defect after the notification is complete. How is the best way to do this so that I could run reports on that and see who is giving me maximum number of defects ?
Thanks

Check if you can use defect location code groups for this. If you refer to QM15 report following texts and codes are visible.
Code group of Defect Location
Code Group description of Defect Location
Code of Defect Location
Code description of Defect Location
Above set will be common (for logic) for catalogs of defects, causes, tasks, activities at item level and coding at header level.
What I can suggest is to explore whether all these have been properly utilized or not and try to set the logic of codes so that the individual code or code group will make some sense for reporting.
I doubt at the last instance of notification closure it will be possible or not but I can give 1 example by which this can be mapped. Create 2 code groups- One for Internal Origin and another for External Origin under defect location catalog. The agencies responsible for externals factors would be the codes of External Origin code group. Same way for internal.
Else you need to go with custome screen mapping and new Z table creations to store the information. When you click on internal or external radio button at the time of notification closure it will take you to different screen say vendor code screen from where you can choose required entry. Earlier option is more advisable, I would say!
Anand

F2 Notification type not picking reference object tab data

Hello experts,
I am facing a problem while creating notification. I have one lot of 01 inspection type(which is created after GRN) to which F2 notification type is attached. When i am trying to create notification against that lot, system is not fetching data in Reference Object Tab i.e. Material number, Plant, Material Doc, etc,.
Please give me some solution on this.

Dear all,
i am adding screen shots of process which i am doing. Please have a look on it.
1. I have done result recording in which i have rejected one parameter and closed RR. As i have not activated automatic defect recording it will allow me to save RR. Now i clicked on Defect recording.
2. Selected report type 00000010 & defect recording at Inspection Lot Level.
3. Added defect & clicked on Notification.
4. Here no data is fetched.

Create Rework/Production order through Notification

Dear Sir
In our scenario we receive inspection lot throug 04 origin in taht we amintain defect and activate notification,in task we want to creta rewor order or production through notification as we do send mail or trigger some task same manner.
Regards
Kunal

You can create re-work order from defect notification or from follow-up function in the UD code. In either case you need some programming.
In the defect notification create a new follow-on function to create re-work order. Problem with this is you still have to complete the 04 inspection so that material can be re-issued to re-work order
The way we have implemented the process is -
1. Complete the UD for 04 inspection lot with re-work disposition.
2. Move materials to special storage location.
3. Re-work order is automatically created as follow-up function from the UD code for re-work.
4. If we do not know whether re-work is possible or not, we reject part and let Quality engineer decide whether to scrap, RTV or re-work. If Enginner decides to re-work inhouse, we manually create re-work order
5. Issue materials to re-work order from this special storage location so that warehouse does not explode the requirements for component again.
6. We use separate inspection type ( copy of 04) when order type is re-work, This way we avoid complete re-testing and parts can received in warehouse as re-worked parts.
Marwadi

Re: Approval procedure for automatic notification creation

Hi All,
I am trying to use Approval procedure in Supplier notifications. While creating a notification manually I am able to restrict the notification for further processing unless it is being approved. But when I am generating automatically through defect recording the notification is not getting the APRQ status.
I have maintained the approval reqd. settings for both of the notification types ( Both Auto and Manual)
Please advice.
Regards,
Vivek

closing

Duedate Notification Instance in Process

Dear Experts,
I am not able to get the Action2 Notification Instance through Due date Notification code.I am able to get the details till Action1.
I observed clearly through above code i can get the details of Notifications only till Current Action.I am unable to get the next Action Notification details.Is der any other way to get all the notification details existing in Process.
If a process Contains Duedate Notification's @ Action level for all Action's in the process.
Process
-->Action1
-->Action2
-->Action3
-->Action4
For example If I performed Action2->Action3.I am writing the code to change Deadline of Action3 before
executionContext.processingComplete();
In Action2 .But I am not able to get Notification Instance details of Action3 through the code which is given in this message Due date Notification.
So please let me know how can i get the Notification details of entire process.
Thanks in Advance.
Regards,
Rajesh N

Hello Sebastien,
"one Q-notification by inspection lot" applies to Inspection lot only irrespective of Notification type and it will set other notifications in-process if you record new defects.
In your case i guess both A1 and B1 are customized notification types. And in B1 notification you have incorporated "inspection lot" field by using some Exit.
When you create manual notification B1 using QM01, you enter Inspection lot number and it hits Table QMEL. Now when you record defects and create notification A1 system gets another Notification with the same inspection lot number and puts it In-Process.
Now if you consider standard notification types F2, Q2; When you go for QM01, you can not maintain Inspection lot number in Q2 notification, but for F2 (Automatically) system copies inspection lot number into notification. And as it does not get any other entry in QMEL there is no effect on Q2 notification created earlier.
Experiment on user Exit QQMA0030 Check validity of status change; and see if you can restrict putting notification in-process if Notification type is Not Same.
Amol.

Defective quantity in Notification

Similar Messages

Maybe you are looking for