All ASI do not show old ASI if storage cleaned
Description
Environment
Attachments
Activity
Deepak Pansheriya June 14, 2016 at 5:13 AM
Looking ASI by transaction is slow approach. Is it good idea to link ASI to product? I can't think of use case where one ASI can be used for multiple products so it may be good to add M_Product_ID on ASI and filter ASI by Product_ID when we do show all.
Deepak Pansheriya July 2, 2015 at 6:05 PM
hieplq,
Please note that your point 2 is not correct. If we do sum then it actually for on hand qty it shows time of transaction then on hand. As locator joined to transaction, when there is storage then it will join to all transaction and actually multiply total stock.
3. There is no other way to map product to asi currently. And hope that need in rare case.
Hiep Lq June 25, 2015 at 3:27 PM
hi your patch don't total match with my requirement but i learn a lot from it for my requirement.
about your improve.
normal, when you has a complete sale order for a product with ASI. you will has a reserved record
next time you open "select exist record dialog", you has two record for this ASI (i description it at https://groups.google.com/forum/#!searchin/idempiere/Attribute/idempiere/oURzcYPv4Zg/WGb7Co2RJBIJ)
now you check "select all" checkbox
1+ just one record per ASI show, i think it's very good effect and should apply back for case non check "select all"
2+ i see you calculator on hand, reserved by avg function it make wrong value, i think must use sum function with add or minus depend trans.movementtype
3+ because 2 is processed per transaction table, maybe it effect performance, maybe in this case don't display column on hand, reserved by, or make new checkbox show store info?
Deepak Pansheriya June 23, 2015 at 10:47 AM
Please note that I have done to show ASI Locator combination for historical ASI.
Waiting for community feedback how all wants?
ASI selection dialog from attribute set editor is Currently looking only those in storage. Now we have storage cleanup script too. This means we may not able to see ASI which already shipped completely and came returns some time.
I suggest when we do show all, it should bring from transaction records. or it should identify ASI to show from transaction and then it join to storage.