Results for “compiled_information”

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

Overview

SO_STANDARD_VALUE_RULE_SETS is an Oracle Order Entry (OE) table that stores standard value rule sets — named containers that group individual standard value rules used to default, derive, or validate attribute values on order lines, order headers, and related entities during order capture. The table belongs to the OE schema and is documented as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the definitional header for the rule-set construct: each row represents one reusable set that can be referenced by downstream configuration such as order types, so that the same collection of defaulting and validation logic can be applied consistently across multiple order entry contexts without redundant setup.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object is hub-leaning. It carries a single, stable business key (NAME) along with a surrogate primary key (STANDARD_VALUE_RULE_SET_ID), and it is referenced as a parent by other tables rather than aggregating transactional detail itself. This classification is heuristic and intended as a modeling suggestion, not a prescriptive design.

Key Information Stored

The table exposes 25 documented columns. The most significant are:

• STANDARD_VALUE_RULE_SET_ID — surrogate primary key (SO_STANDARD_VALUE_RULE_SETS_PK). Uniquely identifies each rule set and is the column propagated to dependent tables.
• NAME — the user-facing business identifier for the rule set, enforced unique by SO_STANDARD_VALUE_RULE_SETS_U2. This is the primary business-key candidate.
• DESCRIPTION — free-text explanation of the rule set's purpose, typically surfaced in setup and inquiry forms.
• CONTEXT — descriptive flexfield context, governing which ATTRIBUTE columns are active for the row.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments for customer-specific or localization extensions.
• COMPILED_INFORMATION — a long/LOB column holding compiled or cached rule-set metadata used at runtime by the order capture engine.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN provide standard EBS who-column auditing.

Note that STANDARD_VALUE_RULE_SET_ID is also exposed through unique index SO_STANDARD_VALUE_RULE_SETS_U1. The documented indexes therefore confirm two natural access paths: by surrogate ID and by NAME.

Common Use Cases and Queries

Typical use cases include setup validation, impact analysis before deleting or renaming a rule set, and reporting on which rule sets are actively bound to order types. A basic lookup by name pattern follows:

• SELECT standard_value_rule_set_id, name, description FROM oe.so_standard_value_rule_sets WHERE UPPER(name) LIKE 'DEFAULT%';
• Impact analysis — find order types referencing a given rule set: SELECT t.order_type_id, t.name FROM oe.so_order_types_115_all t WHERE t.standard_value_rule_set_id = :rule_set_id;
• Rule inventory — count rules per set: SELECT r.standard_value_rule_set_id, COUNT(*) FROM oe.so_standard_value_rules r GROUP BY r.standard_value_rule_set_id;
• Orphan detection — identify rule sets with no child rules or no order type binding.

These queries support setup auditing, migration testing, and reporting for order management implementations.

Related Objects

The most significant related objects, grounded in the documented FK data:

• SO_STANDARD_VALUE_RULES — child table; join on SO_STANDARD_VALUE_RULES.STANDARD_VALUE_RULE_SET_ID = SO_STANDARD_VALUE_RULE_SETS.STANDARD_VALUE_RULE_SET_ID. Holds the individual rules within a set.
• SO_ORDER_TYPES_115_ALL — references this table via STANDARD_VALUE_RULE_SET_ID, associating a rule set with an order type.
• SO_STANDARD_VALUE_RULE_SETS_PK / _U1 / _U2 — primary and unique indexes enforcing identity and business-key uniqueness.
• OE Order Entry setup forms and the order capture runtime engine consume COMPILED_INFORMATION when applying defaults and validations.