Please ignore ma previous message in this thread (for now)... it's not
as urgent as I thought because I've already found a good solution for
the GL posting routine.
We will discuss the best way to go at later point.
Jacopo
Jacopo Cappellato wrote:
I would like to definitely fix this before we
I would like to definitely fix this before we implement the GL posting
service for inventory variances.
Here is my attempt (draft) to implement David's notes on this:
1) deprecate InventoryItemVariance and replace it with a new entity:
InventoryVariance with the following fields:
inventoryVaria
David E Jones wrote:
I think this change is fine. It would throw a little kink in the special
handling of the financial impact for this sort of thing. However we do
this we just need to make sure it's very clear that the change is due to
inventory lost/found/damaged/etc. That would be in the
I think this change is fine. It would throw a little kink in the
special handling of the financial impact for this sort of thing.
However we do this we just need to make sure it's very clear that the
change is due to inventory lost/found/damaged/etc. That would be in
the reasonEnumId.
M
+1 from me
Scott
On 08/11/2007, Jacopo Cappellato <[EMAIL PROTECTED]> wrote:
> What about deprecating the InventoryItemVariance entity?
> It seems duplicated by the newer InventoryItemDetail entity: we could
> use the latter with the following mapping:
>
> InventoryItemVariance.varianceReasonId -
What about deprecating the InventoryItemVariance entity?
It seems duplicated by the newer InventoryItemDetail entity: we could
use the latter with the following mapping:
InventoryItemVariance.varianceReasonId --> InventoryItemDetail.reasonEnumId
and
InventoryItemVariance.comments --> Inventor
