Search Results ece_rule_valueset_u1

Overview

EC.ECE_RULE_VALUESET is a seed table in the Oracle E-Business Suite E-Commerce Gateway (ECE) module, owned by the EC schema and stored in the APPS_TS_SEED tablespace. Its purpose is to store information about column rule valueset validation. Per the documented behavior, a record is created in this table when a column rule valueset is assigned to a column in a transaction. As an extension of column-rule configuration, it defines the value-set constraints applied against specific incoming or outgoing transaction interface columns, supporting data validation during EDI and XML transaction processing.

From a modeling perspective, the Data Vault classification for this table is best characterized as a standalone or reference-style entity. It carries no dependent children and functionally serves as a link between a column rule and a named valueset, combined with descriptive attributes. It should therefore be treated as a durable, seeded configuration table rather than a high-volume transactional fact or a classic hub.

Key Information Stored

The table contains twelve documented columns. The most important are listed below.

• VALUESET_RULE_ID (NUMBER(15)) — the surrogate primary key and the single documented column of the unique index ECE_RULE_VALUESET_U1. It uniquely identifies each rule-to-valueset association and is the primary business-key candidate.
• COLUMN_RULE_ID (NUMBER(15)) — the foreign key to EC.ECE_COLUMN_RULES, tying the valueset assignment back to a specific column rule.
• VALUESET_NAME (VARCHAR2(60)) — the name of the valueset attached to the column rule; this is the primary descriptive, business-meaningful attribute.
• CREATION_DATE, CREATED_BY — standard Who columns recording the creation audit trail.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns recording the most recent modification.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the job that last inserted or updated the row.

The surrogate key (VALUESET_RULE_ID) is distinct from the unique index, but in this design the unique constraint is defined on the same column, making it the definitive single-column business key. No compositionally unique business key is documented.

Common Use Cases and Queries

Typical usage centers on reviewing and auditing the valueset validations that govern transaction column rules. Common scenarios include troubleshooting inbound EDI load failures caused by valueset validation, and reporting the valueset assignments across a configuration set.

• Lookup a rule's valueset: SELECT COLUMN_RULE_ID, VALUESET_NAME FROM EC.ECE_RULE_VALUESET WHERE VALUESET_RULE_ID = :rule_id;
• All valuesets for a given column rule: SELECT VALUESET_NAME FROM EC.ECE_RULE_VALUESET WHERE COLUMN_RULE_ID = :column_rule_id;
• Audit recent changes: SELECT VALUESET_RULE_ID, VALUESET_NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM EC.ECE_RULE_VALUESET ORDER BY LAST_UPDATE_DATE DESC;
• Trace to the concurrent program: join REQUEST_ID and PROGRAM_ID against FND_CONCURRENT_REQUESTS to identify the loader that seeded the row.

Because the table resides in APPS_TS_SEED and is configuration-oriented, its row volume is low and queries are generally simple single-table lookups or joins to ECE_COLUMN_RULES.

Related Objects

• EC.ECE_COLUMN_RULES — referenced via COLUMN_RULE_ID; the parent entity defining column rules.
• APPS.ECE_RULE_VALUESET — the APPS synonym exposed to the application layer.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the seeding program.
• FND_APPLICATION — joined on PROGRAM_APPLICATION_ID for program context.
• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for Who-column resolution.

No other database objects reference ECE_RULE_VALUESET, and it references only ECE_COLUMN_RULES, confirming its role as a leaf-level configuration table within the ECE column-rule framework.