Search Results ibe_lead_import_log_u1

Overview

IBE.IBE_LEAD_IMPORT_LOG is a transactional logging table in the Oracle E-Business Suite iStore/IBE (Internet Business Essentials) schema. It records the outcome of each batch execution of the lead import process, which loads externally sourced order and quote leads into the IBE lead tables. Each row represents a single import run, capturing temporal, operational, and statistical attributes that describe how many leads were processed, how many succeeded, and how many failed.

The table resides in the APPS_TS_TX_DATA tablespace and is classified as VALID in the ETRM 12.2.2 data model. Because it holds no foreign keys to dependent transactional tables other than SECURITY_GROUP_ID, it is modeled as a standalone entity. Under a heuristic Data Vault classification, this table is best treated as a satellite, since it stores descriptive, time-stamped measures about an import event rather than serving as a pure hub or link. Its primary key, IBE_LEAD_IMPORT_LOG_PK, is defined on LOG_ID.

Key Information Stored

The most operationally significant columns are those describing the import run and its results:

• LOG_ID — surrogate primary key and the LOG_ID business-key candidate exposed through the unique index IBE_LEAD_IMPORT_LOG_U1.
• OBJECT_VERSION_NUMBER — optimistic locking version for concurrent updates.
• BEGIN_DATE / END_DATE — start and end timestamps of the import, used to derive run windows.
• LEAD_TYPE — identifies the source as ORDER or QUOTE.
• STATUS — numeric import status: 0 (Not Active), 1 (Active – Success), 2 (Active – Success with Error), -1 (Active – Error).
• IMPORT_MODE — COMPLETE or INCREMENTAL, indicating whether the run reloaded all leads or only new/changed ones.
• ELAPSED_TIME — total duration of the import, useful for performance trending.
• NUM_IMPORTED, NUM_SUCCESS, NUM_FAILED — the counts of leads attempted, successfully created, and rejected.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, supporting multi-tenant or operating-unit scoping.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — audit lineage for the log record itself.

Common Use Cases and Queries

Administrators and support analysts query this table to verify the health of the lead import concurrent program. A frequent pattern retrieves the most recent run per lead type:

SELECT LOG_ID, LEAD_TYPE, STATUS, IMPORT_MODE, BEGIN_DATE, END_DATE, NUM_IMPORTED, NUM_SUCCESS, NUM_FAILED FROM IBE.IBE_LEAD_IMPORT_LOG ORDER BY BEGIN_DATE DESC;

Performance monitoring uses ELAPSED_TIME and NUM_IMPORTED together to compute throughput. Error investigation filters on STATUS = -1 or STATUS = 2 to isolate failed or partially failed runs, while trend reporting groups counts by day using BEGIN_DATE. Because SECURITY_GROUP_ID is the only documented foreign key, security-scoped queries join to FND_SECURITY_GROUPS when data segregation is required.

Related Objects

The documented dependencies for this table are limited. SECURITY_GROUP_ID references FND_SECURITY_GROUPS, making that the primary join partner for access-control reporting. The primary key IBE_LEAD_IMPORT_LOG_PK and the unique index IBE_LEAD_IMPORT_LOG_U1 both cover LOG_ID and should be considered when tuning queries that filter or sort by that column. In practice, the lead import result of each run is consumed by the IBE lead tables (such as IBE_LEADS and their staging equivalents) and surfaced through the iStore lead administration and lead import concurrent programs. Reporting integrations typically combine this log with IBE_LEAD_IMPORT_LOG-level statistics and the corresponding concurrent program request history in FND_CONCURRENT_REQUESTS to reconcile program output against import counts.