KBohn
Active Member
RE: Row Security On Address Book....How about conditional column
Hi everyone,
As there seems to be a lot of Security expertise at the moment, I thought I
would add to the question. Does anyone have a solution for the this?
We need to have conditional column level security for 'E' Search type
Address book records. In Canada, Social Insurance Numbers (Tax ID) & with
new legislation in 2003, employee address information is considered
confidential information. We have been running in Financials & Distrubution
for 2.5 years and are now implementing the HR module. Finance &
Distribution users require access to Address Book records (all information)
for Customers & Vendors & Employee records to pay expense reports etc. We
need only HR to have information to 'E' confidential fields though.
JDE says this can't be done in the application so their solution was a
custom ER modification on P01012 (A/B revisions) to hide those fields based
on user or group id. I did this & yes, that works for the Address Book
revisions application, but what about UTB? What about ODA? What about RDA?
Without actual JDE security setup, these security holes still exist. We
have users outside of the HR group who use ODA extensively to report on
financial data. We can't take that away from them, but there is nothing to
stop them from accessing F0101 (Address Book) or F0116 (Address by Date)
using ODA or UTB?
When evaluating the HR Module, we were assured that JDE Security was
extensive. This appears to be a huge oversight that JDE is not willing to
rectify. If I am missing a JDE solution, please educate me. Of course,
then there are the A/B reports, but that's another story.
Thanks very much,
Kimberley Bohn
QNX Software Systems Ltd., Canada
Xe, NT, SQL7.0, U5, SP17.1
WTS W2K
Hi everyone,
As there seems to be a lot of Security expertise at the moment, I thought I
would add to the question. Does anyone have a solution for the this?
We need to have conditional column level security for 'E' Search type
Address book records. In Canada, Social Insurance Numbers (Tax ID) & with
new legislation in 2003, employee address information is considered
confidential information. We have been running in Financials & Distrubution
for 2.5 years and are now implementing the HR module. Finance &
Distribution users require access to Address Book records (all information)
for Customers & Vendors & Employee records to pay expense reports etc. We
need only HR to have information to 'E' confidential fields though.
JDE says this can't be done in the application so their solution was a
custom ER modification on P01012 (A/B revisions) to hide those fields based
on user or group id. I did this & yes, that works for the Address Book
revisions application, but what about UTB? What about ODA? What about RDA?
Without actual JDE security setup, these security holes still exist. We
have users outside of the HR group who use ODA extensively to report on
financial data. We can't take that away from them, but there is nothing to
stop them from accessing F0101 (Address Book) or F0116 (Address by Date)
using ODA or UTB?
When evaluating the HR Module, we were assured that JDE Security was
extensive. This appears to be a huge oversight that JDE is not willing to
rectify. If I am missing a JDE solution, please educate me. Of course,
then there are the A/B reports, but that's another story.
Thanks very much,
Kimberley Bohn
QNX Software Systems Ltd., Canada
Xe, NT, SQL7.0, U5, SP17.1
WTS W2K