Search Results ece_advo_headers_interface

Overview

The ECE_ADVO_HEADERS_INTERFACE table is an e-Commerce Gateway (EC) staging and interface object in Oracle E-Business Suite, owned by the EC schema. Its documented purpose is to contain the header-level data required to support the outbound Application Advice (824/APERAK) transaction. The Application Advice is an ANSI X12 (824) or EDIFACT (APERAK) message that communicates the acceptance, rejection, or status of a previously received business document, and this table supplies the header segment data that the e-Commerce Gateway outbound extraction program reads when assembling the outbound message.

Under the heuristic Data Vault classification mined from its foreign-key structure, the table is assessed as standalone, meaning it does not exhibit the characteristic hub-and-satellite or link topology of a fully modeled Data Vault. In modeling terms, this classification is best treated as a suggestion only: the table functions as a transient interface or staging entity whose rows are keyed by a run identifier and an advice header identifier, rather than as a durable, historically tracked business entity.

Key Information Stored

The table is defined with a composite primary key, ECE_ADVO_HEADERS_INTERFACE_PK, consisting of ADVICE_HEADER_ID and RUN_ID. A second unique index, ECE_ADVO_HEADERS_INTERFACE_U1, uses the same column pair and therefore constitutes the documented business-key candidate; the surrogate identity of a row is thus inseparable from the batch run that produced it.

• ADVICE_HEADER_ID and RUN_ID — the composite key identifying each header record and its processing run.
• TP_DOCUMENT_ID — foreign key to the trading partner transaction header recorded in ECE_AR_TRX_HEADERS.
• DOCUMENT_TYPE, DOCUMENT_CODE, and DOCUMENT_PURPOSE_CODE — classify the document being advised upon and the purpose of the advice.
• TRANSACTION_DATE and TRANSACTION_RECORD_ID — the business date and record identifier of the advised transaction.
• TP_ENTITY_TYPE, TP_TRANSLATOR_CODE, TP_LOCATION_CODE_EXT, and TP_DESCRIPTION — trading partner routing and description attributes.
• TP_CODE_INTERNAL, TP_CODE_EXTERNAL, and TP_NAME — internal/external partner codes and partner name.
• TP_ADDRESS1 through TP_COUNTY_INT (the TP address group) — the mapped partner address components rendered into the outbound message.
• EXTERNAL_REFERENCE1–6 and INTERNAL_REFERENCE1–6 — free-form reference fields used for cross-referencing the outbound advice.
• TPH_ATTRIBUTE_CATEGORY and TPH_ATTRIBUTE1–15 — the standardized descriptive flexfield columns carrying additional header attributes.
• DOCUMENT_STANDARD, MAP_ID, and COMMUNICATION_METHOD — control the standard, mapping, and transport used for the outbound transmission.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org data security.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID — standard WHO and concurrent-program audit columns.

Common Use Cases and Queries

The primary operational use case is debugging and monitoring outbound Application Advice transmissions. Because rows are populated by the e-Commerce Gateway concurrent program for a specific run, the most common query filters by RUN_ID. A diagnostic query joining to ECE_AR_TRX_HEADERS to correlate an advice header with the originating transaction follows:

• Extracting all header rows for a failed or specific run: SELECT * FROM ECE_ADVO_HEADERS_INTERFACE WHERE RUN_ID = :run_id;
• Correlating advices to source transactions: SELECT h.ADVICE_HEADER_ID, t.* FROM ECE_ADVO_HEADERS_INTERFACE h, ECE_AR_TRX_HEADERS t WHERE h.TP_DOCUMENT_ID = t.TP_DOCUMENT_ID AND h.RUN_ID = :run_id;
• Reporting on rejection volumes by document type and partner over a period, grouped by DOCUMENT_TYPE, DOCUMENT_CODE, and TP_CODE_EXTERNAL with TRANSACTION_DATE range predicates.
• Auditing transmission failures by joining on REQUEST_ID to concurrent request history to identify the program invocation that produced the rows.
• Reviewing mapped partner address output prior to transmission by selecting the TP_ADDRESS* and TP_COUNTRY_INT/TP_STATE_INT columns for a given header.

Because the table is an interface and not a system of record, reporting is generally performed against it only for troubleshooting and audit, and data is subject to purge after successful processing.

Related Objects

The documented foreign keys and key relationships identify the following significant associated objects:

• ECE_AR_TRX_HEADERS — referenced through TP_DOCUMENT_ID; holds the trading partner transaction header against which the advice is raised.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; enforces multi-organization security grouping.
• ECE_ADVO_LINES_INTERFACE — the companion line-level interface that stores detail segments for the same advice header.
• ECE_ADVO_HEADERS_INTERFACE_PK / ECE_ADVO_HEADERS_INTERFACE_U1 — the primary key constraint and unique business-key index, both on ADVICE_HEADER_ID and RUN_ID.
• The e-Commerce Gateway outbound extraction concurrent programs and the EC product's Application Advice mapping definitions, which consume these rows to generate the 824/APERAK message.