Regarding you 2nd Question, please read 
https://www.moqui.org/m/docs/mantle/Mantle+Structure+and+UDM/Product#asset---receipt-mantleproductreceipt.
 It can help you to understand how asset entities are designed.


On 2021/10/21, 3:14 AM, "pratyush Giri" <[email protected]> wrote:

    Hi Inventory Experts,


    1st Question
    ===========
    I am trying to move a serialized product from one location in a facility to 
another location in the same facility. What I observe is that the process 
creates another inventory item with the same data where the location has been 
changed from A to B. What surprises me is that the status on both the rows 
shows up as  INV_AVAILABLE and also the ATP and QOH both show 1. Looking at 
this Entity it seems like I have 2 of the same items where I have only 1.  

    What am I reading wrong here and how this should be read?

    2nd Question
    ===========
    I received the same product (say Prod-1)  with the same lot (LOT-1)  
twice., once with 100 and again with 50 quantities.  So I received them twice 
to the same location (bin/rack etc all same). I see that it creates 2 inventory 
items with different quantities 1 row with 100 and another with 50). Now if I  
receive them together, then it creates one inventory_item_id with quantity as 
150. Why is this? Should it not be one inventory item id with quantity 150 and 
it should not matter how I am receiving them. The way I am looking at inventory 
item entity is that given a facility, location, and product, and a lot(if 
exists), it should tell me how many of these items are available.


    3rd Question
    ===========
    I want to have a 360-degree view of my products, i.e., how they came into 
my facility, what has been done with them including stock and inventory 
transfer, and finally where did they go (customer when s/he bought it). I do 
not see an OOTB functionality for this (unless I am missing something). If 
there is none, I can build this myself and so I am trying to understand the 
data underneath.

    Best,
    Pratyush







Reply via email to