inspection Plan in Qm

[Former Member]

Hi Gurus,

I would like to ask if Inspection plan are required in Qm process?

Can I do QM without Inspection plan and just use Material Inspection Characteristic?

What are the Pro and Con?

Thanks,

raymond

[Former Member · Accepted solution]

Inspection Plan in SAP is provided to link the following bsic Master Data in QM

1. Material Master

2. Master Inspection Characteristics

3. Sampling Procedures

4. Inspection Methods

5. Sample Drawing Procedure

6. Inspection Points

7. Workcenters

With these data system comes to know what are the parameters to be analyzed, how much of sample is to be taken, how to do the tests, what are the standard specifications, how many times inspection must be carried out, etc.

Basic difference between Material Specification and Inspection Plan are

1. Inspection Plan is at Plant Level and MAterial Specification is Client Level

2. DMR cannot be used in Material Specification

3. Inspection Points cannot be used in Material Specification

4. Sampling Drawing Procedure cannot be used in Material Specification

5. In Inspection Plan we can maintain specifications based on Usage whereas in Material Specification only one specification can be maintained.

Best Regards,

K. Raghavendra Nayak

[Former Member · Accepted solution]

Hi,

That was very helpful answer.

It means I need to create inspection plan for each material?

Also, do I need maintain an operation and workcenter? Is it required?

Im new to QM. Thanks for the help.

Raymond

[Former Member]

Hi

Geenerally the sequence of inspection is Result recording->defect recording>Usage decision->stock posting.

Now all these processes are independent.That means without doing RR you can do UD & stock posting.

So You may have Task list or may not have depending upon your requirement.

Advantage of using task list is majorly for Retaining the Results of the Inspection lot.These are mainly used in the Process Induatry like Chemical or Pharma etc where you should have documentry evidence to tests carried on lot.

If you do not use task list still UD can be taken & inspection can be done but results can not be reocrded.

Also if in Inprocess inspection for activity booking like ManHrs or M/C hrs task list(Rautung ) needed.

I hope This will add some value.

Regards

Sujit Gujar

[Former Member]

Hi Sujit.

We do not track manhour or the operation. Only the quantity and what is the defect. It is needed to be available for report.

So do I still need inspection plan?

and also Im quite not sure of the use of result recording. I tried to read documents but it is still unclear to me.

Thank you,

Raymond

[Former Member]

For only monitoring number of defective quantities produced, only UD is enough from QM Side. For this to happen in details of the Inspection Type in Material MAster QM View following indicators must be unmarked:

1. With Task List

2. With MAt. Spec

3. Check Char

4. Auto Assignment

Mark on

1. 100% Sampling

Results Recording is the activity which is to be performed to track the actual results of the tests conducted on samples such as Height, Weight, Carbon Content, Colour, etc.

Best Regards,

K. Raghavendra Nayak

[Former Member]

Hi,

Thank you so much.

One last question. For this, what Qm master data should I maintain?

we have a requirement also about the sampling type. sometimes we only need to inspect 30% of the lot.

Regards,

Raymond

Edited by: Raymond on Dec 1, 2009 5:24 PM

[Former Member]

Hi

We do not track manhour or the operation. Only the quantity and what is the defect. It is needed to be available for report.

So do I still need inspection plan?

No in that case you need not to have task list/Inspection plan in place.

and also Im quite not sure of the use of result recording. I tried to read documents but it is still unclear to me.

See Result recording as I told you earlier is a Documentrory evidence for all the charecteristics that you have measured for a perticular inspection lot.They may be Quantitative or Qualitative depending upon material.

Which helps to keep the history of the component.

Regards

Sujit