Search Results salesforce_fk




Overview
Explore in AI Chat

Overview

BIL_FCTV_SALES_LEADS is a read-only fact-style view within the Oracle E-Business Suite Sales Intelligence (BIL) module. It consolidates quantitative and descriptive measures relating to sales leads into a single denormalized structure intended for operational reporting, business intelligence extraction, and downstream integration. The view draws together transactional lead header information, lead line detail, access-control metadata, and territory assignment data, presenting them as one row per sales lead line.

Because it exposes a flattened representation of lead data, BIL_FCTV_SALES_LEADS is well suited to star-schema style reporting where sales leads function as facts and the associated identifiers (customer, salesforce, territory, interest codes, inventory items) act as dimensional references. The object is defined with a WITH READ ONLY clause, so it cannot be used for DML operations and serves purely as a query and extraction interface. Note that the ETRM metadata documents the view as not implemented in the reference database, meaning it may exist in the data dictionary definition but is not necessarily deployed on every instance.

Underlying Base Objects

The view is defined over four base tables joined on their natural keys. These are the entities that supply the substantive data:

  • AS_SALES_LEADS (ASL) — the sales lead header table, supplying lead-level attributes such as customer, address, assigned salesperson, channel, creation date, and status.
  • AS_SALES_LEAD_LINES (ASLL) — the lead line detail table, supplying line-level attributes such as interest type, primary and secondary interest codes, and inventory item. This is the object users frequently search for under the term as_sales_lead_lines.
  • AS_ACCESSES_ALL (ACC) — the access table that maps leads to salesforces and sales groups, supplying the salesforce and sales group identifiers.
  • AS_TERRITORY_ACCESSES (ATA) — the territory access table, supplying territory identifiers associated with each access record.

The joins are inner joins on SALES_LEAD_ID between the lead header and both the lead lines and the access table, followed by ACCESS_ID between accesses and territory accesses. This means only leads that have at least one line, one access record, and one territory access record will appear in the result set.

Key Columns

The view exposes the following columns, which carry both keys and descriptive attributes:

Common Use Cases and Queries

Typical uses include lead pipeline analysis by territory or salesforce, interest-code trending, and channel effectiveness reporting. Because the view carries both header and line granularity, a simple projection returns one row per lead line. A representative query:

SELECT sales_lead_id, sales_lead_line_id, customer_fk, salesforce_fk, territory_fk, inventory_item_fk, creation_date, status_code FROM bil_fctv_sales_leads WHERE creation_date >= :start_date;

Aggregations commonly group by SALESFORCE_FK or TERRITORY_FK to count open leads, or by CHANNEL_FK to compare source performance. When relating the view back to its underlying lead lines, join on SALES_LEAD_ID and SALES_LEAD_LINE_ID to AS_SALES_LEAD_LINES for additional descriptive attributes not exposed here.