SD Batch Selection Criteria not Working (Bug?)

[Former Member]

Hi gurus,

Am i encountering a bug? What OSS note can fix my below inquiry.

e.g. I got a sales order with Req Del date 7/1/2013 with 1200 pcs

Batch A - Manuf date is 1/1/2011     SLED is 1/1/2013      with 1500 pcs

Batch B - Manuf date is 1/1/2012     SLED is 1/1/2014   with 1500 pcs

My condition record selection criteria is > 10 d, sorting is FEFO (ascending)

The OD batch still gets BATCH A though it was already expired. On OD selection criteria it didnt add the 10 d also on the Req del date. it simply shows the 7/1/2013 instead of 7/11/2013.

Before it was working good, getting Batch A as the expected batch. Way back when Batch A data is detailed as below.

Batch A - Manuf date is 1/1/2012     SLED is 1/1/2014      with 1500 pcs

But the time i changed the manuf date to 1/1/2011 and SLED to 1/1/2013 to make it expired, i now get the unexpected batch determination. It also affects other material, batch determination now are not working properly.

I am in DEV client (modifying my test samples).

Regards.

Deane

[JL23]

I dont see anything wrong here. 1/1/2013 is still the first batch that will expire.

Of course it is logically expired today as we have already April. But this is not considered in that strategy.

SAP expects that you take appropriate action if a batch has expired. E.g. by changing the status from unrestricted to blocked. or creating an inspection lot for further analysis and eventually prolonging the expiration date.

[Former Member]

Hi sir

Required delivery date is 7/1/2013. Condition record on selection criteria is LOBM_RLZ must be > 10 d

It supposed to get those not yet expired on the date July 11, 2013 picking Batch B instead of A and showing also 7/11/2013 and not 7/1/2013 (adding 10 d) if im not mistaken.

[JL23]

Sorry I got screwed up with the date format, we write it DD-MM-YYYY format.

Had you done your customizing according to OSS Note 33396 - Batch determ.: Selection w. remaining life LOBM_RLZ

[Former Member]

Yes sir, set up was according to mentioned OSS. Now currently checking other OSS mentioned in 33396 to implement. I dont think its a standard behavior. We want to use the SD batch search strategy to avoid getting expired items. The unusual behavior started when I manually change the manufacturing date in batch (MSC2) same with the SLED to make it expired.

[JL23]

As these object dependencies is a kind of coding, it is a potential source of errors, maybe the situation that the expiration date is in the past is not covered in the calculations.