Results for “ams_imp_list_headers_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMS_IMP_LIST_HEADERS_VL is an APPS-owned, VALID database view within the AMS (Marketing) product family of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It exposes the translatable attributes of list import header records — principally the user-facing NAME and DESCRIPTION fields — alongside the full set of operational and control columns that govern a list import job. The view follows the standard EBS "_VL" pattern: an "_ALL" entity table joined to its "_TL" translation table, filtered implicitly through the join so that each consumer of the view reads the language-appropriate translatable row. In reporting and integration terms, the view is the natural access point for list import jobs because it decouples consumers from the underlying translation storage while still surfacing every metadata column needed to reconstruct a job's lifecycle.

Underlying Base Objects

The documented base objects are AMS_IMP_LIST_HEADERS_ALL (SYNONYM) and AMS_IMP_LIST_HEADERS_ALL_TL (SYNONYM). The "_ALL" synonym resolves to the multi-org, non-translatable header table carrying the import job's technical and status information, while the "_TL" synonym supplies the language-dependent NAME and DESCRIPTION. The view text joins them on the import list header identifier and translation linkage, selecting ILH-prefixed columns from the header and ILT-prefixed NAME/DESCRIPTION from the translation source. Because _ALL tables are org-striped where applicable, ORG_ID is carried through the view; consumers filtering by operating unit should constrain it explicitly.

Key Columns

• IMPORT_LIST_HEADER_ID — primary identifier for the import job; the join key for all related import detail and list membership data.
• NAME / DESCRIPTION — translatable attributes sourced from the _TL object; the columns that make this a "_VL" view.
• STATUS_CODE, STATUS_DATE, USER_STATUS_ID, CANCEL_FLAG, CANCEL_DATE — lifecycle and cancellation state of the import job.
• DATA_FILENAME, LOG_FILE_NAME — the source data file and the job's log file; LOG_FILE_NAME is the column most frequently referenced when diagnosing a completed or failed import, since it identifies the server-side log produced by the import concurrent program.
• SERVER_FLAG, SERVER_NAME, USER_NAME, EXECUTE_MODE, PROCESS_IMMED_FLAG, SCHEDULED_TIME — execution topology: whether the load ran against a server-side file, the server and credentials, immediate versus concurrent processing, and scheduling.
• RECORD COUNTS — LOADED_NO_OF_ROWS, PROCESSED_ROWS, ROWS_TO_SKIP, NUMBER_OF_RECORDS, NUMBER_OF_FAILED_RECORDS, NUMBER_OF_DUPLICATE_RECORDS; the reconciliation metrics for any import reconciliation report.
• DEDUPE_FLAG, HEADINGS_FLAG, ENABLE_WORD_REPLACEMENT_FLAG, VALIDATE_FILE, ERROR_THRESHOLD, CHARSET, TERMINATED_BY, ENCLOSED_BY — parsing, validation, and duplicate-handling behaviour of the load.
• IMPORT_TYPE, LIST_SOURCE_TYPE_ID, SOURCE_SYSTEM, VENDOR_ID, PIN_ID, RENTED_LIST_FLAG, B2B_FLAG — origin and commercial characteristics of the imported list.
• RECURRING_IMP_NAME, REPEAT_TIME, REPEAT_INTERVAL, REPEAT_UNIT, REPEAT_MODE, REPEAT_START_TIME, REPEAT_END_TIME — recurrence definition for scheduled or repeating imports.
• EXPIRY_DATE, PURGE_DATE, ORG_ID, USAGE, SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER — retention, multi-org, and concurrency-control attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.

Common Use Cases and Queries

The most common scenario is locating the log file for a completed import, which is precisely the "log_file_name" search that surfaces this view. The view is also used to build import history reports, reconcile loaded versus failed record counts, audit deduplication and word-replacement behaviour, and report on recurring import schedules. A representative query listing recent imports with their log files is:

SELECT h.import_list_header_id, h.name, h.status_code, h.status_date, h.data_filename, h.log_file_name, h.number_of_records, h.number_of_failed_records FROM apps.ams_imp_list_headers_vl h WHERE h.org_id = :org_id AND h.creation_date >= :from_date ORDER BY h.creation_date DESC;

To reconcile a contested run, filter on STATUS_CODE and compare the count columns: SELECT name, loaded_no_of_rows, processed_rows, number_of_failed_records, number_of_duplicate_records FROM apps.ams_imp_list_headers_vl WHERE import_list_header_id = :header_id. For schedule administration, select RECURRING_IMP_NAME with the REPEAT_* columns where RECURRING_IMP_NAME IS NOT NULL. Because NAME and DESCRIPTION are translatable, callers must not join the view to _TL tables directly; the view already performs that resolution. All queries should be schema-qualified as APPS and constrained by ORG_ID where operating unit isolation is required.