Expiry Date entered during GR and not at TO creation !

[Former Member]

Hello Experts ,

We are using SELD picking strategy and also batch management is active.

Expiry  date is being maintained automatically at the time of GR.

So during picking  will system correctly pick the batch of a material with (FEFO) minimum shelf life ?

or

Do i need to maintain the expiry date again during Transfer order putaway screen ?

Please give the clarity and prerequisites fro the same.

Thank you in advance.

Regards,

[Former Member]

Hi OM Sharma,

Batch master data are created or updated from inbound delivery
processing not before GR posting. So you will not find data like
expiry date, updated in VL32N, directly in batch master data.

Please read the logic of update from expiry date and date of

manufacturing in note 1167938 in "solution long text".

BR,

Enrique

[Former Member]

Hi Enrique,

Thanks for your reply.

Shelf Life is automatically updated at the time of MIGO against PO(101 mov type)

It will get updated in Batch master(MSC2N) after migo posting

My question is do we again need to maintain the Shelf Life during TO creation ?

So that during WM picking activity it will pick the batch with FEFO strategy

Please throw some light on this.

Regards,

[MANIS]

No, you do not need to specify the shelf life during TO creation, If your picking search strategy is H-Shelf life expiration date and you are doing the batch determination at WM level then in that case system will sort the Batch based on the Shelf life expiration date and whichever is coming first it will start allocating that

Make sure that Batch search strategy is defined at WM level then only this is effective

[Former Member]

Hi OM,

Thanks for the update!

Could you please refer to the below with regards to the use of FEFO picking

stragegy:

******************************************************

If you are trying to use stringent FIFO with SLED date, this means you

want the system to always pick the oldest quant according to SLED

date. If so then your picking strategy should be blank " " and you

add the wildcard option *** to the storage type search, this will ensure

all storage types are searched, or alternatively you can define one

or a selection of storage types here.

Then, in order to make sure that the SLED date is used to identify

the oldest quant you will need to activate the Stringent FIFO with

SLED date flag.

You can do all this in: Picking Strategies -> Define Strategy for

stringent FIFO.

If it is a variation of this strategy that you need then you may need

to activate a user exit on the storage type. The userexits

for own removal and placement strategies are MWMTO003 MWMTO004.

******************************************************

BR,

Enrique

[Former Member]

Hi Manish,

Thanks you understand my requirement.

We have defined batch search strategy in LS53 tcode .

Please correct me if am going wrong.

Also let me know is there anything which i have missed out.

Regards,

[MANIS]

you are right we define the WM batch search strategy in LS51, with that setting what is the result are you getting

[Former Member]

Hello Enrique,

Strigent FIFO mean it will search the oldest quant wref to GR date.

SLED is totally different concept.

Regards,

Olet Malla