0044382: Goods shipment not fully invoiced neither linked to a related sales invoice

Description

Create a sales invoice, create a partial goods shipment for it, then create a new goods shipment completing the rest. The last one doesn't get linked to the sales invoice neither has the 100% invoiced after completing it

Steps To Reproduce

0- Go to livebuilds retail stable
1- Create a “Sales Invoice” for any product and with quantity 100 unit and “Complete” it
2- Create a “Goods Shipment” with “Create Lines from” the previously created invoice, change the quantity to 20 unit (I don’t want to ship all the quantity) then “Complete” it
3- At this level, the previously created “Goods Shipment” will have invoice status = 100%
4- Create another “Goods Shipment” with “Create Lines from” the previously created invoice, the system will show the remaining quantity which is 80 unit, select this line and “Complete” it. This “Goods Shipment” will have invoice status = 0%. Not linked to the original “Sales Invoice”
5- One can keep shipping the same sales invoice, over and over

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

has duplicate

defect

0049449

closed

gsalas

The "Fully Invoiced" check is not checked on some delivery notes.

Notes
(0120898) dmiguelez (developer) 2020-06-18 10:18	This issue has been updated to Design Defect This is a known problem in Openbravo and it is caused due to how the documents are related to each other in the Sales flow. In this case, the relationship between the Shipment Line and the Invoice Line is in the Invoice Line as a Foreign Key. The problem with this approach is that it is a 1:1 relationship, and it is not possible to link several Shipment Lines against the same Invoice Line. In the Purchase flow this problem is solved with the Matched Purchase Orders and Matched Invoices windows, which allows to have an N:M relationship between this documents. Changing the Sales flow to follow this logic will require an important redesign of the full functionality, including a revision of the same flow in the POS.

Issue History
Date Modified	Username	Field	Change
2020-06-17 10:26	santi_lozano	New Issue
2020-06-17 10:26	santi_lozano	Assigned To	=> Triage Finance
2020-06-17 10:26	santi_lozano	Modules	=> Core
2020-06-17 10:26	santi_lozano	Resolution time	=> 1594159200
2020-06-17 10:26	santi_lozano	Triggers an Emergency Pack	=> No
2020-06-18 10:14	dmiguelez	Type	defect => design defect
2020-06-18 10:18	dmiguelez	Note Added: 0120898
2020-07-09 10:17	RenateNieuwkoop	Issue Monitored: RenateNieuwkoop
2022-06-16 11:30	aferraz	Relationship added	has duplicate 0049449