Search Results csd_rules_b_u1

Overview

CSD.CSD_RULES_B is the base table for Defaulting Rules within the Oracle E-Business Suite Customer Service (CSD) schema. Defaulting rules drive automatic population of attribute values on service request, task, and related entity records, allowing organizations to pre-fill fields such as priority, status, owner, or category based on evaluated conditions and precedences. The table stores the header-level definition of each rule, including its type, precedence ranking, target entity attribute, and the value to be applied when the rule fires.

The object resides in the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as CSD.CSD_RULES_B. From a Data Vault modeling heuristic, this table is classified as hub-leaning: RULE_ID behaves as a durable business key that anchors the rule identity, while attributes such as PRECEDENCE, RULE_TYPE_CODE, and the descriptive flexfield segments function as dependent descriptive data. In practice, RULE_ID is also the surrogate primary key from an EBS perspective, so the hub and its associated descriptive context are merged into a single base table rather than being normalized into satellite structures.

Key Information Stored

The table contains 28 documented columns. The most significant are:

• RULE_ID (NUMBER) — Surrogate primary key and business-key candidate. It is enforced by the unique index CSD_RULES_B_U1 on APPS_TS_TX_IDX, and it is the column referenced by child tables.
• RULE_TYPE_CODE (VARCHAR2, 30) — Classifies the rule type, determining which defaulting engine or entity context consumes the rule.
• PRECEDENCE (NUMBER) — Controls evaluation order when multiple rules match the same entity attribute; lower or higher precedence determines which default is applied.
• ENTITY_ATTRIBUTE_TYPE (VARCHAR2, 30) — Identifies the category or type of entity attribute targeted by the rule.
• ENTITY_ATTRIBUTE_CODE (VARCHAR2, 30) — The specific attribute code that the rule defaults.
• VALUE_TYPE_CODE (VARCHAR2, 30) — Indicates how the default value is derived, for example a literal value, a profile option, or a lookup.
• ATTRIBUTE_CATEGORY (VARCHAR2, 30) — Descriptive flexfield structure definition column supporting rule extensibility.
• ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2, 150) — Descriptive flexfield segments that store context-specific rule parameters.
• OBJECT_VERSION_NUMBER — Standard optimistic locking column used by the EBS framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing audit trail information.

Common Use Cases and Queries

Developers and functional analysts query CSD_RULES_B to diagnose why a field defaulted to an unexpected value, to audit rule configuration, or to migrate rules between environments. A typical pattern joins the header to its condition rows:

SELECT r.RULE_ID, r.RULE_TYPE_CODE, r.PRECEDENCE, r.ENTITY_ATTRIBUTE_CODE, r.VALUE_TYPE_CODE, c.CONDITION_ID, c.OPERATOR, c.VALUE FROM CSD.CSD_RULES_B r, CSD.CSD_RULE_CONDITIONS_B c WHERE r.RULE_ID = c.RULE_ID AND r.ENTITY_ATTRIBUTE_CODE = :attribute ORDER BY r.PRECEDENCE;

Reporting use cases include listing active rules by precedence for a given entity attribute, extracting descriptive flexfield context values for documentation, and reconciling rule definitions across instances during a clone or upgrade. Because the table is hub-leaning, incremental extraction patterns commonly use LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER to identify changed rule definitions.

Related Objects

• CSD.CSD_RULE_CONDITIONS_B — Child table linked through the foreign key CSD_RULE_CONDITIONS_B.RULE_ID referencing CSD_RULES_B.RULE_ID. It stores the condition expressions evaluated before a default is applied.
• CSD.CSD_RULES_TL — Translation table for rule names and descriptions, joined on RULE_ID in multilingual deployments.
• FND_USER — Referenced by CREATED_BY and LAST_UPDATED_BY for audit reporting.
• FND_LOGINS — Referenced by LAST_UPDATE_LOGIN to resolve the originating login session.
• CSD Defaulting Rules setup UI and concurrent programs — Application-layer consumers that read RULE_TYPE_CODE, PRECEDENCE, and ENTITY_ATTRIBUTE_CODE to drive the runtime defaulting engine.