Search Results ece_ar_trx_header_1_u1

Overview

EC.ECE_AR_TRX_HEADER_1 is an interface table within the Oracle E-Business Suite E-Commerce Gateway (ECE) module, owned by the EC schema. It stores customer invoice header data that supports the outbound Invoice transaction — the 810 (ANSI X12) or INVOIC (EDIFACT) message — generated by Oracle Receivables. The table is designated a continuation of ECE_AR_TRX_HEADERS, meaning a strict one-to-one relationship exists between the two objects; together they form the complete outbound invoice header record, with ECE_AR_TRX_HEADER_1 carrying the supplemental attributes that did not fit within the base header table.

Its source data derives primarily from RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES in Oracle Receivables. Where Oracle Automotive is implemented, the table additionally draws equipment information from WSH_DEPARTURES in Oracle Order Management Departure Planning and allowance/charge information from VEH_ALLOWANCE_CHARGES. Columns flagged "Int" or "Internal" hold Oracle Applications internal code values, while those flagged "Ext" or "External" hold equivalent values resolved through ECE_XREF_DATA when code conversion is enabled.

The ETRM metadata classifies this object heuristically as standalone under a Data Vault model. As a modeling suggestion, it behaves closest to a satellite-like staging structure: it is transient, purge-driven, and keyed to a transactional parent, rather than a durable business hub.

Key Information Stored

The primary key is documented as ECE_AR_TRX_HEADER_1_PK on TRANSACTION_ID, while the unique index ECE_AR_TRX_HEADER_1_U1 on TRANSACTION_RECORD_ID is the business-key candidate that links each row to its corresponding extension table, ECE_AR_TRX_HEADER_1_X. The most operationally significant columns include:

• TRANSACTION_RECORD_ID — Unique identifier joining this table to its ECE_AR_TRX_HEADER_1_X extension row.
• TRANSACTION_ID — The surrogate primary key column for the row.
• COMMUNICATION_METHOD — The transmission method associated with the outbound invoice header.
• TRANSACTION_TYPE — The transaction classification used during gateway processing.
• RUN_ID — Identifies the concurrent extraction run that produced the row.
• EQUIPMENT_PREFIX and EQUIPMENT_NUMBER — Automotive equipment identification populated from WSH_DEPARTURES.
• ROUTING_INSTRUCTIONS and PACKING_SLIP_NUMBER — Shipping and logistics attributes carried on the invoice header.
• INTERFACE_ATTRIBUTE1–15 and TRANSACTION_ATTRIBUTE1–15 — Standard Oracle descriptive flexfield segments for interface and transaction context.
• SHIP_FROM_CODE_INT and SHIP_FROM_CODE_EXT1–EXT5 — Internal and externally converted ship-from identifiers.
• 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.

Common Use Cases and Queries

The table is used to validate and troubleshoot outbound 810/INVOIC invoice generation. Each row is purged after the data is written to the data file, so queries are typically executed against in-flight extract runs.

• Joining header header halves: SELECT a.*, b.* FROM ec.ece_ar_trx_headers a, ec.ece_ar_trx_header_1 b WHERE a.transaction_record_id = b.transaction_record_id;
• Locating rows from a specific extraction: filter on RUN_ID to isolate a concurrent program output set.
• Isolating Automotive-sourced rows: filter on EQUIPMENT_NUMBER IS NOT NULL to identify invoices carrying departure-planning equipment data.
• Code conversion verification: compare SHIP_FROM_CODE_INT with SHIP_FROM_CODE_EXT1–EXT5 to confirm ECE_XREF_DATA cross-reference resolution.

Related Objects

The following objects are most significant to this table, based on the documented relationship metadata and ETRM source information:

• EC.ECE_AR_TRX_HEADER_1_X — Extension table linked on TRANSACTION_RECORD_ID; one-to-one relationship.
• EC.ECE_AR_TRX_HEADER_1_U1 — Unique index on TRANSACTION_RECORD_ID, enforcing the extension linkage.
• ECE_AR_TRX_HEADERS — Base header table with the documented one-to-one continuation relationship.
• RA_CUSTOMER_TRX — Primary source of invoice header data in Oracle Receivables.
• RA_CUSTOMER_TRX_LINES — Secondary source supplying invoice line-level data.
• WSH_DEPARTURES — Source of equipment information when Oracle Automotive is installed.
• VEH_ALLOWANCE_CHARGES — Source of invoice header allowances and charges.
• ECE_XREF_DATA — Cross-reference table resolving internal (Int) to external (Ext) values.