Knowledge Management

Question:
Hey all you WM batch determination experts,
It appears that batch determination in WM looks only at a storage type at a time and not across the entire warehouse, which is a problem for us. Here's the scenario:
We are on 4.6C.
We manufacture store brand products, so each customer's set of materials are unique by label. We have segregated our warehouse by storage type, each customer having their own storage type.
Because of inventory fluctuations, materials are sometimes stored outside of their normal storage types.
I have set customer's pre-expire date (the date that they will no longer take the product, typically 6 mos prior to real expiration) as a batch characteristic.
Ideally, we would want WM to select the batch with the least amount of remaining pre-expiration ACROSS THE ENTIRE WAREHOUSE. That way, if the oldest batch is somewhere outside of the normal storage type, it would select it.
What appears to be happening is that batch determination is ocurring during the storage type search so that only the oldest batch within that storage type is selected.
Has anyone out there faced a similar issue. Can it be resolved? Can the user exit picking strategy be used to overcome this issue? I hate to write batch determination into a user exit, but I also don't want to obsolete inventory.
If you suggest the picking strategy user exit, can you supply the exit name to use?
Any advice would be greatly appreciated.
Scott
Answer:
Dear SVH (Scott):
This is a very interesting topic. It is hard to answer your question, because you did not say exactly with which logistics process that you are facing the problem.
In fact Batch Determination is almost always done on plant level and in either MM (for Goods Reciepts and other IM Movements) or SD (for Goods Issues).
In PP, it is normally done at the time of release of the Production Order, assuming that your system is configured that way. This is the way that I recommend doing it.
One of two scenarios that I know where Batch Determination is actually performed in WM is where the Batches were not determined for components at the time of the Production Order release, but they are determined after WM Staging, when the Transfer Requirement (for the Production Order) is converted into a Transfer Order (to pick the components to replenish to the Production Supply Area).
Your options for Batch Determination in the PP-WM Interface are well explained in OSS Note #396279. OSS Note #560638 (FAQ on WMPP Interface) is also worth looking at.
As an interesting point, the other scenario where WM Batch Determination is performed in during the running of the RLLNACH1 process/T-Code LP21, which is Fixed Bin Replenishment in WM.
I hope that this helps.
_________________
Ciao,
Sackman
SAP Consultant
Answer:
Hi Scott,
You are right, batch determination happened later than storage type determiantion and it is thus within storage type level.
One way to solve that is: rather than set up customers as storage types, set up storage section, and batch will be searched through all storage sections.
Rgds
Mike
Answer:
Dear MC (Mike) & Scott:
This is why I asked Scott which logistics process he was referring to.
Batch Determination happens at Plant level in the other modules MM/SD/PP first, which is why the Batch is almost always in the Trasnsfer Requirement before it is converted to a Transfer Order.
The only 2 exceptions that I know are the ones I mentioned:
Case A) Production Order when Batch Determination is not done at the
time of Release.
Case B) Fixed Bin Replenishment with RLLNACH1(LP21).
If anyone else knows of any other exceptions, I am always interested to learn.
We can assume that Scott is having a problem with Case A above.
I am almost positive that Batch Determination for these 2 cases will happen after the Storage Type Search has been finished (as Mike says),
and at Storage Type level, EVEN in the case that Storage Sections are being used.
What you could do, is to implement Enhancement MWMTO008 (Storage type search for stock removal), and code in the user exit a search over all Quants which could fulfill the criteria of Material, and then once that preselection was done, you could essentially code the same batch determination logic into the User Exit.
This would force the Storage Type to be selected that fit your batch criteria, and then immediately after, standard SAP would select the correct batch within the WM Batch Determination.
I hope that this helps,
_________________
Ciao,
Sackman
SAP Consultant
Answer:
Actually, this is on the finished goods warehouse side (picking for customer orders) where we are having the problem. Since our goal is to determine the batch as close to the time of the actual pick as possible, we have SD batch determination set up with a selection type of 'N - no selection at beginning of batch determination'. This allows the batch to be selected in WM.
As far as the section vs. storage type solution, we are currently using section to segregate based on case size to facilitate better pallet building during the picking process.
Thank you for your responses. At least I have determined that what I am experiencing is a system "feature" and not the result of our particular configuration.
Right now I am weighing all our options. Have either of you any experience with using the user exit for the picking strategy? If so, can you tell me the appropriate user exit name?
Thanks again!
Scott
Answer:
Dear SVH:
I would summarize your last post by the following statement:
your current problem is created by a system feature AND the
result of specific configuration.
Determine the Batches in the Delivery and your problem is solved.
Normally, there should not be a delay of more than 24 hours between delivery creation and picking and this is usually a short enough period of time to "allocate" a batch to a specific delivery without committing too much stock to early in the process.
Having said that, I do not know the specific business requirements, and there may be very good reasons why you create deliveries substantially in advance of picking. This should be a great exception in most businesses though.
The Enhancement (SMOD) for Own Stock Removel Strategy is MWMTO004, but assuming that you stick with your current process, this will not help you.
Since Batch Determination in WM is done after Storage Type Determination, then I would strongly recommend (as I did yesterday)
Enhancement MWMTO008 (Storage type search for stock removal).
The idea would be that you select that Quant that you would like to pick from according to your idea Batch Determination Criteria.
From here, you will know the Storage Type of that Quant.
With this user exit, you will determine the Storage Type of the Quant that you ideally want to pick.
Once the standard Batch Determination is being performed (for all Quants within the Selected Storage Type), it will determine the Batch of the Quant which you preselected earlier due to the fact that standard SAP system is using the same Batch Determination Logic as you developed in your User Exit.
I really believe that this will solve your problem.
I would be interested to know which final solution that you finally implement.
_________________
Ciao,
Sackman
SAP Consultant
Answer:
Dear all,
If there is not much timing difference between delivery and picking, I do recommend to activate batch search in delivery.
Rgds
Mike
Answer:
Hi MC:
No Question that performing the Batch Determination in the delivery is the preferred solution, unless there is a compelling business requirement against it.
_________________
Ciao,
Sackman
SAP Consultant
Answer:
Hi SVH:
Did you ever resolve this problem?
_________________
Ciao,
Sackman
SAP Consultant
Answer:
Quick question,
R/3, 4.6C Batch managed material (unique at the Material Level - 023)
Question about Fixed Bin Replenishment in WM for LP21 / LP24.
Do I enable this in the IMG, under
Logistics - General=>Batch Management=> Batch Determination and Batch Check
for the Strategy Types=>Define Warehouse Management Strategy Types
Do I use a class of type 023 that has a different name (same elements) than the one used in the Classification view of the Material Master?
(This is the "trick" from SD Sales batch search strategy.)
Then, do I create the Batch Search Strategy - WM (LS51, LS52, LS53)
Batch Management really is one of the 'Dark' Arts
~Vasyl
Answer:
Scott
I found all those answers very positive. Batch determination in the delivery seems to be the best solution.
However, let me give you further inputs. They would be more valid if you are in a test phase than in a going live support. These inputs are focus in your client business process.
1. Instead of considering a storage type for each client, why not considering a storage location; as you know, the storage location with WM can support a logic function, not phisical. With the help of "stock determination strategie" (SPRO > Materials management > Inventory management and physical inventory > stock determination > Define strategies for stock determination)
2. If you don't want to use storage location as a tool, and if the same material are stored for different clients, you can use split valuation. Each valuation type wuold be a client, and the same "stock determination strategie" tool would fit your requirements
I'm not still convinced that batch determination is done after the storage type determination, allthougt this is a minor issue.
REgards
Pedro Bazaliza