Search Results ece_tran_parameters




Overview
Explore in AI Chat

Overview

ECE_TRAN_PARAMETERS is a configuration and seed data table owned by the EC schema within the Oracle e-Commerce Gateway (EC) module of Oracle E-Business Suite. It stores the generic inbound/outbound execution engine parameters that drive the processing of e-Commerce Gateway transactions. Because the e-Commerce Gateway uses a metadata-driven engine rather than hard-coded transaction logic, this table supplies the runtime definitions the engine consumes when it validates, parses, converts, or generates an EDI or XML transaction. Each row describes a single parameter associated with a particular transaction type, giving the execution engine the name, data type, ordinal position, and default value it needs to process that transaction consistently.

The table is documented in ETRM 12.2.2 as an EC-owned table with seven columns and primary key ECE_TRAN_PARAMETERS_PK on PARAMETER_ID. From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone, meaning it is not modeled as a hub, link, or satellite connected to other EC entities through declared foreign keys. It functions as an independent reference or setup table whose rows are consumed by the execution engine at runtime.

Key Information Stored

The documented physical schema contains seven columns. The most significant are:

  • PARAMETER_ID — Surrogate primary key defined by ECE_TRAN_PARAMETERS_PK; uniquely identifies each parameter record.
  • TRANSACTION_TYPE — Identifies the e-Commerce Gateway transaction (for example, an inbound purchase order or outbound invoice) to which the parameter belongs. This is the principal business grouping column.
  • NAME — The parameter name recognized by the inbound/outbound execution engine.
  • DATATYPE — The data type of the parameter, used by the engine to interpret and validate the value.
  • SEQUENCE_NUMBER — Controls the order in which parameters are presented or processed for a given transaction type.
  • DEFAULT_VALUE — The value applied when no explicit value is supplied, supporting seed and default behavior.
  • DESCRIPTION — Human-readable text explaining the parameter's purpose.

The metadata identifies PARAMETER_ID as the sole documented primary key. No separate unique business-key index is documented, so TRANSACTION_TYPE combined with NAME and SEQUENCE_NUMBER represents the most likely logical business identifier for a parameter definition, though this is inferred rather than confirmed by the provided metadata.

Common Use Cases and Queries

Typical uses center on inspecting, comparing, and troubleshooting e-Commerce Gateway engine configuration. Administrators query this table to understand which parameters a transaction expects, their order, and their defaults before running an inbound or outbound process. Reporting frequently joins it to transaction definition tables to document setup across environments.

Representative SQL patterns include:

  • Listing all parameters for a transaction type:
    SELECT parameter_id, name, datatype, sequence_number, default_value FROM ec.ece_tran_parameters WHERE transaction_type = :tran_type ORDER BY sequence_number;
  • Detecting parameters lacking a default:
    SELECT transaction_type, name FROM ec.ece_tran_parameters WHERE default_value IS NULL ORDER BY transaction_type, sequence_number;
  • Comparing configuration between instances by extracting NAME, DATATYPE, and DEFAULT_VALUE and diffing the result sets.
  • Feeding data lineage or metadata reports that document the engine's parameter catalog.

Related Objects

The provided FK metadata classifies this table as standalone, so no formal foreign-key relationships are documented. In practice, it is referenced logically by e-Commerce Gateway engine and transaction-definition components. Significant related objects include:

  • ECE_TRAN_HEADERS and ECE_TRAN_LINES — transaction data processed according to parameters defined here.
  • ECE_TRAN_TYPES (transaction type definitions) — the logical parent of TRANSACTION_TYPE.
  • ECE_TRAN_MAPS and mapping tables — used alongside parameters during conversion.
  • ECE_INBOUND_* and ECE_OUTBOUND_* runtime tables — engine output governed by these parameters.
  • Concurrent programs and the EC execution engine APIs that read ECE_TRAN_PARAMETERS at runtime.

Because relationships are implicit rather than enforced by foreign keys, joins are performed on TRANSACTION_TYPE rather than on PARAMETER_ID.