Search Results marketing_code




Overview

BIL_FCTV_PIPELINE is a read-only reporting view in the Oracle E-Business Suite Sales Intelligence (BIL) module. As its documented description states, it presents "quantitative measures related to sales opportunities." In practice, the view flattens opportunity and sales-credit data into a single denormalized structure, exposing lead identity, customer, sales channel, item, currency, stage, win probability, revenue, credit, and quantity measures. This makes it a convenient source for pipeline reporting, forecasting analysis, and downstream integration where consumers expect opportunity facts in a single cursor rather than a multi-table join.

The view carries a WITH READ ONLY constraint in its definition, confirming it is intended strictly for query and reporting workloads. It is documented in the ETRM metadata at the 12.1.1 and 12.2.2 release levels. Notably, the metadata records "Not implemented in this database," indicating that the object may not be deployed in every environment and is typically present only where the Sales Intelligence / Sales Foundation schema has been installed.

Underlying Base Objects

The documented view text defines BIL_FCTV_PIPELINE over two base objects joined in the WHERE clause:

The join filters on ASCD.OPP_DELETED_FLAG = 'N', excluding logically deleted opportunities. Although ETRM records no documented base objects under the "Referenced base objects" heading, the view text itself explicitly references these two tables, which are the authoritative dependencies. The denormalized credit table already aggregates much of the underlying opportunity model, so the view is effectively a thin projection layer adding credit-type attributes.

Key Columns

The view exposes thirty-six columns. The most significant include:

Common Use Cases and Queries

Typical uses include pipeline value by stage, quota-credited revenue analysis, and product-level quantity reporting. Because LINE_QUANTITY maps from the opportunity line's quantity, aggregations frequently target that column.

Example: quantity and revenue by sales stage.

  • SELECT SALES_STAGE_FK, SUM(LINE_QUANTITY) total_qty, SUM(REVENUE_AMOUNT) total_rev FROM BIL_FCTV_PIPELINE GROUP BY SALES_STAGE_FK;

Example: weighted pipeline using win probability.

  • SELECT LEAD_NUMBER, CUSTOMER_NAME, WIN_PROBABILITY, LINE_QUANTITY, REVENUE_AMOUNT * WIN_PROBABILITY weighted_value FROM BIL_FCTV_PIPELINE ORDER BY weighted_value DESC;

Example: quota-bearing credits only.

  • SELECT SALES_REP_NAME, SUM(CREDIT_AMOUNT) FROM BIL_FCTV_PIPELINE WHERE QUOTA_FLAG = 'Y' GROUP BY SALES_REP_NAME;

Consumers should confirm the view exists in the target instance, since the metadata documents it as not implemented in the reference database.