Results for “edr_rule_condition_temp”

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

Overview

EDR_RULE_CONDITION_TEMP is a temporary table residing in the EDR schema, the database owner associated with the EDR - E-Records product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions within the Oracle E-Records (ERES) framework, which provides electronic signature and electronic record compliance capabilities across EBS transactions. Specifically, this table supports the input variable eRecord by materializing the rule conditions that govern how an eRecord is evaluated at runtime. During transaction processing, ERES evaluates configured rules against transaction data; this temporary table holds the intermediate result set of those rule conditions for the duration of an active session.

From a Data Vault modeling perspective, the metadata's heuristic FK analysis classifies this object as standalone, meaning it exhibits no foreign key dependencies on other EDR objects within the mined relationship structure. A modeling suggestion would be to treat it as neither a conventional hub, link, nor satellite, since the table serves as a transient staging structure rather than a persistent historical store. Data is session-bound and short-lived, populated and consumed within a single ERES processing cycle.

Key Information Stored

The table defines five documented columns. Its primary key, EDR_RULE_CONDITION_TEMP_PK, is a composite surrogate key comprising four columns, which together uniquely identify each condition row within a session:

• SESSION_ID — Identifies the active ERES session under which rule conditions are being evaluated. As part of the composite primary key, it scopes all rows to a single processing context and prevents cross-session collisions in the shared temp table.
• TRANSACTION_TYPE_ID — References the transaction type whose rules are being applied. This distinguishes conditions belonging to different EBS transaction types processed within the same session.
• RULE_ID — Identifies the specific rule being evaluated. Multiple conditions may attach to a single rule, making this a key discriminator.
• CONDITION_ID — Identifies the individual condition within the rule. Combined with RULE_ID, it forms the finest level of granularity in the composite key.
• CONDITION_DESC — A descriptive attribute holding the textual description of the condition. This is the sole non-key column and is typically used for display or diagnostic reporting when presenting rule evaluation results.

The four key columns constitute the business-key candidate set as documented by the PK definition; no separate unique index is recorded in the metadata. Since CONDITION_DESC is the only descriptive attribute, the table is narrow and optimized for fast insert-and-read operations rather than analytical storage.

Common Use Cases and Queries

The primary use case is runtime support of ERES rule evaluation. Application code inserts condition rows at the start of a rule-processing cycle, reads them as eRecord input variables are resolved, and the rows are discarded or truncated at session end. Typical operational queries include:

• Retrieving all conditions for a session to validate rule evaluation: SELECT RULE_ID, CONDITION_ID, CONDITION_DESC FROM EDR_RULE_CONDITION_TEMP WHERE SESSION_ID = :p_session_id ORDER BY RULE_ID, CONDITION_ID;
• Diagnosing which conditions applied to a given transaction type: SELECT TRANSACTION_TYPE_ID, RULE_ID, COUNT(*) FROM EDR_RULE_CONDITION_TEMP GROUP BY TRANSACTION_TYPE_ID, RULE_ID;
• Joining to rule definition tables on RULE_ID and CONDITION_ID to reconcile configured versus evaluated conditions.

Reporting use is limited because rows are ephemeral; auditing should target the permanent rule and eRecord tables, not this temp structure. DBA monitoring may check row counts per SESSION_ID to detect orphaned or stale sessions.

Related Objects

Because the mined relationship data classifies this table as standalone, few hard FK links are documented. The following represent the most significant associated objects based on the EDR E-Records domain and the key columns present:

• EDR_RULES (or the corresponding rule definition table) — joined on RULE_ID to retrieve rule-level metadata.
• EDR_RULE_CONDITIONS — joined on RULE_ID and CONDITION_ID to reconcile runtime condition rows against configuration.
• EDR_TRANSACTION_TYPES — joined on TRANSACTION_TYPE_ID to resolve transaction type context.
• EDR_SESSIONS / ERES session tables — joined on SESSION_ID to correlate conditions with a specific electronic signature session.
• EDR_ERECORD structures supporting the eRecord input variable — the consuming context for these rows.
• ERES PL/SQL packages that populate and read this temp table — the programmatic interface through which all access occurs.

Note that joins should be validated against the actual installed schema, as this table is undocumented beyond the composite key and column list provided.