Hi Everyone,
Thanks for the response. I've tried almost all the suggested solution in several implementation :D
However the major problem lies in the user access and created journal
I'll illustrate using simple scenario:
User A, in Org A, having authorities on Warehouse A and Locator A1, A2, and A3.
User B, in Org B, having authorities on Warehouse B and Locator B1, B2, and B3.
Access for both users are restricted to their own Org. Meaning User A cannot see Warehouse B and vise versa. How can they set the destination warehouse / locator if they cannot see it? If you give both users access to all Orgs, then how do you restrict user A not to use Warehouse / Locator B as source?
My latest workaround is:
1. create some dummy table --> XX_Locator with entries identical to of M_Locator. All entries of XX_Locator has AD_Org_ID = *
2. We pre-define an intransit locator for each warehouse
3. We create a custom Inter-Org Move Out window, adding a custom field Target_Locator pointing to XX_Locator. User A then can select Locator A1 as
its source locator, and locator B1 as Target_Locator indirectly through XX_Locator. The LocatorTo default to intransit locator on Warehouse A, lets say A3. Document Inter-Org Move Out will be in Org A.
4. When completed, we will autocreate a Inter-Org Move In transaction, locator From is A3 (locked from editing) while locator To is B1 (actual from M_Locator). Document is in Org B. User B can update the Qty to confirm the move and update the paper work.
5. If the confirmed qty is less than the moved qty, upon receiving the confirmation, user A must move back the remaining qty into A1.
I know there's quite some steps. But it is less disruptive development, and we can have access restriction and the journals are correct. But then, I am looking for a more generic solution that can be integrated into iDempiere.
So, please share your thoughts. It will be highly appreciated.
Regards,
Edwin Ang