Different Material Type For Same Material

Using Different material type for same material
 

Is it advisable to create different material type for same material?
 

Purpose:
 

One material type would be with quality active. The other would be without quality inspection.
 

In case of emergency, the without quality material shall be issued to production.
 

What may be the disadvantages?
 

How can this situation be handled without creating a different material type?
 

---

Suggested Answer
 

What I could recommend is that instead of defining a separate material for “emergency purpose”, I would suggest you should skip the inspection by forcing completion on the characteristics and make a usage decision as “accepted without inspection”, or something similar.
 

This way, there will be a record that the inspection lot was closed without inspection. The exact circumstances which qualified as emergency can be recorded in the long text for UD.
 
Alternatively, if it is a batch managed material, you could try using the “restricted use” status.

Failing that, if you have the samples, you can still use QA11 to post the material without making the actual usage decision.  When you finish the inspection, finish the lot normally.  If it fails, you will need to track
down where the material was used and bring it back.

SAP QM Tips

Also read

Have a SAP QM Problems?
SAP QM Forum - Do you have a SAP QM Question?

SAP QM Books
SAP Quality Management Certification, Interview Questions and Configuration Reference Books

SAP QM Tips
SAP QM Tips and Quality Management Discussion Forum

Main Index
SAP ERP Modules, Basis, ABAP and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity. Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.