Search Results ece_ar_trx_header_1




Overview
Explore in AI Chat

Overview

ECE_AR_TRX_HEADER_1 is an interface staging table owned by the EC (e-Commerce Gateway) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It contains customer invoice header data used to support the outbound Invoice transaction, published as ANSI X12 810 or UN/EDIFACT INVOIC. The table is documented as a continuation of ECE_AR_TRX_HEADERS, meaning the full invoice header record is distributed across a parent table and this extension table, joined by TRANSACTION_ID. It is not a transactional master table; it is a transient staging object populated during outbound invoice extraction and consumed by the e-Commerce Gateway translation and transmission programs.

The documented Data Vault classification, derived heuristically from the foreign-key structure, is standalone. As a modeling suggestion, this indicates the table does not participate in a classic hub-link-satellite pattern and carries no enforced parent-child foreign keys within the documented schema. Its role is better understood as the transactional detail or satellite segment of the ECE_AR_TRX_HEADERS hub, related by the shared key TRANSACTION_ID rather than by a declared constraint.

Key Information Stored

The table comprises 59 documented columns. The most significant are:

Common Use Cases and Queries

Typical use is diagnosing failed or pending outbound invoices, verifying header-to-document mapping, and reporting on transmitted interface data. A common pattern joins the continuation table to its parent on TRANSACTION_ID and filters by run:

  • Pending processing check: SELECT h.TRANSACTION_ID, a.TRANSACTION_RECORD_ID, a.TRANSACTION_TYPE, a.COMMUNICATION_METHOD FROM EC.ECE_AR_TRX_HEADERS h, EC.ECE_AR_TRX_HEADER_1 a WHERE h.TRANSACTION_ID = a.TRANSACTION_ID AND a.RUN_ID = :run_id.
  • Run audit: SELECT RUN_ID, REQUEST_ID, COUNT(*) FROM EC.ECE_AR_TRX_HEADER_1 GROUP BY RUN_ID, REQUEST_ID.
  • Flexfield inspection: select the INTERFACE_ATTRIBUTE and TRANSACTION_ATTRIBUTE columns to confirm the mapping layer wrote expected values.
  • Reconciliation: compare TRANSACTION_RECORD_ID counts against the AR invoice extract to detect header rows dropped during staging.

Related Objects

The most significant related objects, based on the documented key structure, are:

  • ECE_AR_TRX_HEADERS — the parent header table this object continues; join on TRANSACTION_ID.
  • ECE_AR_TRX_LINES — the outbound invoice line-level staging counterpart, linked through the same transaction context.
  • ECE_AR_TRX_HEADER_1_PK / ECE_AR_TRX_HEADER_1_U1 — the primary key and unique index that govern the table's identity and business key.
  • ECA_* e-Commerce Gateway programs and the outbound extraction concurrent programs — populate and read these rows during invoice transmission.
  • RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL — the Oracle Receivables source tables from which the invoice header data is derived.
  • FND_CONCURRENT_REQUESTS — joined via REQUEST_ID for program and status tracing.