Results for “condition_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SO_SECURITY_RULES is a transaction table owned by the OE (Order Entry) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the configurable order security rules that govern how order management data — orders, lines, and related entities — is filtered, modified, or restricted based on user, responsibility, or organizational context. Each row in this table defines a single rule component: a target object, an attribute, an optional condition, an action, and a result that determines the outcome when the rule is applied.

The table is central to Oracle Order Management's security framework, which determines which orders a user can view, update, delete, or copy. Rules can be configured through the Order Management setup forms without custom code, making this table both a configuration repository and a runtime lookup source for order entry and order inquiry operations.

Based on the foreign key structure — where this table holds references to multiple independent dimension-like parents (SO_OBJECTS, SO_ATTRIBUTES, SO_ACTIONS, SO_RESULTS_B) rather than acting as a parent itself — the heuristic Data Vault classification is link. This suggests a modeling approach where the rule definition connector represents the association among objects, attributes, actions, and results.

Key Information Stored

• SECURITY_RULE_ID — the surrogate primary key, enforced by SO_SECURITY_RULES_PK and additionally constrained by the unique index SO_SECURITY_RULES_U1. It uniquely identifies each rule row.
• OBJECT_ID — foreign key to SO_OBJECTS; identifies the secured business object (for example, an order or a line) to which the rule applies.
• ATTRIBUTE_ID — foreign key to SO_ATTRIBUTES; the attribute of the object that the rule evaluates.
• ACTION_ID — foreign key to SO_ACTIONS; the action the user is attempting, such as view or update.
• RESULT_ID — foreign key to SO_RESULTS_B; the outcome when the condition is satisfied, such as allowing or denying access.
• CONDITION_CODE — encodes the logical condition applied to the attribute value.
• SCOPE_CODE and OPERATION_CODE — control the breadth of the rule and the operation type.
• MODIFIER_CODE — qualifies how the rule interacts with other rules.
• SEQUENCE_NUMBER — orders rule evaluation when multiple rules apply.
• SYSTEM_FLAG — distinguishes seeded system rules from user-defined rules.
• CONTEXT and ATTRIBUTE1–15 — descriptive flexfield columns for extensibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns tracking who created and last modified each rule.

Common Use Cases and Queries

Typical scenarios include auditing which security rules are active, replicating security configuration across environments, and troubleshooting why a user can or cannot access a given order.

To list rules with their object, attribute, action, and result descriptions:

• SELECT ssr.security_rule_id, so.object_name, sa.attribute_name, sac.action_name, srb.result_name FROM oe.so_security_rules ssr JOIN oe.so_objects so ON ssr.object_id = so.object_id JOIN oe.so_attributes sa ON ssr.attribute_id = sa.attribute_id JOIN oe.so_actions sac ON ssr.action_id = sac.action_id JOIN oe.so_results_b srb ON ssr.result_id = srb.result_id ORDER BY ssr.sequence_number;

To isolate seeded versus custom rules, filter on SYSTEM_FLAG. To review recently changed security configuration, order by LAST_UPDATE_DATE descending and join to FND_USER via LAST_UPDATED_BY for the modifier name. For migration audits, extract all rows with SECURITY_RULE_ID beyond the seeded range to identify customer-created rules.

Related Objects

• SO_OBJECTS — joined on OBJECT_ID; defines the secured business objects.
• SO_ATTRIBUTES — joined on ATTRIBUTE_ID; defines rule-evaluated attributes.
• SO_ACTIONS — joined on ACTION_ID; defines permitted/denied actions.
• SO_RESULTS_B — joined on RESULT_ID; holds the outcome definitions that determine the effect of each rule.
• SO_SECURITY_RULES_PK / SO_SECURITY_RULES_U1 — the primary key and unique index enforcing integrity on SECURITY_RULE_ID.

Because the table references multiple parent definitions rather than being referenced itself, dependent logic resides largely in Order Entry security views and the Order Management setup UI rather than in additional FK-dependent child tables.