Search Results ece_column_rules




Overview
Explore in AI Chat

Overview

ECE_COLUMN_RULES is a configuration table in the Oracle e-Commerce Gateway (EC) module, owned by the EC schema. It stores the column rule assignments that govern how individual interface columns are validated, transformed, or defaulted during inbound and outbound e-Commerce Gateway processing. Each row associates a rule with a specific interface column, effectively binding a rule definition to the column to which it applies. This table is central to the ECE rule engine: interface definitions define the columns exchanged with trading partners, and ECE_COLUMN_RULES determines which rule behavior executes against each column.

From a Data Vault modeling perspective, the metadata classifies this table as standalone (no upstream parent foreign key). As a modeling suggestion, ECE_COLUMN_RULES is best treated as a hub-like reference object keyed on COLUMN_RULE_ID, with descriptive rule attributes (RULE_TYPE, ACTION_CODE, SEQUENCE) behaving as satellite attributes. Its dependent rule-implementation tables (list, valueset, simple lookup, null default, null dependency) function as links or satellites that hang off this hub.

Key Information Stored

The documented physical schema for 12.2.2 contains 14 columns. The most significant are:

  • COLUMN_RULE_ID — the surrogate primary key (ECE_COLUMN_RULES_PK) and also the business-key candidate via unique index ECE_COLUMN_RULES_U1. All dependent rule tables reference this column.
  • INTERFACE_COLUMN_ID — identifies the interface column to which the rule is assigned; this is the linkage into the interface definition (column) metadata.
  • SEQUENCE — controls the evaluation or application order when multiple rules apply to a column.
  • RULE_TYPE — indicates the category of rule (for example, list, value set, simple lookup, null default, or null dependency), effectively the discriminator that determines which dependent implementation table supplies the rule body.
  • ACTION_CODE — indicates the action the rule performs on the column (for example, default, validate, or translate).
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing who created and last modified the row and when.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns identifying the request and program that inserted or last updated the row.

The dependent rule tables carry their own payload columns (for example, list entries, value set references, or default values) but always resolve back to ECE_COLUMN_RULES.COLUMN_RULE_ID.

Common Use Cases and Queries

Typical usage centers on diagnosing why a column value was defaulted, translated, or rejected during gateway processing, and on auditing rule configuration before or after a migration.

  • List all rules for a given interface column: SELECT column_rule_id, rule_type, action_code, sequence FROM ece_column_rules WHERE interface_column_id = :col_id ORDER BY sequence;
  • Enumerate dependent rule bodies by joining each implementation table on COLUMN_RULE_ID to see which rule types are in effect for a column.
  • Audit recently changed rules using LAST_UPDATE_DATE and LAST_UPDATED_BY, useful during configuration reviews and troubleshooting.
  • Identify orphaned or unused rules by checking for absence of matching rows in the dependent rule tables.

Reporting use cases include configuration inventories, rule-coverage reports per interface, and reconciliation of rules across environments (development versus production). Because rows are created and updated through concurrent programs, the REQUEST_ID and PROGRAM_ID columns support traceability back to the originating request.

Related Objects

ECE_COLUMN_RULES is referenced by several rule implementation tables, all via COLUMN_RULE_ID:

Together these objects form the rule engine behind e-Commerce Gateway column processing, with ECE_COLUMN_RULES acting as the assignment hub that ties rule definitions to interface columns.