webERP Forum

Full Version: Stock "on the way"
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi all:

When transferring stock from location FROM to location TO, many times there is a time between the goods leaving FROM until the goods arriving and checked at TO (in our case up to 2 days).
webERP does not handle it OK as it is in FROM location until it is received at FROM location, but most of the time it is a flase scenario.

Suppose we have 3 itemA at FROM.

We need to send 2 to locationTO1 and 2 to location TO2 (according to reorder level, as it works out by StockDispatch.php, or by any other reason as 2 users preparing the transfers at the same time, etc...).

So, we prepare a Transfer dispatch for 2 itemA going to TO1. It means NOW we have available only 1 item at FROM location (as 2 are being shipped to TO1), but webERP still thinks we have 3 available at FROM, allowing to prepare the second dispatch, but we do not have enough stock, fooling the check at line 73 at StockLocTransfer.php... Until they are received at any TO location, weberp still takes them as "available"

It could be solved with a "On the way" status, meaning that goods have left (logically or phisically) the FROM location but not yet received at TO location, so are no longer available at FROM (and also not available at TO until received).

Adding a field al locstock table (qtyontransit) and the StockLocTransfer deducting from quantity and adding to ontransit fields should do the trick.
Later on StockLocTransferREceive the logic starting at lines 288 should take this new field into consideration.
Also StockDispatch.php should be modified around line 182 to update the locstock table with the ontransit information.

These 3 are the main changes I see but probably there are many others. Any other ideas, POV's or problems detected with this approach? We'll be happy to code it or to fund this development.
Hi, Richard:

It's a good point.

I thought there are no other tables modification is necessary. We can get the pending quantity from loctransfer table by shipqty-recqty.

If so, we need to add some code to delete or edit the Location Transfer Note. Otherwise, users cannot handle the wrong input.

I suggest to revise this part to add feature:

1) Pending or on the way transferring report.
2) Scripts to reverse or modify the Pending or on the way transferring report.
3) Fixed the bugs without considering the pending or on transferring quantity of each items.

Any suggestion will be appreciated!

Best regards!

Exson



(02-22-2012 05:32 PM)PakRicard Wrote: [ -> ]Hi all:

When transferring stock from location FROM to location TO, many times there is a time between the goods leaving FROM until the goods arriving and checked at TO (in our case up to 2 days).
webERP does not handle it OK as it is in FROM location until it is received at FROM location, but most of the time it is a flase scenario.

Suppose we have 3 itemA at FROM.

We need to send 2 to locationTO1 and 2 to location TO2 (according to reorder level, as it works out by StockDispatch.php, or by any other reason as 2 users preparing the transfers at the same time, etc...).

So, we prepare a Transfer dispatch for 2 itemA going to TO1. It means NOW we have available only 1 item at FROM location (as 2 are being shipped to TO1), but webERP still thinks we have 3 available at FROM, allowing to prepare the second dispatch, but we do not have enough stock, fooling the check at line 73 at StockLocTransfer.php... Until they are received at any TO location, weberp still takes them as "available"

It could be solved with a "On the way" status, meaning that goods have left (logically or phisically) the FROM location but not yet received at TO location, so are no longer available at FROM (and also not available at TO until received).

Adding a field al locstock table (qtyontransit) and the StockLocTransfer deducting from quantity and adding to ontransit fields should do the trick.
Later on StockLocTransferREceive the logic starting at lines 288 should take this new field into consideration.
Also StockDispatch.php should be modified around line 182 to update the locstock table with the ontransit information.

These 3 are the main changes I see but probably there are many others. Any other ideas, POV's or problems detected with this approach? We'll be happy to code it or to fund this development.
Hi all:
This new specification was coded by Tim few months ago and fully tested, so we can consider it solved and closed.

Thanks Tim!
Would be nice to have an intermediary location defined for transfers so we could recycle the existing logic i.e. an intransit location - just like any other location. However, this location is used to hold the goods until received by location.

Not seen this code committed yet?
Hi Phil:

The code is commited and tested.
StockStatus.php already show qty on transit between locations.

From our POV a new location is not needed.
Reference URL's