Results for “source_list_name”

32 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIM_SUMV_SLIST_PROFIT is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the BIM – Marketing Intelligence product family, which Oracle has designated as obsolete, meaning the view is retained for backward compatibility and historical reporting rather than active development. As its documented description states, the view "joins the summary table to the dimension views," presenting a denormalized, presentation-ready result set that combines pre-aggregated profit figures with descriptive source list attributes.

Functionally, the view bridges a fact-style summary table and a dimension-style view. This pattern is typical of Marketing Intelligence reporting objects, where summarized measures are stored in an ST-like summary table and enriched at query time with dimensional descriptions. The view is defined WITH READ ONLY, so it is intended strictly for query and reporting workloads, not for DML. Because the object name embeds "SOURCE_LIST," it is scoped to source-list-level profitability reporting.

Underlying Base Objects

The documented base objects are BIM_DIMV_SOURCE_LISTS (VIEW), BIM_SLIST_PROFIT_SUMM (SYNONYM), and FND_GLOBAL (PACKAGE). The view text confirms a two-table join:

  • BIM_SLIST_PROFIT_SUMM — the summary (fact) table supplying the source list id, period attributes, initiated revenue, and actual cost measures.
  • BIM_DIMV_SOURCE_LISTS — the dimension view supplying the descriptive SOURCE_LIST_NAME, joined on SOURCE_LIST_ID.
  • FND_GLOBAL — referenced as a base object in the documented metadata, indicating the view or its dependencies rely on session context (for example, responsibility, user, or org context) for access control or defaulting behavior.

The join condition is BSP.SOURCE_LIST_ID = BSL.SOURCE_LIST_ID, making SOURCE_LIST_ID the grain key linking fact to dimension.

Key Columns

  • SOURCE_LIST_ID — Surrogate/primary identifier for the source list; the join key between the summary table and the dimension view.
  • SOURCE_LIST_NAME — Descriptive name of the source list, sourced from BIM_DIMV_SOURCE_LISTS. This is the column most commonly used as a report label and search filter (the user query "source_list_name" resolves here).
  • PERIOD_NAME — Accounting or reporting period label associated with the summarized figures.
  • START_DATE / END_DATE — Period start and end dates from BIM_SLIST_PROFIT_SUMM, useful for date-range filtering and trend analysis.
  • INITIATED_REVENUE — Revenue measure recorded against the source list for the period.
  • ACTUAL_COST — Actual cost measure recorded against the source list for the period, enabling margin/profit computation as revenue less cost.

Common Use Cases and Queries

The primary use case is source-list profitability reporting: comparing initiated revenue against actual cost by period, and presenting the results with human-readable source list names. Typical consumers are Marketing Intelligence dashboards, custom BI Publisher reports, and ad hoc SQL.

Simple listing:

SELECT source_list_id, source_list_name, period_name,
       start_date, end_date, initiated_revenue, actual_cost
FROM   apps.bim_sumv_slist_profit;

Profit computation and filtering by a named source list:

SELECT source_list_name,
       period_name,
       initiated_revenue - actual_cost AS gross_profit,
       initiated_revenue, actual_cost
FROM   apps.bim_sumv_slist_profit
WHERE  source_list_name = :p_source_list_name
ORDER  BY start_date;

Period-based margin analysis:

SELECT period_name,
       SUM(initiated_revenue) AS total_revenue,
       SUM(actual_cost)       AS total_cost
FROM   apps.bim_sumv_slist_profit
WHERE  start_date >= :p_from_date
GROUP  BY period_name
ORDER  BY period_name;

Because the object is read-only and part of an obsolete module, new development should avoid building dependencies on it; existing queries should be reviewed for migration to a supported replacement. Where version differences exist between 12.1.1 and 12.2.2, the documented metadata (owner APPS, base objects, and column list) is consistent across both releases.