Search Results lead_source_code

Overview

BIC_OPTY_SUMMARY_V is a reporting view belonging to the BIC (Customer Intelligence) product family in Oracle E-Business Suite. The BIC module historically provided analytical and campaign-oriented reporting over Oracle Marketing and Oracle Trade Management data, allowing organizations to summarize leads, opportunities, and customer interactions in a consolidated form. In EBS 12.1.1 and 12.2.2, the BIC product line is documented as obsolete, and this view is specifically noted as not implemented in the database. As a result, BIC_OPTY_SUMMARY_V should be treated as a legacy metadata artifact rather than a queryable object in a current environment.

The view is designed to present a denormalized summary of lead records, projecting a single row per lead with its associated customer, status, source, probability, and monetary attributes. Its inclusion of the INITIATING_CONTACT_ID column indicates that the view supports attribution-style reporting, allowing analysts to trace a lead or opportunity back to the contact who initiated it. Because the underlying table is AS_LEADS_ALL, the view effectively exposes lead data drawn from Oracle Marketing's lead management schema.

Underlying Base Objects

The documented definition of the view is a straightforward projection over a single base table:

• AS_LEADS_ALL — the primary and only referenced base object, aliased as ASL in the view text. This is the multi-organization lead table used by Oracle Marketing to store lead records.

No joins, unions, or additional base objects are documented. The ETRM metadata explicitly states that no base objects are documented and that the view itself is not implemented, meaning the ETRM record preserves the intended SELECT text but not a live database object. In practice, any environment still carrying BIC objects would derive rows directly from AS_LEADS_ALL filtered only by whatever predicates the consuming report or query applies.

Key Columns

The view exposes twelve columns, all inherited from AS_LEADS_ALL:

• LEAD_ID — primary identifier of the lead record.
• CUSTOMER_ID — identifier of the customer or prospect associated with the lead.
• CREATION_DATE — timestamp when the lead was created.
• STATUS — current life-cycle status of the lead (for example, open, converted, or rejected).
• ORG_ID — operating unit identifier supporting multi-organization security.
• CHANNEL_CODE — the marketing or sales channel through which the lead originated.
• LEAD_SOURCE_CODE — coded source of the lead, such as campaign or referral.
• WIN_PROBABILITY — estimated likelihood of conversion.
• INITIATING_CONTACT_ID — identifier of the contact responsible for initiating the lead; this is the column referenced in the originating search and is central to contact-level attribution reporting.
• SOURCE_PROMOTION_ID — the promotion or campaign that generated the lead.
• TOTAL_AMOUNT — monetary value associated with the lead or opportunity.
• DESCRIPTION — free-text description of the lead.

Common Use Cases and Queries

Because the view flattens lead attributes into a single projection, it supports reporting on lead pipelines, channel effectiveness, and contact attribution. A representative query selecting by initiating contact is:

• SELECT lead_id, customer_id, status, channel_code, win_probability, total_amount FROM bic_opty_summary_v WHERE initiating_contact_id = :contact_id;
• SELECT org_id, lead_source_code, SUM(total_amount) FROM bic_opty_summary_v GROUP BY org_id, lead_source_code;
• SELECT creation_date, COUNT(*) FROM bic_opty_summary_v WHERE status = 'OPEN' GROUP BY creation_date;

Administrators should verify object existence before relying on these queries, since the ETRM documentation confirms BIC_OPTY_SUMMARY_V is not implemented in the documented database and the BIC product is obsolete.