Search Results ibe_lead_import_log




Overview
Explore in AI Chat

Overview

The IBE_LEAD_IMPORT_LOG table is an operational audit and diagnostics table within the Oracle E-Business Suite iStore (IBE) module. It records the results of each attempt to import leads into the iStore application, capturing timing, mode of import, and the disposition of individual records processed during a run. In Oracle EBS 12.1.1 and 12.2.2, iStore supports the capture of marketing and sales leads through the storefront, and the batch import of leads from external sources. Each such import execution results in a log row in this table, making it the primary reference point for administrators investigating why leads did or did not load successfully.

The ETRM metadata classifies this object as standalone under the heuristic Data Vault classification, meaning it has no mandatory parent relationship other than a reference to the security group. In Data Vault modeling terms, IBE_LEAD_IMPORT_LOG behaves most naturally as a satellite attached to an import execution hub, since it carries descriptive, time-stamped attributes about a business event rather than representing a business entity in its own right. The single outbound foreign key to FND_SECURITY_GROUPS confirms the multi-org/security-group partitioning that is standard across iStore tables.

Key Information Stored

The table contains 17 documented columns. The most significant are:

Common Use Cases and Queries

The principal use case is troubleshooting failed or partial lead imports. An administrator can list the most recent import runs and their success/failure counts:

  • SELECT log_id, lead_type, status, import_mode, num_imported, num_success, num_failed, begin_date, end_date FROM ibe.ibe_lead_import_log ORDER BY creation_date DESC;
  • Filtering by security group: ... WHERE security_group_id = :p_security_group_id ORDER BY begin_date DESC;
  • Performance review: SELECT log_id, elapsed_time, num_imported FROM ibe.ibe_lead_import_log WHERE begin_date BETWEEN :from_date AND :to_date;

Reporting use cases include monitoring daily lead-import throughput, identifying recurring failure patterns by LEAD_TYPE or IMPORT_MODE, and providing audit evidence of when a given batch was executed. Because the table is append-style, it also supports trend analysis of import efficiency over time.

Related Objects

The most significant related objects are:

  • FND_SECURITY_GROUPS — joined on IBE_LEAD_IMPORT_LOG.SECURITY_GROUP_ID to resolve the security group owning each log entry.
  • The iStore lead tables themselves (for example the lead header and lead line tables in the IBE schema), which hold the actual imported lead records that the counts in NUM_IMPORTED, NUM_SUCCESS, and NUM_FAILED summarize.
  • IBE_LEAD_IMPORT_LOG_PK and IBE_LEAD_IMPORT_LOG_U1 — the primary key constraint and unique index on LOG_ID, which enforce the uniqueness of each run identifier.
  • Concurrent program and request tables such as FND_CONCURRENT_REQUESTS, commonly correlated with import runs when lead import is scheduled through the concurrent manager.
  • Standard EBS WHO/audit columns and the FND_USER table, joined through CREATED_BY to attribute each import to a user.