Search Results bil_sls_chnl_perf_summ

Overview

BIL_SLS_CHNL_PERF_SUMM is a summary table within the Oracle EBS Sales Intelligence (BIL) product family. Its documented purpose is to store summary measures related to reporting on sales channel performance. In the Oracle E-Business Suite release context of 12.1.1 and 12.2.2, such tables function as pre-aggregated reporting structures that reduce query cost for analytical dashboards and channel performance reports covering order booking, revenue contribution, and territory-level sales achievement.

The ETRM metadata classifies the object's relationship model as standalone, using a heuristic Data Vault classification mined from foreign key structure. As a modeling suggestion, this implies the table behaves as an independent satellite-like summary entity without enforced outbound FK dependencies to parent hub or link tables. In practice, this means the table is populated by concurrent programs or collection processes rather than through transactional DML, and its rows represent aggregated snapshots per period rather than atomic business events.

Notably, the metadata records that the table is "Not implemented in this database." Teams searching for this object should first confirm whether the Sales Intelligence module is licensed and installed in the target instance before attempting to query or reference it.

Key Information Stored

The table is defined by a composite primary key, BIL_SLS_CHNL_PERF_SUMM_PK, comprising six columns. These columns collectively form both the surrogate uniqueness constraint and the natural business-key candidate, since the documentation identifies no separate unique index beyond the primary key.

• PERIOD_NAME — the accounting or reporting period for which the summary measure was calculated; the primary time dimension.
• TERRITORY_ID — identifies the sales territory associated with the aggregated performance data.
• INTEREST_TYPE_ID — classifies the type of sales interest or responsibility recorded against the transaction.
• PRIMARY_INTEREST_CODE_ID — the primary sales credit assignment code applied during summarization.
• SECONDARY_INTEREST_CODE_ID — the secondary sales credit assignment code, enabling split-credit reporting.
• SALES_CHANNEL_ID — the sales channel through which the business was transacted; the central reporting dimension named in the table's title.

The remaining columns, while present in the table definition, are not enumerated in the supplied documentation. Because the primary key is composite and all six components represent dimensions rather than generated identifiers, the table is best interpreted as a dimensional fact summary keyed by period, territory, interest, and channel.

Common Use Cases and Queries

Typical usage centers on channel performance analysis and territory achievement reporting. A representative pattern filters by period and channel to rank territories:

• Aggregating measures by SALES_CHANNEL_ID and PERIOD_NAME to compare channel effectiveness across quarters.
• Drilling from TERRITORY_ID to region-level rollups for sales management dashboards.
• Analyzing primary versus secondary interest credit distribution using PRIMARY_INTEREST_CODE_ID and SECONDARY_INTEREST_CODE_ID.
• Filtering by INTEREST_TYPE_ID to isolate specific responsibility models, such as direct versus indirect sales.

A sample query structure follows the composite key ordering: select the period and channel dimensions, group by territory, and join to the territory and channel lookup tables to resolve names. Because the table holds pre-aggregated summaries, queries should avoid further expensive joins to transactional order tables unless reconciliation is required.

Related Objects

Although the metadata classifies the object as standalone with no documented foreign key relationships, functional dependencies exist against the Sales Intelligence dimension and collection objects. The most significant related objects in a typical BIL implementation include:

• BIL_SLS_CHNL_PERF — the accompanying detail table from which summaries are typically rolled up.
• BIL_PERIODS / BIL_PERIOD_SETS — supply PERIOD_NAME values used in the composite key.
• BIL_TERRITORIES — resolves TERRITORY_ID to territory names and hierarchies.
• BIL_SALES_CHANNELS — resolves SALES_CHANNEL_ID to channel descriptions.
• BIL_INTEREST_TYPES — resolves INTEREST_TYPE_ID and the primary/secondary interest code columns.
• BIL_COLLECTION_PROGRAMS — the concurrent processes that populate and refresh summary data.

Each relationship should be confirmed against the actual instance, since the documented metadata confirms no enforced referential integrity and the table may be absent entirely.