Search Results ece_column_rules_upg




Overview
Explore in AI Chat

Overview

The ECE_COLUMN_RULES_UPG table is an Oracle E-Business Suite table owned by the EC (e-Commerce Gateway) schema. It operates as a transient staging structure used during upgrade processing of column-level transformation rules in the e-Commerce Gateway module. The table holds configuration metadata that governs how inbound and outbound interface files translate or map their column values against the e-Commerce Gateway transaction definitions. It is present in both release 12.1.1 and 12.2.2, where it is documented as a VALID object with a physical schema comprising 14 columns.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies this object as a standalone construct with a single outbound reference rather than a true link entity. Based on its column shape — a surrogate identifier plus descriptive attributes and a full set of audit columns — the most reasonable modeling suggestion is to treat it as a satellite attached to the column-rule hub represented by ECE_COLUMN_RULES, reflecting the upgrade-time state of that business entity.

Key Information Stored

The table carries a surrogate primary key, COLUMN_RULE_ID, which also serves as a foreign-key reference into ECE_COLUMN_RULES. This column is the primary join candidate and is the business-identifying attribute at the row level. The remaining functional attributes capture the transformation semantics:

  • INTERFACE_COLUMN_ID — identifies the specific interface column to which the rule applies.
  • SEQUENCE — orders the application of rules where multiple rules affect the same column.
  • RULE_TYPE — the category of transformation logic being applied.
  • ACTION_CODE — the operation executed when the rule evaluates to true.

The remaining columns form a standard Oracle Applications audit and concurrent-processing envelope. CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide row-level audit tracking. REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE identify the concurrent program and request that last touched the row during the upgrade run. No unique business-key index is documented beyond the surrogate COLUMN_RULE_ID, so referential integrity is anchored entirely on that identifier.

Common Use Cases and Queries

The principal use case is diagnostic: confirming that upgrade-time column rules were staged and processed correctly before the staging rows are retired. A typical verification query filters by the parent rule set:

  • SELECT COLUMN_RULE_ID, INTERFACE_COLUMN_ID, SEQUENCE, RULE_TYPE, ACTION_CODE FROM EC.ECE_COLUMN_RULES_UPG WHERE COLUMN_RULE_ID = :rule_id ORDER BY SEQUENCE;
  • Inspecting REQUEST_ID and PROGRAM_ID to trace which concurrent program populated the rows.
  • Auditing CREATED_BY and LAST_UPDATED_BY to attribute changes to specific users or batch processes.
  • Comparing staged rows in ECE_COLUMN_RULES_UPG against the resident configuration in ECE_COLUMN_RULES to confirm parity post-upgrade.

Because the table is upgrade-scoped, it is not intended as a long-term reporting source; its value lies in reconciliation and troubleshooting during the upgrade window.

Related Objects

The documented foreign-key relationship is the most significant dependency: COLUMN_RULE_ID references ECE_COLUMN_RULES, making that table the parent configuration entity. Surrounding e-Commerce Gateway objects that participate in the same rule and interface definition model include ECE_2_OTHER_COLUMNS, ECE_2_OTHER_COLUMNS_B, ECE_2_OTHER_COLUMNS_TL, and the interface column definitions referenced through INTERFACE_COLUMN_ID. The concurrent-program envelope columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID) tie rows to FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS, which are useful for tracing the upgrade job that created each record.