Results for “as_lead_import_errors”

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

Overview

The AS_LEAD_IMPORT_ERRORS table is a Sales Foundation (AS) module object owned by the OSM schema. It stores the error messages generated during the import of sales leads into Oracle E-Business Suite. When lead records are loaded through the lead import interface, individual rows that fail validation or processing are flagged, and a corresponding error record is written here to preserve the failure reason. This makes the table a diagnostic and reconciliation repository that complements the lead import staging and interface tables, allowing administrators and sales operations users to identify, correct, and reprocess rejected records without inspecting raw interface data.

Under the supplied Data Vault heuristic classification, the table is described as satellite-leaning. Within a dimensional modeling context, this suggests treating AS_LEAD_IMPORT_ERRORS as a descriptive satellite attached to a parent hub or link (the import interface/batch), where its error text and audit attributes are the changing descriptive payload rather than independently defined business entities.

Key Information Stored

The surrogate primary key is LEAD_IMPORT_ERROR_ID, defined by the constraint AS_LEAD_IMPORT_ERRORS_PK and also carried on the unique index AS_LEAD_IMPORT_ERRORS_U1, making it the strongest business-key candidate documented. The most significant data-bearing columns include:

• IMPORT_INTERFACE_ID — foreign key to AS_IMPORT_INTERFACE, tying each error to the specific import interface run.
• BATCH_ID — identifies the batch under which the failed lead record was submitted.
• ERROR_TEXT — the human-readable message describing why the lead import row was rejected.
• REQUEST_ID — associates the error with the concurrent program request that executed the import.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the executing program and its last update timestamp.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/data security boundaries.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle who-columns recording audit history.

Together these fields describe not only the error itself but its execution context, batch origin, and responsible program.

Common Use Cases and Queries

Typical usage centers on diagnosing failed lead imports and reporting on import quality. A common pattern joins the error table to the import interface to retrieve full context:

• Retrieve all errors for a specific batch: SELECT LEAD_IMPORT_ERROR_ID, BATCH_ID, ERROR_TEXT FROM AS_LEAD_IMPORT_ERRORS WHERE BATCH_ID = :batch_id;
• Trace errors back to a concurrent request: filter by REQUEST_ID to isolate failures from a single import run.
• Join to AS_IMPORT_INTERFACE on IMPORT_INTERFACE_ID to correlate the error message with the originating staged record.
• Aggregate error counts by program or batch for data-quality dashboards.

Reporting is frequently performed through the concurrent manager output or custom BI Publisher reports that select from this table after a lead import program completes.

Related Objects

The FK and PK metadata identify the following significant related objects:

• AS_IMPORT_INTERFACE — referenced via IMPORT_INTERFACE_ID; the parent staging interface for lead imports.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security enforcement.
• AS_LEAD_IMPORT_ERRORS_PK / AS_LEAD_IMPORT_ERRORS_U1 — the primary key constraint and unique index on LEAD_IMPORT_ERROR_ID.
• The lead import concurrent programs identified by PROGRAM_ID and PROGRAM_APPLICATION_ID, which populate this table during execution.

These relationships make the table a dependent satellite of the import interface process, useful primarily in conjunction with the interface staging tables it supports.