Security on PartCost

Epicor ERP 10
,
1

We need to restrict some of our users from seeing product costs. Currently these users have access to Part Tracker and Costs is a tab there…

We would prefer to do this at the table-level, so that wherever costs could show up (Method Tracker, Quote worksheet, etc.), these users cannot access them. So, I want to create a security group called “Can View Costs” (or “Cannot View Costs”, depending on which list is bigger).

I have looked at the following options, but cannot figure out which is easiest to implement and maintain.

  1. Table Security. Cannot find a way to secure the whole table. There does not appear to be a business object PartCost in Service Security Maintenance. There is PartCostSearch but that does not appear to be the same thing (maybe it is?)

  2. Field Security. There are around 30 fields in Part Cost and I have not found a DMT template that handles field security. I could slog through each manually, but would prefer not to.

  3. Custom version of Part Tracker (removing tab). This would handle the Part Tracker, aspect, but not BAQ, PartTran records, Method Tracker, Quote worksheets or and anywhere else that I don’t know about. We would prefer not to have customized versions, if we can avoid it (we do have one or two, but mostly use the “out of the box” versions.

Anyone have opinions the best approach to take on this? I would appreciate your thoughts.

Thanks.

—sam

2

I’m only aware of Field Security, you mention both PartCost and PatTran, you would need to the changes per field and table.

I know what DMT is used for but don’t know the internals, can you write your own template from scratch through trial and error? Or is there a specific list of supported Business Objects?

3

As far as I know, I can use only the templates provided.

PartCostSeach is apparently the bo for the PartTracker Costs tab. It doesn’t do anything for Part Tran or Part Tran History or the View Costs functionality in Method Tracker. I can do these manually; just a bit tedious.

Thanks.

4

Double check the forms for fields that might not be explicitly in a table, but are calculated. Or ones that could be used to deduce the cost.

1 Like
5

Field Security has a Masking feature…but only for character fields. :frowning: And as Calvin mentioned, it probably wouldn’t flow to fields that could be used to deduce the amount.

I wonder if one created a text field that was masked. Would it reveal the raw value? :thinking:

6

You could also have a customization that would show/hide the tab based off of the Security Group.