[jira] [Closed] (OFBIZ-207) Invoice creation for order with zero value except for shipping.

["Jacques Le Roux (JIRA)" <ji...@apache.org>]

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

Jacques Le Roux closed OFBIZ-207.
---------------------------------
       Resolution: Duplicate
    Fix Version/s: 14.12.01

Yes, thanks Deepak for the reminder, this has been fixed with OFBIZ-6269

>  Invoice creation for order with zero value except for shipping.
> ----------------------------------------------------------------
>
>                 Key: OFBIZ-207
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-207
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: accounting
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Minor
>             Fix For: 14.12.01
>
>         Attachments: CI1.pdf
>
>
> This is a duplicate of http://jira.undersunconsulting.com/browse/OFBIZ-784
> Excerpt from http://jira.undersunconsulting.com/browse/OFBIZ-777 (now closed) :
> Si___________________________________________________________________________________________
> The problem with this order is that it has zero value except for $6.40 of shipping. As such, the invoices created had zero value. (How do you pro-rate shipping in this case? Not sure....)
> [...]
> The interesting question is that of the boundary condition when the invoice actually had no value--how do you allocate shipping across invoices? I did not solve that.
> Jacques___________________________________________________________________________________________
> For me the customer benefited of a promotion giving him/her a free product.
> But this does not mean that all is free : he/her have to paid for the shipping.
> This must be on the invoice.
> Si___________________________________________________________________________________________
> That sounds reasonable enough, but the current code does not do that. We should probably make a fix for it somewhere.



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