on 06-25-2020 8:44 AM
Hello experts,
For our SC PO cycle, I wish to set up auto batch determination, so that during delivery creation from ME2O, the batches are automatically entered in the delivery created.
My custom delivery type has default order type as 'DL', in transaction OVLK.
I have assigned the sales org/Dc/Div combination to sales doc type DL and a search procedure is also assigned.
I am yet to check the "Activate automatic batch determination in SD" for the custom item category being used in my delivery type but will soon do that.
Can some one please guide me regarding the condition type configurations required here:
After all, delivery is an SD element but the delivery here is created w.r.t a Subcontracting Purchase order (item category L), so doubtful.
I do not know if you came across this blog: Elasticity of batch management in subcontracting using delivery.
Part of the steps are about EWM processing, but at least the rest seems to be applicable to your case.
From what I understood from it and from the referenced notes, you will not see changes to the popup in ME2ON (because such feature is not supported), you have to do the determination in the background, in shipping.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I have tried with ME2O also. If I add the storage location in the PO for the given component (component list for the SC PO), then during delivery creation, the storage location is obviously picked up. The batch field is empty. Now, if I go ahead with the delivery creation, there is no batch assigned in the delivery created like this.
Veselina:- In your comment, you have mentioned that I have to do the determination in the background, in shipping. What do you mean by that? Do, I have to do something after delivery creation, which will assign the batches in the delivery, after which I can start with my processing of the delivery from VL02N?
SD is not really my core area, so inputs will be appreciated.
Thanks.
papri.rudra29 by "in the background" I meant configuring automatic batch determination in the delivery document. The process is also explained in the blog for which I provided a link.
For the business users batch determination will be done without user interaction (at least, initially, at delivery creation; if they want to use different batches after the delivery is created, they can still do this).
If you have configured everything as described in the blog and it still does not work as expected, maybe you can try changing the condition record not to use dialog processing, but I doubt that this setting is the root cause.
Only one thing comes to my mind.
While doing "Activate Automatic Batch Determination in SD
under Logistics - General
Batch Management
Batch Determination and Batch Check",I did only for the second item shown in yellow here, not the first one (circled in blue).
I thought this is an SC PO cycle and not related to a sales order. Do you think, I should maintain this setting too?
Hello experts,
I went ahead and maintained the above mentioned customization also : auto batch det. for sales order items for my delivery type's item category ZLSN but still no difference.
During delivery creation, the message appears at the bottom of the screen that "Batch det. for material #...." but in the delivery, no batches actually get assigned.
I am beginning to wonder if all these settings work for only SD documents only or does it actually work for SC PO at all?
My storage location is WM managed but not EWM.
Hello experts,
I have a question about the way the condition record for the batch determination is to be maintained.
I was able to get the batch assigned directly during the delivery creation but the behaviour is not consistent.
In sorting, I have only one char in my sort rule: Expiration date for the batch.
Now, if my material has two batches which have different expiration dates, then one of them gets picked up automatically For one of the materials, there were two batches, one of which had expiration date in April 2024 , while the other had expiration date as April 2025 but still the second one got picked up. As per 'ascending' in the sort rule, shouldn't the one with April 2024 be the first choice?
For that I wish to add another char to the sort rule, say, the batch number or date of batch manufacture. Unfortunately, these chars are not present in the selection class. Even if I manage to add this new char to the selection class in question, will system first check as per the first char and then go on to the next char?
My business wants to follow the principal of FIFO, i.e, the batch with the earliest expiration date should be chosen first.If the expiration date happens to be same,then batch name wise, the selection will be made and so on.
Hello experts,
As I explained earlier, I am trying to make the batch pick up automatic ,during creation of delivery , from ME2O, for my Subcontracting PO cycle.
I have made the following settings under tcode OCHA for the same but not getting the desired result yet.
[I had earlier checked that the default order type for my SC delivery type was DL]
Still, when I go to ME2O and select the checkbox for my component and click on 'create delivery', the pop-up opens up just as before. Neither sloc nor batch is proposed by the system.
What do I need to do here further?
Thanks and Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello papri.rudra29
You want to do batch determination in delivery, hence you need to define your condition table in SD, not MM. For you scenario I'd include at least plant field into the condition table.
Definitely you need to create batch determination condition in VCH1. That's where you define your batch search and sort criteria.
Best regards
Dominik Tylczynski
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.