This website is not affiliated with, sponsored by, or approved by SAP AG.
3 posts • Page 1 of 1
I have mix-similar issue than describe on these posts :
http://www.sapfans.com/forums/viewtopic ... 6&t=355424
From same produce material A, my custmer C1 and C2 define different shelf life: Let's say :
C1 = 12 months
C2 = 18 months
Business do not want to generate a material A for C1 and material B for C2, juste because they do not require the same shelf life.
How could I deal this with ?
Remark: Batch determination on delivery process is not my point here.
My main goal is to print the right "customer SLED", even if it's the same batch number produce and delivered for C1 and C2.
Thanks for any specific idea!
I am desperate to deal it in std way!
Where do you print your SLED? Is it only on the COA?
If so you could do something similar to what I suggested in the posting you referred to, the SLED by country.
Remove the SLED from any header portions of your COA. Add characteristic LOBM_HSDAT to be outputted as the first characteristic in a profile assigned to customer A. In the profile, have the text for the characteristic taken from the profile where you define it as "Exp. Date:". Or whatever you want.
Setup a second general characteristic (EXP_18MONTH), that references field MCH1-FVDT1 (or MCHA-FVDT1 depending on your batch level). Create a copy of the above COA profile but assign it to customer B. In the profile, replace LOBM_HSDAT with the new characteristic, EXP_18MONTH. Have the text for the characteristic taken from the profile where you define it as "Exp. Date:". Or whatever you want.
Now use a user exit so that everytime the Expiration Date is changed, the Date 1 field (FVDT1) is updated with the 18 month expiration date. The date 2 field (FVDT2) could be used for 24 month expiration date. And so on. You basically decide which of those date fields you want to use for which type of expiration date. But you need a standard convention or business agreement on this.
You can look at using user exit EXIT_SAPLVBMD_001 (Shelf life expiration date) for this. I think it is run everytime the expiration date is changed or updated.
If you need to print the expiration date on labels, or other paperwork, you will have to modify them to use the correct field or batch characterisitic. So you'll need a custom label for the customers that require the different expiration date.
Hope this gives you some ideas.
Thanks Craigs for your ideas.
Today, our business process calculate a SLED as an internal Self Life from material.
The cust-SLED have to be printed on every document (label, CoA, delivery note probably, etc.). Technically, I would like to avoid to write a "calcula" in each forms ... but prefer to store the cust-SLED dependant somewhere in SAP linked to the batch. A Z classification-characteristic or cust field FVDTx ... could be a solution, but not so easy.
I would definitely prefer to convince business to create a new material ...
3 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest