Search Results ece_process_rules_pk

Overview

ECE_PROCESS_RULES is a transactional configuration table owned by the EC schema within the Oracle e-Commerce Gateway (EC) product. Its documented purpose is to contain process rule assignments — the mapping records that determine how inbound and outbound e-commerce transactions are routed and processed. Each row associates a transaction type with a rule type, an action code, and a map identifier, effectively defining the behavior the Gateway applies when processing a given interface document.

In Oracle EBS 12.1.1 and 12.2.2, EC is the module responsible for translating flat files to and from Oracle interface tables for trading partner transactions such as purchase orders, invoices, and advance ship notices. ECE_PROCESS_RULES sits at the center of that configuration logic, alongside the trading partner and map definition tables.

The documented metadata classifies this object heuristically as standalone in Data Vault terms. Adopting that suggestion, ECE_PROCESS_RULES is best modeled as a link-style configuration object: it resolves the relationship between a transaction type and a rule type via a MAP_ID, rather than acting as an immutable hub. Because configuration rows are routinely updated and rarely deleted, a satellite-style treatment keyed on PROCESS_RULE_ID with change tracking on LAST_UPDATE_DATE is also appropriate when historization is required.

Key Information Stored

The table exposes 14 documented columns. The most significant are summarized below; the surrogate primary key is distinguished from the business-key candidates defined by the table's unique indexes.

• PROCESS_RULE_ID — the surrogate primary key, enforced by ECE_PROCESS_RULES_PK and also by the unique index ECE_PROCESS_RULES_U1. It uniquely identifies each process rule assignment.
• TRANSACTION_TYPE — identifies the e-commerce transaction (for example, an outbound purchase order or inbound invoice) to which the rule applies.
• RULE_TYPE — the category of processing rule being assigned, governing which processing stage or handler the row controls.
• MAP_ID — the identifier of the associated map definition that converts the transaction between flat-file and interface formats.
• Together, TRANSACTION_TYPE, RULE_TYPE, and MAP_ID form the business-key candidate enforced by the unique index ECE_PROCESS_RULES_U2, ensuring a one-to-one assignment per transaction type and rule type.
• ACTION_CODE — the action the Gateway performs when the rule is satisfied.
• CREATION_DATE, CREATED_BY — standard audit columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification and its session context.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context, indicating the request and program responsible for the most recent row change. These are valuable for reconciling configuration changes to specific concurrent runs.

Common Use Cases and Queries

The principal use case is diagnosing e-commerce processing behavior: identifying which map and action apply to a given transaction type, and confirming that processing rules are complete and unambiguous. Configuration review, migration validation between environments, and support triage of failed Gateway runs are all common scenarios.

A representative query retrieves all rules for a given transaction type, joining the map definition to obtain a descriptive name:

• SELECT p.process_rule_id, p.transaction_type, p.rule_type, p.action_code, p.map_id FROM ec.ece_process_rules p WHERE p.transaction_type = :transaction_type;

To detect configuration drift or verify the unique assignment, compare environments by transaction type, rule type, and map:

• SELECT transaction_type, rule_type, map_id FROM ec.ece_process_rules ORDER BY transaction_type, rule_type;

Audit-oriented reporting uses the standard audit columns to answer who last changed a rule and through which concurrent request:

• SELECT process_rule_id, last_updated_by, last_update_date, request_id, program_id FROM ec.ece_process_rules WHERE last_update_date > :since;

Related Objects

Because the mined relationship data classifies ECE_PROCESS_RULES as standalone — no inbound or outbound foreign keys are documented — the related objects are inferred from the business meaning of its MAP_ID and TRANSACTION_TYPE columns and from standard EC module conventions. The most significant associations are:

• ECE_MAP_DEFINITIONS — the map definition table referenced logically by MAP_ID, supplying the map used for file-to-interface conversion.
• ECE_TRADING_PARTNERS — the trading partner configuration governing which partners participate in a transaction type.
• ECE_TP_DETAILS — trading partner detail records that further qualify processing behavior.
• FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS — joined on PROGRAM_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID to trace configuration changes to concurrent program executions.
• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY to resolve the user identities recorded in the audit columns.

Joins on PROCESS_RULE_ID are not documented to any child table; treat the primary key as internal to this configuration object and rely on the business-key columns for integration.