Search Results datatype_checking

Overview

EC.ECE_COLUMN_RULES is a seed data table within the Oracle E-Business Suite EC (e-Commerce/Advanced Supply Chain) schema that stores column rule definitions used by the generic inbound execution engine of the EDI/interface processing framework. Each row represents a single rule applied against a specific column of an inbound interface, governing validation and transformation behavior during execution. The table sits at the center of a rule-driven architecture: a parent interface column may carry many rules, and each rule in turn spawns one or more type-specific child records that supply the parameters for the rule's execution.

The object is classified heuristically as a standalone Data Vault structure. In Data Vault modeling terms, this classification suggests the table can be treated as an independent hub-like entity keyed on its own surrogate identifier rather than participating in a hub-and-link relationship with other hubs. The absence of outbound foreign keys supports this treatment; the table is referenced by dependent child tables but does not itself resolve to a parent.

Key Information Stored

Each row is anchored by COLUMN_RULE_ID, a NUMBER(15) surrogate primary key that uniquely identifies the rule and is enforced by the unique index ECE_COLUMN_RULES_U1. This index is the documented business-key candidate; because the identifier is system-generated, it functions as a surrogate rather than a natural business key. The column is referenced by every child rule table, making it the principal join key across the rule subsystem.

The INTERFACE_COLUMN_ID column ties each rule to exactly one row in ECE_INTERFACE_COLUMNS, establishing the one-to-many parent-child relationship between an interface column and its rules. The SEQUENCE column determines execution order when multiple rules apply to the same column, ensuring deterministic validation and transformation behavior. RULE_TYPE is a VARCHAR2(80) discriminator that identifies the nature of the rule; seeded examples documented by Oracle include VALUE_REQUIRED, applied automatically to mandatory (not null) columns, and DATATYPE_CHECKING, seeded for Number and Date columns. The VARCHAR2(20) ACTION_CODE column specifies the action to take when the rule is violated, supporting conditional processing outcomes rather than a simple pass/fail.

The remaining columns are standard WHO audit attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. These track row provenance and support concurrent program diagnostics.

Common Use Cases and Queries

The primary operational scenario is diagnosing why an inbound interface load fails. A support analyst queries the column rules for a failing interface column to determine which rule was violated and what action the engine should have taken:

• List all rules for a specific interface column in execution order: SELECT COLUMN_RULE_ID, SEQUENCE, RULE_TYPE, ACTION_CODE FROM ECE_COLUMN_RULES WHERE INTERFACE_COLUMN_ID = :column_id ORDER BY SEQUENCE.
• Identify required-value enforcement across an interface: SELECT r.RULE_TYPE, c.COLUMN_NAME FROM ECE_COLUMN_RULES r, ECE_INTERFACE_COLUMNS c WHERE r.INTERFACE_COLUMN_ID = c.INTERFACE_COLUMN_ID AND r.RULE_TYPE = 'VALUE_REQUIRED'.
• Audit rule maintenance activity using the WHO columns, filtering on CREATED_BY or LAST_UPDATE_DATE to review changes made through the Interface File Definition form.
• Reconcile rule types against their child parameter tables to confirm that every rule of a given type has the supporting detail record it requires.

Because rules are seeded by Oracle for standard columns, reporting should distinguish seeded rows from customer-defined rows when assessing configuration drift between environments.

Related Objects

ECE_COLUMN_RULES is the parent of a family of rule-detail tables, each holding parameters for a specific rule type. The documented foreign key relationships are:

• ECE_RULE_NULL_DEP — null-dependency rule parameters.
• ECE_RULE_NULL_DEFAULT — null defaulting behavior.
• ECE_RULE_SIMPLE_LOOKUP — simple lookup validation.
• ECE_RULE_VALUESET — value set validation.
• ECE_RULE_LIST — list-based validation.
• ECE_COLUMN_RULES_UPG — upgrade staging for column rules.
• AMS_COLUMN_RULES — marketing schema rules referencing the same identifier.

All of these join on COLUMN_RULE_ID. The parent object ECE_INTERFACE_COLUMNS is joined on INTERFACE_COLUMN_ID, and the nonunique index ECE_COLUMN_RULES_N1 supports efficient retrieval of all rules for a given interface column.