Search Results ece_ar_trx_headers_x_pk

Overview

ECE_AR_TRX_HEADERS_X is a table in the EC (e-Commerce Gateway) product schema of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. As its description states, it is the extension table for ECE_AR_TRX_HEADERS, the base interface table that stages inbound and outbound Accounts Receivable transaction header data during e-Commerce Gateway processing. Extension tables of this pattern hold customer-specific or implementation-specific attributes that are not part of the seeded column set of the parent interface table, allowing inbound transactional data (such as invoice, debit memo, credit memo, and commitment headers) to carry additional fields through the gateway into Receivables without modifying the delivered schema.

The ETRM relationship metadata classifies this object heuristically as standalone under a Data Vault modelling lens, meaning it carries no foreign key relationships to other tables. In Data Vault terms this suggests that the table is best modelled as a satellite or attribute-bearing structure rather than a hub or link; it does not itself define a business key relationship to the parent ECE_AR_TRX_HEADERS table through a declared foreign key constraint.

Key Information Stored

The documented physical schema contains ten columns. The primary key is enforced by ECE_AR_TRX_HEADERS_X_PK on TRANSACTION_RECORD_ID, and a unique index ECE_AR_TRX_HEADERS_X_U1 also exists on TRANSACTION_RECORD_ID, making that column both the surrogate primary key and the business-key candidate for this table. The most significant columns are:

• TRANSACTION_RECORD_ID — the surrogate primary key and unique business-key candidate; used to correlate the extension row back to its corresponding header record in the base interface structure.
• CREATION_DATE and CREATED_BY — standard WHO-column audit attributes recording when and by whom the extension row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — audit attributes capturing the most recent modification to the record, including the login session that performed it.
• REQUEST_ID — the concurrent request identifier that created or updated the row, essential for tracing the gateway import process.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — identify the concurrent program and application that populated the record.
• PROGRAM_UPDATE_DATE — the date on which the originating concurrent program last updated the row, supporting incremental processing and reconciliation.

Common Use Cases and Queries

Because only standard Who columns and process-audit columns are documented for this table, it is most commonly queried for diagnostic and audit purposes rather than as a reporting source in its own right. Typical scenarios include tracing a failed or stuck e-Commerce Gateway import back to the concurrent request that created the extension row, and auditing who modified extension data in a multi-user environment.

A representative query joins the extension table to the base interface table on the transaction record identifier, filtering by the concurrent request that populated it:

• SELECT x.transaction_record_id, x.request_id, x.program_id, x.creation_date, x.last_update_date FROM ec.ece_ar_trx_headers_x x WHERE x.request_id = :request_id;
• SELECT COUNT(*) FROM ec.ece_ar_trx_headers_x WHERE creation_date BETWEEN :from_date AND :to_date;
• A join pattern to the base header table keys on x.transaction_record_id = h.transaction_record_id to surface the extension attributes alongside delivered header columns.

Related Objects

The metadata documents no foreign keys, so relationships below are based on functional dependency and shared key columns.

• ECE_AR_TRX_HEADERS — the parent interface table this object extends; joined on TRANSACTION_RECORD_ID.
• FND_CONCURRENT_REQUESTS — referenced through REQUEST_ID to identify the gateway import run.
• FND_CONCURRENT_PROGRAMS — referenced through PROGRAM_ID and PROGRAM_APPLICATION_ID.
• FND_USER — referenced through CREATED_BY and LAST_UPDATED_BY for user attribution.
• AR_INTERFACE_LINES_ALL and AR_INTERFACE_LINES_GT — downstream Receivables interface structures ultimately populated from gateway header data.
• RA_CUSTOMER_TRX_ALL — the destination Receivables transaction table for successfully imported records.

In summary, ECE_AR_TRX_HEADERS_X provides the auditable extension surface for AR e-Commerce Gateway header transactions, with its value concentrated in process traceability rather than business attribute storage.