Search Results ece_ar_trx_headers




Overview
Explore in AI Chat

Overview

ECE_AR_TRX_HEADERS is an e-Commerce Gateway (EC) staging table in Oracle E-Business Suite, owned by the EC schema. It stores customer invoice header data used to support the outbound Invoice transaction, delivered as either the ANSI X12 810 or the UN/EDIFACT INVOIC message. During outbound invoice processing, Oracle Receivables data is extracted, translated, and written into this table so the e-Commerce Gateway translator can format the invoice header segment for transmission to a trading partner.

The table is populated by the e-Commerce Gateway extraction program and is keyed by TC_DOCUMENT_ID, with TP_DOCUMENT_ID serving as a secondary identifier in the documented primary key. The transaction record is uniquely identified through the unique indexes ECE_AR_TRX_HEADERS_U1 (COMMUNICATION_METHOD, TRANSACTION_ID) and ECE_AR_TRX_HEADERS_U2 (TRANSACTION_RECORD_ID). The table is highly denormalized, containing 274 documented columns that carry header-level invoice information along with pre-formatted bill-to, ship-to, sold-to, and remit-to party data.

Based on the foreign key relationship structure documented in the ETRM metadata, this object is a standalone table. Under a Data Vault modeling heuristic, it would be classified as a standalone structure rather than a hub, link, or satellite, meaning it acts as an independent staging entity rather than a member of a normalized Data Vault model. This reflects its role as a physical staging area rather than a normalized master data table.

Key Information Stored

The table stores a broad set of header attributes. The following columns are the most significant for identification, processing, and reporting:

Common Use Cases and Queries

Typical usage centers on verifying, troubleshooting, and reconciling outbound 810/INVOIC transmissions. Because the table can hold many messages per run, queries usually filter by transaction identifiers, communication method, or creation date. A representative pattern joins the header to related EC tables to confirm that a generated invoice corresponds to the intended trading partner:

  • Transmission audit — list invoice headers by TRANSACTION_ID and COMMUNICATION_METHOD to confirm successful extraction and to inspect the TP_DOCUMENT_ID assigned to the message.
  • Amount reconciliation — compare TOTAL_AMOUNT_DUE and its component amounts against the source invoice in Oracle Receivables to detect extraction discrepancies.
  • Party data verification — review the BILL_TO_, SHIP_TO_, SOLD_TO_, and REMIT_TO_ code and name columns to confirm that party roles and address segments are populated correctly for the target trading partner.
  • Currency analysis — verify CURRENCY_CODE, BASE_CURRENCY_CODE, and CURRENCY_EXCHANGE_RATE on invoices transmitted to international partners.
  • Run diagnostics — query by REQUEST_ID and PROGRAM_UPDATE_DATE to isolate records produced by a specific concurrent request.

Because ECE_AR_TRX_HEADERS is a staging artifact rather than an interface or base table, direct DML is not recommended; queries are read-only. High-volume reporting on historical outbound invoices should generally target the permanent Receivables tables, using this table only for gateway reconciliation.

Related Objects

Two tables are documented as referencing ECE_AR_TRX_HEADERS through the TP_DOCUMENT_ID column:

  • ECE_ADVO_HEADERS_INTERFACE — references ECE_AR_TRX_HEADERS via TP_DOCUMENT_ID; used for advance ship notice related header interface data.
  • ECE_MVSTO_HEADERS — references ECE_AR_TRX_HEADERS via TP_DOCUMENT_ID; used for movement/stock transfer order header data.

In practice, the invoice header staging table is complemented by EC line-level and control tables that share the same extraction architecture, including the ECE_AR_TRX_LINES counterpart and the gateway code conversion and document definition tables that drive message assembly. Oracle Receivables (AR) is the upstream source application that populates the header through the e-Commerce Gateway extraction concurrent program, and the outbound translator reads the resulting records to produce the ANSI X12 810 or UN/EDIFACT INVOIC message delivered to the trading partner.