Hi Juergen L,
We post good receipt with VL32N. All scenerio, there are two plants. In first plant, user change sled to increase material life but do not change production date in batch master data. After that, user create outbound delivery (cross company sto --> 641 movement type is working) . In second plant, another user create inbound delivery to good receipt so we use handling unit management. Good receipt is done with inbound delivery and finally turn back before the changing sled. Because, in good movements sled is recalculated from manufacture date + shelf life. We want to prevent recalculation in this process.
Sir, i checked oss notes , manufacture date is not empty and problem is not related with checking of sled. I hope that i can explain all details.
I find a oss note 616028 - FAQ: Minimum shelf life processing , there are two scenerio like given belowed. First scenario is related with system message , second is related with user exit.
I did not try implemantion of these solutions, what you think these might be useful for this thread.
****
- How can I avoid recalculation of the expiration date in the case of goods movements?
Start Transaction OCHS (Define properties of system messages) and change the category of message 005(12) from 'W' (Warning) to 'E' (Error).
- It is possible to control the shelf life processing depending on the movement type (Transaction OMJ5). How can I distinguish between different business transactions within a movement type with regard to shelf life processing (e.g. Movement type 101: GR goods receipt for purchase order / for production order) ? ?
Within customer exit EXIT_SAPLVBMD_001 (called in function module VB_MAINTAIN_MHD) you can control recalculation or expiration date using the indicators C_CALC (calculate) and C_CHECK (check). For more information refer to the documentation of function module VB_MAINTAIN_MHD.
Regards.
M.Ozgur Unal