Skip to Content

Is it possible to Normal UD a batch which is expired?

The below stock movement has happened.

1-Jun-17 -> This batch was moved from unrestricted to QI (Generating inspection lot)

06-Jun-17 -> Batch Expired

25-Jun-17 (11:22:31) -> Batch SLED was not changed but this batch was normal UDed and stock auto posted from QI to unrestricted

25-Jun-17 (23:00:30) - A daily Batch job set this batch to 'restricted'

My Questions are

1. Why didn't the batch job set the batch to "Restricted" on 06-June-17 23:00:00?

2. How did the system allow the batch to be normal UDed on 25-June (after Batch expiry)?

Please advise

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jul 14, 2017 at 04:35 AM

    1. On 25th June, you already had an inspection lot in QI, which was created on 1st June, this is in-turn before the Shelf Life expiry of the batch. I believe this is a logistic MvT related inspection lot and not a recurring inspection lot which has put the stock to QI. So it was expired on 6th June, during UD the user should know what has to be done with this material. But if the user has put UD = A, then as per process the material was put to unrestricted stock.

    2. When Recurring Inspection lot (09) got created by the batch job, I think, batch job variant controls the check like whether to put the batch to blocked stock or not, and it did exactly the same thing, as the expired stock check is found.

    Normally, the recurring inspection lot creating batch Job has 30 days search which runs to move the batches to QI/Blocked stock. But I see that you were able to receive the stock in Unrestricted stock. It seems to be like you received near to-be expired materials via logistic process. Also, when the stock is in QI, your batch job didn't pick it as you had a chance of putting it to Blocked stock for UD screen.

    You can think of two new enhancements to fix this gap -

    a) If materials with batches having SLED near to expire, they shouldn't be accepted during GR process.

    b) During UD, if the batch is expired, then UD = A shouldn't be allowed.

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 18, 2017 at 06:04 PM

    Just a few clarification "rules" on the batch monitoring program.

    1) It only considers stock in unrestricted inventory. Nothing else. Since your batch was in QI stock, it was not even reviewed.

    2) UD's have no interaction with SLED date. 09 lots only change the next inspection dates, not SLED dates. SAP assumes that the people you have are knowledgeable enough to not post an expired batch to unrestricted stock unless they are going to do something with it immediately.

    3) There are times you might post an expired batch out to UR. For instance, if you are immediately going to consume it in a rework order. Businesses are different. Each business has their own rules. SAP can't assume every business, (cars, chemicals, foods, planes, minerals, steel plate, glass, wine, beer, etc etc..) wants to block expired stock from going to UR from an inspection lot UD. If that's your business rule, then train your users to not do that. Or, if your risk is to high, or the employees to untrainable, then put in a customization, user exit, follow-up action etc.. that blocks that. But then remember.. you set up a rule that makes the process more inflexible... not SAP.

    Add comment
    10|10000 characters needed characters exceeded