Results for “bim_dimv_sales_channels”

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

Overview

BIM_DIMV_SALES_CHANNELS is a read-only dimensional view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BIM (Marketing Intelligence) product family. It is categorized as a dimension view, meaning that its primary purpose is to expose a clean, denormalized list of sales channel reference values for use by Oracle Business Intelligence and other analytical reporting layers that consume Marketing Intelligence data. The view surfaces the set of valid sales channels defined in the E-Business Suite lookup framework, along with their codes, user-facing names, effective date ranges, and enabled status, so that downstream fact tables and dashboards can resolve a channel identifier to a human-readable label.

In Oracle EBS 12.1.1 and 12.2.2 the view retains the same definition and status (VALID) in both releases. Because it carries only reference data rather than transactional data, it functions as a lookup or dimension source rather than a staging or interface object. The view is defined with the WITH READ ONLY clause, so consumers should treat it strictly as a query target; any maintenance of sales channel values must occur in the underlying lookup tables, not through this view.

Underlying Base Objects

The documented base objects underlying the view are OE_LOOKUPS (a view), FND_LOOKUPS (a view), and the package FND_GLOBAL. The core SELECT reads from OE_LOOKUPS, filtering on LOOKUP_TYPE = 'SALES_CHANNEL', and projects the lookup code, enabled flag, start and end active dates, meaning, and description. A UNION ALL branch then appends a single placeholder row sourced from FND_LOOKUPS, restricted to LOOKUP_TYPE = 'BIM_VALUE_TYPE' and LOOKUP_CODE = '-999'.

This second branch implements the Marketing Intelligence convention of supplying a "no value" or "unknown" member for the dimension. It hard-codes the code as '-999', leaves the enabled flag and active dates null, and derives the display name from the MEANING column of the '-999' entry in the BIM_VALUE_TYPE lookup. The reference to FND_GLOBAL is consistent with the standard multi-org/lookup access pattern used across EBS lookup views. The result is a two-source union: the live sales channel lookups plus a synthetic default member.

Key Columns

• SALES_CHANNEL_CODE — the lookup code from the sales channel lookup type; the stable identifier for each channel, and '-999' for the synthetic member.
• ENABLED_FLAG — indicates whether the channel is currently enabled in the lookup definition. It is null for the '-999' row.
• START_DATE_ACTIVE — the date from which the sales channel becomes effective, if maintained on the lookup.
• END_DATE_ACTIVE — the date on which the sales channel ceases to be effective, if maintained.
• SALES_CHANNEL_NAME — the MEANING value of the lookup, providing the descriptive and user-searchable name of the sales channel. This is the column that answers the common query for sales_channel_name.
• DESCRIPTION — the lookup description; null for the synthetic '-999' row.

Common Use Cases and Queries

Typical usage is to resolve a sales channel code to its name, to populate dimension attributes in Marketing Intelligence reports, or to drive pick lists in custom concurrent programs and inbound interfaces. A basic listing query resembles the following:

• SELECT sales_channel_code, sales_channel_name, enabled_flag, start_date_active, end_date_active FROM apps.bim_dimv_sales_channels;
• SELECT sales_channel_code, sales_channel_name FROM apps.bim_dimv_sales_channels WHERE enabled_flag = 'Y' AND sales_channel_code <> '-999';
• SELECT sales_channel_name FROM apps.bim_dimv_sales_channels WHERE sales_channel_code = :channel_code;

Because the view is read only and sourced from lookup views, joins to fact tables are ordinarily performed on SALES_CHANNEL_CODE. Where the synthetic '-999' member is unwanted in operational extracts, it should be excluded explicitly. Queries should also account for null ENABLED_FLAG and date values on the '-999' row.