[jira] [Commented] (OFBIZ-7533) Not able to set new Lot Id to existing inventory item

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-7533) Not able to set new Lot Id to existing inventory item

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466872#comment-15466872 ]

Swapnil Shah commented on OFBIZ-7533:
-------------------------------------

Thanks [~ankush.upadhyay] [~diveshdut] for contribution. I validated the fixes as follows and found to be working better now:
# Updated the lotId (using non-existent lot) on existing inventoryItem without any error/stack-trace (*PASS*)
# Checked that a new Lot is created in DB (*PASS*)

Though i expect that in future we might need to overhaul the existing lot management process (as per OFBIZ-5704) but i reckon many existing users are still using the current version of this feature and the fixes here could be helpful, Closing this ticket for now.

> Not able to set new Lot Id to existing inventory item
> -----------------------------------------------------
>
>                 Key: OFBIZ-7533
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7533
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: product
>    Affects Versions: Upcoming Branch
>            Reporter: Swapnil Shah
>            Assignee: Swapnil Shah
>             Fix For: Upcoming Branch
>
>         Attachments: II_LOT.png, OFBIZ-7533.patch
>
>
> When any new lot is assigned to exiting inventory item then it ends up throwing foreign key constraint.
> We could allow it by creating first new lot (if its not found already existent in DB) and then associate the same with given inventory item. (Also currently i couldn't find any screen to create new lot in given facility)
> Please refer to attached screenshot for reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)