Search Results ece_stage




Overview
Explore in AI Chat

Overview

ECE_STAGE is the inbound staging table for Oracle E-Business Suite's e-Commerce Gateway (EC) module. It serves as the transient landing zone where inbound electronic documents — purchase orders, invoices, ship notices, and similar transactions received from external trading partners — are loaded, validated, and staged before the gateway's processing programs translate them into native EBS application tables. Because this table operates within the EC schema and carries the prefix ECE, it is tightly bound to the e-Commerce Gateway architecture rather than to any single transactional module. In Oracle EBS 12.1.1 and 12.2.2, ECE_STAGE is documented as VALID under owner EC and is classified heuristically as a standalone structure within the Data Vault model — that is, neither a hub, link, nor satellite. Treated as a modeling suggestion, this classification implies the table functions as an integration or transient object rather than a core reference entity, and it participates in few permanent relationships.

Key Information Stored

ECE_STAGE spans 519 documented columns, the great majority of which are a very wide, generic FIELD1 through FIELD500 block. This design allows the gateway to bind positional columns from flat-file or EDI inbound extracts into fixed column slots without requiring schema changes per transaction type. The most important columns are:

Common Use Cases and Queries

Support specialists typically query ECE_STAGE to diagnose failed or stalled inbound interfaces — rows whose STATUS never advances indicate mapping or validation failures. A common pattern retrieves header rows for a given trading partner:

  • SELECT STAGE_ID, DOCUMENT_NUMBER, TRANSACTION_TYPE, STATUS FROM ECE_STAGE WHERE TP_CODE = :tp AND RUN_ID = :run ORDER BY STAGE_ID;
  • Hierarchy reconstruction: SELECT c.STAGE_ID, c.LINE_NUMBER FROM ECE_STAGE c WHERE c.PARENT_STAGE_ID = :stage_id;
  • Status monitoring and purge reporting for housekeeping concurrent programs.

Because FIELD1 through FIELD500 are generic, reporting against them requires the active mapping definition (MAP_ID) to interpret which field maps to which business attribute.

Related Objects

Although ECE_STAGE is heuristic-standalone, several tables reference its STAGE_ID key, forming the practical dependency graph:

The primary inbound processing is driven by e-Commerce Gateway concurrent programs operating in schema EC, which read ECE_STAGE, apply the MAP_ID mapping, and write translated results to the target application interface tables.