Sage 100

As background this client is in the pharmaceutical industry and thus they have a lot of unusual requirements for both secrecy and reporting. They asked me if there was any way to block certain users from seeing information in a specific warehouse. I'm drawing a complete blank on any way to achieve this. Using a separate company is not an option due to DEA requirements and audits. Does anyone have any ideas or thoughts?

I am not sure if this would be a complete solution. I haven't tested it but DSD has Security by Whse: http://www.dsdinc.com/enhancement/security-by-warehouse-2/

What is it that you are trying to hide? Access to the whole warehouse or data for an item in the warehouse? You could setup a security group that the user belongs to and then use customizer to hide some things based on that group. Warehouse info can be found in a lot of places so how effective it is depends on what you are trying to block and what access they have to specific functions.

I would first look at @RobertWood suggestion of DSD.

Thanks @RobertWood they mentioned that they wanted to hide the warehouse so that users don't even know it exists, I don't think this will get them that far but it should get them 90% closer than they are today. @WayneSchulz - LOL - they didn't tell me what they were going to be putting in this secret warehouse. Based on my history with this particular client I would be shocked but I guess you never know.

I know we just did some pretty granular security for an SAP customer using row level security and a scripting tool for SAP, so that should be possible in Sage 100 as well. It would need to be applied in a number of places within the application (all lookups, reports, etc.), so I would think the security would need to be at the DB level to make invisible (and that would definitely require SQL). I think the problem is going to be that whatever you do will be hard coded in some way shape or form even if users are grouped via role or something of that nature. If the environment changes, the coding (scripts etc.) will need to be modified. So it could be form of partner security.

Hiding it would be the tricky part.

I agree with you both. if they are not acceptable to what the enhancement offers, I don't think we can help them make it entirely invisible to users.