Warehouse Restriction by Company/User combo

Hi, to my knowledge, it is not possible unless, they have different login names.

However, to avoid having errors when entering the transactions, you can create an approval workflow when the warehouse selected doesn’t match the branch used. The workgroup assigned for the approval could be SELECT ANOTHER WRHS.

Also to make sure that no transaction is made, you must not configure a due to due from for the inventory account. That being, any financial transaction that would involve inventory transfer between companies would be prohibited by the system.

A customization can also be developed.

I feared that would be the case. I’ll look into the approval option - that might at least give warning when things don’t match up

@BrittLass, the filter you want is built in, but it's tied to a feature you need. Acumatica limits the Warehouse lookup on PO and SO lines to the order's company only while Inter-Branch Transactions is turned off (Enable/Disable Features, CS100000). Intercompany PO, SO and bill generation requires that feature, so you see all nine.

Eric's approval route works on 26R1. In the rule conditions on Approval Maps (EP205015), pair Purchase Order, Branch, Equals the branch with Purchase Order Line, Warehouse, Does Not Equal for each of that company's warehouses. One catch when you test: a PO saved before approval was turned on skips the map until it goes back on hold.

If you'd rather block it at entry, the customization is small. Acumatica's own check is SameOrganizationBranch on INSite.branchID, so a developer can reapply it as a PXRestrictor on POLine.siteID and SOLine.siteID in a graph extension.

Thanks ​@Steve Milner! I appreciate the details for the approval map that would be needed and the customization details.