Wrong organization in m_transaction, organization doesnt fit locator

Description

idempiere enable for user to create two related scenarious when move inventory from loc1 to loc 2, follow: (diff. in org and loc)

use case 1. (default)
ORG-A (header)
loc1(orgA) to loc2 (orgB)

use case 2. (alternative, users use accidentaly)
ORG-B(header)
loc1(orgA) to loc2 (orgB)

BUG 1. the second scenario cause error in m_transactions. entries created to m_transactions to header org instead location org.
so in case 2 we await idempiere creates m_transactions to orgA instead orgB (header)

another solution is fix BUG1, then make this behaviour enable/disable by system config.

This behaviour can cause errors in subsystems like costing.

Environment

public demo 25 july

Activity

Show:
Heng Sin Low
May 9, 2020, 2:35 AM

I think the right fix here is when header is orgB, user shouldn’t be allowed to select loc1(orgA).

Deepak Pansheriya
May 9, 2020, 7:13 AM

I am not agree as in multiple organization installation, It is quite common that inventory moves across organizations.

Heng Sin Low
May 9, 2020, 9:58 AM

hi , you miss read my message, I say loc1, not both loc.

Carlos Ruiz
June 19, 2020, 11:58 AM

Agree with , that sounds the right fix.

Attached the

containing the migration script that creates the validation rule and assign it to the column.

However, it seems WLocatorDialog and WLocatorEditor are not taking into account validation rules, just filtering by warehouse.

Assignee

Carlos Ruiz

Reporter

Norbert Bede

Labels

None

Tested By

Norbert Bede

Components

Fix versions

Affects versions

Priority

Major
Configure