0028562: Cash up does not finish and an error is shown at the console

Description

I've done a Cashup process, but the last step does not finish. It freezes on "Loading" screen and the console show the following messages (first marked as an error, second marked as a warning)

OB.Dal.save: table 'cashup'; {"message":"could not execute statement due to a constaint failure (19 constraint failed)","code":6};

SynchronizationHelper timeout reached but the watchers poll is not cleared because the timout actions are deactivated. This is happening because an asynchronous call is lasting more than 60000 milliseconds (set a longer timeout) or because there is an unbalanced process registered in the SynchronizationHelper watchers poll (fix the process). To activate the timeout actions (i.e. clear the poll and fire the 'synchronized' event), set 'isTimeoutThresholdActivated' to 'true'. This process(s) didn't finish: (124) processAndFinishCashUp

Steps To Reproduce

Clear browser's cache to get the proper initialisation
Enter WebPOS as vallblanca user
Create an order for 5 backpacks and complete the order
Go to Cashup and pick Nothing in all the options to keep.
The cashup is shown in screen, click the button to process
The error described above is shown in the console, and the loading screen never change.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

duplicate of	defect	0028635		closed	marvintm	cashup is not finished when receipt exists in "Errors while importing" window
related to	defect	0028608		new	marvintm	After completing a receipt, POS shows a successful synchronization message, but Sales Orders are lost

Notes
(0073439) migueldejuana (developer) 2015-01-12 20:53	The Fiscal Calendar for 2015 is not created yet and this is why is failing. The usability issue of completing a Cashup only to find at the end that the data is not valid. This could be solved by preventing the user to start any task related with non valid periods, starting by creating the orders in first place. In the ERP, you can create orders for non existent periods but you cannot complete them. In any case, the user should be informed that the action is not valid because of the missing periods.

Issue History
Date Modified	Username	Field	Change
2015-01-12 11:29	plujan	New Issue
2015-01-12 11:29	plujan	Assigned To	=> marvintm
2015-01-12 11:29	plujan	Triggers an Emergency Pack	=> No
2015-01-12 20:53	migueldejuana	Note Added: 0073439
2015-01-14 11:34	lorenzofidalgo	Relationship added	related to 0028608
2015-01-30 11:00	malsasua	Relationship added	duplicate of 0028635
2015-01-30 11:00	malsasua	Status	new => closed
2015-01-30 11:00	malsasua	Resolution	open => duplicate
2015-01-30 11:00	malsasua	Fixed in Version	=> RR15Q1