Stockkeeping Unit within Branch

kamleshji56

Hi Experts,

I was trying to create and stock-keeping unit between the branch, the system (NAV-2016 IN) is throwing an error. below is the case.
Stockkeeping created for - Location From "A" TO location "B", but vice-versa created from Location "B" to Location "A", then the system (NAV 2016 IN) is not allowing the same.

Kindly advise ASAP.

Thanks

Miklos_Hollender

Ugh, last time I looked at this was 10 years ago but I remember that it is not allowing this indeed and for good reason. The whole Requisition / Planning Worksheet things works so that an SKU can be replenished by purchasing, by manufacturing or by transfering from another location and the later is strictly one-way, you replenish A from B like a factory from a raw materials warehouse but not the other way around. So it is only meant for these scenarios when it is clearly one-way, you purchase in A but not in B, so you transfer from A to B.

If you have a different scenario, say, retail shops that transfer to each other goods when one of them is running low, I am afraid this whole requisition worksheet thing will not work (unless they really changed the code since), so there is no point in using SKUs. You probably have to develop something yourself but that sounds like a complicated development, for example, if B and C both have low stocks, which one has priority for transfering goods from A?

On the plus side, while the programming behind filling the requsition worksheet is insanely complicated and never ever even try to customize it, at the end of the day nothing is stopping you from not using it at all and just writing some processing only report that fills out the requisition worksheet for that specific scenario.

NateHatesEDI

What is the error you're receiving?

Miklos_Hollender

Ugh, last time I looked at this was 10 years ago but I remember that it is not allowing this indeed and for good reason. The whole Requisition / Planning Worksheet things works so that an SKU can be replenished by purchasing, by manufacturing or by transfering from another location and the later is strictly one-way, you replenish A from B like a factory from a raw materials warehouse but not the other way around. So it is only meant for these scenarios when it is clearly one-way, you purchase in A but not in B, so you transfer from A to B.

If you have a different scenario, say, retail shops that transfer to each other goods when one of them is running low, I am afraid this whole requisition worksheet thing will not work (unless they really changed the code since), so there is no point in using SKUs. You probably have to develop something yourself but that sounds like a complicated development, for example, if B and C both have low stocks, which one has priority for transfering goods from A?

On the plus side, while the programming behind filling the requsition worksheet is insanely complicated and never ever even try to customize it, at the end of the day nothing is stopping you from not using it at all and just writing some processing only report that fills out the requisition worksheet for that specific scenario.