Search Results default_type_code

Overview

EC.ECE_RULE_NULL_DEFAULT is a seed data table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 trading model (ETRM) schema. It stores the null default rules that govern what action the rules engine should take, and what value should be defaulted into a column, when a column rule with a null default is applied to a column in a transaction. Each row represents one null default rule instance, linked back to its parent column rule. The table resides in the APPS_TS_SEED tablespace, confirming its role as configuration and reference data rather than transactional data.

From a Data Vault modeling perspective, the metadata classifies this object as standalone (heuristic, mined from its foreign key structure). In practice this suggests ECE_RULE_NULL_DEFAULT functions as a satellite-like attribute table attached to the ECE_COLUMN_RULES business key, carrying descriptive default behavior attributes rather than serving as a pure hub or link. Administrators generally treat this as supporting detail behind the column rule definition.

Key Information Stored

The table contains 13 columns. The primary key is NULL_DEFAULT_ID, a NUMBER(15) surrogate identifier for the null default rule, and it is also enforced through the unique index ECE_RULE_NULL_DEFAULT_U1 on the same column. The business relationship is carried by COLUMN_RULE_ID, which references ECE_COLUMN_RULES and determines which column rule the default action belongs to.

• DEFAULT_TYPE_CODE — the VARCHAR2(20) code that indicates whether VALUE_COLUMN_NAME holds a literal value or a source column name. This is the column most frequently queried by users searching for "default_type_code".
• VALUE_COLUMN_NAME — VARCHAR2(240), holding either the default value or the column name to copy from, interpreted according to DEFAULT_TYPE_CODE.
• NULL_DEFAULT_ID — the surrogate primary key and unique index column.
• COLUMN_RULE_ID — foreign key to the parent column rule in ECE_COLUMN_RULES.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The principal use case is auditing and troubleshooting which default behavior will be applied when a column rule executes in a transaction. Reporting typically joins this table to ECE_COLUMN_RULES to resolve the parent rule context. A typical query filtering on the requested attribute is:

• SELECT NULL_DEFAULT_ID, COLUMN_RULE_ID, DEFAULT_TYPE_CODE, VALUE_COLUMN_NAME FROM EC.ECE_RULE_NULL_DEFAULT WHERE DEFAULT_TYPE_CODE = :code;
• Join to the parent rule: SELECT a.COLUMN_RULE_ID, a.DEFAULT_TYPE_CODE, a.VALUE_COLUMN_NAME FROM EC.ECE_RULE_NULL_DEFAULT a, EC.ECE_COLUMN_RULES b WHERE a.COLUMN_RULE_ID = b.COLUMN_RULE_ID;
• Concurrent program audit: filter by REQUEST_ID or PROGRAM_ID to trace which load populated a given rule row.

Because DEFAULT_TYPE_CODE determines the interpretation of VALUE_COLUMN_NAME, validation reports should assert that when the code denotes a column reference, the named column is resolvable in the target transaction context.

Related Objects

The documentation identifies one direct referential relationship and one internal reference. Significant related objects include:

• EC.ECE_COLUMN_RULES — parent table referenced through COLUMN_RULE_ID; the primary join target.
• EC.ECE_RULE_NULL_DEFAULT# — the internal shadow object referenced by this table.
• EC.ECE_RULE_NULL_DEFAULT_U1 — the unique index on NULL_DEFAULT_ID.
• EC.ECE_RULE_NULL_DEFAULT_PK — the primary key constraint.

Any rule maintenance, transaction model configuration, or seed data extraction in the EC schema should be examined alongside this table to fully understand defaulting behavior.