matching PO-receipt error make session break.

Description

step redo:
1. Make receipt rc1 = 150
2. Make receipt rc2 = 50

3. Make invoice iv1 = 100
4. Make invoice iv2 = 100

5. Make match rc1 - iv1
6. Make match rc1 - iv2
7. Make match rc2 - iv2

8. make purchase order po1 = 120

9. in Matching PO-Receipt-Invoice window
+ Match from choose receipt
+ match to choose Purchase order
+ product search by product use above
+ in list result receipt choose rc1
+ in list result PO choose po1
click process to match => error by ticket
reclick process, display wait dialog => use can switch tab but not do anything => user must refresh browse.

Current you can check with my data test in demo.idempiere.com
open Matching PO-Receipt-Invoice window
+ Match from choose receipt
+ match to choose Purchase order
+ product search by Holly Bush
+ in search list see two receipt ...516, ...517
+ select one receipt, display PO 800008
+ click process => wait dialog display (error by ticket only display first time).

I debug in client but don't find anything. event click to process button is not rise in server.

Environment

None

Activity

Show:
Hiep Lq
October 22, 2014, 2:58 PM

thanks for feedback.
example we has 5 record need match
current process:

match 2 record (with commit).
exception at record 3
stop matching with error message

in case all match in a record not need.
why not continue match next record after record 3?
and message will is list of un-success record.

Carlos Ruiz
October 22, 2014, 2:47 PM

, on big installations is usual to move in the other direction, making transactions littler.
I don't see if there is a gain making the whole process a single trx.
In the meantime I prefer not to integrate it, but please let me know if there are strong reasons to move that way.

Hiep Lq
October 17, 2014, 5:51 PM

Hi please also consider about make all match at a transaction patch

Hiep Lq
September 6, 2014, 2:30 PM

, current all match is not in same transaction.
it make not friendly with end user in below case.

1 line at "from list" match with 2 line at "to list".
line 1 is match ok.
line 2 is match with error.
conclude user receive message error, but line 1 is match ok. he don't know about success of line 1.
i think all match must in process in a transaction.
WDYT?

Hiep Lq
September 6, 2014, 11:42 AM

i still redo it. but i'm fixed it.
it's by deadlock. please help me review it.

Fixed

Assignee

Hiep Lq

Reporter

Hiep Lq

Labels

Tested By

None

Components

Affects versions

Priority

Blocker