Results for “processed_rows”

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

Overview

AMS_IMP_LIST_HEADERS_ALL_V is a marketing (AMS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes import list header information used by Oracle Marketing and its import engine for list management, list upload, and third-party list ingestion. The view acts as a denormalized reporting and integration layer over the base import list header entity, joining header rows to a resource (employee) view so that a human-readable owner name is returned alongside the numeric owner identifier.

Because the view filters and enriches the underlying table in a controlled manner, it is a convenient target for custom reports, concurrent program extracts, interface staging validation, and integration queries. Any column referencing ROWS_TO_SKIP resides here; the view is where application teams inspect how many leading lines of an uploaded flat file were skipped before row processing, together with counts of loaded and processed rows.

Underlying Base Objects

The view is defined over two documented referenced objects:

• AMS_IMP_LIST_HEADERS_ALL (synonym) — the base import list header entity holding all persisted import list header attributes. The view selects its columns without restriction, using the alias I.
• AMS_JTF_RS_EMP_V (view) — a resource/employee view supplying the owner's full name. The view is joined to the header on I.OWNER_USER_ID = U.RESOURCE_ID and contributes the derived column OWNER (U.FULL_NAME).

All columns from the base header entity are projected. The join is an equi-join on the owner resource identifier, so header rows whose owner does not resolve in the resource view are not returned. The view is read-only in practice; DML should be directed at the base table.

Key Columns

• IMPORT_LIST_HEADER_ID — primary identifier of the import list header.
• NAME, VERSION, DESCRIPTION, KEYWORDS — identity and descriptive attributes of the list.
• IMPORT_TYPE, LIST_SOURCE_TYPE_ID, SOURCE_SYSTEM, VENDOR_ID, PIN_ID — classify the origin and format of the imported list.
• OWNER_USER_ID, OWNER — the owning resource identifier and the resolved full name from AMS_JTF_RS_EMP_V.
• STATUS_CODE, USER_STATUS_ID, STATUS_DATE — lifecycle state of the import list header.
• ROWS_TO_SKIP — number of leading rows in the source data file to ignore before data collection begins; directly relevant to the user's search term.
• LOADED_NO_OF_ROWS, PROCESSED_ROWS, LOADED_DATE — row-count and timing metrics for upload and processing.
• HEADINGS_FLAG, DEDUPE_FLAG, PROCESS_IMMED_FLAG — processing options controlling header handling, duplicate elimination, and immediate processing.
• DATA_FILENAME, TERMINATED_BY, ENCLOSED_BY — flat-file import characteristics and delimiters.
• ORG_ID — multi-org operating unit identifier.
• EXPIRY_DATE, PURGE_DATE, SCHEDULED_TIME — scheduling and retention attributes.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — DFF (descriptive flexfield) columns.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, VIEW_APPLICATION_ID.

Common Use Cases and Queries

Typical scenarios include auditing skipped rows on failed imports, reporting list volume and status by owner, and validating file-parsing settings in integrations.

• Inspect skip configuration and processing counts for a given list.
• Report all import lists owned by a resource, using the resolved OWNER name.
• Identify uploads whose loaded or processed counts diverge.

Sample queries:

• SELECT name, rows_to_skip, loaded_no_of_rows, processed_rows, status_code FROM ams_imp_list_headers_all_v WHERE import_list_header_id = :p_id;
• SELECT import_list_header_id, name, owner, source_system, loaded_date FROM ams_imp_list_headers_all_v WHERE owner = :p_owner AND status_code = 'ACTIVE' ORDER BY loaded_date DESC;
• SELECT name, data_filename, terminated_by, enclosed_by, headings_flag FROM ams_imp_list_headers_all_v WHERE rows_to_skip > 0;

Because the view joins to AMS_JTF_RS_EMP_V, queries that filter or sort by OWNER benefit from the resolved full name but will exclude headers whose OWNER_USER_ID has no matching resource. For bulk or DML operations, use the base table AMS_IMP_LIST_HEADERS_ALL.