warehouse picking more then required

DanyLeemans

In our warehouse we have pickings and putaways for both finished products and raw materials.
In our company, pickings and putaways for finished products are always done in unit of measure PCS (pieces). People in the warehouse are not allowed to pick more then the quantity on their scanner (picking list). This works fine.
For raw materials it’s a completely different story. Some raw materials are delivered in M (meters) or KG (kilograms). Each roll can have a different length (ex. 470 to 525 M) or weight (ex 695 to 760 KG). All raw materials have a barcode label with the exact quantity, length or weight.
The production department can order for example 500 M, but if a roll measures 530 meter we deliver that roll. Unfortunately Navision doesn’t allow us to pick that roll because the quantity is higher then the outstanding qty.
I want to be able to pick more then the outstanding qty (maybe between certain limits like 10%), update my shipment line and update my sales order line to the new quantity.
The same story for putaways.
It’s possible that we order 2000 M but we receive 2100 M. First we create a whse. receipt based on the purchase order(s), scan all the pallets on the receiving zone (this scanning updates our Qty to Handle on the whse. receipt) and then we post the receipt. But as you know, Navision doesn’t allow us to receive more then the outstanding. qty.

In our company, we have different “Navision” locations for raw materials and finished products. We can use this location as a trigger to allow or not allow “over-receiving” and “over-picking”.
Small detail: all whse. transactions (Pickings, putaways, internal movements, bin counts, etc.) are done with scanners (with built-in PDA). These RF-scanners are linked directly to the nav. database. The advantage is “no more papers”, real time error checking because each box is scanned and checked with the picking list, etc. The “disadvantage” is that there is no room to write something down on a paper and ask (or forget to ask) it to a supervisor afterwards (for ex. I took a roll of 530M while there’s only 500 M to take on the picking).

Any suggestions to make this work? I can imagine that this can be a huge modification to the standard Navision code. Maybe it’s a good idea to create a new codeunit with all these modifications and leave the original codeunit as much as possible “untouched”?

Thanks in advance,
Dany

fl

Some time ago, I did make a solution to receive "within limits". Not only more will be accepted within prefixed margins, but als less (think of you ordered 500kg, but they deliver a coil of 485kg) could be nicely registrated. It was not combined with WMS, so directly on an the purchase order. For every item there can be a limit range placed on the item card. If new item are created they inherite this from the item category. The same could be done on location in stead of item. It took me some time to solve all the problems, but it works well at customer site. My opinion at that moment was already that it even might be more simple by using WMS.

Yes all the modifications should be made in codeunits, but I would NOT create new codeunits, because you need then to change also all the code that is calling these new codeunits instead of the current ones.

Kowa

One of our clients has a pick override function. They wanted it because sometimes a customer orders 9, and there are 10 in the package, and then the warehouse employee picks 10 to avoid breaking up the package. Within limits , it is possible. But if the customer has reached his credit limit with the order as it is, should the warehouse employee be allowed to accecpt the credit limit warning ? Usually , no one in the warehouse is allowed to do this.
We disabled the normal credit limit warning, and changed it to just one check upon order release.

If the item has a special price for 10 or more (you will have to increase the order quantiy and add a new field "Customer Order Quantity" to the sales line to document the change ), is the customer supposed to get he lower price for 10 or the 9 he ordered? Or maybe the price for the 9 was a special offer, fixed up on the phone talking with the customer, and the normal price for 10 will be higher ? If you want to freeze the price, you need new functions in the sales line to avoid a new sales price being calculated when the quantity is changed.

There was no need to create new codeunits for this, just some new fields and functions.

RanaDemashkieh

I miss understood you sorry :oops: