[
https://issues.apache.org/jira/browse/OFBIZ-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327696#comment-15327696 ]
Pierre Smits edited comment on OFBIZ-7174 at 6/13/16 4:29 PM:
--------------------------------------------------------------
In your description you are referencing 'inventory item level details' and furter on you're mentioning 'inventory details'.
Are you talking about referencing records from 'InventoryItem' or from 'InventoryItemDetail'?
was (Author: pfm.smits):
In your description you are referencing 'inventory item level details' and furter on you're mentioning 'inventory details'.
Are you talking about referencing record from 'InventoryItem' or from 'InventoryItemDetail'?
> Simplify UI by grouping all newly added Product Name along inventory item level detail shown against each task over Actual Material Screen of Production Run
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-7174
> URL:
https://issues.apache.org/jira/browse/OFBIZ-7174> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: 14.12.01
> Reporter: Swapnil Shah
> Assignee: Divesh Dutta
> Attachments: AM_2.png
>
>
> Currently all the task over production runs are shown separately in their own panel along with respective Product Id and Inventory level details.
> We can try to simplify it by showing a single panel listing all the associated routing (tasks) of a given production run and list the product/inventory details showing following fields in this panel:
> || ROUTING TASK (ID) || PRODUCT NAME (ID) || INVENTORY ITEM ID || QUANTITY || UNIT COST || REASON ENUM ID || DESCRIPTION ||
> Also its bit difficult to identify actual product (name) just by looking at Product Id & inventory item id over Actual Material screen of Production run. Possibly the above layout could help in achieving better traceability between task/product/inventory
> Please refer to attached screenshot for reference.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)