Search Results ece_output_u1

Overview

EC.ECE_OUTPUT is a transient interface table within the e-Commerce Gateway module of Oracle EBS 12.1.1 and 12.2.2. It serves as the staging repository for the contents of outbound data files generated by the e-Commerce Gateway extract program. Each row in ECE_OUTPUT corresponds to a single line of the eventual data file, allowing the extract process to assemble transaction-specific content before it is spooled to the physical output file. Once the file has been successfully created, the contents of ECE_OUTPUT are purged, confirming its role as a short-lived, process-scoped staging object rather than a persistent transaction store.

The table resides in the APPS_TS_INTERFACE tablespace with a PCT Free of 10, consistent with other high-churn interface tables in the E-Business Suite. Its FND Design Data identifier is EC.ECE_OUTPUT, and the object is documented as VALID in the ETRM repository. From a heuristic Data Vault modeling perspective, the mined relationship data classifies ECE_OUTPUT as standalone, meaning it does not participate in foreign key relationships with other tables. This suggests a satellite-style structure whose grain is defined entirely by its own composite key, and any Data Vault representation would most naturally be modeled as a satellite attached to the e-Commerce Gateway run or transaction request hub, keyed by RUN_ID with LINE_ID as the sequence attribute.

Key Information Stored

ECE_OUTPUT contains twelve documented columns. The most operationally significant are the two that form the composite primary key and the payload column that carries the file content:

• RUN_ID — the transaction request ID, identifying the specific extract run that produced the row.
• LINE_ID — the sequential line number of the data file, defining ordering within a run.
• TEXT — VARCHAR2(4000), the actual output text written to that line of the data file.

The surrogate primary key is ECE_OUTPUT_PK (RUN_ID, LINE_ID). The unique index ECE_OUTPUT_U1 also covers (RUN_ID, LINE_ID), making this pair the business-key candidate that enforces one-and-only-one text line per run per sequence position. The remaining columns are Standard WHO audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. The concurrent program context columns (REQUEST_ID and PROGRAM_*) allow administrators to trace which concurrent request populated a given set of output rows.

Common Use Cases and Queries

Typical usage centers on troubleshooting output files, auditing extract runs, and reconstructing spilled content. A reviewer investigating a malformed outbound file can query rows for a specific run ordered by LINE_ID to reproduce the file contents exactly as spooled:

• SELECT LINE_ID, TEXT FROM EC.ECE_OUTPUT WHERE RUN_ID = :run_id ORDER BY LINE_ID;
• SELECT RUN_ID, COUNT(*) FROM EC.ECE_OUTPUT GROUP BY RUN_ID; to verify row counts per extract run.
• Joining REQUEST_ID to FND_CONCURRENT_REQUESTS to relate output content back to the submitting concurrent request and its completion status.

Because the table is purged after file creation, queries are only meaningful while the extract is in flight or when a run has failed and left residual rows. Reporting on historical extract volumes therefore requires capturing snapshots before the purge cycle completes.

Related Objects

The ETRM metadata indicates ECE_OUTPUT does not reference any database object and is referenced by APPS.ECE_OUTPUT through a synonym. Practical dependencies relevant to its lifecycle include:

• EC.ECE_OUTPUT (synonym: APPS.ECE_OUTPUT) — the APPS-layer alias used by concurrent programs and reports.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the parent extract request.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_ID and PROGRAM_APPLICATION_ID to identify the extract program.
• Transaction-specific e-Commerce Gateway interface tables — the upstream sources whose data is moved into ECE_OUTPUT before spooling.
• FND_USER — joined on CREATED_BY or LAST_UPDATED_BY to attribute row creation.