Search Results ece_rule_null_dep_pk

Overview

ECE_RULE_NULL_DEP is a configuration table in the Oracle e-Commerce Gateway (EC) module, residing in the EC schema and documented as VALID in Oracle EBS 12.1.1 and 12.2.2. Its stated purpose is to hold column rule null dependency information — that is, the metadata that governs how a null value in one inbound or outbound interface column constrains the validity of another column during gateway processing. The table functions as part of the rule-driven translation and validation engine that e-Commerce Gateway applies to flat-file and XML transactions before data is loaded into or extracted from Oracle EBS.

From the mined foreign-key topology, the object is heuristic-classified as hub-leaning in Data Vault terms. Treated as a modelling suggestion rather than a normative declaration, the single-column primary key and its role as the parent of a details table suggest ECE_RULE_NULL_DEP behaves like a hub (a relatively stable list of distinct dependency rules), while date and audit columns give it a satellite flavor. Designers building a Data Vault layer over EBS should treat it accordingly.

Key Information Stored

The table is documented with 12 physical columns in the ETRM 12.2.2 schema. The most significant include:

• NULL_DEPENDENCY_RULE_ID — the surrogate primary key, enforced by index ECE_RULE_NULL_DEP_PK, and also the sole column of unique index ECE_RULE_NULL_DEP_U1. It is therefore both the surrogate and the documented business-key candidate.
• COLUMN_RULE_ID — a foreign key to ECE_COLUMN_RULES, tying the null dependency back to the parent column rule it qualifies.
• COMPARISON_CODE — the operator or comparison logic applied when evaluating the null dependency condition between the related columns.
• CREATION_DATE, CREATED_BY — standard who/when audit columns recording rule creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit trail for the most recent modification and the session that made it.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context, identifying the request and program that inserted or last updated the row, enabling traceability to the defining process.

The audit and concurrent-program columns are the standard EBS “WHO” and “program context” column sets; they are rarely meaningful for functional reporting but are essential for troubleshooting rule changes.

Common Use Cases and Queries

Typical usage centers on diagnosing why a gateway interface rejected, defaulted, or failed to populate a column. Administrators join the table to ECE_COLUMN_RULES and ECE_RULE_NULL_DEP_DETAILS to reconstruct the complete dependency definition:

• Dependency listing: SELECT r.NULL_DEPENDENCY_RULE_ID, r.COLUMN_RULE_ID, r.COMPARISON_CODE FROM EC.ECE_RULE_NULL_DEP r ORDER BY r.NULL_DEPENDENCY_RULE_ID;
• Rule lineage join: join COLUMN_RULE_ID to ECE_COLUMN_RULES to identify the owning interface, transaction type, and column.
• Detail expansion: join to ECE_RULE_NULL_DEP_DETAILS on NULL_DEPENDENCY_RULE_ID to see the specific dependent columns and their conditions.
• Change auditing: filter on LAST_UPDATE_DATE or REQUEST_ID to find rules altered by a particular concurrent program run during interface troubleshooting.

Reporting use cases include documenting gateway validation configuration during upgrades and reconciling customizations before patching EC module logic.

Related Objects

• ECE_COLUMN_RULES — referenced by COLUMN_RULE_ID; the parent definition of the column being constrained.
• ECE_RULE_NULL_DEP_DETAILS — child table referencing NULL_DEPENDENCY_RULE_ID; stores the individual null dependency detail rows.
• ECE_RULE_NULL_DEP_PK — primary key index on NULL_DEPENDENCY_RULE_ID.
• ECE_RULE_NULL_DEP_U1 — unique index on NULL_DEPENDENCY_RULE_ID, the documented business-key candidate.

These objects together form the configuration substrate that the e-Commerce Gateway validation engine consults when translating transaction data between external formats and Oracle EBS interface tables.