[jira] [Updated] (OFBIZ-7173) The Product Added from 'Actual Material' screen could be consumed for producing end product during routing task execution

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

[jira] [Updated] (OFBIZ-7173) The Product Added from 'Actual Material' screen could be consumed for producing end product during routing task execution

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-7173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Swapnil Shah updated OFBIZ-7173:
--------------------------------
    Attachment: AM.png

> The Product Added from 'Actual Material' screen could be consumed for producing end product during routing task execution
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-7173
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7173
>             Project: OFBiz
>          Issue Type: New Feature
>            Reporter: Swapnil Shah
>            Assignee: Divesh Dutta
>         Attachments: AM.png
>
>
> Currently any new product added against given routing task via Actual Material screen just reflects the inventory statistics it.
> We could try to add the feature of having the added products actually be added in conjunction with Actual projected Material requirement based on original BoM associated with the routing.
> # This could be done by creating fresh WorkEffortGoodStandard (WEGS) with such added products against specified routing.
> # We can begin with simple constraint of allowing new material against the only those routing task that has not completed/cancelled yet within a production run
> # Start showing such newly added material requirement in conjunction with original requirement (based on BoM) under all relevant sections over Production Declaration Screen
> Please refer to attached screenshot for reference



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