Aged Controlled Inventory - Bad Age?

[VortecCPI]

AgedControlledInventory.php

This report is showing data based upon oldest stock but I think it should be showing data based upon newest stock (latest received - FIFO).

   

I used MAX(stockmoves.trandate) AS trandate to fix if for our case.

   

Note Age was not using newest stock.

[TurboPT]

Instead of MAX, would adding:

Code:

trandate DESC

To the end of the ORDER BY clause make any difference?

[VortecCPI]

Not in this case. For FIFO I need to use MAX(). Perhaps a drop-down so the user can choose ALL / FIFO / LIFO?

[VortecCPI]

This is not the answer to the problem as I just issued stock and now it shows today's date.

[TimSchofield]

As I recall the aim of this inquiry was to show all batches, with the age of each batch, so as to see at a glance whether you had old batches that needed to be used or obsoleted. However a quick look at it seems to show that isn't working properly.

I like Paul's idea of having the LIFO/FIFO/All option, and maybe we should include an option to show only batches where the expiration date has been breeched, or is about to be breeched?

Tim

[VortecCPI]

In the mean time I added UoM to the table.

When we first started with webERP we noticed a few places where UoM was not shown so we added it to our stock description. In my opinion this is bad practice so having it shown in as many tables as possible is a good thing. In my opinion any time we show stick we should show its associated UoM.

---

I believe my issue is due to receipt of inventory with the same Lot/Batch number on two occasions. The first receipt has come and gone (old age) and the remainder of the last receipt (new age) is still in the warehouse. The report is showing the age/date for the first receipt instead of the last receipt.

Perhaps I have a very odd case here? Below is table data:

   

[TurboPT]

As I recall the aim of this inquiry was to show all batches, with the age of each batch, so as to see at a glance whether you had old batches that needed to be used or obsoleted. However a quick look at it seems to show that isn't working properly.

I like Paul's idea of having the LIFO/FIFO/All option, and maybe we should include an option to show only batches where the expiration date has been breeched, or is about to be breeched?

Tim

Those ideas sound good to me too.

[TurboPT]

Paul, in the code changes (I can't cross-check with sourceforge at the moment, 503 error says repositories are down -- been most of the day), and SVN is not giving me a diff to the previous version.

Adding the units pieces are ok.

But is the createdate replacements with using trandate intentional? ... as I see that createdate is to be removed from the SQL as well.

[VortecCPI]

Paul,

We are using 4.14.1 for production so I didn't check the version in SVN.

I will do it right now...

PB

---

No can do as our schema is old and does not have createdate.

---

Right now we can not afford the time to move all the data over to the SVN version.

This is the problem with mixing bug fixes with new features in the main Trunk...

[TimSchofield]

This is the problem with mixing bug fixes with new features in the main Trunk...

Couldn't agree more. I never did understand why we stopped having the stable branch. I have tried hard to find someone to maintain one.