Search Results ece_advo_headers_interface_x




Overview
Explore in AI Chat

Overview

ECE_ADVO_HEADERS_INTERFACE_X is a concurrent-program interface table owned by the EC (e-Commerce Gateway) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description identifies it as the extension table for ECE_ADVO_HEADERS_INTERFACE, the base staging table that receives outbound or inbound Advance Shipment Notice and related order/ASN header data during e-Commerce Gateway processing. Extension tables in the EBS interface model follow a consistent pattern: the base table carries the functional transactional payload, while the corresponding _X table stores customer-specific, flexfield, or ancillary attributes associated with the same transaction line or header. The two are linked by the primary key, TRANSACTION_RECORD_ID, which is generated and managed by the interface program rather than entered manually.

Only 11 columns are documented for this object in the ETRM repository, nearly all of which are standard EBS installation and audit columns. The table therefore functions primarily as a controlled extension point rather than an analytical subject area. Based on the mined foreign-key structure and the absence of downstream references, the metadata suggests classifying this object as a standalone data vault structure; it holds descriptive attributes keyed by a single identifier and is not itself a junction between two independent business entities.

Key Information Stored

The documented column set is compact and can be grouped as follows:

  • TRANSACTION_RECORD_ID — the surrogate primary key and sole component of ECE_ADVO_HEADERS_INT_X_PK. This value matches the corresponding row in ECE_ADVO_HEADERS_INTERFACE and is the only reliable join key to the base interface table.
  • SECURITY_GROUP_ID — the foreign key referencing FND_SECURITY_GROUPS. It controls multi-org and security-group visibility of the extension row in a manner consistent with other EC interface tables.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns populated by the EBS application framework at insert and update time. They are useful for identifying which interface run last touched a row and for purge and archival logic.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program traceability columns. REQUEST_ID ties the row to a specific concurrent request, while PROGRAM_APPLICATION_ID and PROGRAM_ID identify the program that inserted or updated it. These support reconciliation of interface population to the interface execution log.

No unique business-key index beyond the primary key is documented, which reinforces that TRANSACTION_RECORD_ID is the single durable identifier for this object.

Common Use Cases and Queries

Typical usage is diagnostic and reconciliation oriented. Because this table is populated during e-Commerce Gateway inbound processing of Advance Shipment Notice data, developers and support analysts frequently query it to confirm whether extension attributes were written for a given interface transaction, and to correlate them with the base header row.

  • Joining the extension table to the base interface table on TRANSACTION_RECORD_ID to compare functional and extended attribute sets for a set of staged transactions.
  • Filtering by REQUEST_ID or PROGRAM_UPDATE_DATE to isolate rows produced by a specific concurrent request when investigating a failed interface run.
  • Using CREATION_DATE and LAST_UPDATE_DATE for purge, archival, or retention reporting, since interface tables accumulate data until explicitly cleared.
  • Checking SECURITY_GROUP_ID to determine which security context the imported extension data was written under.

A representative pattern is a SELECT joining ECE_ADVO_HEADERS_INTERFACE and ECE_ADVO_HEADERS_INTERFACE_X on TRANSACTION_RECORD_ID, with the extension table restricted by REQUEST_ID to a single concurrent request.

Related Objects

The documented relationships make ECE_ADVO_HEADERS_INTERFACE_X tightly coupled to a small set of objects:

  • ECE_ADVO_HEADERS_INTERFACE — the base table for which this is the extension; join on TRANSACTION_RECORD_ID. This is the primary and most important relationship.
  • FND_SECURITY_GROUPS — referenced through the SECURITY_GROUP_ID foreign key; join on SECURITY_GROUP_ID to resolve the security group name.
  • FND_CONCURRENT_REQUESTS — the natural join target for REQUEST_ID, used to resolve request name, phase, and status for traceability.
  • FND_APPLICATION and FND_CONCURRENT_PROGRAMS — join targets for PROGRAM_APPLICATION_ID and PROGRAM_ID respectively, identifying the program that wrote each row.
  • FND_USER — referenced conceptually through CREATED_BY and LAST_UPDATED_BY to resolve the responsible user.

No dependent views, APIs, or child tables on this object are documented in the ETRM metadata; it is a leaf interface structure whose lifecycle is governed by the e-Commerce Gateway concurrent programs rather than by application-tier DML.