I am working as an BI Consultant at a large pan-European Oracle Apps implementation (11.5.8). We want to extract a daily sales report from GL. This report should be available each day for all the sales-persons all over Europe.

This report should be secured based on set_of_books_id. That shouldn’t be a problem. We are also looking for a way to secure this report based on the accounting segments. The account structure consists of 10 segements. We want to be able to secure the report based on one or more segments.

Can anyone point me in the right direction or give me some information to get the security working?

Thanks in advance.

Whatever security rules you create to prevent an account from being viewed in Oracle should also apply to the reports. So, for example, if you create a security rule which prevents a user from posting to or accessing a specific account in the GL then when you print the Trial Balance you should not be able to see that account. Let me know if that helps.

Thanks Richard,

This helps a bit. I am still trying to find out how to set up those security rules. Next to it I am trying to find out how these rules apply to a responsibility. I would like to get a clear view of the functionality of these security rules.
The account structure exists of 10 segments. 2 of these segments are the company (related to a country) and the sales-channel. A sales person eg. should be either able to see everything for one company or see one sales-channel across all companies.

Maybe you are able to give me an example of how this works.

Thanks.

Daan

Security Rules work on individual segments and are applied to a particular segment. Security rules are assigned to responsibilities. Creating a security rule for a particular segment means that users should not be able to view or enter data into the value against which a security rule has been created. For example, if you don’t want a Payables Clerk to see the balance in the payroll a/c you would create a security rule and assign it to the payables clerk, this would ensure the payables clerk could not view online or in report format the payroll a/c. Note in this instance the rule only applies to one segment. To apply rules to many different segments you would have to create more rules for those segments so in your instance it could get quite complex if you have 10 segments.

Cross validation rules work on combinations of segments and apply to everyone in the organisation (i.e. you don’t assign these rules to a particular user as in the case of security rules). An example might be that you want to create a rule stating that when a user enters a journal for a balance sheet account they cannot specify a cost centre. In this instance the cross validation rule applies to both the cost centre segment and the account segment. Cross validation rules also apply more to entry than viewing i.e. they prevent you from entering data incorrectly whereas security rules apply to both entry of data and viewing.

Thanks a lot for your quick help Richard.