Search Results ece_rule_null_dep_details




Overview
Explore in AI Chat

Overview

ECE_RULE_NULL_DEP_DETAILS is a child table within the e-Commerce Gateway (EC) module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. It resides in the EC schema and holds the attribute-level criteria that define how null-dependency rules are evaluated during outbound and inbound interface processing. The parent object, ECE_RULE_NULL_DEP, stores the rule header — the interface context and rule identity — while this child table stores the ordered detail rows that specify which interface column is tested, how it is compared, and against what value. Together the two tables drive the logic that determines whether a transaction's dependent fields are considered null, an evaluation that governs whether a record is suppressed, defaulted, or processed by the gateway.

The ETRM record documents the table as VALID with a single foreign key relationship and fourteen columns. From a Data Vault modeling perspective, the mined FK structure suggests this object is satellite-leaning: it is a descriptive, multi-row extension hanging off a parent rule key rather than an independent hub or an associative link between two business entities. This classification is a heuristic suggestion derived from the foreign-key topology, not an enforced physical design, and it should be treated as guidance for integration or warehousing efforts rather than a constraint on the EBS schema itself.

Key Information Stored

The table's surrogate primary key is NULL_DEPENDENCY_DETAIL_ID, enforced by the constraint ECE_RULE_NULL_DEP_DETAILS_PK and mirrored by the unique index ECE_RULE_NULL_DEP_DETAILS_U1. Although the unique index is documented as a business-key candidate, in practice this column is a system-generated identifier rather than a meaningful business key; the genuine business identity of a row is the combination of its parent rule and its target interface column.

The audit and concurrent-program columns follow the standard EBS WHO-column convention and are typically populated automatically by the application or by concurrent processing rather than by user entry.

Common Use Cases and Queries

Typical uses center on inspecting, exporting, or migrating gateway rule configuration. A configuration analyst reviewing which columns are tested for a given rule joins the detail table to its parent:

  • Rule inspection: SELECT d.INTERFACE_COLUMN, d.COMPARISON_CODE, d.VALUE FROM ECE_RULE_NULL_DEP_DETAILS d WHERE d.NULL_DEPENDENCY_RULE_ID = :rule_id ORDER BY d.NULL_DEPENDENCY_DETAIL_ID;
  • Environment comparison: extract both tables from development and production and diff by rule and interface column to detect configuration drift.
  • Audit reporting: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify who modified gateway rule logic and when.
  • Migration and cloning: the detail rows must be carried alongside the parent header, since a rule without its details has no evaluation criteria.

Because this is configuration metadata rather than transactional data, volumes are low and full-table scans are acceptable; index-driven access via the foreign key is the normal path.

Related Objects

  • ECE_RULE_NULL_DEP — the mandatory parent, joined on ECE_RULE_NULL_DEP_DETAILS.NULL_DEPENDENCY_RULE_ID = ECE_RULE_NULL_DEP.NULL_DEPENDENCY_RULE_ID. This is the primary relationship documented in the FK metadata.
  • ECE_RULE_NULL_DEP_DETAILS_PK / _U1 — the primary key constraint and unique index enforcing row identity.
  • ECE interface definition tables — the EC module tables that define interface columns referenced by INTERFACE_COLUMN, which provide the vocabulary for the values stored here.
  • EC concurrent programs and requests — FND_CONCURRENT_REQUESTS and related program definitions referenced indirectly by REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID.
  • FND_USER — the user referenced by CREATED_BY and LAST_UPDATED_BY for ownership and audit reporting.

These objects should be considered the core set for any query, extract, or integration touching null-dependency rule detail data.