Process - Booking into Stock

[Former Member]

Our Organization a setup of the following process from procurement to inventory as shown below.

We are having issues with this current process flow as after parts are delivered, it goes into inspections and on QM-Lot status. Once inspection is done it goes into stock (showing in SAP as already in-stock) regardless wether there is a NCR or QN generated during inspection. This creates two problems for us

1. stock levels are inaccurate as it doesn't differentiate bad stock from a good stock.
2. Items with QN does not get focus to get resolved (as it shows to be in stock). We always get caught out that there is an issue with a part when we are picking/issuing from stores

I would like to add another step in between QM-Lot and Stores when there is an NCR on the part preventing it to go into stock.

is there something in SAP to change this flow?

Thanks,

Edison

[JL23]

You just have one bucket for stock, while SAP differentiates between unrestricted use, quality inspection and blocked stock.

If you have a problem with the quality, then I wonder why you do a usage decision into unrestricted use stock. post it to blocked stock and it is not available for picking.

[Former Member]

Our Quality department does not want their performance metrics with items on NCR stuck in QM-Lot so they clear it off QM-Lot and it gets book into stock in a MRB location(bucket for items is quality issues though they are show in SAP as in stock). However checking in MD04 does not differentiate that this are bad stock.

Posting it to block stock just not really help. When you run MD4C report with more than 200 components, it does not show you which of components is in block stock. We also don't want to generate planned orders and loose focus on resolving items in block stock

my forte is JDEdwards which has a solution by selecting which process type you want to assign to purchase parts. is there anything in SAP?

[former_member182673]

So basically your requirement is to exclude the stocks that are in MRB location from the MRP run. If so then you have to look at Storage location level MRP and exclude this location. But if you have too many SLocs and hence this solution will be cumbersome, then look for user exit solution to exclude the stocks in MRB SLoc in the MRP run.

[former_member42743]

Are you batch managed?  If so post the batches to restricted batch status instead of blocked or unrestricted?

A second option is to make a new UD code like "REV", (under review), or "NCR".  These would have no automatic stock posting behind them.  Use them for making the UD and just leave the stock in QI until you complete the investigation.  Then come back via QA12 and change the UD code to the final UD code based on the investigation and post the stock appropriately.

Base the QM metrics on the day the UD code is made, (which is probably what you are doing now).  The UD codes can be displayed in the QA32/33 worklists and give you visibility to the those lots with a "NCR" UD code.

Craig

[Former Member]

Hi Craig,

Could you possibly sent a screen shot of the second option you mentioned as they may be the solution. Thanks,

[former_member42743]

I'm not sure what you want a screen shot of.  The UD code is just another code added to the selected set for the UD.  Should be straight forward for who ever does your QM config. (QS41 and QS51). 

To view in QA32 or QA33 it's just a screen layout variant to display the UD code and maybe posting quantities if you want.

Craig