Search Results ece_process_rules_u2

Overview

EC.ECE_PROCESS_RULES is a seed data table in the Oracle E-Business Suite EDI/EC (e-Commerce Gateway) schema. It stores the process rule assignments that drive the execution of the generic inbound process, allowing the EDI subsystem to determine which process rules are associated with a given transaction during inbound processing. Each row represents a single rule assignment bound to a specific map, and each process rule carries an associated ACTION_CODE that indicates the action to perform when the rule is violated. The table resides in the APPS_TS_SEED tablespace, which is characteristic of configuration and reference data rather than high-volume transactional data, reinforcing its role as a definition rather than a transaction store.

In Data Vault modeling terms, the heuristic classification for this object is a standalone structure. Since the metadata identifies no foreign-key dependencies to or from other tables, it is best modeled as an independent hub or reference construct rather than a link or satellite. The primary key ECE_PROCESS_RULES_PK is defined on PROCESS_RULE_ID, establishing the row-level surrogate identifier.

Key Information Stored

The table contains 14 documented columns. The most functionally significant are:

• PROCESS_RULE_ID (NUMBER 15) — Surrogate primary key of the table, backed by the unique index ECE_PROCESS_RULES_U1.
• TRANSACTION_TYPE (VARCHAR2 30) — The EDI transaction type to which the rule applies.
• RULE_TYPE (VARCHAR2 80) — The process rule type being evaluated.
• ACTION_CODE (VARCHAR2 20) — The action to perform when the rule is violated.
• MAP_ID (NUMBER 15) — The map with which the process rule is associated; documentedly one-to-many from ECE_MAPPINGS to ECE_PROCESS_RULES.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Who audit columns recording row creation and modification.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard concurrent program columns identifying the request and program that last updated the row.

The business-key candidate is defined by the composite unique index ECE_PROCESS_RULES_U2 on (TRANSACTION_TYPE, RULE_TYPE, MAP_ID), meaning the combination of transaction type, rule type, and map must be unique within the table. This composite index, rather than the surrogate PROCESS_RULE_ID, expresses the natural grain of the rule assignment.

Common Use Cases and Queries

Typical uses include reporting on configured process rules per map and transaction type, auditing rule changes, and troubleshooting inbound EDI failures when a rule is violated. A direct extraction follows the documented query text:

• SELECT PROCESS_RULE_ID, TRANSACTION_TYPE, RULE_TYPE, ACTION_CODE, MAP_ID FROM EC.ECE_PROCESS_RULES;
• Filter by map: ... WHERE MAP_ID = :p_map_id; to enumerate all rules bound to a map.
• Filter by transaction: ... WHERE TRANSACTION_TYPE = :p_txn_type; to review rules for a specific EDI transaction.
• Join to mapping definitions using MAP_ID to resolve map names for reporting.

Related Objects

The metadata documents that ECE_PROCESS_RULES is referenced by the APPS synonym ECE_PROCESS_RULES. It does not itself reference any database object through declared foreign keys. The most significant logically related object is ECE_MAPPINGS, joined on MAP_ID, with which it shares a documented one-to-many relationship. Reporting queries therefore commonly join EC.ECE_PROCESS_RULES to EC.ECE_MAPPINGS via MAP_ID, and the APPS synonym exposes the table for custom concurrent programs and reports. Because the object is classified as standalone with no FK dependencies, broader integration should be validated against the actual ETRM relationship data for the release in use.