Search Results ece_advo_headers_interface_u1

Overview

The EC.ECE_ADVO_HEADERS_INTERFACE table is an Oracle E-Business Suite interface staging table that holds outbound Application Advice (EDI transaction set 824 / APERAK) data prior to it being written to the outbound data file. It resides in the EC schema (the E-Commerce Gateway / EDI schema) and is governed by FND Design Data EC.ECE_ADVO_HEADERS_INTERFACE. Its structure is modeled on the permanent ECE_ADVO_HEADERS table, from which it is populated when an Application Advice outbound transaction is generated.

Because the table is an interface (staging) object, each row is transient: a row is purged after its data has been written to the outbound data file. The physical storage is the APPS_TS_INTERFACE tablespace, with PCT Free of 10 percent — a configuration typical of high-turnaround interface tables rather than long-term data stores.

Under a heuristic Data Vault classification, this table is a standalone object — it is not modeled as a hub, link, or satellite. In Data Vault terms it most closely resembles a transient staging structure that captures a business event (the generation of an Application Advice transaction) along with descriptive context. It is best treated as a link-like bridge between the source document and its external trading-partner representation, but the mined metadata does not identify a formal dependent-child or hub relationship.

Key Information Stored

The most operationally important columns fall into several groups:

• Surrogate/key columns: ADVICE_HEADER_ID is the system-generated primary key, invisible to the user. RUN_ID is the run batch identifier. The unique index ECE_ADVO_HEADERS_INTERFACE_U1 is defined on (ADVICE_HEADER_ID, RUN_ID), making this pair the business-key candidate. TRANSACTION_RECORD_ID is the unique key linking this table to its extension table ECE_ADVO_HEADERS_INTERFACE_X.
• Trading partner attributes: TP_DOCUMENT_ID, TP_ENTITY_TYPE, TP_TRANSLATOR_CODE, TP_LOCATION_CODE_EXT, TP_DESCRIPTION, TP_REFERENCE_EXT1 and TP_REFERENCE_EXT2. These identify the recipient and the partner-specific references carried on the outbound transaction.
• Document classification: DOCUMENT_TYPE, DOCUMENT_CODE, DOCUMENT_PURPOSE_CODE, and DOCUMENT_STANDARD.
• Cross-reference keys: EXTERNAL_REFERENCE1–EXTERNAL_REFERENCE6 and INTERNAL_REFERENCE1–INTERNAL_REFERENCE6, each holding up to six key values that uniquely identify the EDI document. Columns suffixed _INT/_INTERNAL hold Oracle internal values; _EXT/_EXTERNAL hold equivalent external values sourced from ECE_XREF_DATA when code conversion is enabled.
• Other context: COMMUNICATION_METHOD, TP_TEST_FLAG, TRANSACTION_DATE, and the standard WHO/audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, SECURITY_GROUP_ID).

Common Use Cases and Queries

Typical uses include diagnosing why an outbound 824/APERAK was not produced, confirming trading-partner routing details, and reconstructing the content of an advice run for audit purposes. Because rows are transient, queries are usually executed within the outbound run window or against archive copies.

Representative queries include joining interface rows to the extension table on TRANSACTION_RECORD_ID:

• SELECT h.ADVICE_HEADER_ID, h.RUN_ID, h.TP_DOCUMENT_ID, h.DOCUMENT_TYPE, h.TP_TRANSLATOR_CODE, x.* FROM EC.ECE_ADVO_HEADERS_INTERFACE h, EC.ECE_ADVO_HEADERS_INTERFACE_X x WHERE h.TRANSACTION_RECORD_ID = x.TRANSACTION_RECORD_ID;
• Filtering by run: WHERE RUN_ID = :run_id to inspect all advice headers produced in a single batch.
• Reconciling partner references: SELECT TP_DOCUMENT_ID, INTERNAL_REFERENCE1, EXTERNAL_REFERENCE1, DOCUMENT_STANDARD FROM EC.ECE_ADVO_HEADERS_INTERFACE WHERE ADVICE_HEADER_ID = :id;

Reporting scenarios commonly cross-check TP_DOCUMENT_ID against ECE_AR_TRX_HEADERS to confirm the source receivables transaction, and validate that DOCUMENT_TYPE/DOCUMENT_PURPOSE_CODE match the expected 824 content.

Related Objects

The most significant related objects are:

• EC.ECE_ADVO_HEADERS_INTERFACE_X — the extension table keyed by TRANSACTION_RECORD_ID, storing additional descriptive flexfield/extensible attributes.
• EC.ECE_ADVO_HEADERS — the permanent base table whose data source populates this interface table.
• EC.ECE_AR_TRX_HEADERS — referenced by TP_DOCUMENT_ID, providing the source receivables transaction context.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, enforcing operating-unit/security context.
• EC.ECE_XREF_DATA — the code-conversion source for the external values (_EXT columns).