Results for “ams_list_import_errors”

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

Overview

AMS_LIST_IMPORT_ERRORS is a transactional table in the AMS (Marketing) product schema of Oracle E-Business Suite, valid in both Release 12.1.1 and 12.2.2. It stores the errors that occur during the marketing list import process, acting as the diagnostic log for bulk list and source-line loads performed through the AMS import concurrent programs. Each row captures a single failure condition associated with a specific import list header and, where applicable, a specific source line, together with the batch and concurrent request context that generated it.

Under the heuristic Data Vault classification mined from its foreign-key structure, this table behaves as a link object: it connects import headers, import source lines, and the Oracle Applications security model rather than functioning as a standalone hub or a descriptive satellite. This classification is a modeling suggestion only; the table is a conventional EBS error-staging table and is not physically implemented as a Data Vault structure.

Key Information Stored

The physical schema documents 367 columns, the majority of which are generic staging slots (COL1 through COL350). The functionally significant attributes are concentrated in the leading and trailing column groups.

• LIST_IMPORT_ERROR_ID — the surrogate primary key, enforced by unique index AMS_LIST_IMPORT_ERRORS_U1. This is the only documented business-key candidate.
• IMPORT_LIST_HEADER_ID — identifies the import list header that failed, joining to AMS_IMP_LIST_HEADERS_ALL.
• IMPORT_SOURCE_LINE_ID — identifies the individual source line that produced the error, joining to AMS_IMP_SOURCE_LINES.
• IMPORT_TYPE — the category of import being processed, allowing errors to be segmented by load type.
• ERROR_TYPE and ERROR_FLAG — the classification of the failure and a status indicator used to mark whether the error has been reviewed or resolved.
• COL1 – COL250 — generic staging columns populated by the import program with the raw values of the failing record.
• SECURITY_GROUP_ID — the multi-organization security context, joining to FND_SECURITY_GROUPS.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the originating import request.
• BATCH_ID — groups errors belonging to a single import batch.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-columns.

Common Use Cases and Queries

The primary use case is post-import troubleshooting. After an AMS list import concurrent request completes with errors, developers and functional users query this table to determine which lines failed and why. A typical diagnostic query retrieves all errors for a given batch or request:

• Filter by BATCH_ID or REQUEST_ID to isolate errors from a single import run.
• Join to AMS_IMP_LIST_HEADERS_ALL and AMS_IMP_SOURCE_LINES to resolve the failing record to its source list and line context.
• Aggregate by ERROR_TYPE or IMPORT_TYPE to produce summary error reports for business users.
• Use ERROR_FLAG to build worklists of unresolved errors for reprocessing.

A representative pattern selects the error identifier, type, and header context filtered on the request identifier, optionally restricted by SECURITY_GROUP_ID in multi-org environments. Reporting extracts are commonly delivered through a custom concurrent program or BI Publisher report rather than a seeded AMS report.

Related Objects

• AMS_IMP_LIST_HEADERS_ALL — referenced via AMS_LIST_IMPORT_ERRORS.IMPORT_LIST_HEADER_ID; the header-level import record whose processing failed.
• AMS_IMP_SOURCE_LINES — referenced via AMS_LIST_IMPORT_ERRORS.IMPORT_SOURCE_LINE_ID; the individual source line that raised the error.
• FND_SECURITY_GROUPS — referenced via AMS_LIST_IMPORT_ERRORS.SECURITY_GROUP_ID; provides the security group context.
• FND_CONCURRENT_REQUESTS — related through REQUEST_ID, used to attribute errors to a specific concurrent program run.
• FND_USER — related through CREATED_BY and LAST_UPDATED_BY for user attribution.
• AMS List Import concurrent programs — the AMS import programs that populate this table as part of the list and source-line load process.

Because the table is a pure error log, it is normally read by diagnostic queries and reporting tools; it is not a maintenance target for application users, and rows are typically purged or archived in line with the retention policy applied to the associated import batches.