Search Results lost_amt




Overview

BIL.BIL_BI_OPDTL_F is a Business Intelligence summary (fact) table in the Oracle EBS Business Intelligence (BIL) schema, stored in the APPS_TS_SUMMARY tablespace. It holds opportunity detail fact records drawn from Oracle Sales (AS) and related CRM sources, aggregated at the grain of the sales credit. Each row captures an opportunity, its sales team assignment, the associated customer and product context, and a set of pre-computed amount metrics used by Oracle Sales Analytics and CRM reporting. The "_F" suffix denotes a fact table, and the row-level grain is anchored by the SALES_CREDIT_ID unique key.

The ETRM metadata classifies this object heuristically as standalone within the Data Vault modeling suggestion — that is, it functions as a self-contained fact/dimension-flattened table rather than a normalized hub, link, or satellite. Because its foreign keys point outward to dimensions (FND_SECURITY_GROUPS, AS_SALES_STAGES_ALL_B, AS_LEAD_LINES_ALL) while the table itself carries measures, it is best treated as a fact satellite in a dimensional model. Note the explicit Oracle warning: this object is Oracle Internal Use Only and is not supported for direct access except from standard Oracle Applications programs. The lost_amt column that prompted the search resides here.

Key Information Stored

Of the 56 documented columns, the most significant are the identifiers, temporal keys (stored in Julian format), and the amount measures:

Common Use Cases and Queries

Because the table pre-aggregates opportunity outcomes, it is the natural source for win/loss analysis, pipeline reporting, and rep performance summaries. A typical pattern filters by Julian time and groups by sales group:

  • Win/loss ratio by period: SELECT SALES_GROUP_ID, SUM(WON_AMT), SUM(LOST_AMT) FROM BIL_BI_OPDTL_F WHERE TXN_TIME_ID BETWEEN :p_start AND :p_end GROUP BY SALES_GROUP_ID;
  • Lost-amount drill-down by customer or product: aggregate LOST_AMT filtering WIN_LOSS_INDICATOR or STATUS.
  • Rep-level pipeline: sum PIPELINE_AMT and the WTD_PIPELINE_PB* buckets grouped by SALESREP_ID.
  • Item/product analysis: join on ITEM_ID and ITEM_ORGANIZATION_ID, supported by the non-unique index.

Oracle recommends accessing this data through delivered BI/CRM programs rather than direct SQL, and all query access should be security-masked via SECURITY_GROUP_ID.

Related Objects

The table participates in a small but meaningful set of dimensional relationships:

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for security-group filtering.
  • AS_SALES_STAGES_ALL_B — joined via SALES_STAGE_ID for sales-stage descriptions.
  • AS_LEAD_LINES_ALL — joined via LEAD_LINE_ID to link to originating lead lines.
  • AS_OPPORTUNITIES_ALL_B / AS_OPPORTUNITY_LINES — source of OPTY_ID and opportunity attributes.
  • AS_SALES_CREDITS_ALL and JTF_RS_SALESREPS — supply SALES_CREDIT_ID and SALESREP_ID context.
  • BIL_BI_* family tables and the Oracle Sales Analytics materialized views that consume this fact.