Search Results so_security_rules_pk

Overview

The SO_SECURITY_RULES table is a core repository for defining and managing data security policies within the Order Entry (OE) module of Oracle E-Business Suite (EBS). It functions as the central rule engine for controlling user access to specific order management objects, attributes, and actions based on defined criteria. This table enables the implementation of granular, rule-based security, ensuring that users can only view or modify data pertinent to their organizational role, responsibility, or other business dimensions. Its role is critical for enforcing data segregation and compliance within complex, multi-organization deployment environments.

Key Information Stored

The table stores the definition of individual security rules. While the full column list is not detailed in the provided metadata, the foreign key relationships explicitly identify the core components of each rule. The primary identifier is the SECURITY_RULE_ID column. Each rule is constructed by linking to key reference tables: it associates a specific OBJECT_ID (from SO_OBJECTS, such as an order header or line), an ATTRIBUTE_ID (from SO_ATTRIBUTES, a field like customer or price), and an ACTION_ID (from SO_ACTIONS, like query or update). The rule's outcome or enforcement logic is determined by its link to a RESULT_ID in the SO_RESULTS_B table, which defines the security condition or restriction to apply.

Common Use Cases and Queries

A primary use case is troubleshooting user access issues within the Order Management forms. For instance, if a user cannot view orders for a specific operating unit, an administrator can query the active rules to diagnose the conflict. Common reporting needs include listing all security rules applicable to a particular responsibility or generating a security matrix for audit purposes. A typical diagnostic query would join SO_SECURITY_RULES to its referenced tables to make the rule components human-readable:

• SELECT s.security_rule_id, obj.name object_name, attr.name attribute_name, act.name action_name FROM oe.so_security_rules s, so_objects obj, so_attributes attr, so_actions act WHERE s.object_id = obj.object_id AND s.attribute_id = attr.attribute_id(+) AND s.action_id = act.action_id;

Rule creation and maintenance are typically performed via the Oracle EBS front-end "Order Security Rules" form, not via direct SQL DML.

Related Objects

As documented, SO_SECURITY_RULES maintains integral foreign key relationships with several foundational tables in the Order Entry security model. These relationships define the rule's components:

• SO_OBJECTS: Links via OBJECT_ID. Defines the order management entity (e.g., Order Header) to which the rule applies.
• SO_ATTRIBUTES: Links via ATTRIBUTE_ID. Defines the specific attribute or column of the object that is secured.
• SO_ACTIONS: Links via ACTION_ID. Defines the user operation (e.g., SELECT, UPDATE) that the rule governs.
• SO_RESULTS_B: Links via RESULT_ID. Contains the security condition logic (the "result") that is enforced when the rule is triggered, such as a WHERE clause predicate.

The table is also governed by its primary key constraint, SO_SECURITY_RULES_PK, on the SECURITY_RULE_ID column.