Batch-specific / -neutral available quantity in storage type when picking for supply to produciton

[castin]

Customer wants to pick whole pallets and the pallets have several batches on them. When setting rounding to storage type or pocess type it will round to want is need to the next batch and that is all. So if there are the batchs and the second batch satifies the order and it rounds to that batch the last batch on the pallet is not requested.

We have changed it to Batch Neutral storage type and now it requests everthing on the pallet. My question is can you still use the FEFO rule for stock removal. Some testing has given different results and just not sure if the data is bad,

@Christian_Ries 

[TobiasAdler]

Hello castin,
Can you please help me to understand your process and setup better?
What was your original issue and what is different with the storage type being set to Avail. Qt. Batches = batch-neutral? With batch-neutral the created WT normally contains no batch information (as the available stock contains no batch). Or did you model this differently?
Thanks, Tobias

[castin]

the customer needs to be able to pick full HU that have batch managed products on them. The HU can have several batches on one pallets. In the first testing with batch-specific storage type we set rounding on the stage for production process type. if the PMR was for 600 and there were 3 batchs on a HU each with 500lbs will take the first 500lbs and the remaining PMR 100lb would take the second batch and round to the 500lb of the batch. The issue was the third batch would not be requested which cuases a issue. The second test was to use a batch-neutral sotrage type that still had batch managed materials. In this test with the same PMR of 600LBS it would request to pull the 1500lbs on the pallet and operator is requested to scan each batch on the pallet and enter the qty totalling the full PMR of 1500lbs. This works the question was does it still use FEFO in the warehouse for selecting batches. WHich I beleive it does after some further testing.

[TobiasAdler]

Hello castin,

[TobiasAdler]

Hello castin,

Thanks for your response. Unfortunately, I have to admit that I still did not fully understand your example. So, let me try to rephrase.

First, you started with a PMR requesting 600 LB. On one source bin you had three batches on one pallet. Simplified available stock looks like this:

• 500 LB Batch001, SLED 31.12.2025
• 500 LB Batch002, SLED 31.12.2026
• 500 LB Batch003, SLED 31.12.2027

The system proposed to pick 500 LB of Batch001. As you set up to round up, the system additionally proposes to pick 500 LB of Batch002. That’s it. But you wanted to let the system round up to the whole quantity on the pallet.

Second, you switched to a storage type with Avail. Qt. Batches set to batch-neutral. Additionally, I assume that you set up rounding to Round WT Quantity to Available Quantity. Is that correct? Next, it is open to me how you set Mixed Storage in Storage Bin/HU: Shelf Life Expiration Date on storage type level. This will influence how available stock looks like. I assume you set it to Allowed - Earliest Date Dominant. Thus, simplified available stock in the second case would look like this:

• 1500 LB (no batch info as batch-neutral), SLED 31.12.2025

When creating the WT for your PMR requesting 600 LB, the system would round up to 1500 LB according to the available quantity. During WT confirmation the picker would have to specify the batches picked.

If there would be multiple stock items on different bins with different SLED (see comment on Mixed Storage in Storage Bin/HU: Shelf Life Expiration Date on storage type level above), the system can sort available stock based on their SLED depending on the stock removal rule – in your case FEFO. You can see the SLED of available stock in the app Warehouse Monitor using e.g. node Stock and Bin -> Available Stock.

Best regards, Tobias