Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0033624Openbravo ERP07. Sales managementpublic2016-08-04 14:072016-10-17 15:24
ngarcia 
AtulOpenbravo 
urgentmajoralways
closedno change required 
5
 
 
Core
No
0033624: Different total net amount and total gross amount in order and invoice is the order line is split in more than one shipment line
Different total net amount and total gross amount in order and invoice is the order line is split in more than one shipment line
Configure the instance to accept more than 2 decimals in prices:

http://wiki.openbravo.com/wiki/How_to_change_the_price_precision [^]


As group admin role:
   Create a new product
   Add a sales price list of 0.756 to it
   Create a goods receipt and receive one unit of the product in two different storage bins of the same warehouse
   Create a Sales Order with POS Order type and add 2 units of the previously created product
   Check the total net amount is 1.51 in the order and 1.52 in the invoice
   Check the total gross amount is 1.83 in the order and 1.84 in the invoice
   
   The same happens if you create a standard order, a goods shipment with two lines and a sales invoice from it
Issue changed as Design Defect as Openbravo is not currently designed now to support this scenario.

In this scenario purchase order shows below info while ordering 2 units of the same product at a price of 0.756:

Line Net Amount = Taxable Amount = 1.51
Tax Rate = 21%
Tax Amount = 0.32
Total Gross Amount = 1.83

However sales invoice shows below info while invoicing 1 unit at a price of 0.756 (storage bin x), and another 1 unit at a price of 0.756 (storage bin y):

Line Net Amount = Taxable Amount = 1.52
Tax Rate = 21%
Tax Amount = 0.32
Total Gross Amount = 1.84

It would be necessary to adjust taxable amount (-0.01) and therefore total gross amount (0.01) as described in the issue 25506 related.

This issue (design defect) is currently blocked by issue 25506 (feature request).


Proposed solution above do not valid.
No tags attached.
related to defect 0034150 scheduled collazoandy4 Create Lines From function selects only shipped units while invoicing from orders. 
related to design defect 0032061 new Triage Omni OMS No "Cost" information shown in Sales Invoice Dimensional Report in case there is no 1 to 1 relation between SO line and GS line 
Issue History
2016-08-04 14:07ngarciaNew Issue
2016-08-04 14:07ngarciaAssigned To => Triage Finance
2016-08-04 14:07ngarciaModules => Core
2016-08-04 14:07ngarciaResolution time => 1472076000
2016-08-04 14:07ngarciaTriggers an Emergency Pack => No
2016-08-04 14:12ngarciaIssue Monitored: networkb
2016-08-09 08:34aferrazAssigned ToTriage Finance => AtulOpenbravo
2016-08-18 12:09aferrazRelationship addedrelated to 0032265
2016-08-19 09:45psanjuanTypedefect => design defect
2016-08-19 09:45psanjuanProposed Solution updated
2016-08-19 09:45psanjuanRelationship addedrelated to 0025506
2016-08-19 09:46psanjuanProposed Solution updated
2016-08-19 09:47psanjuanRelationship replaceddepends on 0025506
2016-08-19 09:49psanjuanRelationship deletedrelated to 0032265
2016-10-13 09:58psanjuanProposed Solution updated
2016-10-13 10:46psanjuanProposed Solution updated
2016-10-14 13:23psanjuanNote Added: 0090586
2016-10-14 13:24psanjuanRelationship deleteddepends on 0025506
2016-10-14 13:24psanjuanRelationship addedrelated to 0034150
2016-10-14 13:25psanjuanNote Edited: 0090586bug_revision_view_page.php?bugnote_id=0090586#r13372
2016-10-14 13:26psanjuanNote Edited: 0090586bug_revision_view_page.php?bugnote_id=0090586#r13373
2016-10-14 13:26psanjuanStatusnew => scheduled
2016-10-14 13:27psanjuanStatusscheduled => resolved
2016-10-14 13:27psanjuanResolutionopen => no change required
2016-10-14 13:27psanjuanFixed in SCM revision => no change required
2016-10-14 13:28psanjuanProposed Solution updated
2016-10-17 10:57psanjuanStatusresolved => new
2016-10-17 10:57psanjuanNote Added: 0090613
2016-10-17 10:57psanjuanStatusnew => closed
2016-10-17 15:24psanjuanRelationship addedrelated to 0032061
2016-10-17 15:30psanjuanNote Edited: 0090586bug_revision_view_page.php?bugnote_id=0090586#r13385
2016-10-17 15:36psanjuanNote Edited: 0090586bug_revision_view_page.php?bugnote_id=0090586#r13386
2016-10-17 15:37psanjuanNote Edited: 0090586bug_revision_view_page.php?bugnote_id=0090586#r13387

Notes
(0090586)
psanjuan   
2016-10-14 13:23   
(edited on: 2016-10-17 15:37)
It is not the same to invoice 1 line of 2 units than 2 lines of 1 units. There could be mathematical rounding issues do not caused by Openbravo.

It should be clear what strategy customer needs to follow in regards to invoicing.

If they want to invoice from the shipment, invoice lines could be split.
If they want to invoice from the order, invoice lines could not be split.

Therefore there are two options:


Option A - In the case of creating a POS Sales order, that requires that the invoice is created taking into account the shipment(s), please select "After Delivery" as Invoice Terms.

Option B - In the case of creating a POS Sales order, that requires that the invoice do not need to take into account the shipments but just the order, please select "Inmediate" as Invoice Terms.

This is already working.

Following option B in the example provided, the invoice will contain just 1 line for 2 units of the product, otherwise it will be split into 2 lines of 1 unit each (same as in the shipment).

Havind said that, please be aware that option B does not properly reflects cost in the Sales Invoice Dimensional report. See issue related 32061 (Design Defect).

Once double check, we can not consider this issue either a defect or a design defect.

Finally, and in the case of not using a POS Sales Order, there is a defect related that reflects an issue related to "Create Lines From" whenever an order is selected. Create Lines From (Order) function needs to be improved, therefore invoice created does not take the units shipped but just ordered ones, having into account that once the corresponding shipment(s) are booked, correct cost are calculated and shown in the Sales Invoice Dimensional Report.

Please see issue related 34150

(0090613)
psanjuan   
2016-10-17 10:57   
No change required