For this, PartPlant is filtered to site A. Site B people can’t see the detail from site A, like the buyer (yeah I don’t know why they wanted that either), but that’s OK for me. It at least works in both sites. It’s just that one site doesn’t get all the detailed info. But they get all the rows, which is what matters.
Yeah I’m only two months into live multi-site and I’m frustrated.
Three random tables are restricted. Not PartQty or PartWhse or PartCost, thankfully, so I can work around cost and quantity. But why not just remove the restriction on all of them? We do BAQs and menu security! We know how to block info! But I can’t unblock what the system restricts.
Still not sure what the business case is, i.e. why you need to block one thing and not another and when but…
Referring to a post about Code Widgets this week, in a BPM you can write your own query in LINQ in a Code Widget and fill a dataset without any restrictions for territory, tenant, or plant security. That dataset can be use later in the BPM.
I don’t know where you are using this so this may or may not help. But if you’re willing to manage security manually and you’re not updating anything, it’s a possible solution.
Yeah, in the end you’re right, the best control is trusting people.
Our people are excellent. They are smart and try to do what’s best for the system. Problem is, the system that they came from, they had to switch sites all the time to see inventory in another site, for example. I’m trying to break them of this habit and let them stay in one site all day every day. I sure try to myself. It’s a good thing each site has wildly different conventions for bin names, for example - that’s saved me a few times. And POs can’t be received in the wrong site. But if you made the PO in the wrong site…