Security Rules in Fusion/Cloud

Security Rules are used to restrict specific values of the segments at Role level.

It is a bit different when compared with EBS. Security Rules are set at Value Set level in Fusion whereas at Segment level in EBS.

We can apply Security Rule to any of the segments in Chart of accounts. For example, we have a company which has different segment values in Company Segment i.e 1000, 2000 and 3000 etc. If you want to allow only 1000 company and restrict 2000 and 3000 values, we can set up a rule with conditions accordingly and assign it to a role.

Setup

·        Create Security Rule

·        Assign SR to Role (General Accounting Manager)

·        Deploy COA Structure (Accounting Flex field)

Enter Journal to test

Create Security Rule

Create SR for Company Values

1000-Allow
2000-Don’t Allow
3000-Don’t Allow

Task: Manage Chart of Accounts Value Sets à Value Set Code: CP Company –search

Edit

Below window appears

Check Chart of Accounts Structure is Deployed

Task: Manage Chart of Accounts Structure à Accounting Flexfield should be in Deployed status

Testing

Login with new user and check if user is allowed for only 1000 Company

Go to GL à Create Journal

You can only see 1000.

Whoever is assigned with this role can have same access, because SR is assigned to this role.

We can apply this rule to any segment but we tried with Company

Rules

The chart of accounts uses two different types of rules to control functionality.

·        Security rules: Prohibit certain users from accessing specific segment values. For example, you can create a security rule that grants a user access only to his or her department.

·        Cross-validation rules: Control the account combinations that can be created during data entry. For example, you may decide that sales cost centers 600 to 699 should enter amounts only to product sales accounts 4000 to 4999.