Results for “market_segment_id”

50+ results




Overview
Explore in AI Chat

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

Overview

BIM_DIMV_MARKET_SGMTS is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the BIM (Marketing Intelligence) product family. In the Oracle EBS 12.1.1 and 12.2.2 releases, BIM is documented as obsolete; the view persists in the data dictionary as VALID and is supported primarily for backward compatibility with existing customizations, reports, and interfaces that still reference it. Its stated purpose is to expose all market segments defined in the marketing dictionary, presenting them through a dimension-oriented interface that maps internal cell identifiers to business-friendly market segment attributes.

The view is relevant to the search term ams_cells_vl because it is defined directly over the AMS_CELLS_VL view, filtering that source to only those cells flagged as market segments. It therefore represents the canonical "market segment dimension" used by Oracle Marketing and Marketing Intelligence reporting layers, and it provides a consistent column naming convention (MARKET_SEGMENT_*) that abstracts the underlying cell-based storage model.

Underlying Base Objects

The documented base objects referenced by the view are:

  • AMS_CELLS_VL (VIEW) — the primary source. This is the marketing cells view, which stores classification cells including market segments, and resolves translated name columns through the _VL (view with translation) pattern.
  • FND_LOOKUPS (VIEW) — used to supply a synthetic row representing the "-999" lookup code from the BIM_VALUE_TYPE lookup type.
  • FND_GLOBAL (PACKAGE) — referenced by the environment for session context such as organization and user identifiers, consistent with standard EBS multilanguage view behavior.

The view text performs a UNION ALL: the first branch selects from AMS_CELLS_VL aliased as AMC, restricted by AMC.MARKET_SEGMENT_FLAG = 'Y' and ordered by code and name. The second branch injects a sentinel row with MARKET_SEGMENT_ID of -999 and a MEANING value pulled from FND_LOOKUPS where LOOKUP_TYPE = 'BIM_VALUE_TYPE' and LOOKUP_CODE = '-999'. The view is declared WITH READ ONLY, so no DML is permitted against it.

Key Columns

The artificial -999 row provides a reserved "unknown/not applicable" member, a common dimensional modeling technique that ensures outer joins and reporting totals do not drop unmatched facts.

Common Use Cases and Queries

Typical scenarios include LOV population for market segment selection in custom concurrent programs, dimension lookups for marketing analytics extracts, and reconciliation of legacy AMS cell data to reporting structures.

List active market segments:

  • SELECT market_segment_id, market_segment_code, market_segment_name FROM apps.bim_dimv_market_sgmts WHERE enabled_flag = 'Y' AND market_segment_id > 0 ORDER BY market_segment_code;

Resolve a code to its name and description:

  • SELECT market_segment_name, description FROM apps.bim_dimv_market_sgmts WHERE market_segment_code = :p_code;

Build a lookup with the sentinel member for outer joins:

  • SELECT market_segment_id, NVL(market_segment_name, 'Unassigned') seg_name FROM apps.bim_dimv_market_sgmts ORDER BY market_segment_id;

Because BIM is obsolete, new development should avoid hard dependency on this view where an AMS_CELLS_VL query suffices; existing reports can continue to consume it, but the MARKET_SEGMENT_FLAG filter and READ ONLY nature must be respected.