Search Results external_reference6




Overview
Explore in AI Chat

Overview

APPS.ECE_ADVO_DETAILS_V is an Oracle E-Business Suite view owned by the APPS schema that exposes the row-level detail records of the ECE Advance Ship Notice / advice (ADVO) process. The view presents the individual line-level or message-level entries associated with an advice header, capturing the date and time of the advice event, its processing status, external and internal reference values, message codes and descriptions, and progress indicators for data validation. In ETRM 12.2.2 the object is documented as a view over the ECE_ADVO_DETAILS synonym, making it the reporting-friendly interface through which advice detail data is queried by concurrent programs, integration interfaces, and ad hoc reports.

Within the ECE (e-Commerce Gateway) product family, advice transactions represent outbound or inbound business documents exchanged with trading partners. This view provides the granular detail beneath an advice header, and its columns such as ADVICE_HEADER_ID establish the foreign-key relationship back to the parent advice record. Because the view is a simple projection of the underlying detail table without joins, filters, or aggregations, it preserves row cardinality and is suitable for direct query, extraction, and diagnostic use.

Underlying Base Objects

The view is defined over a single documented base object: the ECE_ADVO_DETAILS synonym, which resolves to the physical advice detail table in the APPS schema. The ETRM metadata lists ECE_ADVO_DETAILS as the only referenced base object, and the view text confirms a straightforward SELECT of all columns from that table with no WHERE clause, no joins, and no transformation logic.

  • Owner: APPS.
  • Referenced base object: ECE_ADVO_DETAILS (SYNONYM).
  • View definition: A column-for-column projection of ECE_ADVO_DETAILS, retaining ADVICE_DETAIL_ID and ADVICE_HEADER_ID as the primary identifying and relational keys.
  • Relationship: Many detail rows can belong to a single advice header, linked via ADVICE_HEADER_ID.

Key Columns

The view exposes the following documented columns, each corresponding to a field in ECE_ADVO_DETAILS.

  • ADVICE_DETAIL_ID — Unique identifier for each advice detail row; the primary key of the underlying table.
  • ADVICE_HEADER_ID — Foreign key to the parent advice header, used to group or join detail records to their header. This is the column most commonly searched by users.
  • ADVO_DATE_TIME — Date and time the advice detail event or message was processed.
  • ADVO_STATUS_CODE — Status of the advice detail, indicating its processing or transmission state.
  • EXTERNAL_REFERENCE1 through EXTERNAL_REFERENCE6 — Six configurable external reference attributes for partner-defined or document-specific data.
  • INTERNAL_REFERENCE1 through INTERNAL_REFERENCE6 — Six configurable internal reference attributes used for application-side identifiers and cross-references.
  • ADVO_MESSAGE_CODE — Code identifying the advice message associated with the detail row.
  • ADVO_MESSAGE_DESC — Descriptive text for the message code.
  • ADVO_DATA_BAD — Indicator capturing data validation failures for the detail row.
  • ADVO_DATA_GOOD — Indicator capturing successfully validated data for the detail row.

Common Use Cases and Queries

The view is typically queried to inspect advice processing outcomes, diagnose validation errors, and retrieve advice details by header. A common scenario is retrieving all detail rows for a known advice header:

  • Retrieve details by header: SELECT ADVICE_DETAIL_ID, ADVICE_HEADER_ID, ADVO_DATE_TIME, ADVO_STATUS_CODE, ADVO_MESSAGE_CODE, ADVO_MESSAGE_DESC FROM APPS.ECE_ADVO_DETAILS_V WHERE ADVICE_HEADER_ID = :header_id;
  • Identify validation failures: SELECT ADVICE_DETAIL_ID, ADVICE_HEADER_ID, ADVO_MESSAGE_DESC FROM APPS.ECE_ADVO_DETAILS_V WHERE ADVO_DATA_BAD IS NOT NULL;
  • Filter by status and date: SELECT * FROM APPS.ECE_ADVO_DETAILS_V WHERE ADVO_STATUS_CODE = :status AND ADVO_DATE_TIME >= :start_date;
  • Join to header data: Join ADVICE_HEADER_ID to the corresponding advice header view or table to combine header-level and detail-level reporting.

Because the view performs no filtering, queries against it should always constrain results by ADVICE_HEADER_ID, status, or date range to avoid full-table scans on large advice detail volumes. This makes the view well suited to diagnostics, reconciliation reports, and integration troubleshooting where the ADVICE_HEADER_ID is known.