Search Results ec_a

Overview

ECE_ADVO_HEADERS_V is a private, active view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the e-Commerce Gateway (EC) product. Its documented purpose is to extract advice header information for the outbound Application Advice (824/APERAK) transaction. In the EDI messaging model, the 824 Application Advice conveys the acceptance, rejection, or acknowledgement status of a previously received business document, and it is functionally paired with the APERAK message used in the automotive and other standards-based interchange environments. The view supplies the header-level segment of that outbound message, giving the translation engine and downstream extraction programs a single, pre-joined source of advice-level attributes.

Because the object is a view rather than a table, it carries no storage of its own. It presents a read-only, denormalized projection over the advice header table and supporting trading partner configuration tables, which is the standard pattern across EC outbound extract views. Its display name in the repository is "Application Advice Header View," and it is classified under the BUSINESS_ENTITY category EC_A. Note that the view is scoped private, meaning it is intended for internal use by the e-Commerce Gateway extraction layer rather than as a general-purpose public interface.

Underlying Base Objects

The view is defined over four documented base objects, exposed in the APPS schema as synonyms:

• ECE_ADVO_HEADERS — the primary advice header table, aliased EAH in the view text, supplying advice identifiers, document classification, transaction controls, and reference columns.
• ECE_TP_HEADERS — trading partner group header table, aliased ETH, supplying partner description and descriptive flexfield attributes.
• ECE_TP_DETAILS — trading partner detail table, aliased ETD, supplying the test flag and translator code used to drive outbound processing.
• ECE_TP_GROUP — trading partner grouping table participating in the join that resolves the correct partner configuration for the advice.

The join between the advice header and the trading partner configuration tables is what allows a single row to carry both the advice content and the partner-specific routing and translation context required to emit a valid outbound 824/APERAK message.

Key Columns

• ADVICE_HEADER_ID — primary identifier of the advice header; the driving key for the extract.
• COMMUNICATION_METHOD — the EDI communication method associated with the advice header. This is the column most relevant to searches on "communication_method," which identifies how the outbound advice is transmitted (for example, the configured transport) for that trading partner relationship.
• DOCUMENT_TYPE / DOCUMENT_CODE — classification of the advice and its associated business document.
• TP_ENTITY_TYPE, TP_HEADER_ID, TP_LOCATION_CODE_EXT — trading partner entity type, internal partner header identifier, and external location code, used to resolve the recipient.
• TP_TEST_FLAG, TP_TRANSLATOR_CODE, TP_DOCUMENT_ID — test-versus-production indicator, the translator/map to be used, and the literal document identifier ('ADVO') assigned to this transaction.
• TRANSACTION_DATE, TRANSACTION_CONTROL1–3 — date and control values carried into the outbound message envelope.
• TP_DESCRIPTION, TP_REFERENCE_EXT1–2 — partner description and external reference values.
• TPH_ATTRIBUTE_CATEGORY and TPH_ATTRIBUTE1–15 — descriptive flexfield context and segments from the trading partner header.
• EXTERNAL_REFERENCE1–6 and INTERNAL_REFERENCE1–2 — free-form reference columns for cross-referencing the advice to related documents.
• RELATED_DOCUMENT_ID — link to the originating business document that the advice acknowledges.

Common Use Cases and Queries

Typical usage is diagnostic and operational: confirming that an advice header is configured for a given communication method, auditing partner routing before an outbound run, or extracting header data for a custom 824 interface.

• Review advice headers by communication method:

  SELECT advice_header_id, communication_method, document_type, transaction_date
  FROM   apps.ece_advo_headers_v
  WHERE  communication_method = :p_method;

• Inspect partner and translator configuration for an advice:

  SELECT advice_header_id, tp_header_id, tp_location_code_ext,
         tp_test_flag, tp_translator_code
  FROM   apps.ece_advo_headers_v
  WHERE  advice_header_id = :p_id;

• List test versus production advice traffic:

  SELECT advice_header_id, tp_test_flag, communication_method, transaction_date
  FROM   apps.ece_advo_headers_v
  WHERE  tp_test_flag = 'Y';

Because the view is private and read-only, it should be queried rather than updated, and any custom extraction logic should treat its columns as stable projectors of the underlying ECE_ADVO_HEADERS data.