Search Results export_data

Overview

AMS_EXP_LIST_HEADERS_VL is a translated (VL) view in the Oracle Marketing (AMS) module of Oracle E-Business Suite. It presents the header-level definition of export lists — the reusable export configurations that drive the Marketing module's list export functionality. Each row represents one export list header, combining language-independent attributes from the base table with the translated display name from the translation table. The view exposes descriptive metadata such as the export type, owner, lifecycle status, version, and security group, alongside execution-related attributes including request identifiers, generated SQL, recurrence settings, and the EXPORT_DATA column referenced in the user's search.

Because it is a VL view, AMS_EXP_LIST_HEADERS_VL automatically filters translated rows by the session language via USERENV('LANG'), returning a single localized name per header. This makes it the appropriate source for reports, concurrent programs, and integration extracts that need user-facing export list names rather than internal identifiers.

Underlying Base Objects

The view is defined over two documented base objects:

• AMS_EXP_LIST_HEADERS_ALL — the language-independent table holding all operational columns, including EXPORT_DATA, FINAL_SQL_STRING, STATUS_CODE, and the recurrence fields.
• AMS_EXP_LIST_HEADERS_ALL_TL — the translation table supplying the NAME column for the current language.

The join is on EXPORT_LIST_HEADER_ID, restricted by ILT.LANGUAGE = USERENV('LANG'). The ETRM metadata notes "Not implemented in this database" for the documented instance, and no owner was recorded. In a functioning 12.1.1 or 12.2.2 environment, the view resides in the AMS (or APPS) schema and is granted to APPS for reporting and concurrent processing.

Key Columns

• EXPORT_LIST_HEADER_ID — primary key of the export list header, used for all joins to detail and history objects.
• NAME — localized export list name sourced from the _TL table; the primary user-facing identifier.
• EXPORT_TYPE — classification of the export (for example, standard versus template-driven), governing downstream behavior.
• EXPORT_DATA — the stored export payload/configuration data associated with the header; this column is the target of the user's "export_data" search and holds the serialized definition used when the export executes.
• EXP_TEMPLATE_ID — reference to the export template on which the list is based.
• REQUEST_ID — the concurrent request that generated or last processed the export.
• FINAL_SQL_STRING — the resolved SQL statement used to extract the exported population.
• OWNER_USER_ID and SECURITY_GROUP_ID — ownership and security context controlling visibility and access.
• STATUS_CODE / USER_STATUS_ID / STATUS_DATE — lifecycle status and its timestamp.
• VIEW_APPLICATION_ID and VERSION — application context and record versioning.
• PARENT_EXP_HEADER_ID — self-referencing link identifying parent/child export relationships.
• RECURRING_EXP_NAME, CANCEL_FLAG, CANCEL_DATE, REPEAT_TIME, REPEAT_INTERVAL, REPEAT_UNIT, REPEAT_END_TIME, REPEAT_START_TIME, REPEAT_MODE — recurrence scheduling attributes for repeated exports.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include reporting on export lists and their status, replicating or auditing export configurations, tracing a concurrent request to its export list, and extracting the EXPORT_DATA payload for migration or analysis.

• List active export headers by owner and status.
• Retrieve the EXPORT_DATA and FINAL_SQL_STRING for a specific header.
• Identify recurring export schedules and canceled exports.
• Reconcile headers to concurrent requests via REQUEST_ID.

Sample query:

SELECT h.EXPORT_LIST_HEADER_ID,
       h.NAME,
       h.EXPORT_TYPE,
       h.STATUS_CODE,
       h.OWNER_USER_ID,
       h.REQUEST_ID,
       h.REPEAT_MODE,
       h.EXPORT_DATA
FROM   AMS_EXP_LIST_HEADERS_VL h
WHERE  h.STATUS_CODE = 'ACTIVE'
ORDER  BY h.LAST_UPDATE_DATE DESC;

Because the view is language-sensitive, query results reflect the language of the connected session, and the NAME value may change accordingly.