Search Results csd_rules_b_pk1

Overview

CSD_RULES_B is the base table that stores Defaulting Rules within the Oracle E-Business Suite Depot Repair (CSD) module. It is owned by the CSD schema and holds the master definition rows for the rule engine that determines how attribute values are defaulted onto depot repair entities such as repair orders, repair lines, and related transactions. Each row in CSD_RULES_B represents a single defaulting rule, identified by a rule identifier and qualified by a rule type code, a precedence ranking, an entity attribute target, and a value type directive. The table is the parent (header) and CSD_RULE_CONDITIONS_B supplies the child condition rows that must be satisfied for a rule to fire.

The ETRM metadata records a Data Vault classification of "hub-leaning," which is a modeling suggestion rather than a physical fact: the table behaves like a hub because it is referenced by a dependent child via foreign key and its primary key, RULE_ID, is a stable, non-repeating surrogate identifier. In a Data Vault rendition, RULE_ID would form the hub business key, while descriptive and audit columns would be modeled as satellites and the relationship to CSD_RULE_CONDITIONS_B as a link or dependent child.

Key Information Stored

The documented physical schema for CSD_RULES_B in ETRM 12.2.2 contains 28 columns. The most significant are:

• RULE_ID — the primary key (constraint CSD_RULES_B_PK1) and the only documented unique index candidate (CSD_RULES_B_U1). It is the surrogate identifier for each defaulting rule and the join key to CSD_RULE_CONDITIONS_B.
• RULE_TYPE_CODE — classifies the rule, allowing the engine to group rules that apply to the same defaulting context.
• PRECEDENCE — determines evaluation order when multiple rules qualify for the same attribute.
• ENTITY_ATTRIBUTE_TYPE and ENTITY_ATTRIBUTE_CODE — identify the target entity and the attribute that the rule defaults.
• VALUE_TYPE_CODE — indicates how the default value is derived (for example, a constant, a profile option, or another source).
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications Framework for concurrent-update protection.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard who-column audit trail maintained across EBS tables.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns, giving customers an extensible segment area for site-specific rule metadata.

Business-key candidates are limited to RULE_ID; no composite natural key is documented, so RULE_ID should be treated as the durable identifier for joins and reconciliation.

Common Use Cases and Queries

Typical scenarios include diagnosing why a value was defaulted on a repair order, auditing rule configuration before upgrades, and reporting on the active rule set per rule type or precedence.

• List rules by type and precedence: SELECT rule_id, rule_type_code, precedence, entity_attribute_type, entity_attribute_code, value_type_code FROM csd.csd_rules_b ORDER BY rule_type_code, precedence;
• Retrieve a rule with its conditions: SELECT b.rule_id, b.rule_type_code, c.* FROM csd.csd_rules_b b, csd.csd_rule_conditions_b c WHERE b.rule_id = c.rule_id AND b.rule_id = :rule_id;
• Identify rules targeting a specific attribute: filter on ENTITY_ATTRIBUTE_TYPE and ENTITY_ATTRIBUTE_CODE, then rank by PRECEDENCE to predict which rule wins.
• DFF reporting: query ATTRIBUTE_CATEGORY with the ATTRIBUTE1–ATTRIBUTE15 columns to surface customer-defined rule segments.
• Concurrency and audit review: join on OBJECT_VERSION_NUMBER and the who-columns to detect recent or conflicting rule edits.

Related Objects

• CSD_RULE_CONDITIONS_B — the child table holding rule conditions; join on CSD_RULE_CONDITIONS_B.RULE_ID = CSD_RULES_B.RULE_ID. This is the only documented foreign-key relationship and the primary dependent object.
• CSD_RULES_TL — the translation table expected for multi-language rule names and descriptions, keyed by RULE_ID.
• CSD_RULE_CONDITIONS_TL — translation table for condition text, referenced indirectly through the conditions table.
• Defaulting rule engine / Depot Repair concurrent programs and forms — evaluate CSD_RULES_B and its conditions at runtime to populate repair entity attributes.
• CSD_REPAIR_ORDERS and CSD_REPAIR_LINES — repair entities whose attributes receive defaulted values produced by rules defined here.
• FND / DFF metadata tables — support the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 descriptive flexfield definitions used on this table.