Skip to Content
author's profile photo Former Member
Former Member

Automatic inspection lot issue

Hi experts,

We are a very discreet manufacturing company with very configurable products. Currently, we have QM configure to inspection type 03 (inspection during production) to automatically create an inspection lot when production order is release. The materials that need inspection are ticked for insp.setup in Material master QM view. We've created Master inspection characteristics (MIC) and assigned them to master routing operations. Because the fact that our materials are configurable (say material A may get a component B that requires inspection, and the same material A sometimes may not get component B ) we use dependencies on our master routing to determine if an inspection operation should be pulled to the order.

The issue we are having is that for materials that are ticked in MM view for inspection, sometimes based on dependency doesn't require inspection and does not require inspection lot, but sometimes it does require inspection based on the dependence set on the routing. How do we set up the system so that when a material that is ticked to get inspection lot in MM, but do not require inspection based on object dependencies not get an inspection lot automatically assigned.

Any suggestion will help.

Thanks in advance.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Dec 04, 2015 at 08:07 AM

    I do not have much idea bout the configurable material but I think there should not be any option apart from manually deactivating the inspection type in material master before you release the order. System on its own can not come to know when to create the lot and when it shouldn't.

    Let's wait for the experts to have more thoughts on this!


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 04, 2015 at 09:32 AM

    It'll probably be tricky to find a logic to block or create inspection lot for such process. I worked on one such process long ago where inspection lots were blocked on the basis of W/c for the common material.

    What I understand that A, as a finished good, will need an inspection on the basis of BoM component. If it is B, you need an inspection lot for A. When it is something else, you don't want to generate inspection lots for A, Correct?

    Please share what is the ultimate need? As final inspection on the basis of BoM component is bit tricky and it gets even more complicated when your finished product is same. How do you differentiate between two finished products (Two A's) whether they are produced from B or non-B?


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Nitin Jinagal

      You are correct on the second paragraph. Material A (as a finished good) will need an inspection on the basis of BoM component B. If B exist as component for A, I need an inspection lot created for A. When A doesn't contain component B or contain something else I don't want to generate inspection lot for A. Because again based on dependencies (whether material A has component B or not), the inspection operation and MIC on the master routing will not get pulled to the order. therefore inspection will never get done for those orders.

      The goal is to change system so it doesn't create inspection lot for those orders with Material A that doesn't contain component B. Production will never do inspection for those orders. When an inspection lot is created, the order is set an ILAS system status. Our need is to be able to close all TECO production order in a timely manner because we are on actual costing and it affects our P&L at month end. We cannot close an order without first setting the Usage Decision on the inspection lot. There are a lot of orders that fall in this scenario where an inspection lot is automatically created but really does not need an inspection at all.

      Thank you for your reply, any suggestion will help.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.