ecarverHT
Member
Long time reader, first time poster, please let me know if more detail is required!
I am currently working with our Inventory Control team to cleanup unauthorized change access to several important Inventory Data forms and I'm having challenges implementing security in an effective way based on their requests. Example scenario for W4101A is as follows:
Only INVCTL role should have full access to W4101A. The idea was originally to secure W4101A at *PUBLIC and grant explicit access to INVCTL at the role level. However, several other areas own the data in certain columns shown in W4101A. Let's use Planner/Buyer Number (alias ALKY) as an example since our PURPLAN team will need to be able to update that.
If W4101A Action is secured at *PUBLIC, would adding Column security for ALKY allow PURPLAN to Change/Save on W4101A? Or is the only way to achieve this limited change access to W4101A to add Action security for PURPLAN and then Column security for all OTHER fields?
Thanks in advance for any help!
I am currently working with our Inventory Control team to cleanup unauthorized change access to several important Inventory Data forms and I'm having challenges implementing security in an effective way based on their requests. Example scenario for W4101A is as follows:
Only INVCTL role should have full access to W4101A. The idea was originally to secure W4101A at *PUBLIC and grant explicit access to INVCTL at the role level. However, several other areas own the data in certain columns shown in W4101A. Let's use Planner/Buyer Number (alias ALKY) as an example since our PURPLAN team will need to be able to update that.
If W4101A Action is secured at *PUBLIC, would adding Column security for ALKY allow PURPLAN to Change/Save on W4101A? Or is the only way to achieve this limited change access to W4101A to add Action security for PURPLAN and then Column security for all OTHER fields?
Thanks in advance for any help!