cancel
Showing results for 
Search instead for 
Did you mean: 

SLED /Manufacture date update.

Former Member
0 Kudos

Hi Gurus

We have some issue in SLED . Production done and batch is upadate with manufacture date and expiry date. later this was stock tranfered to other plant ( Australia) having received a batch in Australia & updated the manufacture date & expiry date correctly, a quantity of the same sku/batch was, one month later received in India and when they performed the receipt (MIGO transaction) entered different Manufacture date / expiry date, which has apparently updated the dates on the batch details in the Australian plant.

Actually, while doing the MIGO this is update manually, so the the batch is tagged to the wrong expiry date.

Is it possble to control this from manual override, to control the wrong entry.

Santha

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I am not very sure about what can be done but when it comes to shelf life expiration of a batch following user exits are available

CIFSHLF1 Customer Exits for Shelf Life

SAPLMHD1 Shelf life expiration date

Also you can put check in MSC2n when manually overriding from one plant to another.

Former Member
0 Kudos

Is it possible to put a check in MSC2n when manually overriding from one plant to another,with out user exit.? Or can we do any batch level control.

santha.

former_member42743
Active Contributor
0 Kudos

You can use a check (via a user exit), in MSC2n but that won't solve your problem. It is that you are entering a different manufacture date in the MIGO transaction when receiving the material. So that is where you need the check to prevent that. Again, you'll need to ask a MM person about available user exits or checks for MIGO.

FF

Former Member
0 Kudos

Try exit;Use :EXIT_SAPVBMD_001 which triggers at the time of MIGO and you can do some checks on the dates related to Batch.

Thanks,

Ram

Former Member
0 Kudos

Hi,

Check the Enhancement SAPLMHD1

It should meet your requirement,

Navin

former_member42743
Active Contributor
0 Kudos

No. The receivers need to be trained that if they receive batch from another plant, and it is an SAP batch, they should not update it. They are provided warnings at the time of receipt that the batch already exists which should clue them in. In addition, the manufacture date from Australia should have been correct and the expiration date would be correct anyway. So I would be more concerned about, and inquiring as to how, where and why they got the manufacture date they used instead. Having a mfg. date, and hence the expiration date of a batch is a very serious issue and violation of most company procedures, not to mention of regulatory and customs agencies.

I'm sure there is probably a user exit that can used to check the data before saving. You should check with a purchasing person to check the available user exits for MIGO if you want to go that route.

FF