Hi Swapnil, Shipment is currently used for Delivery and Goods Inwards. Why would you want a Shipment for Inventory Transfer?
Regards, James Yong On 2017-10-16 21:32, Swapnil Shah <[email protected]> wrote: > Yes James, > ITH should work. I would prefer to have ITH tightly coupled with > InventoryTransfer(IT) i.e. even in case of single item transfer create > corresponding entries in ITH and IT both to maintain data integrity. Also, > We can try tying up Inventory Transfer with Shipment through ITH itself or > a separate entity e.g., InventoryTransferShipment. > > Thanks & Regards, > Swapnil > > -----Original Message----- > From: James Yong [mailto:[email protected]] > Sent: Sunday, October 15, 2017 9:26 PM > To: [email protected] > Subject: Re: RE: Quantity missing for inventory transfer records > > Hi Swapnil, > > Another possible solution is to have an header entity, e.g. > InventoryTransferHeader (ITH), containing additional or common info > related to the group transfer. > For group transfer, ITH is created and each InventoryTransfer will contain > a FK to ITH. > For single transfer, ITH can be empty. > > Regards, > James Yong > > On 2017-10-14 18:59, Swapnil Shah <[email protected]> wrote: > > Folks, > > One very frequent use case that we encounter is that any transfer > > request initiated from one facility to another is generally for > > multiple products as they all need to go in a single shipment against > > transfer request so as to be cost effective. > > > > Current schema has the limitation that any given inventory transfer > > can only be for single inventory item (and hence only one product). > > Would it make sense and be feasible if we enhance the existing design > > such that multiple products/inventory can be tied with a single > > transfer > > (InventoryTransferId) request (possibly by having InventoryTransferId > > + InventoryItemId as PK) and shipment is tied up with it as well. Of > > course by leaving a proper audit trail via InventoryItemDetail etc. > > > > Let's share any further thoughts or similar business cases and then we > > can try to support it if it is generic enough. > > > > Thanks & Regards, > > Swapnil > > > > -----Original Message----- > > From: James Yong [mailto:[email protected]] > > Sent: Friday, October 13, 2017 9:36 PM > > To: [email protected] > > Subject: Re: Quantity missing for inventory transfer records > > > > Hi all, > > > > It is better to add InventoryTransferId column to Inventory Item > > Detail > > (IID) table so that we easily link the IID record to the Inventory > > Transfer table. > > > > What do you think? > > > > Regards, > > James Yong > > > > On 2017-10-13 23:18, "James Yong"<[email protected]> wrote: > > > Hi Suraj, > > > > > > Shouldn't the transfer detail be stored at Inventory Item Detail > table? > > > > > > Regards, > > > James Yong > > > > > > On 2017-10-13 16:44, Suraj Khurana <[email protected]> > > wrote: > > > > Hello, > > > > > > > > While creating inventory transfers, a new inventory item is > > > > created and successfully gets updated after completing inventory > transfer. > > > > As per current implementation, we don't store transferred quantity > > > > anywhere in *InventoryTransfer *entity and quantity is only > > > > available on the newly created inventory item. Problem is, it gets > > > > deluded on time being and user won't get exact quantity for which > > inventory transfer was initialized. > > > > > > > > IMO, we should maintain transferred quantity at *InventoryTransfer > > > > *entity as well for proper history maintenance of records. > > > > > > > > Please share your thoughts on this. > > > > > > > > -- > > > > Thanks and Regards, > > > > *Suraj Khurana* | Sr. Enterprise Software Engineer *HotWax > > > > Commerce* by *HotWax Systems* Plot no. 80, Scheme no. 78, Vijay > > > > Nagar, Indore, M.P. India 452010 > > > > > > > > > >
