ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-5672) UOM conversion for supplier and sale order
Date Wed, 09 Mar 2016 14:36:40 GMT

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

Jacques Le Roux commented on OFBIZ-5672:

Did you try on trunk?

> UOM conversion for supplier and sale order
> ------------------------------------------
>                 Key: OFBIZ-5672
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5672
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: order
>    Affects Versions: Release Branch 13.07, Trunk
>         Environment: OOTB
>            Reporter: Julien NICOLAS
>            Assignee: Jacques Le Roux
>            Priority: Minor
>              Labels: features
>         Attachments: OFBIZ-5672-UOM-conversion-supplier-and-sale-order.13.07
>   Original Estimate: 120h
>  Remaining Estimate: 120h
> It's possible to define different UomQuantity in measures tab, supplier tab or price
tab of a product but OFBiz don't manage it in stock.
> The improvement must manage it using UomConversion table for standard conversions.
> When a new order (supplier or sale) is created, the user can choose the UomQuantity if
more than one UomQuantity is available.
> By default if only one conversion is defined in UomConversion table, OFBiz will use it
for both conversion way.
> However, it's possible to define different rules for each ways.
> Add new concept in UomConversion rules : rouding method and number of digit after decimal
> To be more flexible, add new fields in price and supplier product tab.
>   - Uom conversion factor
>   - Rounding method
>   - Number of digit after decimal point
> If those fields are empty, OFBiz will use the standard UomConversion table.

This message was sent by Atlassian JIRA

View raw message