Column Security!!!

hi there,
Guys am trying to set up some column security for my client, one of the requirements needed by that client is that some users should not see any cost for their items in any report.
I tried to set up security for these using
"security workbench – column security", then select *ALL for all tables and mention the data item name…it didn’t work they still can see the cost, also I tried the same but choose UBE instead of tables….but same same it didn’t work.
Now I am doubting that OW have column security for reports….is any fox here know if that correct or no???
Also did any body have a brilliant idea how to setup this kind of security instead of running like creasy all around oneworld to make new reports without that column!!!

Thanks,

Hatem,

Someone else with direct knowledge in this area may contradict me, but I doubt that column security is fully implemented (or even implemented at all) in UBEs.

This is because a UBE is a BATCH PROGRAM that can also produce a report. Because many UBEs perform calculations and updates of tables you cannot keep the UBE from reading the data out of the table - otherwise many UBE programs would no longer work correctly if column security became involved. Now its still possible to allow the program to retrieve the field values and not display them, but what about report fields that are not direct from the business view, but are instead moved into ER variables or Report variables? Column security couldn't handle this kind of situation.

I just checked and there IS a SAR on this - 6074924. Its status is closed - indicating JDE does not intend to address this issue.

Net, net I think you get to run around like crazy . . .

Cheers,

Hey, this is a setup we have here. It doesn't deal with cost, but with payroll so, you know it has to work!

We have row security setup on a table locking out particular business units from seeing other business units or salary payroll. It holds true in the UBEs as well. I know this because I can't print the pay info from employees from different Business units other then my own. I designed the reports, and tested them using the hr/pr accounts.

Object name is the table
security type is the row
View/Add/Change/Delete are all no's except for the grouping we want yes

Hope this helps.

jeremey,

but you're using Row Security - not Column - right?

Yes, but it is to hide certain items in a table. In our case - pay rates.

Nevertheless there is a distinct difference between the two. By using Row Security you are preventing UBEs and Applications from retrieving whole rows of data. You're not hiding columns - you're not seeing any of the data for the Business Units!

Ahhh, I guess there is a big difference. Thanks for the education. Guess, what I said wouldn't work. Thanks Larry.

Larry, i agree with u... Column security couldn't handle this kind of situation.