Oracle General Ledger has a unique feature of defining security rules. With recurity rules, a user can restrict data entry and online inquiry for the ranges of segment values. While defining security rules one thing to keep in mind is that each rule is defined for a specific segment. Security rules become effective only when the same are attached to a responsibility. Thus, security rules do not affect reporting in anyway.

Oracle GL by default excludes all values except those specifically included when a security rule is defined. To put it in another way, each rule must have at least one include rule element.

The security rules can be assigned to responsibilities using the Assign Security Rules window.

Personally, I recommend that while defining security rules, you start with a general include element for the entire range and then have exclude elements for the ranges that should be restricted. After having assigned the rules to users, users should log off and then log on so that the security rules take effect.