Search Results cust_satisfaction_pct

Overview

BIL_SUMV_OPTY_PERF is a reporting view historically delivered within the Oracle E-Business Suite Sales Intelligence (BIL) product family. In the ETRM metadata for both 12.1.1 and 12.2.2, the owning product is explicitly flagged as "BIL - Sales Intelligence (Obsolete)," and the implementation note states "Not implemented in this database." This means the view is retained as legacy metadata rather than as an active database object in current releases. Its purpose was to expose quantitative measures related to opportunity performance, allowing Sales Intelligence reporting and analytics to summarize opportunity activity by period, territory, sales channel, sales representative, and customer, alongside customer satisfaction and win-probability measures.

The object is defined as a read-only view (WITH READ ONLY) that joins the summary table BIL_OPTY_PERF_SUMM to two customer and opportunity dimension views, BIL_DIMV_CUSTOMERS and BIL_DIMV_OPTY. It therefore functioned as a denormalized reporting surface for opportunity performance metrics rather than as a transactional entity.

Underlying Base Objects

The view text joins three documented sources:

• BIL_OPTY_PERF_SUMM BOP — the primary summary table supplying period, territory, interest, channel, salesrep, customer, financial, win-probability, and satisfaction measures. All standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) originate here.
• BIL_DIMV_CUSTOMERS BDC — a customer dimension view joined on CUSTOMER_ID, contributing CUSTOMER_NAME.
• BIL_DIMV_OPTY BDO — an opportunity dimension view joined on LEAD_ID, contributing the opportunity descriptor (referenced as DESCRIPTION in the view text, surfaced as OPTY_NAME in the reported column list).

The ETRM 12.2.2 metadata documents no referenced base objects, so the join relationships above are derived from the supplied view SQL. The READ ONLY clause confirms the object is intended exclusively for query access.

Key Columns

The columns fall into several functional groups:

• Operational/audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• Time and dimension keys: LEAD_ID, PERIOD_NAME, START_DATE, END_DATE, TERRITORY_ID, INTEREST_TYPE_ID, PRIMARY_INTEREST_CODE_ID, SECONDARY_INTEREST_CODE_ID, SALES_CHANNEL_ID, SALESREP_ID, SALES_GROUP_ID, ADDRESS_ID, CUSTOMER_ID.
• Descriptive attributes: CUSTOMER_NAME (from the customer dimension) and OPTY_NAME (the opportunity name, sourced from the opportunity dimension's DESCRIPTION).
• Performance measures: INVOICED_AMOUNT, OPTY_AMOUNT, WIN_PROBABILITY, and CUST_SATISFACTION_PCT. The CUST_SATISFACTION_PCT column is the customer satisfaction percentage — the specific column associated with the user's search term "cust_satisfaction_pct," used to report satisfaction levels in opportunity performance analysis.

Common Use Cases and Queries

In its original scope, the view supported opportunity performance dashboards combining revenue (INVOICED_AMOUNT), pipeline value (OPTY_AMOUNT), win probability, and customer satisfaction by period and territory. Representative queries include:

• Filtering by search attribute: SELECT customer_name, opty_name, cust_satisfaction_pct FROM bil_sumv_opty_perf WHERE cust_satisfaction_pct IS NOT NULL ORDER BY cust_satisfaction_pct DESC;
• Period-based performance reporting: SELECT period_name, salesrep_id, territory_id, SUM(invoiced_amount), AVG(cust_satisfaction_pct) FROM bil_sumv_opty_perf GROUP BY period_name, salesrep_id, territory_id;
• Channel and opportunity analysis: SELECT sales_channel_id, opty_name, opty_amount, win_probability FROM bil_sumv_opty_perf WHERE sales_channel_id = :p_channel;

Because the object is documented as obsolete and not implemented, these queries apply to legacy environments where the Sales Intelligence schema was deployed; in current 12.1.1 and 12.2.2 instances the view will not resolve.